Re: Cannot boot with latest Lenny kernel 2.6.26
On Tue, Nov 25, 2008 at 11:55:59AM -0800, Neil Gunton wrote:
> My server is a dual Opteron 265, 4GB RAM, 4x10k SCSI drives in RAID0 on
> an Adaptec zero channel SmartRaid V card (the drive appears as
> /dev/i2o/hda1, so it's using the i2o_block driver).
> I am running fully up-to-date Debian Lenny, using the AMD64 port.
> I cannot boot with the latest kernel - 220.127.116.11. It stops early on, just
> after detecting disks, with this line:
> Begin: Waiting for root file system...
> It just hangs there.
> The last "good" kernel that works is 18.104.22.168. I haven't tweaked
> anything, these are both the stock build AMD64 kernels. I'm fairly
> certain this is a bug of some kind, since everything works ok with the
> earlier kernel. Things seemed to break going from 2.6.25 to 2.6.26.
> I am wondering if anyone else is having this issue, if it's a known bug,
> or something that I need to enter as a bug. Can anybody help?
Well one change for I2O between 2.6.25 and 2.6.25 is this:
mythtv64:~# grep I2O /boot/config-2.6.26-1-amd64
mythtv64:~# grep I2O /boot/config-2.6.25-2-amd64
So CONFIG_SCSI_DPT_I2O is now enabled. If that happens to have anything
to do with your I2O device, perhaps it is causing a different driver
name to be used or maybe it is causing interference.
Everything else looks the same of course.
Hitting control-c or alt+sysrq+i a few times might drop you to a shell
where you can see what devices if any for disk access have been detected
by the initramfs so far.
If the drive name does change, I often find it much better to use UUID
rather than device names in grub and fstab.
Similar in fstab.
That way the device names can do whatever they want and you still find
the right filesystems for the right places.