Bug 524546 - Kernel driver order changes from boot to boot
Summary: Kernel driver order changes from boot to boot
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-09-21 07:00 UTC by Pablo Iranzo Gómez
Modified: 2009-09-23 11:13 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-09-23 11:13:17 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Pablo Iranzo Gómez 2009-09-21 07:00:16 UTC
Description of problem:
On aparently random reboots, Fedora kernel changes IDE HDD from 'sdb' (imho it should be hda), to 'sda', causing problems in boot

Version-Release number of selected component (if applicable):

Fedora rawhide updated until yesterday

How reproducible:


Steps to Reproduce:
1. boot computer
2. have fsck abort while trying to check 'sda1' (supposedly /boot)
3. check that 'sda' is not SATA drive 1, being instead IDE drive 1 renamed.
4. reboot
5. sometimes it will work
  
Actual results:

-IDE hdd is using ide-scsi
-Drive ordering is changing randomly


Expected results:
-IDE drives should be hd* as with previous releases
- most important: drive ordering should not change randomly


Additional info:
after putting LABEL="/boot" in fstab and using e2label to label correct drive, I always get my system booting, sometimes as 'sdb', sometimes as 'sda' (checked when asking for LUKS password)

Comment 1 Chuck Ebbert 2009-09-23 11:13:17 UTC
(In reply to comment #1)
> Actual results:
> 
> -IDE hdd is using ide-scsi
> -Drive ordering is changing randomly

The kernel is using the libata drivers, not ide-scsi. Drive order changing randomly is expected and the installer sets up fstab using labels and/or UUIDs to deal with that.


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