-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Grub and LVM issues #337
Comments
The question is did your system boot up properly? |
Yes only if the first boot order is on sda. |
Hum, seems to me we might have hit one of the problems with grub itself - see http://lists.gnu.org/archive/html/bug-grub/2009-11/msg00024.html @dagwieers in script 21_install_grub.sh you've added the check:
I wonder shouldn't we have foreseen an exit out of the do-loop when grub was successful? |
I don't understand the aim of the do-loop. |
I don't know the exact reason anymore, but @dagwieers had a good explanation for why we should do it on all disks. I think it was multipath related. Is it causing problems? |
With any kind of MPIO or SW RAID you should anticipate booting off any of BTW, if you don't test that "feature" then it probably won't work (sad On 27 November 2013 14:55, Jeroen Hoekx notifications@github.com wrote:
|
Yes Schlomo, that's indeed the explanation. We had to recover machines with a software RAID over two HW RAID controllers. In order to let them boot reliably we had to add the loop. |
IMHO, any disk with a copy of the OS on it should be bootable. If we don't On 27 November 2013 15:15, Jeroen Hoekx notifications@github.com wrote:
|
However, the question here is: did every disk contain a boot partition? Apparently not, so it might be that we should check this first before applying blindly grub on it - as I said before the exit code of the old grub is bad (or always 0 even if it fails). |
Is there something that fails when you add multiple MBRs? If not, the comments in finalize/Linux-i386/21_install_grub.sh seem to indicate we encountered a case where we needed to boot from another disk and that it was fixed by adding it to all disks. As long as that's not causing problems, I would continue to do so. |
Do we all agree it is the expected behavior? As long as the system boots up properly it is not considered as a problem. |
It's not causing problems for the moment. |
guess we better close this issue? |
Hi,
On RHEL 6.4 with lvm on three hard drive (sda, sdb, sdc and boot partition on sda1) :
The ouput of lsblk :
Rear install grub on sda, sdb, and sdc.
1/
2/
3/
Here is the full log of rear recover -D : https://gist.github.com/Florent38/7640386
The text was updated successfully, but these errors were encountered: