Bug 423691 - initrd contains usb_storage, /dev/sda might be an external disk instead of an internal one
initrd contains usb_storage, /dev/sda might be an external disk instead of an...
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
8
i386 Linux
low Severity low
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-12-13 11:46 EST by wwp
Modified: 2007-12-19 16:27 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-12-19 15:19:42 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description wwp 2007-12-13 11:46:12 EST
Description of problem:
/boot/initrd-2.6.23.8-63.fc8.img contains the usb_storage module. 

Version-Release number of selected component (if applicable):
initrd from kernel 2.6.23.8-63.fc8.

How reproducible:
Always.

Steps to Reproduce:
1. Have F8 installed on a system w/ a SATA (or maybe SCSI too) internal disk and
some external USB disk (plugged in and powered). In my case it's a Dell D810 laptop.
2. Possibly have booting from USB disk enabled in BIOS and before internal disk
in boot sequence.
3. Boot kernel 2.6.23.8-63.fc8.
  
Actual results:
/dev/sda is not the internal disk. USB disks are /dev/sda, /dev/sdb, etc. The
internal drive will be the last /dev/sdX.

Expected results:
/dev/sda should be the internal drive, external disks should follow.

Additional info:
As a side effet, Nautilus will fail to mount devices by their label, obviously
trying to mount the wrong disk, *IF* Nautilus already mounted those disks from
correct label when system was booted w/ kernel < 2.6.23.8-63).

/boot/initrd-2.6.23.1-49.fc8.img was NOT containing the usb_storage module,
problem came when upgraded kernel to 2.6.23.8-63 using yum and was not
encountered before.

Thread reference in Fedora Users mailing list:
https://www.redhat.com/archives/fedora-list/2007-December/msg01331.html
Comment 1 wwp 2007-12-19 03:31:36 EST
I've just checked: booting USB devices is *NOT* enabled in BIOS settings, this
invalidates Step 2 only.
Comment 2 Chuck Ebbert 2007-12-19 15:19:42 EST
(In reply to comment #0)
> Actual results:
> /dev/sda is not the internal disk. USB disks are /dev/sda, /dev/sdb, etc. The
> internal drive will be the last /dev/sdX.
> 
> Expected results:
> /dev/sda should be the internal drive, external disks should follow.
>

There is no guarantee of that. SCSI devices are randomly assigned.
 
> Additional info:
> As a side effet, Nautilus will fail to mount devices by their label, obviously
> trying to mount the wrong disk, *IF* Nautilus already mounted those disks from
> correct label when system was booted w/ kernel < 2.6.23.8-63).
>

That would be a Nautilus bug, and would happen with two USB disks connected at
the same time too.
 
> /boot/initrd-2.6.23.1-49.fc8.img was NOT containing the usb_storage module,
> problem came when upgraded kernel to 2.6.23.8-63 using yum and was not
> encountered before.
>

If a USB disk is connected at kernel install/upgrade time, usb-storage will be
included on the initrd. If that's not desired, disconnect the USB disk and then
uninstall/reinstall the kernel, or rebuild the initrd.
 
> Thread reference in Fedora Users mailing list:
> https://www.redhat.com/archives/fedora-list/2007-December/msg01331.html
Comment 3 wwp 2007-12-19 16:08:18 EST
OK, thanks!

As a workaround, I've set hal rules to force mount locations according to device
labels.

I think that there's definitely a problem w/ Nautilus, as it raises an error
when trying to mount a disk (Nautilus shows a mount label that doesn't
correspond to the device it attempts to mount).

Should I file another bug, assigning it to Nautilus or reassign this one and
reopen it?

Comment 4 Chuck Ebbert 2007-12-19 16:27:19 EST
I would file a new bug against nautilus.

Note You need to log in before you can comment on or make changes to this bug.