Bug 138603 - FC1 to FC3 upgrade with dpt_i2o card fails
Summary: FC1 to FC3 upgrade with dpt_i2o card fails
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: hwdata
Version: 3
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-11-10 06:49 UTC by Gordon Ewasiuk
Modified: 2014-03-17 02:50 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-11-10 20:15:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
df and fstab output (1.31 KB, text/plain)
2004-11-10 06:50 UTC, Gordon Ewasiuk
no flags Details
dmesg output (8.83 KB, text/plain)
2004-11-10 06:51 UTC, Gordon Ewasiuk
no flags Details
lspci output (3.93 KB, text/plain)
2004-11-10 06:51 UTC, Gordon Ewasiuk
no flags Details

Description Gordon Ewasiuk 2004-11-10 06:49:09 UTC
Description of problem:

Upgrading from an FC1 server with Adaptec 2100 IDE RAID card (uses
dpt_i2o) to FC3 resulted in system that wouldn't boot.  Kernel panic
with "mkinitrd: label / not found".

How reproducible:

100% of the time

Steps to Reproduce:
1.  Build FC1 server with Adaptec 2100 IDE RAID Controller
2.  Update to FC3
3.  Reboot and get kernel panic.
  
Actual results:

mkinitrd: label / not found

Expected results:

A working FC3 system.  Expected dpt_i2o to be replaced with new
i2o_block driver.  

Additional info:

Found initrd still used dpt_i2o after upgrade.  Made new initrd with
module i2o_block.  System booted normally and without a problem.  All
i2o devices were detected.

Release notes warn of possible problems during upgrade but don't
address whether dpt_i2o is replaced with i2o_block.

Comment 1 Gordon Ewasiuk 2004-11-10 06:50:31 UTC
Created attachment 106391 [details]
df and fstab output

Comment 2 Gordon Ewasiuk 2004-11-10 06:51:00 UTC
Created attachment 106392 [details]
dmesg output

Comment 3 Gordon Ewasiuk 2004-11-10 06:51:33 UTC
Created attachment 106393 [details]
lspci output

Comment 4 Jwahar Bammi 2004-11-10 12:36:04 UTC
I am seeing the exact same problem (integrated sil sata on a shuttle 
ft61 motherboard).
It would help a lot if Gordon or someone could attach the exact steps 
required to make a "new initrd with module i2o_block"  (for those of 
us less familiar with linux).
thanks

Comment 5 Gordon Ewasiuk 2004-11-10 13:29:59 UTC
Someone asked for the fix.  Here it is:

boot server to rescue mode
chroot /mnt/sysimage
mkinitrd -v --with-module=i2o_block /boot/initrd-2.6.9-1.667 2.6.9-1.667

reboot

that fixed my problem.

Comment 6 Bill Nottingham 2004-11-10 20:15:26 UTC
Fixed in hwdata-0.147-1.

Comment 7 Jason Duerstock 2005-02-01 17:22:54 UTC
Just to clear up the temporary fix, the mkinitrd line should read:
mkinitrd -v --with=i2o_block /boot/initrd-2.6.9-1.667.img 2.6.9-1.667


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