how do you empty deleted files with MC

mitu

@comet424 said in how do you empty deleted files with MC:

and didnt think retropie write protects/hides that location on the SD card

There's no 'protection' , the local ROM folders are 'hidden' when you configure an external USB drive to take over.

comet424

@mitu well what i ment is protection it hides it so you cant delete it..

but thats probably what happened its hidden.. ill check it in a few hours i be home..

thanks and ill let you know

YFZdude

EDIT: nevermind...

mitu

@comet424 said in how do you empty deleted files with MC:

@mitu well what i ment is protection it hides it so you cant delete it..

Yes, I was referring to the rest of the sdcard, which is not 'protected' - you're free to delete files from it, from other locations than the roms folder.

YFZdude

I found a handy way to see what folders take up space if you want to hunt down the source of the problem.

du -h --max-depth=1 | sort -hr

You could do this from the root (/) of the sdcard, then cd into the largest folder and repeat the command one level at a time. Or you can increase max-depth to see more levels at once. Not quite as fast as a GUI tool like WinDirStat, but it should get the job done.

BuZz

As mentioned when a USB stick is configured with a retropie-mount folder it will be mounted automatically over the existing RetroPie folder via what's called a bind mount so that folder will be pointing to the USB stick. If you have lots of files in the original folder you can manage them by either bottling without the USB stick or exiting EmulationStation and then running

sudo umount ~/RetroPie

And then removing files via the network, commandline or using mc.

comet424

sorry had internet issues yesterday

and i did the remove the SSD and then i got the files again on the SD card... and then i just deleted them with the MC
and then re plugged back the SSD in and rebooted..

always learning something new everyday

thank you for all the help (:

comet424

something else seems to be wrong??
used to boot up fast

now when i reboot or start up it hangs as the Emulation page.. saying Loading config files

it hangs for a couple mins before loading up
whats gone on?

i did run sudo ~/RetroPie-Setup/retropie_setup.sh
from a ssh in figured running update of all fix it but didnt help

what causes it to load so slow now? used to be lighting fast... and transfering to the SSD is slow i shuld be getting 80-120mbs but i only get 20 megs sec copying... i know i had another page a while ago i did a manual edit instead of auto mount not sure if that matters also cant find my old post

as this is the 2nd nintendo retropie i built for someone else and its just not working right cant cant remember what i did last time.. but ya seems to be hanging at loading config files and slow copy transfers over the network

mitu

If you're using the NesPi 4 case, then it's probably this.

comet424

@mitu oh ok ya i remember that from someone posted in my last post i had issues earlier this year and since i doing 2nd one i have forgotten and couldnt find it.. and was also to do Manual mount instead of Automount as i found auto mounting unmounts the drive from this case..

ill do that and see if that fixes the speed and the loading config files at emulation i only noticed now because i have had it left on all this time but i was just rebooting it today and noticed it was not booting up fast anymore and then i did the update of retropie figure it was that... ill re due this one and try to find the manual mount too as i remember automount doesnt like it with this case if you do a reboot it will unmount the drive i noticed.. i guess its the usb to sata device the firmware in it or the chip that cause the issues i take it

comet424

@mitu im remember again
that trick doesnt work for the nespi 4 case
i remember it didnt work with the other one either..
as

pi@retropie:~ $ sudo dmesg -C
pi@retropie:~ $ sudo dmesg -C
pi@retropie:~ $ dmesg
pi@retropie:~ $

it does nothing it doesnt display.. but the tricks that were done before fixed it i still cant find my old post like 6 months ago..
it doesnt display the log ..

comet424

@mitu so i found my old post and was trying some of the commands but it isnt working the same now

then i made sure only 1 partition and fat32

i ran
ls -l /dev/disk/by-uuid/

and got my uuid
lrwxrwxrwx 1 root root 10 Dec 12 23:25 4A099D4A0F439B23 -> ../../sda1
lrwxrwxrwx 1 root root 15 Dec 12 23:25 8988cf8f-d459-476f-9a4a-16c56702dc40 -> ../../mmcblk0p2
lrwxrwxrwx 1 root root 15 Dec 12 23:25 C367-3F28 -> ../../mmcblk0p1

so i edited the fstab and added for the sda1

UUID=4A099D4A0F439B23 /home/pi/RetroPie vfat rw,exec,uid=pi,gid=pi,umask=022 0

i chose that as that showed for Fat32 file system from
https://retropie.org.uk/docs/Running-ROMs-from-a-USB-drive/

i rebooted and the root account is locked it says it wont boot up and i cant ssh in.. the other post the dmesg worked after using the tail command but this one isnt working
its also in emergency mode.. i tried pulling usb out and rebooting but still console is locked

like
dmesg | grep usb-storage
is not working

so how do i fix or isa format to fix this issue?

mitu

@comet424 The root account does not have a password by default, so it's 'locked'. You can use sudo with the pi account and perform admin tasks.

UUID=4A099D4A0F439B23 /home/pi/RetroPie vfat rw,exec,uid=pi,gid=pi,umask=022 0

the line is incomplete, it should have another number at the end.

If you've booted in emergency mode because of a bad /etc/fstab, then you should boot in 'safe' mode by modifying /boot/cmdline.txt and adding init=/bin/sh at the end of the line present in the file. This should boot you to a root command line, where you can mount the root partition and repair the /etc/fstab file.

comet424

@mitu i thought i added the 2 after the last 0 from the linw now i cant remember

and i cant modify nothing raspberry pi booted into emgency mode on itself.. then talks about using jorurnal program

says root console acccess been locked..

tells you to look at slulogin(8)
tells me press enter
reloading system manager configuration
starting default target

then just repeats the above cant get into anything

mitu

Assuming the problem is caused only by the erroneous /etc/fstab entry, you can try fixing it by modifying the file on the Linux partition on the sdcard from a separate Linux system (if you have one) or maybe from Windows (using the Paragon Ext4 driver).

If that doesn't work, maybe re-install from scratch.

comet424

@mitu ah ok
so i used my usb parted Magic program
edited the fstab file so ya i was missing that last 2

so it booted and got back in had bunch of fails and RF kill switch failed multiple times
but it booted up

i also remmed out the UUID and rebooted also pulled the ssd still gave errors
i ssh'd in and ran the retropi_setup and did the update it couldnt told me fetch_head is read only mode

its amazing how just forgettng that 2 changes it mess's this up

so what did that last 2 do???

and guess the whole thing is in read only... so i gonna do fresh install and try the manual mount...
and try the uuid line again and add that 2 i didnt see

mitu

@comet424 said in how do you empty deleted files with MC:

so what did that last 2 do???

man fstab

comet424

@mitu so the man fstab means manual add file system? for the 2

so i tried again
UUID=4A099D4A0F439B23 /home/pi/RetroPie vfat rw,exec,uid=pi,gid=pi,umask=022 0 2

added the extra 2... and yet again it corrupted soo many failed com errors etc
and then when i remmed it out using Parted Magic again it wouldnt boot up

so i cant see what difference from my older post i had ntfs and 1tb drive but this is 250gb set for Fat32
the commands in old post
https://retropie.org.uk/forum/topic/27809/ssd-doesnt-always-mount/29?_=1607815702974
dont seem to be working some are

so should i keep the File system fat32? i have retropie-mount folder on the SSD
what should the manual fstab be since i redownloading retropie iso to the SD card

should it be this
/home/pi/RetroPie vfat nofail,user,uid=pi,gid=pi 0 2

not the
/home/pi/RetroPie vfat rw,exec,uid=pi,gid=pi,umask=022 0 2

i did the 2nd one for getting maybe MSDos programs to run as i cant seem to get my Command and Conqurer to run on dosbox figured the option for the execuatble will fix it

mitu

@comet424 said in how do you empty deleted files with MC:

so i tried again
UUID=4A099D4A0F439B23 /home/pi/RetroPie vfat rw,exec,uid=pi,gid=pi,umask=022 0 2
added the extra 2... and yet again it corrupted soo many failed com errors etc
and then when i remmed it out using Parted Magic again it wouldnt boot up

Are you sure the UUID is correct for your external disc ? Post the complete /etc/fstab.

comet424

@mitu
i seem to be having major issues trying to mount manually with the 250GB WD Blue drive i didn have this issue with the 1TB but i dont have that setup here i know the dmesg command didnt work right for it and doesnt work that well here

but for this 250GB SSD setup this is my setup
SSD formated Fat32
folder retropie-mount <all roms under it>

i install retropie
<boots up and it fails the usb@.... mount> i forget what it says rest go Green "OK"
i configure joypad
i install dosbox and vice
i add SSH
i add the samba

i ssh in
and run

pi@retropie:~ $ ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 10 Dec 13 15:03 4A099D4A0F439B23 -> ../../sda1
lrwxrwxrwx 1 root root 15 Dec 13 15:03 AC15-4763 -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 15 Dec 13 15:03 f1351d7a-72a6-4d65-b1e2-62653795df48 -> ../../mmcblk0p2

i then

cd /etc
sudo nano fstab

proc            /proc           proc    defaults          0       0
PARTUUID=3c0d1f86-01  /boot           vfat    defaults          0       2
PARTUUID=3c0d1f86-02  /               ext4    defaults,noatime  0       1
# a swapfile is not a swap partition, no line here
#   use  dphys-swapfile swap[on|off]  for that
UUID=4A099D4A0F439B23   /home/pi/RetroPie       vfat    nofail,user,uid=pi,gid=pi       0       2

i chose the other one this time not that exec it seems to mess it up totally

then i save
then i did the run raspi-config and goto configurartions and disble the usb mount service
and reboot.. it boots up but still slow.. and now i cant remember while typing this if it mounted the roms i dont think so i think only mounted priper me editig the fstab..

this last time i did from the manual mount documentation

sudo mv -v /home/pi/RetroPie/* /media/usb0/

i then run the raspi config and goto configurations and disable the usb mount service
i then rebooted
it still fails the "usb@mount... whatever it says" but i turned off automount
when it boots up it tells me there is no emulation goto the website and goes to the command prompt

is this because i formated in fat32? when i did the other setup it was a NFTS but i remember you guys saying and documentation Fat32 is better.. but is fat32 the issue with Western Digital? i havent had this much problems before and this time i was trying to do it the proper way Fat32 but been having issues is it WD on the black list? and maybe i need to format NTFS and i forget when you manualy mount usb do you scrap the retropie-mount folder and just post everything in the root of the drive

just cant figure whats going on..