Bugzilla – Bug 512251
System using LVM for root won't boot (to second stage)
Last modified: 2010-01-25 13:17:47 UTC
Created attachment 297542 [details] Screenshot -- booting (where is /dev/system/root?) I've run into this bug on my workstation and "fixed" that by not using LVM for root partition. This comes from my (successful) attempt for reproducing that issue in VirtualBox (with the very same result): /dev/sda /dev/sda1 --> swap /dev/sda2 --> /boot /dev/sda3 (Linux) LVM "system" root --> /
Created attachment 297547 [details] YaST and other logs
See, for instance, y2logmkinitrd -- you can find several errors and warnings there (such as /etc/modprobe.conf* not found).
Created attachment 297561 [details] YaST log from inital stage (the full log till the end)
I think I see similar bug few days ago, it is related to few missing binaries for LVM in initrd.
Any progress here?
*** This bug has been marked as a duplicate of bug 505670 ***
Not exactly a duplicate, see also comment #2, it that one fixed too?
I think this is a duplicate of that BUG, they haven't really shown the same logs but the symptoms are exactly the same and the cause is probably also the same? Also they have already assigned someone for that BUG.
And the cause is not in the Bootloader but kernel? The Bootloader bootstraps the system fine right?? It's later that something doesn't work.
Yes, it's a duplicate by the symptoms, you're right, however it needs additional fixing in Milan Vancura's code, not only in Xin Wei Hu's. I was talking with him about the other issues before and it's up to him to close it as a duplicate or not. Of course, it depends on the way how he fixes the code.
Then maybe we could add Milan Vancura's mail to the 505670 as an assigned person if it depends on him?
I don't think it really 'depends' on him but the system is actually broken on several places. What about leaving the decision on him?
You're right. Lets leave the decision to him ;)
Could you try to reproduce this BUG with M4? It would make life easier for Novell devs if they had one BUG less to take care of :)
The root-on-lvm issue was fixed in bug 505670, the modprobe.conf warnings were fixed in the meantime as well.