OK, heres my situation, I got a 120 gigabyte hard drive for christmas, I decided to make a software raid 0 array with my other hard drives, a 40 and an 80. I figured out the best system for doing this. I would make my 40 and my 80 in one raid 0 array, then put this raid 0 array in another raid 0 array with my 120
This would offer me a preformance advantage over just sticking them all in one big raid 0 array because for the first for the first 160 gigabytes I would have 3 disks running, then the 40 runs out of space and until I have 240 gigabyes (fill the array) I have 2 disks.
If I went with all 3 in one raid 0 array then for the first 120 gigabytes I would have all 3, until 200 gigabytes I would have 2, and for the last 40 gigabytes (until 240 gigabytes) It wouldn't even be a raid 0 array as I would only have one disk (the 120) accepting data.
Now that I have justified why I am doing this (everyone I know who knows about linux thought I was nuts until I explained the advantages to them). I have a problem. I can get this setup hooked up fine on the live-cd (am using gentoo BTW). I installed the packages, everything. When I try to reboot I get that ... well heres the panic message.
Quote:
md: Autodetecting RAID arrays.
md: autorun ...
md: adding hdf3 ...
md: adding hdb3 ...
md: hda3 has different UUID to hdf3
md:created md0
md: bind<hdb3>
md: bind<hdf3>
md: running: <hdf4><hdb3>
md0: setting max_sectors to 64, segment boundryto 16383
raid0: looking at hdf3
raid0: comparing hdf3(78943296) with hdf3(78943296)
raid0: END
raid0: ==>UNIQUE
raid0: 1 zones
raid0: looking at hdb3
raid0: comparing hdb(38925376) with hdf3(78943296)
raid0: NOT EQUAL
raid0: comparing hdb(38925376) with hdf3(38925476)
raid0: END
raid0: UNIQUE
raid0: 2 zones
raid0: FINAL2 zones
raid0: zone 1
raid0: checking hdb3 .... nope
raid0: checking hdf3 ... contained as device 0
(78943296) is the smallet!.
raid0: zone->nb_zone is 2.
raid0 : Allocating 8 bytes for hash.
md: considering hda3 ...
md adding hda3 ...
md:created md1
md: bind<hda3>
md: running: <hda3>
md1: setting max_sectors to 64, segment boundry to 16383
raid0: looking at hda3
raid0: copmaring hda3(116125760) with hda3(116125760)
raid0: END
raid0: ==> UNIQUE
raid0: 1 zones
raid0: FINAL1 zones
raid0: toofew disks (1 of 2) - aborting!
md: pers->run() failed ...
md :do_md_run() returneed -22
md: md1 stopped
md: unbind<hda3>
md: export_rdev(hda3)
md: ... autorun DONE.
EXT3-fs: unable to read supeblock
EXT2-fs: unable to read supeblock
FAT: unable to read superblock
VFS: Cannot open root device "md1" or md1
Please append a correct "root=" boot option
Kernel Panic: VFS:Unable to mount root fs on md1
|
Wow. alot of typing. And now for my raidtab
Quote:
#The Bitch Raid (sub raid)
raiddev /dev/md0
raid-level 0
nr-raid-disks 2
chunk-size 32
persistent-superblock 1
device /dev/hdb3
raid-disk 0
device /dev/hdf3
raid-disk 1
#The Master Raid
raiddev /dev/md1
raid-level 0
nr-raid-disks 2
chunk-size 32
persistent-superblock 1
device /dev/md0
raid-disk 0
device /dev/hda3
raid-disk 1
#The Boot Raid (Raid 1)
raiddev /dev/md2
raid-level 1
nr-raid-disks 3
chunk-size 32
persistent-superblock 1
device /dev/hda1
raid-disk 0
device /dev/hdb1
raid-disk 1
device /dev/hdf1
raid-disk 2
|
I have also tried it with the /dev/md/x replacing /dev/mdx, the arrangment of my hard drives as follows is that hda3 is the partition on my 120 gigabyte hard drive, and hdb3 and hdf are on my 40 and 80 gigabyte hard drives respecivly and combine to make /dev/md0
This arrangment works great on the live-cd however I can't get it to work as my rootfs. The boot partition is a raid 1 array over all 3 drives.
