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

    Having trouble running ROMs from USB using automount

    Scheduled Pinned Locked Moved Help and Support
    usb romshard driveautomatic mount
    17 Posts 3 Posters 3.0k 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.
    • 2
      2fst4u
      last edited by

      I'm not sure if it's running. When I run df as per the docs for manual mounting I can't see my hard drive either, which is very weird since as you say, it copied the ROMs over.

      I have just spotted an error as I rebooted the pi, it said:

      Failed to start Usbmount@dev-sda.service

      Which sounds curiously relevant! Any ideas what might cause that?

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

        @2fst4u said in Having trouble running ROMs from USB using automount:

        Which sounds curiously relevant! Any ideas what might cause that?

        Run sudo systemctl status ubmount@dev-sda.service and see what errors are reported.

        1 Reply Last reply Reply Quote 0
        • 2
          2fst4u
          last edited by 2fst4u 

          pi@retropie:~ $ sudo systemctl status usbmount@dev-sda.service
● usbmount@dev-sda.service
   Loaded: loaded (/lib/systemd/system/usbmount@.service; static; vendor preset: en   Active: failed (Result: exit-code) since Thu 2019-03-21 08:52:45 UTC; 4min 9s ag Main PID: 251 (code=exited, status=1/FAILURE)

Mar 21 08:52:42 retropie systemd[1]: Starting usbmount@dev-sda.service...
Mar 21 08:52:45 retropie systemd[1]: usbmount@dev-sda.service: Main process exited,Mar 21 08:52:45 retropie systemd[1]: Failed to start usbmount@dev-sda.service.
Mar 21 08:52:45 retropie systemd[1]: usbmount@dev-sda.service: Unit entered failed Mar 21 08:52:45 retropie systemd[1]: usbmount@dev-sda.service: Failed with result 'lines 1-10/10 (END)...skipping...
● usbmount@dev-sda.service
   Loaded: loaded (/lib/systemd/system/usbmount@.service; static; vendor preset: en   Active: failed (Result: exit-code) since Thu 2019-03-21 08:52:45 UTC; 4min 9s ag Main PID: 251 (code=exited, status=1/FAILURE)

Mar 21 08:52:42 retropie systemd[1]: Starting usbmount@dev-sda.service...
Mar 21 08:52:45 retropie systemd[1]: usbmount@dev-sda.service: Main process exited,Mar 21 08:52:45 retropie systemd[1]: Failed to start usbmount@dev-sda.service.
Mar 21 08:52:45 retropie systemd[1]: usbmount@dev-sda.service: Unit entered failed Mar 21 08:52:45 retropie systemd[1]: usbmount@dev-sda.service: Failed with result '~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
● usbmount@dev-sda.service
   Loaded: loaded (/lib/systemd/system/usbmount@.service; static; vendor preset: en   Active: failed (Result: exit-code) since Thu 2019-03-21 08:52:45 UTC; 4min 9s ag Main PID: 251 (code=exited, status=1/FAILURE)

Mar 21 08:52:42 retropie systemd[1]: Starting usbmount@dev-sda.service...
Mar 21 08:52:45 retropie systemd[1]: usbmount@dev-sda.service: Main process exited,Mar 21 08:52:45 retropie systemd[1]: Failed to start usbmount@dev-sda.service.
Mar 21 08:52:45 retropie systemd[1]: usbmount@dev-sda.service: Unit entered failed Mar 21 08:52:45 retropie systemd[1]: usbmount@dev-sda.service: Failed with result '~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-10/10 (END)

          (Corrected the assumed typo in the command)

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

            Does manually mounting the disk works ?

            1 Reply Last reply Reply Quote 0
            • 2
              2fst4u
              last edited by

              I'm not sure how I can do that if the commands the documentation say to use don't show the disk? When I use df it doesn't show.

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

                @2fst4u dfonly shows the mounted filesystems, it doesn't show all disk devices. If your disk is not mounted, then it will not show up in df's output.

                1 Reply Last reply Reply Quote 0
                • 2
                  2fst4u
                  last edited by

                  Right, what command should I be looking to use then? What can I use to see the device before it has been mounted?

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

                    @2fst4u You can query the device with fdisk, to see the available partitions

                    fdisk -l /dev/sda

                    then mount the corresponding partition under a temporary mountpoint

                    sudo mount /dev/sdaX /mnt/

                    The name of the device should apper in the log, immediately after you plug in the drive:

                    dmesg | tail -n 20
                    1 Reply Last reply Reply Quote 0
                    • 2
                      2fst4u
                      last edited by

                      Ok cool, that seems to have worked and it's telling me there are some issues:

                      pi@retropie:~ $ dmesg | tail -n 20
[ 4220.659452] usb 1-1.7.4: reset high-speed USB device number 5 using dwc_otg
[ 4220.793028] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
[ 4220.793080] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 08 38 00 00 08 00
[ 4220.793099] print_req_error: I/O error, dev sda, sector 2104
[ 4220.793124] Buffer I/O error on dev sda1, logical block 7, async page read
[ 4220.919442] usb 1-1.7.4: reset high-speed USB device number 5 using dwc_otg
[ 4221.053501] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
[ 4221.053548] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 07 4e b2 00 00 01 00
[ 4221.053572] print_req_error: I/O error, dev sda, sector 478898
[ 4221.159458] usb 1-1.7.4: reset high-speed USB device number 5 using dwc_otg
[ 4221.429444] usb 1-1.7.4: reset high-speed USB device number 5 using dwc_otg
[ 4221.699504] usb 1-1.7.4: reset high-speed USB device number 5 using dwc_otg
[ 4221.969453] usb 1-1.7.4: reset high-speed USB device number 5 using dwc_otg
[ 4222.239450] usb 1-1.7.4: reset high-speed USB device number 5 using dwc_otg
[ 4222.509590] usb 1-1.7.4: reset high-speed USB device number 5 using dwc_otg
[ 4222.643061] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00
[ 4222.643113] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 07 4e b2 00 00 01 00
[ 4222.643132] print_req_error: I/O error, dev sda, sector 478898
[ 4222.643315] FAT-fs (sda1): Directory bread(block 476850) failed
[ 4222.643793] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

                      Could this be the reason it doesn't want to mount it automatically?

                      mituM EfriimE 2 Replies Last reply Reply Quote 0
                      • mituM
                        mitu Global Moderator @2fst4u
                        last edited by

                        @2fst4u Looks like the hub/usb disk connection is reset

                        [ 4222.509590] usb 1-1.7.4: reset high-speed USB device number 5 using dwc_otg

                        You could try a check of the filesystem (on your PC) and see if it produces anything.

                        2 1 Reply Last reply Reply Quote 0
                        • EfriimE
                          Efriim @2fst4u
                          last edited by

                          @2fst4u A lot of external hard drives the 10-pin usb port is easily damaged, and will make faulty connections unless carefully situated. Which is awful engineering.

                          1 Reply Last reply Reply Quote 0
                          • 2
                            2fst4u @mitu
                            last edited by

                            Ah what an absolute prick of a thing! @mitu thank you for all your help so far, you've been great. I think you hit the nail on the head, @Efriim! I removed the hub from the equation and now it's working properly! How bloody annoying.

                            I went to all the effort to use an externally powered hub and it ended up being the problem haha. Thankfully the power supply seems to be able to power both the zero and the HDD directly through the USB port just fine so now it's working as expected.

                            Tl;dr - if you have this problem check the hub isn't causing it!

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

                              @2fst4u To be fair, this is the most common problem when dealing with a Pi Zero - the hub. Glad you got it working.

                              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.