[opensuse] 11.1 upgrade on md raid root fails to boot
Well, i have managed to get enough info to know this is bug https://bugzilla.novell.com/show_bug.cgi?id=445490, which says it is resolved, but obviously not in the GM version of packages. Unfortunately, I cannot see what was needed to fix this, as I get an access denied when clicking on https://bugzilla.novell.com/show_bug.cgi?id=435778 at the end (where the fix was supposed to be). Is there an update of mkinitrd, or udev, or something to fix this? I upgraded from 10.3 yesterday, but not being able to boot after it was finished was a real problem. I was finally able to boot installed system (hidden in the repair tools) to be able to boot again and was able to find the above bug report and found out with a few tweaks I could eventually boot up by hitting Ctrl-D to seemingly exit the bootup system. I have been running mdraid 1 since 8.0, and mdraid 1 roots since 9.1 IIRC, but this was the hardest to figure out, and appears to be a problem that is quite old ( http://lists.opensuse.org/opensuse-bugs/2008-08/msg07297.html ). I would really appreciate it if anyone knows how I can repair the boot process in 11.1 so boot.md does not fail, and I do not need to hit Ctrl-D to be able to boot? BTW, I have a mdraid root and home, and yesterday trying to repair it I was seeing it go from md0 & md1 to md126 and md127, trying the repair option was a disaster, as it fscked the individual disk, which failed (and I canceled, but that I eventually figured out had somehow split the 2 partitions to one disk was md125_0 and the other md127_0. It was bizarre. Seems the mdraid part of 11.1 has some real problems this time around (and the server at our office has 4 mdraid devices, not looking forward to that upgrade). Does anyone know if this was worse because of the upgrade path (or in other words, has anyone installed 11.1 on a mdraid root device and did not have problems)? TIA for any help. -- Joe Morris Registered Linux user 231871 running openSUSE 10.3 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I had a similar problem I managed to work through! Take a look at another grizzly saga https://bugzilla.novell.com/show_bug.cgi?id=457037 In my case I couldn't mount LVM on root disk, after changing driver and getting the same message, it's because the initrd doesn't contain the stuff the kernel needs to mount / and get access to the /lib/modules directory and /etc for auto-mounting to work. 2008/12/21 Joe Morris <Joe_Morris@ntm.org>:
Well, i have managed to get enough info to know this is bug https://bugzilla.novell.com/show_bug.cgi?id=445490, which says it is resolved, but obviously not in the GM version of packages. Unfortunately, I cannot see what was needed to fix this, as I get an access denied when clicking on https://bugzilla.novell.com/show_bug.cgi?id=435778 at the end (where the fix was supposed to be). Is there an update of mkinitrd, or udev, or something to fix this?
Now, my workround to alter the boot modules, was to do following : Install into spare space with "brokenmodules=pata_pdc202xx_old" Copy the initrd, into where I needed. Copy out the LVM / stuff onto a normal disk area Make GRUB entries, and boot The issue as I understood it, was mkinitrd(8) is using udev (for a good reason) to figure out the modules that will be needed, but the fatal flaw is that it's using the information of the running system. So it's hard to make changes, and once you're hosed, you are totally screwed. You will have to bring Linux up, with an alternative root filesytem. I think, if you can get spare disk space up, then get the RAID devices working, making a specific initrd (may be the jumbo one used by installers) could do the trick. Alternatively you could turn off (if you have been wise and used mirroring 1 of the devices) and un-raid the other. But if you have been using RAID 5, then here's where you apply to join the BAARF party http://www.baarf.com/ :) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Joe Morris wrote:
Well, i have managed to get enough info to know this is bug https://bugzilla.novell.com/show_bug.cgi?id=445490, which says it is resolved, but obviously not in the GM version of packages. Unfortunately, I cannot see what was needed to fix this, as I get an access denied when clicking on https://bugzilla.novell.com/show_bug.cgi?id=435778 at the end (where the fix was supposed to be). Is there an update of mkinitrd, or udev, or something to fix this? I upgraded from 10.3 yesterday, but not being able to boot after it was finished was a real problem. I was finally able to boot installed system (hidden in the repair tools) to be able to boot again and was able to find the above bug report and found out with a few tweaks I could eventually boot up by hitting Ctrl-D to seemingly exit the bootup system. I have been running mdraid 1 since 8.0, and mdraid 1 roots since 9.1 IIRC, but this was the hardest to figure out, and appears to be a problem that is quite old ( http://lists.opensuse.org/opensuse-bugs/2008-08/msg07297.html ).
Joe, If you haven't stumbled on this one yet, it provides a few more pieces of the puzzle: https://bugzilla.novell.com/show_bug.cgi?id=445602 -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
David C. Rankin -
Joe Morris -
Rob OpenSuSE