this post was submitted on 19 Aug 2025
15 points (100.0% liked)

Linux Questions

2517 readers
1 users here now

Linux questions Rules (in addition of the Lemmy.zip rules)

Tips for giving and receiving help

Any rule violations will result in disciplinary actions

founded 2 years ago
MODERATORS
possiblylinux127@lemmy.zip
15
[Solved - likely hardware issue] large USB storage devices don't work since Debian 13 update (infosec.pub)
submitted 1 week ago* (last edited 2 days ago) by ProfessorHoover@infosec.pub to c/linuxquestions@lemmy.zip
6 comments fedilink hide all child comments
 

2nd Edit: the problem was not the PSU but either the motherboard or the CPU. I installed a USB expansion card with an internal USB 3 header that has narrowed down the issue. I am aware that early Ryzen chips had issues with USB reliability, so maybe the Trixie update installed a new chipset driver that caused this. Either way I'm saving for an upgrade so hopefully won't be an issue too much longer.

Edit: I've now tested in other OSes and had the same issue. So it's probably just a poorly timed hardware issue.

Since I updated my desktop to Debian 13, my external SSDs (Over 1TB) are only detected by gnome-disks as "no media". They also bring down my other USB drives if I leave the unrecognised SSDs plugged in while trying to make other transfers. All these drives work in Debian 12 on my laptop.

I've checked dmesg for my external SSD:

`[ 1801.737164] usb 1-4: new high-speed USB device number 7 using xhci_hcd

[ 1801.909543] usb 1-4: New USB device found, idVendor=152d, idProduct=0580, bcdDevice= 2.14

[ 1801.909549] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[ 1801.909551] usb 1-4: Product: PX10

[ 1801.909552] usb 1-4: Manufacturer: SP

[ 1801.909554] usb 1-4: SerialNumber: 2405185321200000000D

[ 1801.946647] scsi host41: uas

[ 1801.947031] scsi 41:0:0:0: Direct-Access SP PX10 0214 PQ: 0 ANSI: 6

[ 1801.949657] sd 41:0:0:0: Attached scsi generic sg7 type 0

[ 1803.041153] usb 2-3: USB disconnect, device number 2

[ 1813.106975] sd 41:0:0:0: [sdg] Unit Not Ready

[ 1813.106981] sd 41:0:0:0: [sdg] Sense Key : Hardware Error [current]

[ 1813.106984] sd 41:0:0:0: [sdg] ASC=0x44 <>ASCQ=0x81

[ 1813.107229] sd 41:0:0:0: [sdg] Read Capacity(16) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK

[ 1813.107232] sd 41:0:0:0: [sdg] Sense Key : Hardware Error [current]

[ 1813.107235] sd 41:0:0:0: [sdg] ASC=0x44 <>ASCQ=0x81

[ 1813.107549] sd 41:0:0:0: [sdg] Read Capacity(10) failed: Result: hostbyte=DID_OK driverbyte=DRIVER_OK

[ 1813.107552] sd 41:0:0:0: [sdg] Sense Key : Hardware Error [current]

[ 1813.107555] sd 41:0:0:0: [sdg] ASC=0x44 <>ASCQ=0x81

[ 1813.107631] sd 41:0:0:0: [sdg] 0 512-byte logical blocks: (0 B/0 B)

[ 1813.107634] sd 41:0:0:0: [sdg] 0-byte physical blocks

[ 1813.107872] sd 41:0:0:0: [sdg] Test WP failed, assume Write Enabled

[ 1813.107952] sd 41:0:0:0: [sdg] Asking for cache data failed

[ 1813.107955] sd 41:0:0:0: [sdg] Assuming drive cache: write through

[ 1813.108195] sd 41:0:0:0: [sdg] Preferred minimum I/O size 4096 bytes not a multiple of physical block size (0 bytes)

[ 1813.108198] sd 41:0:0:0: [sdg] Optimal transfer size 33553920 bytes not a multiple of physical block size (0 bytes)

[ 1813.108560] sd 41:0:0:0: [sdg] Attached SCSI disk`

I'd assume the issue is corruption in my SSD, but it's happening with two different drives.

top 6 comments
sorted by: hot top controversial new old
[–] helloworld@lemmy.ml 1 points 5 days ago* (last edited 5 days ago)

can you check lsblk command output, while the device is plugged in? does it show up there?

If it does, try to use the mount command to mount it from the terminal manually.

[–] brickfrog@lemmy.dbzer0.com 3 points 1 week ago* (last edited 1 week ago) (1 children)

I’d assume the issue is corruption in my SSD, but it’s happening with two different drives.

Based on the error it doesn't sound like corruption on the SSD itself, rather it's an issue with the USB storage chassis that the SSD is inside of. Or maybe an issue with the USB cable if there is one. But that doesn't explain why it was working fine pre-upgrade :/

Are your USB drives all the same make/model? I'm wondering if maybe they're using the same chipset and maybe it doesn't play nice with Debian 13 for whatever reason.

For what it's worth I have a Terramaster USB chassis with a 14 TB SATA drive inside it, it seems to work fine on a fresh install of Debian 13.

[–] fuckwit_mcbumcrumble@lemmy.dbzer0.com 3 points 1 week ago (1 children)

OP specified over 1TB. OP does that mean that a drive under 1TB works fine?

[–] ProfessorHoover@infosec.pub 2 points 1 week ago (1 children)

I had written half the post before I got the idea that the large SSDs were causing my smaller USBs to fail too. Unfortunately that doesn't seem to be the case. Further testing indicates that my 128GB USB drive doesn't work, but a 32 GB one with Ventoy does work.

It doesn't appear to be a specific chipset as when the drives show up in gnome-disks I can see the chipset. The two that I just tested are Realtek and Phison.

[–] Successful_Try543@feddit.org 3 points 1 week ago* (last edited 1 week ago) (1 children)

[ 1813.107232] sd 41:0:0:0: [sdg] Sense Key : Hardware Error [current]

Might indicate that the chip requires more current (power) than it requests or the system provides. As your hardware didn't change by upgrading to trixie, it's probably a driver issue.
Unfortunately, the only solution for that error I could find was for RHEL and thus behind a paywall. I hope you have more luck.

Edit: Some chips in usb ssd cases use the usb_storage driver instead of uas which sometimes causes problems:

https://bbs.archlinux.org/viewtopic.php?id=280390

[–] ProfessorHoover@infosec.pub 2 points 4 days ago

That's the rabbit hole I was starting to go down. I've finally had some time to do more testing and the issue also occurs in windows and a live cd. So I'm assuming it's a hardware issue, although the 5v rail on my PSU is reading right on 5v when unloaded. I'll start replacing parts.