On Tue, Jun 9, 2015 at 5:54 PM, Alex Regan <[email protected]> wrote: > Hi, > >>>> Looks good (for each of four disks). >>>> >> >> Except that it did not show grub.cfg, but that is script problem; >> something to look at. > > > Okay, I've attached the grub.cfg as well. > >>>> Could you run grub2-install using additional parameters >>>> >>>> --debug --debug-image=all >>>> >>>> and send me output of grub2-install? debug-image will enable debugging >>>> for loaded grub image so you hopefully will get a lot of output; it >>>> may give some hint where it stops. >>> >>> >>> >>> Okay, I'm attaching it here. >>> >> >> Well, it still looks good but you have a bit dated grub2 (still with >> shell scripts). Did you try to boot it? > > > You mean after running it with the debug options you provided? Is that > really going to make a difference? Or should I see something else printed > during boot with these options? >
I hoped so (as I said --debug-image should enable quite verbose output on boot). > The system is at the colo about 25 miles away, and is currently booted using > a sysrescue CDROM with the "boot from existing system" option. Rebooting it > remotely would cause it to not be able to boot unless it works. > Oh. You said you reinstalled grub2 on all four disks so I assumed you have possibility to also test it. Unfortunately I do not really see anything wrong so far. The worst case would be your BIOS having issues with more that 2 disks; because this is the only explanation I see so far. GRUB needs to scan all disks to find MD RAID. _______________________________________________ Help-grub mailing list [email protected] https://lists.gnu.org/mailman/listinfo/help-grub
