On Saturday 08 September 2007 05:46:36 am Andreas Vetter wrote: > On Sat, 8 Sep 2007, Richard C Creighton wrote: > > Andreas Vetter wrote: > > > Hi, > > > > > > I updated a x86_64 machine from beta1 to beta3. After the packages were > > > installed I found the machine in a reboot loop. The grub boot loader > > > was not working any longer. So I tried Repair System. The automatic one > > > obviously deleted Windows from menu.lst. Then it threw an error about > > > not being able to access /dev/fd/62. A second try with this one left me > > > with a single entry for linux (i.e. failsafe and xen were gone, too).
This is a bug in Repair system. > > > So I tried the Expert option Repair Boot Loader. It recreated the > > > default and failsafe entries in menu.lst, but was not able to create > > > initrd. the script complained about not being able to access /dev/sda6 > > > which is the root / partition of my system (xfs containing /boot, too). It acts like xfs driver is missing. > > > After that wreckage I decided to try a new installation of beta3. So I > > > have no logs for the above problems. > > > > > > Has anybody similar behaviour? > > > > check out https://bugzilla.novell.com/show_bug.cgi?id=304657#c11 and see > > if anything rings a bell in your case and if it does, leave them a > > comment giving as much info as possible. > > Hm, I don't think this is related to my case. I think the bug in the 10.3 > update kernel package is the culprit in that case. The primary reason that you needed Repair System is kernel update, but -- Regards, Rajko. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
