how do you empty deleted files with MC

mitu

If you have set up your ROMs to be stored on an USB stick/disc (I see there's an USB device attached from the df output), then deleting the ROM files has deleted them just from the external USB device, so that's why don't see any space getting freed-up on the SD card. Do you have such setup in place ?

What exactly did you do before getting to 0% free space ? Scraping, copying ROMs, something else ?

comet424

@mitu so yes i have a 250gb hard drive plugged in it copied it over to the /media/usb0
once it was done i used the MC and went to the /home/pi/roms i think it is to delete the Roms off the SD card so i can get like 20gb back
so i would be able to update or what not..

and yes i noticed it deleted the files off the usb0 too but that was ok i have them stored on unraid
but i was trying to get the SD card freed up

i was copying roms from unraid to retropie with the 250 gb wd sdd but apparently it wasnt copying to the SDD in windows samba share roms
was copying to SD card ran out after 25gb i copied..

so i then was sshing in and checking how could 250 gb drive be full after 25gb

then i googled etc found the df command SD full so i went to the .home/pi/roms to delete the roms off the SD card
in usb0 i noticed i didnt have the retropie-mount so i did retropie-mount under MC in /usb0 and rebooted
and it copied over and then i went and deleted the files from /pi/home /roms as it doesnt move the files off but copies
but deleting that folder deletes the usb0 share but also hides my files i deleted

so dunno

comet424

but what i think i not at home at the moment

i think maybe when you mount the retropie-mount

it right protects the location on the SD card so it wont delete it.. i didnt try pulling the usb hard drive out and rebooting just off the SD i only thought of that now...
but cant test that now

does it do that hide that then maybe?

mitu

Shutdown your Pi, then remove the USB stick. Start it back and then delete again the ROMs from the their folders (not the folders themselves). This way, you make sure you're deleting your local files and not the ones from the USB stick/disc. After you delete, check the space on the sdcard with df, then plug back your external USB storage.

comet424

@mitu ok ill try that when i get home

i dunno why i didnt think of it really.. oh its because i have the NES case for the raspberry pi 4 where you shove the cartridge inside the unit
and never though of unplugging
and didnt think retropie write protects/hides that location on the SD card

but ill try it when i get home and let you know

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.