On Fri, Oct 4, 2013 at 3:11 AM, Francesco Pietra <chiendar...@gmail.com> wrote: >> >> recall that it has been added with Wheezy. But let me put forward >> that it doesn't really matter. If you have RAID then you know you >> want grub on both disks. After installing simply run the grub install >> script against both disks manually and then you will be assured that >> it has been installed on both disks. > > I had problems with that methodology and was unable to detect my error. From > a thread on debian dated Mar 2, 2013: >> >> I carried out a reinstall of amd64 wheezy >> on the machine with new HD. md0 (boot, ext20, md1 (LVM, home, usr, >> etc). GRUB came installed on /dev/sda only >> >> Then the command >> >> grub-install /dev/sdb >> was reported by complete installation. No error, no warning. >> >> On rebooting, GRUB was no more found. Then entering in >> >> grub rescue > >> >> prefix/root/ were now wrong. > > Now I am in the same situation, two servers with mirroring raid, grub on > /dev/sda only. Identical data on both servers to cope with grub on one disk > only. Not smart from my side.
Does grub-probe output the correct grub device when you probe "/dev/mdX_of_boot", "/dev/md/X_of_boot", and "/boot" for the "drive" target? Does grub-probe output the correct fs uuid when you probe "/dev/mdX_of_boot", "/dev/md/X_of_boot", "/boot", and "/" for the "fs_uuid" target? I'm assuming that "/boot" is on mdraid. If it isn't, you'll need to replace "mdX" by "sdX". If "/" and "/boot" are on the same partition, you only need to check the fs_uuid of one of them (of course...). (In what way does the output of "ls" and "set" in "grub rescue" differ from what it's supposed to be?) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOdo=swveouvaxr5chufhkpznrhuba+ozfj29jwrihu2mzn...@mail.gmail.com
