A little birdy told me that Christian Hügel said: ] Heitor Augusto M. Cardozo schrieb: ] > The same problem happened with a server after I upgrade the kernel ] > to 2.6.9-42.0.2. ] > ] > Another server, with similar configuration, boots normally on new ] > kernel. ] > ] > Both uses software RAID and LVM2, (/boot on md0 and Logical Volume ] > on md1). Only differences between the servers is HD, on first have ] > two Seagate (ST380013AS Rev: 3.18) 80 GB, another have two ] > Western Digital (WDC WD2000JD-55H Rev: 08.0) 120 GB. ] > ] > As it is a production server, I didn't make any test to investigate ] > the problem, just boot on previous kernel. ] > ] > Heitor A. M. Cardozo ] > ] > ] ] Just a short note: the kernel 2.6.9-42.0.2.EL boots fine now on my RAID1 ] machine. ] I´m gonna test this days the one from the plus repo. just to chime in... in case it helps anyone identify a problem... but it wasn't the 2.6.9-42.0.2.EL kernel which broke my LILO boots on RAIDed drives... i think it was more likely something like "udev"... as i was running the 2.6.9-42.0.2.EL fine before the larger v4.4 update came out... and LILO did not demonstrate the problems i mentioned... in any case... i wasn't keen on retrograding other packages to stabilize the problem... instead i chose to jump LILO ahead (the new LILO has so many nice features... even just the "-T" switches made it worthwhile)... the "grubby" problem was something else altogether... that's purely a RH package that has been let slip in its maintenance... i wasn't heavily interested in all the maintenance that it needed... but i'm a stickler about making sure things "work" the way they should... B. Karhan simon at pop.psu.edu PRI/SSRI Unix Administrator