Differences between version 3 and predecessor to the previous major change of SoftwareRaid.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 3 | Last edited on Saturday, January 10, 2004 12:28:58 pm | by JasonCater | Revert |
| Older page: | version 1 | Last edited on Monday, August 11, 2003 6:54:56 pm | by MattBrown | Revert |
@@ -13,9 +13,9 @@
!!! How To Setup a machine using Software RAID-1
Allthough I setup this machine up with Debian I am pretty sure that most of the steps listed below will be distribution independent. We will start from the basic hardware that doesn't do anything useful and progress until we have a machine that boots up into a full working Debian install off the raid array.
-The machine that I used for this configuration has a Intel S845WD1-E Motherboard with two on-board IDE channels plus an extra two channels controlled by a Promise PDC20267 RAID chipset (commonly known as a Promise FastTrak100). Unfortunately Promise is not clever enough to release open source drivers for the RAID portion of this chipset so it is only useable as an IDE controller under linux. The rest of the machine is configured as follows. There is one 40GB Seagate IDE Disk on each of the FastTrak's channels. We want to use these two disks to create a RAID-1 array for redunant
storage.
+The machine that I used for this configuration has a Intel S845WD1-E Motherboard with two on-board IDE channels plus an extra two channels controlled by a Promise PDC20267 RAID chipset (commonly known as a Promise FastTrak100). Unfortunately Promise is not clever enough to release open source drivers for the RAID portion of this chipset so it is only useable as an IDE controller under linux. The rest of the machine is configured as follows. There is one 40GB Seagate IDE Disk on each of the FastTrak's channels. We want to use these two disks to create a RAID-1 array for redundant
storage.
Assuming that the physical installation has been completed correctly with a single disk on each IDE channel, 80pin IDE cables, etc. The next problem we face is that the Debian installer (an all other distributions installers?) cannot install directly onto a raid array as the standard kernels do not have software raid support included. To get around this problem I used the first method described in [HowToSoftwareRAIDHOWTO] of placing a 3rd disk on the first on-board IDE channel and installing a Basic Debian install on to that.
!Install Debian onto a different disk to the ones in your RAID array (On the first on-board IDE controller)
@@ -120,11 +120,10 @@
boot=/dev/hde
root=/dev/md0
This tells lilo to install the boot record in the MBR of /dev/hde (the first disk in the RAID array) and that the root filesystem will be located at /dev/md0 (the first RAID array)
-To install this boot block you need to
- chroot /mnt
-
lilo -v
+To install this boot block you need to run
+ #
chroot /mnt lilo -v
! Reboot
While you are turning the machine off to reboot remove the extra drive that you used for the initial install and make sure that you BIOS is correctly configured to boot of the Promise Controller.
@@ -163,4 +162,35 @@
md4 : active raid1 hdc8[[1] hda8[[0]
25872576 blocks [[2/2] [[UU]
unused devices: <none>
+
+! Debian initrd kernel support
+You can also do root-on-RAID1 using a recent stock debian kernel without compiling your own custom kernel. To do so, use mkinitrd to create a custom initrd image with the necessary RAID1 modules.
+
+This step should happen during the __Make the system bootable__ section above, before running "chroot /mnt lilo -v".
+
+Modify "/etc/mkinitrd/modules" to contain the following lines:
+ raid1
+ md
+ ext2
+ ext3
+ ide-disk
+ ide-probe-mod
+ ide-mod
+
+This will tell mkinitrd to include those kernel modules at bootup time. Also, add the following to "/etc/mkinitrd/files":
+ /dev/md0
+
+Change the line in "/etc/mkinitrd/mkinitrd.conf" that reads
+ ROOT=probe
+to read ROOT=/dev/md0
+
+Now, create a new initrd image.
+ # mkinitrd -o /mnt/initrd-raid1.img
+
+You now have an initrd image that supports your RAID setup. You will need to edit "/mnt/etc/lilo.conf" and include the following in each stanza you intend to boot into.
+ initrd=/initrd-raid1.img
+
+Finally, install the new lilo configuration
+ # chroot /mnt lilo -v
+and continue with the rest of the instructions.
