On Wed, Sep 7, 2011 at 11:38 PM, Devin Reade <gdr@gno.org> wrote:

--On Wednesday, September 07, 2011 08:22:47 PM +0300 Bünyamin İzzet

<bunyamin.izzet@gmail.com> wrote:

- made sure we have boot blocks on both disks, based on information
at http://grub.enbug.org/MirroringRAID
modified /boot/grub/device.map from:

(hd0) /dev/sda
(hd1) /dev/sdb

to:
(hd0) /dev/sda
(hd0) /dev/sdb

I have changed the device.map as you said

and then:
# grub
grub> device (hd0) /dev/sdb
grub> root (hd0,0)
grub> setup (hd0)
grub> quit

And, it is done too.

It still does not boot. I could not see the error message, because it is a dedicated server and I am not sitting at the monitor of the server. So I type the lines in grub.conf manually to see the error (I'm not sure if it is the right thing to see the error).

# grub
Probing devices to guess BIOS drives. This may take a long time.

    GNU GRUB version 0.97 (640K lower / 3072K upper memory)

[ Minimal BASH-like line editing is supported. For the first word, TAB
   lists possible command completions. Anywhere else TAB lists the possible
   completions of a device/filename.]
grub> root (hd1,0)
root (hd1,0)
Filesystem type is ext2fs, partition type 0xfd
grub> kernel /vmlinuz-2.6.18-238.19.1.el5 ro root=/dev/md1 vga=0x317
kernel /vmlinuz-2.6.18-238.19.1.el5 ro root=/dev/md1 vga=0x317
   [Linux-bzImage, setup=0x1e00, size=0x1fe01c]
grub> initrd /initrd-2.6.18-238.19.1.el5.img
initrd /initrd-2.6.18-238.19.1.el5.img

Error 28: Selected item cannot fit into memory
grub> quit
quit

If it is not the right thing to see the error message at boot time, is there any chance to log grub errors, boot errors?

Thanks,
Bunyamin.