[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: RAID1 all bootable



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
Am 06.03.2013 22:40, schrieb Francesco Pietra:
> ... I must confess that I am confused, or my description was unclear. Hope not to bother you, I
summarize my procedure;
> Using the amd64 wheezy beta 4 installer, downloaded Feb 1, 2013, I got
the same situation as described above by "fdisk -l".
> That installation ended by asking "install grub on /dev/sda?".
> I accepted the proposal, whereby the terminal showed grub-install /dev/sda
> update grub
> At next boot, I run
> grub-install /dev/sdb
> which was accepted without any error or warning message.
> After "shutdown -h now", trying to boot, the system entered "grub
rescue". ...

Hello debian users,

I can verify the error Francesco reported. I have a Laptop, swapped the
optical drive for a ssd. To test debian 7. There is already windows and
debian 6 on sda with grub installed on sda. The installation was fine an
ended with grub installing two Linux boot entries (sda, sdb) and one
entry for windows on sda (very sad you can't choose the device grub
should install at this point). And it does work well.

As I thought by myself: It would be nice to use the ssd as an emergency
(usb) boot device for other computers, it was mbr formated and the root
partition was marked as bootable. So it should have grub installed to
it, too.

I thought "grub-install /dev/sdb" should be enough to make the sdb
bootable. Done that without an error message. But ...

I restarted the Laptop, telling the BIOS to boot from ssd (sdb) ... I
get the error: symbol not found: 'grub_divmod64_full'
And all I get is the 'grub rescue' prompt.

On the other hand ... I have a desktop running windows on sda (without
grub) and debian 7 & grub on sdb. To boot into Linux, I change the BIOS
boot device to sdb. I have choosen the sdb even before installing Linux.
I assume Linux isn't messed up by this. But on the Laptop (or Francescos
raid1 setup)  it gets confused, because the BIOS (or the lost raid1
drive) changed the numbering of the disks?

But what's the point of installing grub on more than one disk, if it
doesn't boot when one disk is missing?

Thanks
Ralf Saalmüller
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
 
iEYEARECAAYFAlE4R/QACgkQtKcsE7vsbMHjgwCfecEGdd0ZPo/A9UgXjJddyU6Q
fQgAn0k2NWUORXhNOzzrzIUR6DSvFHAT
=+DcM
-----END PGP SIGNATURE-----


Reply to: