https://bugzilla.kernel.org/show_bug.cgi?id=209089 --- Comment #8 from Manish Jain (bourne.identity@xxxxxxxxxxx) --- Hi Allan, Thanks for tuning in. The following has happened to me a couple of times, and the only way a third occurrence could be avoided is if USB mass storage devices nodes use a different nomenclature series vis-a-vis SATA disks. Here is the incident: I installed Linux using a memstick (USB pen drive), which got enumerated as sda while my internal hard disk got enumerated as sdb. When installation finished, my system was ready for reboot - except that I was not aware that my hard disk will next time appear as sda, not sdb as was the case during installation. So my fstab was all a mess, and it took me hours to figure out why my Linux was failing to boot. The only way I could correct the situation was to boot into FreeBSD and set up my Linux fstab correctly. Now as for your assertion "many USB drives actually are SATA drives attached via a USB-SATA adapter". It could not be more true. I have an internal SATA SSD myself that I occasionally attach to my system as an external USB device using a USB-SATA adapter. The right thing for Linux to do is allocate the device node for the SSD depending on the interface via which it was plugged in. Meaning, if it was plugged in as an internal SATA disk, it will acquire the moniker sd*. But if it is plugged in via the USB interface, it should get the moniker ud* (or anything different from sd*). I hope I have made my case clearly enough. Thank you, Manish Jain -- You are receiving this mail because: You are watching the assignee of the bug.
