manual mount not mounting usb

Shadowron

@lukevin Did you disable usbromservice?

lukevin

yes this is a clean install and i disabled usb rom service before beginning this experiment

using the 128gb sandisk drive
i tried to mount /dev/sda1 just now as i was poking around and got this
...
pi@retropie:~ $ sudo mount /dev/sda1
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or helper program, or other error

   In some cases useful info is found in syslog - try
   dmesg | tail or so.

...

Shadowron

@lukevin Sounds like wrong filesystem. Are you sure you entered correct fs and right uuid?

lukevin

@shadowron said in manual mount not mounting usb:

@lukevin Sounds like wrong filesystem. Are you sure you entered correct fs and right uuid?

reformating the usb now

sudo mkfs.ext4 /dev/sda1

Sano

Did you try to use PARTUUID=xxxx in fstab (for the sda1 partition), and finding the /dev/sda1 PARTUUID by doing a ls -l /dev/disk/by-partuuid/ ?
Just saying, because existing entries in fstab use PARTUUID...

A mount -v /home/pi/RetroPie after editing fstab could also provide interesting informations.

lukevin

@sano said in manual mount not mounting usb:

mount -v /home/pi/RetroPie

ok heres what i got

df
Filesystem     1K-blocks    Used Available Use% Mounted on
/dev/root        7517500 2438572   4737052  34% /
devtmpfs          370708       0    370708   0% /dev
tmpfs             375316       4    375312   1% /dev/shm
tmpfs             375316    5324    369992   2% /run
tmpfs               5120       4      5116   1% /run/lock
tmpfs             375316       0    375316   0% /sys/fs/cgroup
/dev/mmcblk0p1     58234   21534     36700  37% /boot
pi@retropie:~ $ ls -l /dev/disk/by-partuuid
total 0
lrwxrwxrwx 1 root root 10 Mar 16 17:40 5728b712-01 -> ../../sda1
lrwxrwxrwx 1 root root 15 Mar 16 17:40 5728b712-02 -> ../../mmcblk0p2

 GNU nano 2.2.6              File: /etc/fstab

proc    /proc   proc    defaults        0       0
PARTUUID=5728b712-01    /boot   vfat    defaults        0       2
PARTUUID=5728b712-02    /       ext4    defaults,noatime        0       1
# a swapfile is not a swap partition, no line here
#   use  dphys-swapfile swap[on|off]  for that
PARTUUID=5728b712-01    /home/pi/RetroPie       ext4    nofail,detfaults       0       0

mount -v /home/pi/RetroPie
reboot

still doesn't show up

lukevin

@sano said in manual mount not mounting usb:

mount -v /home/pi/RetroPie

sudo mount -v /home/pi/RetroPie
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try
       dmesg | tail or so.

Sano

What does the mount -v says ?

Moreover, you have the same partuuid for /boot and your USB, this can't be.
Your boot partition seems to be linked to /dev/sda1

Could you remove the line you added to fstab, issue a tail -f /var/log/messagesin terminal and then plug your usb drive, then copy the result here (the lines appearing after plugging the USB drive) ?

lukevin

@sano said in manual mount not mounting usb:

What does the mount -v says ?

Moreover, you have the same partuuid for /boot and your USB, this can't be.
Your boot partition seems to be linked to /dev/sda1

Could you remove the line you added to fstab, issue a tail -f /var/log/messagesin terminal and then plug your usb drive, then copy the result here (the lines appearing after plugging the USB drive) ?

#'d out the line in fstab but did not reboot

pi@retropie:~ $ sudo tail -f /var/log/messages
Mar 16 17:53:05 retropie kernel: [    9.666435] Bluetooth: SCO socket layer initialized
Mar 16 17:53:05 retropie kernel: [    9.673985] Bluetooth: HCI UART driver ver 2.3
Mar 16 17:53:05 retropie kernel: [    9.673998] Bluetooth: HCI UART protocol H4 registered
Mar 16 17:53:05 retropie kernel: [    9.674003] Bluetooth: HCI UART protocol Three-wire (H5) registered
Mar 16 17:53:05 retropie kernel: [    9.674177] Bluetooth: HCI UART protocol Broadcom registered
Mar 16 17:53:05 retropie kernel: [    9.844866] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Mar 16 17:53:05 retropie kernel: [    9.844877] Bluetooth: BNEP filters: protocol multicast
Mar 16 17:53:05 retropie kernel: [    9.844897] Bluetooth: BNEP socket layer initialized
Mar 16 17:53:06 retropie usbmount[466]: dev/sda does not contain a filesystem or disklabel
Mar 16 17:53:33 retropie kernel: [   30.579994] random: crng init done
Mar 16 18:01:34 retropie kernel: [  511.097352] usb 1-1.5: USB disconnect, device number 5
Mar 16 18:01:43 retropie kernel: [  520.095376] usb 1-1.5: new high-speed USB device number 6 using dwc_otg
Mar 16 18:01:43 retropie kernel: [  520.226762] usb 1-1.5: New USB device found, idVendor=0781, idProduct=5583
Mar 16 18:01:43 retropie kernel: [  520.226774] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Mar 16 18:01:43 retropie kernel: [  520.226782] usb 1-1.5: Product: Ultra Fit
Mar 16 18:01:43 retropie kernel: [  520.226790] usb 1-1.5: Manufacturer: SanDisk
Mar 16 18:01:43 retropie kernel: [  520.226798] usb 1-1.5: SerialNumber: 4C530001180512111165
Mar 16 18:01:43 retropie kernel: [  520.229395] usb-storage 1-1.5:1.0: USB Mass Storage device detected
Mar 16 18:01:43 retropie kernel: [  520.231095] scsi host0: usb-storage 1-1.5:1.0
Mar 16 18:01:44 retropie kernel: [  521.286963] scsi 0:0:0:0: Direct-Access     SanDisk  Ultra Fit        1.00 PQ: 0 ANSI: 6
Mar 16 18:01:44 retropie kernel: [  521.288210] sd 0:0:0:0: Attached scsi generic sg0 type 0
Mar 16 18:01:44 retropie kernel: [  521.289192] sd 0:0:0:0: [sda] 242614272 512-byte logical blocks: (124 GB/116 GiB)
Mar 16 18:01:44 retropie kernel: [  521.291101] sd 0:0:0:0: [sda] Write Protect is off
Mar 16 18:01:44 retropie kernel: [  521.293355] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Mar 16 18:01:44 retropie kernel: [  521.312824]  sda: sda1
Mar 16 18:01:44 retropie kernel: [  521.315519] sd 0:0:0:0: [sda] Attached SCSI removable disk
Mar 16 18:01:45 retropie usbmount[1327]: dev/sda does not contain a filesystem or disklabel
Mar 16 18:01:50 retropie usbmount[1334]: executing command: mount -text4 -osync,noexec,nodev,noatime,nodiratime,uid=1000,gid=1000 dev/sda1 /media/usb0

lukevin

so i took a look at my /boot/cmdline.txt and found that

root=PARTUUID=5728b712-02

i assume it should actually read

root=/dev/mmcblk0p2

i have no idea why that isn't right on a clean img

Sano

No, it's ok. PARTUUID is preferred due to possible device name change with udev.
Your usb drive partition is sda1, but usbmount seems to mount it to /media/usb0.
This should be disabled first if you plan to use fstab, like it's said in the wiki and by @Shadowron .

Edit : my bad, this is usbmount and not usbromservice, but it should be removed if usbromservice is disabled...

lukevin

@sano said in manual mount not mounting usb:

No, it's ok. PARTUUID is preferred due to possible device name change with udev.
Your usb drive partition is sda1, but usbmount seems to mount it to /media/usb0.
This should be disabled first if you plan to use fstab, like it's said in the wiki and by @Shadowron .

so the first thing i did after i made this img and turn on the pi was go to the retropie_setup.sh and disable the usb rom service as per the instructions right?

then i went to find the actual file /etc/usbmount/usbmount.conf
and it was still enabled. fixed that and reran the guide again to no avial

though my uuid changed for sda1 now to

pi@retropie:~ $ ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 15 Mar 16 18:24 0d5d7270-400a-4069-90ce-5547c464af88 -> .                                  ./../mmcblk0p2
lrwxrwxrwx 1 root root 10 Mar 16 18:24 88c49436-bc28-40e4-a132-15c30e12b363 -> .                                  ./../sda1
lrwxrwxrwx 1 root root 15 Mar 16 18:24 F800-84AD -> ../../mmcblk0p1
pi@retropie:~ $

pi@retropie:~ $ ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 15 Mar 16 18:24 0d5d7270-400a-4069-90ce-5547c464af88 -> .                                  ./../mmcblk0p2
lrwxrwxrwx 1 root root 10 Mar 16 18:24 88c49436-bc28-40e4-a132-15c30e12b363 -> .                                  ./../sda1
lrwxrwxrwx 1 root root 15 Mar 16 18:24 F800-84AD -> ../../mmcblk0p1

so should my change to fstab be PARTUUID or UUID as per the guide?

lukevin

after saying wrong fs over and over when i would try to mount it suddenly it mounted via a mount command this time. I have no idea why but
how do i add this to fstab and have it mount at boot? i add this to fstab yes?
UUID=88c49436-bc28-40e4-a132-15c30e12b363 /home/pi/Retropie ext4 nofail,defaults 0 0

pi@retropie:~ $ ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 15 Mar 16 18:36 0d5d7270-400a-4069-90ce-5547c464af88 -> .                                  ./../mmcblk0p2
lrwxrwxrwx 1 root root 10 Mar 16 18:36 88c49436-bc28-40e4-a132-15c30e12b363 -> .                                  ./../sda1
lrwxrwxrwx 1 root root 15 Mar 16 18:36 F800-84AD -> ../../mmcblk0p1
pi@retropie:~ $ df -T -h
Filesystem     Type      Size  Used Avail Use% Mounted on
/dev/root      ext4      7.2G  2.4G  4.6G  34% /
devtmpfs       devtmpfs  363M     0  363M   0% /dev
tmpfs          tmpfs     367M  4.0K  367M   1% /dev/shm
tmpfs          tmpfs     367M  5.2M  362M   2% /run
tmpfs          tmpfs     5.0M  4.0K  5.0M   1% /run/lock
tmpfs          tmpfs     367M     0  367M   0% /sys/fs/cgroup
/dev/mmcblk0p1 vfat       57M   22M   36M  37% /boot
pi@retropie:~ $ sudo mount /dev/sda1 /home/pi/RetroPie
pi@retropie:~ $ df -T -h
Filesystem     Type      Size  Used Avail Use% Mounted on
/dev/root      ext4      7.2G  2.4G  4.6G  34% /
devtmpfs       devtmpfs  363M     0  363M   0% /dev
tmpfs          tmpfs     367M  4.0K  367M   1% /dev/shm
tmpfs          tmpfs     367M  5.2M  362M   2% /run
tmpfs          tmpfs     5.0M  4.0K  5.0M   1% /run/lock
tmpfs          tmpfs     367M     0  367M   0% /sys/fs/cgroup
/dev/mmcblk0p1 vfat       57M   22M   36M  37% /boot
/dev/sda1      ext4      114G   61M  108G   1% /home/pi/RetroPie

Sano

@lukevin
Ok this seems good now.
It should work by adding the line you mention in /etc/fstab.
The previous UUID you had for sda1 looked like a VFAT UUID (see for example the UUID of /boot).
It may explain why the wrong fs message. After formatting ext4, you got a ext-type UUID and the mount command works.
I don't see another explanation.

lukevin

@sano

i had to chown my permissions back but this is now solved. windows powershell format and partition to fat32 on my drives originally as the guide was fat32 then changing to ext4 and it seems that when i was doing the new partitioning it just wasn't taking effect for some reason but this is now solved.

thank you sano and shadowron

i've been banging my head on the desk for a week trying to understand linux commands and forcing myself to learn a new OS.