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.
Created attachment 106391 [details] df and fstab output
Created attachment 106392 [details] dmesg output
Created attachment 106393 [details] lspci output
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
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.
Fixed in hwdata-0.147-1.
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