Linux software raid.
Deprecated. As I understand, mdadm is what's used these days.
- 1 2006-09-03 - (version not recorded)
- 1.1 My setup
- 1.2 raidtools troubleshooting
2006-09-03 - (version not recorded) ∞
So I got
raidtools working again. It gave me flashbacks from my experimentation with it back in its alpha days, when I was using Slackware.
As it turns out, my backup script is adaptable to these drives, except that it's not smart enough to fsck the source drives.
With PCLinuxOS .92, I installed this with:
\apt-get install raidtools
Creating a RAID-1 array (mirroring):
First, set up
/dev/raidtab like so:
raiddev /dev/md0 raid-level 0 nr-raid-disks 2 persistent-superblock 1 chunk-size 4 device /dev/sdc1 raid-disk 0 device /dev/sdd1 raid-disk 1
mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sdc1 /dev/sdd1
My setup ∞
fstab with raidtools ∞
fstab without raidtools ∞
here for reference
raidtools troubleshooting ∞
mdadm: SET_ARRAY_INFO failed for /dev/md0: Invalid argument ∞
mdadm --create /dev/md2 --level=1 --raid-devices=2 /dev/sdc2 /dev/sdd2
mdadm: /dev/sdc2 appears to be part of a raid array: level=1 devices=2 ctime=Sun Sep 3 20:24:44 2006 mdadm: /dev/sdd2 appears to be part of a raid array: level=1 devices=2 ctime=Sun Sep 3 20:24:44 2006 Continue creating array? y mdadm: SET_ARRAY_INFO failed for /dev/md2: Invalid argument
- You've probably already run this command.
Maybe you just ran
mknodand you still need to
/dev/md0: Invalid argument ∞
/dev/md0: Invalid argument
Something which participates in
/dev/md0 might already be mounted in the traditional way. Unmount the device and then you can raidstart the md device.
Either the superblock or the partition table is likely to be corrupt! ∞
fsck 1.39 (29-May-2006) e2fsck 1.39 (29-May-2006) The filesystem size (according to the superblock) is 17101184 blocks The physical size of the device is 17101168 blocks Either the superblock or the partition table is likely to be corrupt! Abort<y>?
md device. Use it on the original source drives which combine into the