Can anyone on this list shed some light on my question below? Thanks, Brett -------- Original Message -------- Subject: Clarify: GRUB setup on RAID1 Date: Tue, 19 Nov 2002 15:34:03 -0500 From: Brett Russ <icycle@charter.net> To: bug-grub@gnu.org I looked through all of the archives on this list as well as google searching for help. I want to make sure that GRUB supports installation on RAID1 (mirror) units. I have seen several methods to do this: Method 1) device (hd0) /dev/hde root (hd0,0) install /boot/grub/stage1 (hd0,0) /boot/grub/stage2 0x8000 (hd0,0)/boot/grub/menu.lst install /boot/grub/stage1 d (hd0) /boot/grub/stage2 0x8000 (hd0,0)/boot/grub/menu.lst device (hd0) /dev/hdg root (hd0,0) install /boot/grub/stage1 (hd0,0) /boot/grub/stage2 0x8000 (hd0,0)/boot/grub/menu.lst install /boot/grub/stage1 d (hd0) /boot/grub/stage2 0x8000 (hd0,0)/boot/grub/menu.lst ...and so on for each device--substituting each additional RAID1 member drive in the /dev/hdX line. Method 2) echo '(hd0) /dev/md0' > /boot/grub/device.map grub-install '(hd0)' ...and so on for each (hd#) that is part of the md. Method 3) root (hd0,0) setup (hd0) ...and so on for each hd# present in the RAID1. My question is whether the /dev/hdX syntax or /dev/md# or (hd#) syntax is correct and what the significance of the value 0x8000 for the Stage 2 load address. It certainly seems like method 3 is the cleanest. And, are any of these methods considered better than the others? Thanks, Brett _______________________________________________ Bug-grub mailing list Bug-grub@gnu.org http://mail.gnu.org/mailman/listinfo/bug-grub
icycle> I looked through all of the archives on this list as well as google icycle> searching for help. I want to make sure that GRUB supports installation icycle> on RAID1 (mirror) units. I have seen several methods to do this: Well, on a Red Hat system I have here, this works fine: #boot=/dev/sda default=0 timeout=10 #splashimage=(hd0,0)/grub/splash.xpm.gz title Red Hat Linux (2.4.9-34enterprise) root (hd0,0) kernel /vmlinuz-2.4.9-34enterprise ro root=/dev/md3 console=ttyS0,9600n8 initrd /initrd-2.4.9-34enterprise.img There are multiple RAID1 partitions on two disks, and grub is installed to /dev/sda. I don't believe grub is mirrored across disks, though. Since software RAID on Linux works partition-by-partition, and not on whole disks, I don't see how you could automatically mirror the MBR across disks. You could install grub to multiple MBR's, though, one for each disk. It wouldn't gain you anything unless your BIOS can boot from the other disks, though. -- Charles R. Anderson <cra@wpi.edu> / http://angus.ind.wpi.edu/~cra/ PGP Key ID: 49BB5886 Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886
Charles R. Anderson wrote:
There are multiple RAID1 partitions on two disks, and grub is installed to /dev/sda. I don't believe grub is mirrored across disks, though. Since software RAID on Linux works partition-by-partition, and not on whole disks, I don't see how you could automatically mirror the MBR across disks. You could install grub to multiple MBR's, though, one for each disk. It wouldn't gain you anything unless your BIOS can boot from the other disks, though.
To clarify my question, I wanted to make sure GRUB has the capability to access (for example) /boot/grub/grub.conf if /boot is not a separate partition but rather part of / which is a RAID1. As far as I know, RAID1 configured units are very similar to standard filesystems except in the superblock. It is difference between similar and the same that worries me. The goal is to get rid of the separate (non-RAID) /boot partition OR make the /boot partition into a RAID1. Either one would require GRUB to read from it successfully. thanks! Brett
On Wed, Nov 20, 2002 at 04:18:01PM -0500, Brett Russ wrote: icycle> The goal is to get rid of the separate (non-RAID) /boot partition OR icycle> make the /boot partition into a RAID1. Either one would require GRUB to icycle> read from it successfully. That works, yes. -- Charles R. Anderson <cra@wpi.edu> / http://angus.ind.wpi.edu/~cra/ PGP Key ID: 49BB5886 Fingerprint: EBA3 A106 7C93 FA07 8E15 3AC2 C367 A0F9 49BB 5886
Hi all, I've got a Baracuda 7200 RPM 80 Gbs Seagate. I've creating the partition using fdisk on Linux RedHat. Why does it always leave 7 Gbs that not partitioned ? So, Here I have 7 Gbs space useless :( Any idea to solve this ? Thanks,
participants (3)
-
Aramico -
Brett Russ -
Charles R. Anderson