[SOLVED] One Linux System All-of-a-Sudden Unable to Mount SSD

tony5429 · 2023-08-07 02:36:08

I have two laptops each running an identical Arch Linux OS. For months both laptops have had no trouble accessing an external USB SSD. But as of today, one of the two laptops became unable to mount the drive. When I plug it into either the USB-C or USB-A port and try to mount it in KDE, after about 30 seconds I get a message saying I'm not authorised to mount it. No problem at all in the other laptop. What's more, I can access the drive just fine in a dual-booted Windows partition on the problematic laptop, using the same two USB ports. I also tried "fdisk -l" as root in the problematic Linux install, and it actually hangs indefinitely when trying to list the drive... Does anyone have any ideas what could've happened and how I might be able to troubleshoot it?

Last edited by tony5429 (2023-08-13 01:55:48)

Beuman · 2023-08-07 03:28:45

Can you mount it with sudo using the terminal ?

seth · 2023-08-07 06:22:30

25s would be the dbus timeout, the session is probably degenerated

loginctl session-status
echo $DBUS_SESSION_BUS_ADDRESS

fine in a dual-booted Windows partition

Likely not directly related, but see teh 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

tony5429 · 2023-08-07 11:05:10

Beuman, I could try but I don't know how to find its device address since "fdisk -l" hangs.

Seth: OK, this is what I get running those two commands...

[karam@phobos ~]$ loginctl session-status
1 - karam (1000)
           Since: Mon 2023-08-07 06:27:31 EDT; 28min ago
          Leader: 392 (sddm-helper)
            Seat: seat0; vc1
         Display: :0
         Service: sddm-autologin; type x11; class user
         Desktop: KDE
           State: active
            Unit: session-1.scope
                  ├─392 /usr/lib/sddm/sddm-helper --socket /tmp/sddm-auth96ed2776-aa4d->
                  ├─403 /usr/bin/startplasma-x11
                  ├─411 minidlnad -f /home/karam/.config/minidlna_movies/minidlna.conf >
                  ├─414 minidlnad -f /home/karam/.config/minidlna_mrn/minidlna.conf -P >
                  ├─417 minidlnad -f /home/karam/.config/minidlna_planet_earth/minidlna>
                  ├─420 minidlnad -f /home/karam/.config/minidlna_fpu/minidlna.conf -P >
                  ├─423 minidlnad -f /home/karam/.config/minidlna_tmsb/minidlna.conf -P>
                  ├─426 minidlnad -f /home/karam/.config/minidlna_vt/minidlna.conf -P />
                  ├─429 minidlnad -f /home/karam/.config/minidlna_other/minidlna.conf ->
                  └─432 minidlnad -f /home/karam/.config/minidlna_superbook/minidlna.co>

Aug 07 06:27:32 phobos sddm-helper[403]: Adding cookie to "/home/karam/.Xauthority"
[karam@phobos ~]$ echo $DBUS_SESSION_BUS_ADDRESS
unix:path=/run/user/1000/bus

As for Windows Fast-Start, my dual-booted Windows OS is actually Windows 7 so no issue there.

Lone_Wolf · 2023-08-07 11:19:47

tony5429 wrote:

Beuman, I could try but I don't know how to find its device address since "fdisk -l" hangs.

lsblk -f helps a lot to find such an address. see https://man.archlinux.org/man/lsblk.8 for details

seth · 2023-08-07 12:25:39

Session and dbus address are ok, but

since "fdisk -l" hangs

I'd look into dmesg or the system journal for IO errers…

tony5429 · 2023-08-08 10:04:52

OK, this is what dmesg gives me when I plug in the drive...

[Tue Aug  8 06:02:02 2023] audit: type=1326 audit(1691488922.668:26133): auid=1000 uid=1000 gid=1000 ses=2 pid=1275000 comm="snap-confine" exe="/snap/snapd/x1/usr/lib/snapd/snap-confine" sig=0 arch=c000003e syscall=308 compat=0 ip=0x7fb39f531427 code=0x50000
[Tue Aug  8 06:02:05 2023] audit: type=1326 audit(1691488925.922:26134): auid=1000 uid=1000 gid=1000 ses=2 pid=1275049 comm="snap-confine" exe="/snap/snapd/x1/usr/lib/snapd/snap-confine" sig=0 arch=c000003e syscall=308 compat=0 ip=0x7f82305f9427 code=0x50000
[Tue Aug  8 06:02:09 2023] audit: type=1326 audit(1691488929.245:26135): auid=1000 uid=1000 gid=1000 ses=2 pid=1275096 comm="snap-confine" exe="/snap/snapd/x1/usr/lib/snapd/snap-confine" sig=0 arch=c000003e syscall=308 compat=0 ip=0x7f43d6b20427 code=0x50000
[Tue Aug  8 06:02:12 2023] audit: type=1326 audit(1691488932.485:26136): auid=1000 uid=1000 gid=1000 ses=2 pid=1275144 comm="snap-confine" exe="/snap/snapd/x1/usr/lib/snapd/snap-confine" sig=0 arch=c000003e syscall=308 compat=0 ip=0x7f75cd0ba427 code=0x50000
[Tue Aug  8 06:02:12 2023] usb 1-1: new high-speed USB device number 6 using xhci_hcd
[Tue Aug  8 06:02:12 2023] usb 1-1: New USB device found, idVendor=0781, idProduct=55ae, bcdDevice=80.55
[Tue Aug  8 06:02:12 2023] usb 1-1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[Tue Aug  8 06:02:12 2023] usb 1-1: Product: Extreme 55AE
[Tue Aug  8 06:02:12 2023] usb 1-1: Manufacturer: SanDisk
[Tue Aug  8 06:02:12 2023] usb 1-1: SerialNumber: 32333035464D343034353632
[Tue Aug  8 06:02:12 2023] scsi host2: uas
[Tue Aug  8 06:02:13 2023] scsi 2:0:0:0: Direct-Access     SanDisk  Extreme 55AE     8055 PQ: 0 ANSI: 6
[Tue Aug  8 06:02:13 2023] scsi 2:0:0:1: Enclosure         SanDisk  SES Device       8055 PQ: 0 ANSI: 6
[Tue Aug  8 06:02:13 2023] sd 2:0:0:0: Attached scsi generic sg1 type 0
[Tue Aug  8 06:02:13 2023] sd 2:0:0:0: [sdb] 7813971617 512-byte logical blocks: (4.00 TB/3.64 TiB)
[Tue Aug  8 06:02:13 2023] sd 2:0:0:0: [sdb] Write Protect is off
[Tue Aug  8 06:02:13 2023] sd 2:0:0:0: [sdb] Mode Sense: 37 00 10 00
[Tue Aug  8 06:02:13 2023] scsi 2:0:0:1: Attached scsi generic sg2 type 13
[Tue Aug  8 06:02:13 2023] sd 2:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
[Tue Aug  8 06:02:13 2023] sd 2:0:0:0: [sdb] Preferred minimum I/O size 512 bytes
[Tue Aug  8 06:02:13 2023] sd 2:0:0:0: [sdb] Optimal transfer size 1048576 bytes
[Tue Aug  8 06:02:13 2023]  sdb: sdb1
[Tue Aug  8 06:02:13 2023] sd 2:0:0:0: [sdb] Attached SCSI disk
[Tue Aug  8 06:02:13 2023] scsi 2:0:0:1: Failed to get diagnostic page 0x1
[Tue Aug  8 06:02:13 2023] scsi 2:0:0:1: Failed to bind enclosure -19
[Tue Aug  8 06:02:13 2023] ses 2:0:0:1: Attached Enclosure device
[Tue Aug  8 06:02:15 2023] audit: type=1326 audit(1691488935.758:26137): auid=1000 uid=1000 gid=1000 ses=2 pid=1275222 comm="snap-confine" exe="/snap/snapd/x1/usr/lib/snapd/snap-confine" sig=0 arch=c000003e syscall=308 compat=0 ip=0x7f7d97d07427 code=0x50000
[Tue Aug  8 06:02:18 2023] audit: type=1326 audit(1691488939.095:26138): auid=1000 uid=1000 gid=1000 ses=2 pid=1275273 comm="snap-confine" exe="/snap/snapd/x1/usr/lib/snapd/snap-confine" sig=0 arch=c000003e syscall=308 compat=0 ip=0x7f732824a427 code=0x50000
[Tue Aug  8 06:02:22 2023] audit: type=1326 audit(1691488942.648:26139): auid=1000 uid=1000 gid=1000 ses=2 pid=1275321 comm="snap-confine" exe="/snap/snapd/x1/usr/lib/snapd/snap-confine" sig=0 arch=c000003e syscall=308 compat=0 ip=0x7f98ffb8e427 code=0x50000
[Tue Aug  8 06:02:25 2023] audit: type=1326 audit(1691488945.948:26140): auid=1000 uid=1000 gid=1000 ses=2 pid=1275370 comm="snap-confine" exe="/snap/snapd/x1/usr/lib/snapd/snap-confine" sig=0 arch=c000003e syscall=308 compat=0 ip=0x7f934351b427 code=0x50000
[Tue Aug  8 06:02:29 2023] audit: type=1326 audit(1691488949.228:26141): auid=1000 uid=1000 gid=1000 ses=2 pid=1275422 comm="snap-confine" exe="/snap/snapd/x1/usr/lib/snapd/snap-confine" sig=0 arch=c000003e syscall=308 compat=0 ip=0x7f78914de427 code=0x50000
[Tue Aug  8 06:02:32 2023] audit: type=1326 audit(1691488952.472:26142): auid=1000 uid=1000 gid=1000 ses=2 pid=1275468 comm="snap-confine" exe="/snap/snapd/x1/usr/lib/snapd/snap-confine" sig=0 arch=c000003e syscall=308 compat=0 ip=0x7f8461c87427 code=0x50000
[Tue Aug  8 06:02:35 2023] audit: type=1326 audit(1691488955.692:26143): auid=1000 uid=1000 gid=1000 ses=2 pid=1275516 comm="snap-confine" exe="/snap/snapd/x1/usr/lib/snapd/snap-confine" sig=0 arch=c000003e syscall=308 compat=0 ip=0x7f0704b47427 code=0x50000
[Tue Aug  8 06:02:38 2023] audit: type=1326 audit(1691488958.952:26144): auid=1000 uid=1000 gid=1000 ses=2 pid=1275566 comm="snap-confine" exe="/snap/snapd/x1/usr/lib/snapd/snap-confine" sig=0 arch=c000003e syscall=308 compat=0 ip=0x7f7ad92dc427 code=0x50000
[Tue Aug  8 06:02:42 2023] audit: type=1326 audit(1691488962.222:26145): auid=1000 uid=1000 gid=1000 ses=2 pid=1275615 comm="snap-confine" exe="/snap/snapd/x1/usr/lib/snapd/snap-confine" sig=0 arch=c000003e syscall=308 compat=0 ip=0x7f1d6ff13427 code=0x50000
[Tue Aug  8 06:02:45 2023] audit: type=1326 audit(1691488965.498:26146): auid=1000 uid=1000 gid=1000 ses=2 pid=1275663 comm="snap-confine" exe="/snap/snapd/x1/usr/lib/snapd/snap-confine" sig=0 arch=c000003e syscall=308 compat=0 ip=0x7fe0d53b3427 code=0x50000
[Tue Aug  8 06:02:48 2023] audit: type=1326 audit(1691488968.758:26147): auid=1000 uid=1000 gid=1000 ses=2 pid=1275711 comm="snap-confine" exe="/snap/snapd/x1/usr/lib/snapd/snap-confine" sig=0 arch=c000003e syscall=308 compat=0 ip=0x7ff58ebfa427 code=0x50000

tony5429 · 2023-08-08 10:13:03

Seeing the reference in dmesg to sdb1, I did also just try to mount the drive in command-line, but it's been stuck here for 4 minutes...

[root@phobos karam]# mkdir /run/media/mydrive
[root@phobos karam]# mount /dev/sdb1 /run/media/mydrive

tony5429 · 2023-08-08 10:22:24

Oh, this is interesting though... After cancelling the mount attempt, I just checked the mount location (/run/media/mydrive) and can actually see my drive's files in there... Even appear to be able to write to it (echo'd a new text file in root which seemed to work just fine). Then I unmounted, unplugged, and re-plugged in the drive, and tried again. It again successfully mounted in command line similar to before (where the /run/media/mydrive folder populated but it looked like the mount process was still in-progress). Then I CTRL+C'd the mount command (as I had before), and tried ls'ing through directories and the drive started hanging / not responding. Ctrl+C'd and couldn't unmount it (got an error about the drive being busy). Then typed this message and attempted to unmount again, and the unmount worked this time...

Last edited by tony5429 (2023-08-08 10:23:44)

seth · 2023-08-08 11:43:45

[Tue Aug  8 06:02:13 2023] scsi 2:0:0:1: Failed to get diagnostic page 0x1
[Tue Aug  8 06:02:13 2023] scsi 2:0:0:1: Failed to bind enclosure -19
[Tue Aug  8 06:02:13 2023] ses 2:0:0:1: Attached Enclosure device

doesn't look all that good.

What happens if you "mount -v …" it?
Can you try a different USB (3) slot?

tony5429 · 2023-08-13 01:55:31

So, trying mount with the verbose flag, it just hung again as before but still didn't show any messages. I decided to just wait though and after something like ten minutes, it successfully mounted (with the single message about it successfully mounting). Then I unmounted and tried mounting through KDE and it worked. Then I restarted the computer and tried my other port (a USB-C port) and it worked fine. Then I tried on the USB-A port and it spun for a while before providing the message about not having authorisation. I went back to the USB-C port a couple times afterwards and tried reading/writing and it continued to work there. So my theory is that it's some sort of issue that is created and seems to persist to some extent by mounting it off my USB-A port (could also be related to my USB-A-to-USB-C cable maybe?). Thanks for your help, seth especially.

seth · 2023-08-13 05:55:11

"Underpowered", the drive requires more power to spin up than the USB-A port delivers (2.5W standard, some ports may provide more but that's optional) where USB-C is getting you 7.5W at least.

Arch Linux

#1 2023-08-07 02:36:08

[SOLVED] One Linux System All-of-a-Sudden Unable to Mount SSD

#2 2023-08-07 03:28:45

Re: [SOLVED] One Linux System All-of-a-Sudden Unable to Mount SSD

#3 2023-08-07 06:22:30

Re: [SOLVED] One Linux System All-of-a-Sudden Unable to Mount SSD

#4 2023-08-07 11:05:10

Re: [SOLVED] One Linux System All-of-a-Sudden Unable to Mount SSD

#5 2023-08-07 11:19:47

Re: [SOLVED] One Linux System All-of-a-Sudden Unable to Mount SSD

#6 2023-08-07 12:25:39

Re: [SOLVED] One Linux System All-of-a-Sudden Unable to Mount SSD

#7 2023-08-08 10:04:52

Re: [SOLVED] One Linux System All-of-a-Sudden Unable to Mount SSD

#8 2023-08-08 10:13:03

Re: [SOLVED] One Linux System All-of-a-Sudden Unable to Mount SSD

#9 2023-08-08 10:22:24

Re: [SOLVED] One Linux System All-of-a-Sudden Unable to Mount SSD

#10 2023-08-08 11:43:45

Re: [SOLVED] One Linux System All-of-a-Sudden Unable to Mount SSD

#11 2023-08-13 01:55:31

Re: [SOLVED] One Linux System All-of-a-Sudden Unable to Mount SSD

#12 2023-08-13 05:55:11

Re: [SOLVED] One Linux System All-of-a-Sudden Unable to Mount SSD

Board footer