RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login
    Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

    how do you empty deleted files with MC

    Scheduled Pinned Locked Moved Help and Support
    delete
    56 Posts 5 Posters 7.8k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • C
      comet424 @comet424
      last edited by

      i tried
      pi@retropie:~ $ fdisk /dev/sda1

      Welcome to fdisk (util-linux 2.33.1).
      Changes will remain in memory only, until you decide to write them.
      Be careful before using the write command.

      fdisk: cannot open /dev/sda1: Permission denied
      pi@retropie:~ $

      as i figured may display something... i least have my roms on the server.... i guess ill pull the hard drive and test it in windows or unraid to see if it has a file system

      i guess that executable fstab had to do it as it really fell apart after that ill test the ssd now in windows

      1 Reply Last reply Reply Quote 0
      • mituM
        mitu Global Moderator @comet424
        last edited by

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

        but i wonder if the UUID with the rw,exec and forgetting that 2 at the end correupted it then?

        No, that would not corrupt the filesystem/disc.

        how do i check the FS on the SSD? i only really know windows

        Run sudo fdisk -l /dev/sda and it should list the partitions on the disc. Try to mount it using the mount command and see if you can read what's on it.

        sudo mount /dev/sda1 /media/usb0 -t vfat
        

        Check /media/usb0 for the ROM files.

        how do i do it in linux here

        I suggest you use the automatic mounting method, if you're not familiar with the Linux commands.

        C 1 Reply Last reply Reply Quote 0
        • C
          comet424 @mitu
          last edited by

          @mitu
          ok ill try that.

          and reason i went with the manual mode is the slow problems Nespi4 and that it unmounts on its own when you do a reboot or emulation reboot
          or like how emulation config files hangs for 2 min.. so had to do the manual mode

          but i chose that exec rw version in the fstab and thats when things just gone really crazy

          i had this issue 6 months ago with the 1TB SSD WD and i got help but i found the steps we did then didnt 100% work with the 250GB this time.. and last time was NTFS and this is fat32 so i tried to follow that then

          but ill give those a try and see what happens..

          C 1 Reply Last reply Reply Quote 0
          • C
            comet424 @comet424
            last edited by

            @mitu

            guess the file system just corrupted.. ill pop it out and shove in windows or unraid and erase the SSD and just copy over
            probably unraid to format it since it can do bigger where windows cant
            ill re copy things over and ill get back to you later.. ill retry the UUID in fstab after a clean format
            as this frustrating

            pi@retropie:~ $ sudo fdisk -l /dev/sda
            fdisk: cannot open /dev/sda: Input/output error
            pi@retropie:~ $ sudo fdisk -l /dev/sda1
            fdisk: cannot open /dev/sda1: Input/output error
            pi@retropie:~ $ sudo mount /dev/sda1 /media/usb0 -t vfat
            mount: /media/usb0: can't read superblock on /dev/sda1.
            pi@retropie:~ $
            

            a

            C 1 Reply Last reply Reply Quote 0
            • C
              comet424 @comet424
              last edited by comet424

              @mitu
              so file system was file but i moved all the files off the ssd.. erased the partition and re formated for Fat32
              and then moved the files back
              i also got a new UUID number the short form one
              but so if a rem out the UUID in Fstab and the

              pi@retropie:~ $ ls -l /dev/disk/by-uuid/
              total 0
              lrwxrwxrwx 1 root root 10 Dec 13 20:15 9290-791F -> ../../sda1
              lrwxrwxrwx 1 root root 15 Dec 13 20:15 AC15-4763 -> ../../mmcblk0p1
              lrwxrwxrwx 1 root root 15 Dec 13 20:15 f1351d7a-72a6-4d65-b1e2-62653795df48 -> ../../mmcblk0p2
              pi@retropie:~ $ sudo mount -a
              mount: /proc: \proc already mounted or mount point busy.
              pi@retropie:~ $ sudo fdisk -l /dev/sda1
              Disk /dev/sda1: 232.9 GiB, 250058113024 bytes, 488394752 sectors
              Units: sectors of 1 * 512 = 512 bytes
              Sector size (logical/physical): 512 bytes / 4096 bytes
              I/O size (minimum/optimal): 4096 bytes / 4096 bytes
              Disklabel type: dos
              Disk identifier: 0x00000000
              pi@retropie:~ $ sudo mount /dev/sda1 /media/usb0 -t vfat
              pi@retropie:~ $ mc
              
              
              pi@retropie:~ $ cd /media/usb0
              pi@retropie:/media/usb0 $ cd retropie-mount
              pi@retropie:/media/usb0/retropie-mount $ cd roms
              pi@retropie:/media/usb0/retropie-mount/roms $
              

              i still get usbmount@dev-sda/server even when usb mounting is off

              so with usb mount services enabled..
              the SSD mounts the roms

              when i disable the usb mount services
              and edit the fstab it cant the roms so emulation issue

              these commands are with USB services Off the FStab file enabled for that UUID

              pi@retropie:~ $ ls -l /dev/disk/by-uuid/
              total 0
              lrwxrwxrwx 1 root root 10 Dec 13 20:27 9290-791F -> ../../sda1
              lrwxrwxrwx 1 root root 15 Dec 13 20:27 AC15-4763 -> ../../mmcblk0p1
              lrwxrwxrwx 1 root root 15 Dec 13 20:27 f1351d7a-72a6-4d65-b1e2-62653795df48 -> ../../mmcblk0p2
              pi@retropie:~ $
              
              pi@retropie:~ $ sudo fdisk -l /dev/sda1
              Disk /dev/sda1: 232.9 GiB, 250058113024 bytes, 488394752 sectors
              Units: sectors of 1 * 512 = 512 bytes
              Sector size (logical/physical): 512 bytes / 4096 bytes
              I/O size (minimum/optimal): 4096 bytes / 4096 bytes
              Disklabel type: dos
              Disk identifier: 0x00000000
              pi@retropie:~ $
              
              pi@retropie:~ $ sudo mount -a
              mount: /proc: \proc already mounted or mount point busy.
              pi@retropie:~ $
              
              pi@retropie:~ $ df
              Filesystem     1K-blocks      Used Available Use% Mounted on
              /dev/root       30368644   2886112  26206944  10% /
              devtmpfs         1801484         0   1801484   0% /dev
              tmpfs            1933580         0   1933580   0% /dev/shm
              tmpfs            1933580      9632   1923948   1% /run
              tmpfs               5120         4      5116   1% /run/lock
              tmpfs            1933580         0   1933580   0% /sys/fs/cgroup
              /dev/mmcblk0p1    261868     55708    206160  22% /boot
              /dev/sda1      243721336 115772748 127948588  48% /home/pi/RetroPie
              tmpfs             386716         0    386716   0% /run/user/1000
              pi@retropie:~ $
              
              pi@retropie:~ $ cd /home/pi
              pi@retropie:~ $ ls
              RetroPie  RetroPie-Setup
              pi@retropie:~ $ cd RetroPie
              pi@retropie:~/RetroPie $ ls
              retropie-mount
              pi@retropie:~/RetroPie $
              
              
              \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=9290-791F  /home/pi/RetroPie       vfat    nofail,user,uid=pi,gid=pi       0       2
              

              the roms show up fine under retropie-mount

              but i still get the usbmount fail and i didnt try the rw,exec version for the UUID
              but it is mounting

              what else you need me to test.. but least i dont have that long number its a 4 characters then a dash then 4 characters

              do i change the /home/pi/RetroPie in the fstab to /home/pi/RetroPie/retropie-mount
              or do i move all the files out of the retromount folder to the room then on the SSD since its least mounting or least the file system is showing

              C 1 Reply Last reply Reply Quote 0
              • C
                comet424 @comet424
                last edited by comet424

                so its mounting
                with the fstab
                UUID=9290-791F /home/pi/RetroPie vfat nofail,user,uid=pi,gid=pi 0 2

                i had to move those files out of the retropie-mount and put the folders in root

                its still failing usbmount@dev-sda service
                and still loading config files slow as can be.. so manually mount finally works, but its is not improving speeds yet

                but least its mounting through the fstab must been corrpted SSD file system
                so that part is working just still no improved speed still slow and still booting up slow

                C mituM 2 Replies Last reply Reply Quote 0
                • C
                  comet424 @comet424
                  last edited by

                  only getting average of 5m/s over the network from my 7200rpm drive to the SSD on retropie but i know when i had the 1TB 6 months ago i was getting close to 100m/s so something slowing this down still

                  1 Reply Last reply Reply Quote 0
                  • mituM
                    mitu Global Moderator @comet424
                    last edited by

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

                    its still failing usbmount@dev-sda service

                    You can ignore that error, it's harmless. It means there's no partition on /dev/sda (which is normal, since the partition is on /dev/sda1).

                    and still loading config files slow as can be.. so manually mount finally works, but its is not improving speeds yet

                    That may be the drive's speed or the issue with the NesPI case SATA controller.

                    C 2 Replies Last reply Reply Quote 0
                    • C
                      comet424 @mitu
                      last edited by

                      @mitu

                      oh ok that is frustrating all this work and all these trouble shooting and find out still cant get improvements
                      guess its just going to be slow.. you think the sata to usb for the nespi could be upgraded
                      the ssd i should be getting 520mb/s well least i get that in crystal mark bench marks

                      but ya frustrating... least the issue of loosing the mount wont happen when its manually mounted

                      and what does that exec rw the one for fstab
                      for excecuting commands what does that allow you do to?? as i never tried it yet with this setup the way i have it right now least its finally working

                      guess ill live with it unless the nespi comes out with firmware i guess

                      1 Reply Last reply Reply Quote 0
                      • C
                        comet424 @mitu
                        last edited by comet424

                        @mitu i figured it out/ remembered for the slow speed issue

                        for anyone with the Nespi4 enclosures you gotta add
                        usb-storage.quirks=152d:0562:u

                        to the /boot/cmdline.txt file adding it at the beginning..

                        so instead of 3 min 30 seconds to load up the configuration files before it shows up the retropie screen.. now it only takes 28 seconds to sit at the loading configuaration

                        and now i get 80meg/s instead of the 5meg/s

                        gonna write steps in a text file the procedure so i can remember next time the orders and what to add if i format or build another one of thess

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post

                        Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

                        Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.