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 - 2.6.26.1. 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 2.6.25.2. 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 CONFIG_SCSI_DPT_I2O=m CONFIG_I2O=m CONFIG_I2O_LCT_NOTIFY_ON_CHANGES=y CONFIG_I2O_EXT_ADAPTEC=y CONFIG_I2O_EXT_ADAPTEC_DMA64=y CONFIG_I2O_CONFIG=m CONFIG_I2O_CONFIG_OLD_IOCTL=y CONFIG_I2O_BUS=m CONFIG_I2O_BLOCK=m CONFIG_I2O_SCSI=m CONFIG_I2O_PROC=m mythtv64:~# grep I2O /boot/config-2.6.25-2-amd64 CONFIG_I2O=m CONFIG_I2O_LCT_NOTIFY_ON_CHANGES=y CONFIG_I2O_EXT_ADAPTEC=y CONFIG_I2O_EXT_ADAPTEC_DMA64=y CONFIG_I2O_CONFIG=m CONFIG_I2O_CONFIG_OLD_IOCTL=y CONFIG_I2O_BUS=m CONFIG_I2O_BLOCK=m CONFIG_I2O_SCSI=m CONFIG_I2O_PROC=m 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. ie: root=/dev/sda1 becomes: root=UUID=abce-2312323-ssasdads Similar in fstab. That way the device names can do whatever they want and you still find the right filesystems for the right places. -- Len Sorensen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]