On Fri, 10 Sep 2010, walt wrote:
On 09/10/2010 03:18 PM, Ajai Khattri wrote:
I upgraded several machines and some failed to boot 2.6.35, they just hang
after grub starts loading the kernel. Some of these I managed to fix by
comparing kernel configs with working machines...
What kernel config items did you change to fix those broken machines?
The two main ones seemed to be disabling the deprecated ATA drivers and
another one was disabling some sysfs options. But these changes didn't
help in this case. At this point, I think Im better off sticking to the
older kernel until I figure this out properly so Ive focussed my efforts
on getting that working.
I have since booted off a recent boot CD, mounted the RAID partitions and
tried downgrading udev so I can maybe boot the older kernel. This didn't
work since the LiveCD is newer than the original CD I used to build this
box, and the naming conventions for RAID devices seems to have changed
(and building udev from a LiveCD means Im using newer /proc and /dev!).
The older kernel loads but then says my root device doens't exist.
Under the old scheme I specified /dev/md1 as my root in grub.conf but
since this doesn't exist the boot fails. In trying to fix this I see that
the LiveCD uses the following device files for the RAID partitions:
/dev/md123 /dev/md124 /dev/md125 /dev/md126. Should I be using those in
grub.conf now?
--
A
