
(Read the ATA, ATAPI and USB storage specs for details). There are quite a few different ways to get the drive serial number. So, it seems purely over USB or UASP that this goes bonkers.Įven weirder when using the same hardware on Debian Linux 10/Buster, it works fine ( ata instead of scsi by the way! and yes UASP is enabled scsi host4: uas in dmesg): ├── ata-TOSHIBA_MQ01ABB200_1234ABCD ->. I am also using a more professional hot plug storage enclosure and this one works fine with those drives. Why is this? What piece of software is responsible for these errors? /sdbĪlso sometimes it's an i prepended instead of an S, depending on the manufacturer. The Western Digital non-UASP drive does not suffer from any of the two problems: └── usb-WD_Elements_1048_1234ABCD-0:0 ->.
The StarTech enclosure does not have the serial reversion: ├── scsi-STOSHIBA_MQ01ABB200_1234ABCD ->.
The serial number is reversed 12345688ACF4 became 4FCA88654321.
The manufacturer name is prepended with an S. This is really cool, as it allows me to be sure I'm working on the correct drive rather than a dangerous assumption sdb would be the correct drive.Īs you can see the string scsi-SSamsung_Portable_SSD_T5_4FCA88654321 contains two errors, though: When adding a drive, a convenient link is created for them in /dev/disk/by-id/: /dev/disk/by-id/ It's not something we can solve and my question is about something else. Their serial number reported over USB to the kernel is sometimes wrong, but that seems a hardware issue with them. WD Elements USB hard disk drive without UASPĪll these are single-disk to USB enclosures basically. (Reports bogus disk serial 000000004BA8 over USB, it's always the same.) StarTech USB 3.1 gen2 enclosure for SATA hard disk drive, with UASPĮwent EW7017 USB to SATA dongle with UASP (Reports correct disk serial over USB identical to SMART data and disk label.) Samsung Portable SSD T7 (NVMe to USB with UASP internally) (This is a bogus disk serial over USB, different from label and SMART data.) S/N reported to kernel (as per dmesg & lsusb -v): 12345688ACF4
Samsung Portable SSD T5 (mSATA to USB with UASP internally) I've got a bunch of USB enclosures for hard disk drives here (or rather sold as external drives): I'm using Ubuntu 20.04 with USB external drives and experiencing a rather odd bug.