linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 209089] USB storage devices appear as SATA devices
Date: Tue, 01 Sep 2020 15:47:50 +0000	[thread overview]
Message-ID: <bug-209089-208809-gBTIndJGBV@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209089-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=209089

--- Comment #8 from Manish Jain (bourne.identity@hotmail.com) ---
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.

  parent reply	other threads:[~2020-09-01 15:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-209089-208809@https.bugzilla.kernel.org/>
2020-09-01 11:30 ` [Bug 209089] USB storage devices appear as SATA devices bugzilla-daemon
2020-09-01 13:15 ` bugzilla-daemon
2020-09-01 13:28 ` bugzilla-daemon
2020-09-01 13:34 ` bugzilla-daemon
2020-09-01 13:35 ` bugzilla-daemon
2020-09-01 14:51 ` bugzilla-daemon
2020-09-01 15:03 ` bugzilla-daemon
2020-09-01 15:47 ` bugzilla-daemon [this message]
2020-09-01 16:10 ` bugzilla-daemon
2020-09-01 16:48 ` bugzilla-daemon
2020-09-01 20:31 ` bugzilla-daemon
2020-09-01 21:13 ` bugzilla-daemon
2020-09-14 20:42 ` bugzilla-daemon
2020-09-14 20:45 ` bugzilla-daemon
2020-09-15  1:25 ` bugzilla-daemon
2020-09-15 14:27 ` bugzilla-daemon
2020-09-15 14:30 ` bugzilla-daemon
2020-09-16  8:43 ` bugzilla-daemon
2020-09-16  8:56 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-209089-208809-gBTIndJGBV@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).