Correct way to create multiple RAID volumes with hot-spare?
Hi,
I have a set of 11 500 GB drives. Currently each has two 250 GB partitions (/dev/sd?1 and /dev/sd?2). I have two RAID6 arrays set up, each with 10 drives and then I wanted the 11th drive to be a hot-spare.
When I originally created the array I used mdadm and only specified
the use of 10 drives since the 11th one wasn't even a thought at the time (I didn't think I could get an 11th drive in the case). Now I can manually add in the 11th drive partitions into each of the arrays and they show up as a spares but on reboot they aren't part of the set anymore. I have added them into /etc/mdadm.conf and the partition type is set to be Software RAID (fd).
Maybe I shouldn't be splitting the drives up into partitions. I did this due to issues with volumes greater than 2TB. Maybe this isn't an issue anymore and I should just rebuild the array from scratch with single partitions. Or should there even be partitions? Should I just use /dev/sd[abcdefghijk] ?
On a side note, maybe for another thread, the arrays work great until a reboot (using 'shutdown' or 'reboot' and they seem to be shutting down the md system correctly). Sometimes one or even two (yikes!) partitions in each array go offline and I have to mdadm /dev/md0 -a /dev/sdx1 it back in. Do others experience this regularly with RAID6? Is RAID6 not ready for prime time?
As for system information, it is (was) a Dual Opteron with CentOS 4.3 (now I'm putting FC5 on it as I write) with a 3Ware 8506-12 SATA RAID card that I am using in JBOD mode so I could do software RAID6.
Thanks for your help.
Steve
Signature · 4 lines
______________________________________________________________________ Steve Cousins, Ocean Modeling Group Email: [email protected] Marine Sciences, 452 Aubert Hall http://rocky.umeoce.maine.edu Univ. of Maine, Orono, ME 04469 Phone: (207) 581-4302
Quoted 6 lines · Steve Cousins
Hi,
I have a set of 11 500 GB drives. Currently each has two 250 GB partitions (/dev/sd?1 and /dev/sd?2). I have two RAID6 arrays set up, each with 10 drives and then I wanted the 11th drive to be a hot-spare. When I originally created the array I used mdadm and only specified the use of 10 drives since the 11th one wasn't even a thought at the time (I didn't think I could get an 11th drive in the case). Now I can manually add in the 11th drive partitions into each of the arrays and they show up as a spares but on reboot they aren't part of the set anymore. I have added them into
/etc/mdadm.confand the partition type is set to be Software RAID (fd).Maybe I shouldn't be splitting the drives up into partitions. I did this due to issues with volumes greater than 2TB. Maybe this isn't an issue anymore and I should just rebuild the array from scratch with single partitions. Or should there even be partitions? Should I just use /dev/sd[abcdefghijk] ?
Quoted 19 lines
On a side note, maybe for another thread, the arrays work great until a reboot (using 'shutdown' or 'reboot' and they seem to be shutting down the md system correctly). Sometimes one or even two (yikes!) partitions in each array go offline and I have to mdadm
/dev/md0-a/dev/sdx1it back in. Do others experience this regularly with RAID6? Is RAID6 not ready for prime time?As for system information, it is (was) a Dual Opteron with CentOS 4.3 (now I'm putting FC5 on it as I write) with a 3Ware 8506-12 SATA RAID card that I am using in JBOD mode so I could do software RAID6.
Thanks for your help.
Steve
Signature · 10 lines
______________________________________________________________________ Steve Cousins, Ocean Modeling Group Email: [email protected] Marine Sciences, 452 Aubert Hall http://rocky.umeoce.maine.edu Univ. of Maine, Orono, ME 04469 Phone: (207) 581-4302 - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
If you are using SW RAID, there is no 2TB limit.
Justin.
On Wed, 23 Aug 2006 at 6:34am, Justin Piszcz wrote
Quoted 6 lines · Steve Cousins
Quoted 3 lines
As for system information, it is (was) a Dual Opteron with CentOS 4.3 (now I'm putting FC5 on it as I write) with a 3Ware 8506-12 SATA RAID card that I am using in JBOD mode so I could do software RAID6.
If you are using SW RAID, there is no 2TB limit.
Ditto for more recent HW RAIDs. *However*, there are other considerations when dealing with >2TiB devices. E.g. you can't boot from them.
Signature · 3 lines
Joshua Baker-LePain Department of Biomedical Engineering Duke University
Quoted 9 lines · Joshua Baker-LePain
On Wed, 23 Aug 2006 at 6:34am, Justin Piszcz wrote
Quoted 7 lines · Steve Cousins
Quoted 5 lines
As for system information, it is (was) a Dual Opteron with CentOS 4.3 (now I'm putting FC5 on it as I write) with a 3Ware 8506-12 SATA RAID card that I am using in JBOD mode so I could do software RAID6.
Quoted 5 lines
Quoted 1 line
If you are using SW RAID, there is no 2TB limit.
Ditto for more recent HW RAIDs. *However*, there are other considerations when dealing with >2TiB devices. E.g. you can't boot from them.
You are both correct. When I said "due to issues with volumes greater than 2TB" I should have indicated that they were more to do with my issues and/or our environment. I probably wasn't persistent enough with it. I now have a DAS box with >2TB volumes and it is working fine so I should probably start over using no partions and see how it goes.
Thanks,
Steve
Quoted 12 lines · On Tuesday August 22, [email protected] wrote:
Hi,
I have a set of 11 500 GB drives. Currently each has two 250 GB partitions (/dev/sd?1 and /dev/sd?2). I have two RAID6 arrays set up, each with 10 drives and then I wanted the 11th drive to be a hot-spare.
When I originally created the array I used mdadm and only specified
the use of 10 drives since the 11th one wasn't even a thought at the time (I didn't think I could get an 11th drive in the case). Now I can manually add in the 11th drive partitions into each of the arrays and they show up as a spares but on reboot they aren't part of the set anymore. I have added them into/etc/mdadm.confand the partition type is set to be Software RAID (fd).
Can you show us exactly what /etc/mdadm.conf contains? And what kernel messages do you get when it assembled the array but leaves off the spare?
Quoted 7 lines
Maybe I shouldn't be splitting the drives up into partitions. I did this due to issues with volumes greater than 2TB. Maybe this isn't an issue anymore and I should just rebuild the array from scratch with single partitions. Or should there even be partitions? Should I just use /dev/sd[abcdefghijk] ?
I tend to just use whole drives, but your set up should work fine. md/raid isn't limited to 2TB, but some filesystems might have size issues (though i think even ext2 gots to at least 8 TB these days).
Quoted 6 lines
On a side note, maybe for another thread, the arrays work great until a reboot (using 'shutdown' or 'reboot' and they seem to be shutting down the md system correctly). Sometimes one or even two (yikes!) partitions in each array go offline and I have to mdadm
/dev/md0-a/dev/sdx1it back in. Do others experience this regularly with RAID6? Is RAID6 not ready for prime time?
This doesn't sound like a raid issues. Do you have kernel logs of what happens when the array is reassembled and some drive(s) are missing?
NeilBrown
Quoted 14 lines · Neil Brown
Quoted 12 lines · On Tuesday August 22, [email protected] wrote:
Hi,
I have a set of 11 500 GB drives. Currently each has two 250 GB partitions (/dev/sd?1 and /dev/sd?2). I have two RAID6 arrays set up, each with 10 drives and then I wanted the 11th drive to be a hot-spare.
When I originally created the array I used mdadm and only specified
the use of 10 drives since the 11th one wasn't even a thought at the time (I didn't think I could get an 11th drive in the case). Now I can manually add in the 11th drive partitions into each of the arrays and they show up as a spares but on reboot they aren't part of the set anymore. I have added them into/etc/mdadm.confand the partition type is set to be Software RAID (fd).
Quoted 4 lines
Can you show us exactly what
/etc/mdadm.confcontains? And what kernel messages do you get when it assembled the array but leaves off the spare?
Here is mdadm.conf:
DEVICE /dev/sd[abcdefghijk]*
ARRAY /dev/md0 level=raid6 num-devices=10 spares=1
UUID=70c02805:0a324ae8:679fc224:3112a95f devices=/dev/sda1,/dev/sdb1,/dev/sdc1,/dev/sdd1,/dev/sde1,/dev/sdf1,/dev/sdg1,/dev/sdh1,/dev/sdi1,/dev/sdj1,/dev/sdk1
ARRAY /dev/md1 level=raid6 num-devices=10 spares=1
UUID=87692745:1a99d67a:462b8426:4e181b2e devices=/dev/sda2,/dev/sdb2,/dev/sdc2,/dev/sdd2,/dev/sde2,/dev/sdf2,/dev/sdg2,/dev/sdh2,/dev/sdi2,/dev/sdj2,/dev/sdk2
Below is the info from /var/log/messages. This is a listing of when two partitions from each array were left off. It also is an example of when it doesn't list the spare. If you want me a newer listing from when the array builds correctly but doesn't have a spare let me know.
What I hadn't really looked at before is the lines that say:
sdk1 has different UUID to sdk2
etc. Of course it doesn't. Maybe this isn't part of the problem
Aug 21 18:56:09 juno mdmonitor: mdadm shutdown succeeded Aug 21 19:01:03 juno mdmonitor: mdadm startup succeeded Aug 21 19:01:04 juno mdmonitor: mdadm succeeded Aug 21 19:01:06 juno kernel: md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 Aug 21 19:01:06 juno kernel: md: bitmap version 4.39 Aug 21 19:01:06 juno kernel: md: raid6 personality registered for level 6 Aug 21 19:01:06 juno kernel: md: Autodetecting RAID arrays. Aug 21 19:01:06 juno kernel: md: autorun ... Aug 21 19:01:06 juno kernel: md: considering sdk2 ... Aug 21 19:01:06 juno kernel: md: adding sdk2 ... Aug 21 19:01:06 juno kernel: md: sdk1 has different UUID to sdk2 Aug 21 19:01:06 juno kernel: md: adding sdj2 ... Aug 21 19:01:06 juno kernel: md: sdj1 has different UUID to sdk2 Aug 21 19:01:06 juno kernel: md: adding sdi2 ... Aug 21 19:01:06 juno kernel: md: sdi1 has different UUID to sdk2 Aug 21 19:01:06 juno kernel: md: adding sdh2 ... Aug 21 19:01:06 juno kernel: md: sdh1 has different UUID to sdk2 Aug 21 19:01:06 juno kernel: md: adding sdg2 ... Aug 21 19:01:06 juno kernel: md: sdg1 has different UUID to sdk2 Aug 21 19:01:06 juno kernel: md: adding sdf2 ... Aug 21 19:01:06 juno kernel: md: sdf1 has different UUID to sdk2 Aug 21 19:01:06 juno kernel: md: adding sde2 ... Aug 21 19:01:06 juno kernel: md: sde1 has different UUID to sdk2 Aug 21 19:01:07 juno kernel: md: adding sdd2 ... Aug 21 19:01:07 juno kernel: md: sdd1 has different UUID to sdk2 Aug 21 19:01:07 juno kernel: md: adding sdc2 ... Aug 21 19:01:07 juno kernel: md: sdc1 has different UUID to sdk2 Aug 21 19:01:07 juno kernel: md: adding sdb2 ... Aug 21 19:01:07 juno kernel: md: sdb1 has different UUID to sdk2 Aug 21 19:01:07 juno kernel: md: adding sda2 ... Aug 21 19:01:07 juno kernel: md: sda1 has different UUID to sdk2 Aug 21 19:01:07 juno kernel: md: created md1 Aug 21 19:01:07 juno kernel: md: bind<sda2> Aug 21 19:01:07 juno kernel: md: bind<sdb2> Aug 21 19:01:07 juno kernel: md: bind<sdc2> Aug 21 19:01:07 juno kernel: md: bind<sdd2> Aug 21 19:01:07 juno kernel: md: bind<sde2> Aug 21 19:01:07 juno kernel: md: bind<sdf2> Aug 21 19:01:07 juno kernel: md: bind<sdg2> Aug 21 19:01:07 juno kernel: md: bind<sdh2> Aug 21 19:01:07 juno kernel: md: bind<sdi2> Aug 21 19:01:07 juno kernel: md: bind<sdj2> Aug 21 19:01:07 juno kernel: md: export_rdev(sdk2) Aug 21 19:01:07 juno kernel: md: running: <sdj2><sdi2><sdh2><sdg2><sdf2><sde2><sdd2><sdc2><sdb2><sda2> Aug 21 19:01:07 juno kernel: md: kicking non-fresh sdi2 from array! Aug 21 19:01:07 juno kernel: md: unbind<sdi2> Aug 21 19:01:07 juno kernel: md: export_rdev(sdi2) Aug 21 19:01:07 juno kernel: md: kicking non-fresh sdb2 from array! Aug 21 19:01:07 juno kernel: md: unbind<sdb2> Aug 21 19:01:07 juno kernel: md: export_rdev(sdb2) Aug 21 19:01:07 juno kernel: raid6: allocated 10568kB for md1 Aug 21 19:01:07 juno kernel: raid6: raid level 6 set md1 active with 8 out of 10 devices, algorithm 2 Aug 21 19:01:07 juno kernel: md: considering sdk1 ... Aug 21 19:01:07 juno kernel: md: adding sdk1 ... Aug 21 19:01:07 juno kernel: md: adding sdj1 ... Aug 21 19:01:07 juno kernel: md: adding sdi1 ... Aug 21 19:01:07 juno kernel: md: adding sdh1 ... Aug 21 19:01:07 juno kernel: md: adding sdg1 ... Aug 21 19:01:07 juno kernel: md: adding sdf1 ... Aug 21 19:01:07 juno kernel: md: adding sde1 ... Aug 21 19:01:07 juno kernel: md: adding sdd1 ... Aug 21 19:01:07 juno kernel: md: adding sdc1 ... Aug 21 19:01:07 juno kernel: md: adding sdb1 ... Aug 21 19:01:07 juno kernel: md: adding sda1 ... Aug 21 19:01:07 juno kernel: md: created md0 Aug 21 19:01:07 juno kernel: md: bind<sda1> Aug 21 19:01:07 juno kernel: md: bind<sdb1> Aug 21 19:01:07 juno kernel: md: bind<sdc1> Aug 21 19:01:07 juno kernel: md: bind<sdd1> Aug 21 19:01:07 juno kernel: md: bind<sde1> Aug 21 19:01:07 juno kernel: md: bind<sdf1> Aug 21 19:01:07 juno kernel: md: bind<sdg1> Aug 21 19:01:07 juno kernel: md: bind<sdh1> Aug 21 19:01:07 juno kernel: md: bind<sdi1> Aug 21 19:01:07 juno kernel: md: bind<sdj1> Aug 21 19:01:07 juno kernel: md: export_rdev(sdk1) Aug 21 19:01:07 juno kernel: md: running: <sdj1><sdi1><sdh1><sdg1><sdf1><sde1><sdd1><sdc1><sdb1><sda1> Aug 21 19:01:07 juno kernel: md: kicking non-fresh sdi1 from array! Aug 21 19:01:07 juno kernel: md: unbind<sdi1> Aug 21 19:01:07 juno kernel: md: export_rdev(sdi1) Aug 21 19:01:07 juno kernel: md: kicking non-fresh sdb1 from array! Aug 21 19:01:07 juno kernel: md: unbind<sdb1> Aug 21 19:01:07 juno kernel: md: export_rdev(sdb1) Aug 21 19:01:08 juno kernel: raid6: allocated 10568kB for md0 Aug 21 19:01:08 juno kernel: raid6: raid level 6 set md0 active with 8 out of 10 devices, algorithm 2 Aug 21 19:01:08 juno kernel: md: ... autorun DONE. Aug 21 19:01:08 juno kernel: md: Autodetecting RAID arrays. Aug 21 19:01:08 juno kernel: md: autorun ... Aug 21 19:01:08 juno kernel: md: considering sdb1 ... Aug 21 19:01:08 juno kernel: md: adding sdb1 ... Aug 21 19:01:08 juno kernel: md: adding sdi1 ... Aug 21 19:01:08 juno kernel: md: adding sdk1 ... Aug 21 19:01:08 juno kernel: md: sdb2 has different UUID to sdb1 Aug 21 19:01:08 juno kernel: md: sdi2 has different UUID to sdb1 Aug 21 19:01:09 juno kernel: md: sdk2 has different UUID to sdb1 Aug 21 19:01:09 juno kernel: md: md0 already running, cannot run sdb1 Aug 21 19:01:09 juno kernel: md: export_rdev(sdk1) Aug 21 19:01:09 juno kernel: md: export_rdev(sdi1) Aug 21 19:01:09 juno kernel: md: export_rdev(sdb1) Aug 21 19:01:09 juno kernel: md: considering sdb2 ... Aug 21 19:01:09 juno kernel: md: adding sdb2 ... Aug 21 19:01:09 juno kernel: md: adding sdi2 ... Aug 21 19:01:10 juno kernel: md: adding sdk2 ... Aug 21 19:01:10 juno kernel: md: md1 already running, cannot run sdb2 Aug 21 19:01:10 juno kernel: md: export_rdev(sdk2) Aug 21 19:01:10 juno kernel: md: export_rdev(sdi2) Aug 21 19:01:10 juno kernel: md: export_rdev(sdb2) Aug 21 19:01:10 juno kernel: md: ... autorun DONE. Aug 21 19:01:11 juno kernel: md: Autodetecting RAID arrays. Aug 21 19:01:11 juno kernel: md: autorun ... Aug 21 19:01:11 juno kernel: md: considering sdb2 ... Aug 21 19:01:11 juno kernel: md: adding sdb2 ... Aug 21 19:01:11 juno kernel: md: adding sdi2 ... Aug 21 19:01:11 juno kernel: md: adding sdk2 ... Aug 21 19:01:11 juno kernel: md: sdb1 has different UUID to sdb2 Aug 21 19:01:11 juno kernel: md: sdi1 has different UUID to sdb2 Aug 21 19:01:12 juno kernel: md: sdk1 has different UUID to sdb2 Aug 21 19:01:12 juno kernel: md: md1 already running, cannot run sdb2 Aug 21 19:01:12 juno kernel: md: export_rdev(sdk2) Aug 21 19:01:12 juno kernel: md: export_rdev(sdi2) Aug 21 19:01:12 juno kernel: md: export_rdev(sdb2) Aug 21 19:01:12 juno kernel: md: considering sdb1 ... Aug 21 19:01:12 juno kernel: md: adding sdb1 ... Aug 21 19:01:12 juno kernel: md: adding sdi1 ... Aug 21 19:01:12 juno kernel: md: adding sdk1 ... Aug 21 19:01:12 juno kernel: md: md0 already running, cannot run sdb1 Aug 21 19:01:12 juno kernel: md: export_rdev(sdk1) Aug 21 19:01:12 juno kernel: md: export_rdev(sdi1) Aug 21 19:01:12 juno kernel: md: export_rdev(sdb1) Aug 21 19:01:12 juno kernel: md: ... autorun DONE. Aug 21 19:01:13 juno kernel: XFS mounting filesystem md0 Aug 21 19:01:13 juno kernel: XFS mounting filesystem md1 Aug 21 19:03:08 juno kernel: md: bind<sdb1> Aug 21 19:03:08 juno kernel: md: syncing RAID array md0 Aug 21 19:03:08 juno kernel: md: minimum _guaranteed_ reconstruction speed: 20000 KB/sec/disc. Aug 21 19:03:08 juno kernel: md: using maximum available idle IO bandwidth (but not more than 200000 KB/sec) for reconstruction. Aug 21 19:03:08 juno kernel: md: using 128k window, over a total of 244141952 blocks. Aug 21 19:03:15 juno kernel: md: bind<sdb2> Aug 21 19:03:15 juno kernel: md: delaying resync of md1 until md0 has finished resync (they share one or more physical units) Aug 21 19:03:42 juno kernel: md: bind<sdi1> Aug 21 19:03:51 juno kernel: md: bind<sdi2>
FWIW, I have installed FC5 and in the two or three reboots so far I haven't seen any of this weirdness.
Quoted 9 lines
Quoted 8 lines
Maybe I shouldn't be splitting the drives up into partitions. I did this due to issues with volumes greater than 2TB. Maybe this isn't an issue anymore and I should just rebuild the array from scratch with single partitions. Or should there even be partitions? Should I just use /dev/sd[abcdefghijk] ?
Quoted 3 lines
I tend to just use whole drives, but your set up should work fine. md/raid isn't limited to 2TB, but some filesystems might have size issues (though i think even ext2 gots to at least 8 TB these days).
I'm using XFS. I'll probably give this a try with a 4TB volume.
Quoted 11 lines
Quoted 7 lines
On a side note, maybe for another thread, the arrays work great until a reboot (using 'shutdown' or 'reboot' and they seem to be shutting down the md system correctly). Sometimes one or even two (yikes!) partitions in each array go offline and I have to mdadm
/dev/md0-a/dev/sdx1it back in. Do others experience this regularly with RAID6? Is RAID6 not ready for prime time?This doesn't sound like a raid issues. Do you have kernel logs of what happens when the array is reassembled and some drive(s) are missing?
See above.
If you'd rather not spend time on this that is fine. Since the OS is changed and I haven't seen this issue yet with the new OS it is probably moot. Not having the spare set up each time though is still an issue.
Thanks,
Steve
Quoted 9 lines · Neil Brown
Quoted 3 lines · On Tuesday August 22, [email protected] wrote:
Maybe I shouldn't be splitting the drives up into partitions. I did this due to issues with volumes greater than 2TB. Maybe this isn't an issue anymore and I should just rebuild the array from scratch with single partitions. Or should there even be partitions? Should I just use /dev/sd[abcdefghijk] ?
I tend to just use whole drives, but your set up should work fine. md/raid isn't limited to 2TB, but some filesystems might have size issues (though i think even ext2 gots to at least 8 TB these days).
The recent "Messed up creating new array..." thread has someone who started by using the whole drives but she now wants to use partitions because the array is not starting automatically on boot (I think that was the symptom). I'm guessing this is because there is no partigion ID of "fd" since there isn't even a partition.
I'm on the verge of re-doing this array with 11 full drives (/dev/sd? as opposed to /dev/sd?1 and /dev/sd?2). Will I have the same problems with booting? I like the idea of not having to partition the drives but not if it is going to cause hassles. I realize that there could be a potential problem if I need to replace a drive with a slightly different model that is slightly smaller.
Thanks,
Steve
Signature · 4 lines
______________________________________________________________________ Steve Cousins, Ocean Modeling Group Email: [email protected] Marine Sciences, 452 Aubert Hall http://rocky.umeoce.maine.edu Univ. of Maine, Orono, ME 04469 Phone: (207) 581-4302
Steve,
Quoted 6 lines
The recent "Messed up creating new array..." thread has someone who started by using the whole drives but she now wants to use partitions because the array is not starting automatically on boot (I think that was the symptom). I'm guessing this is because there is no partigion ID of "fd" since there isn't even a partition.
Yes, that's right.
Quoted 7 lines
I'm on the verge of re-doing this array with 11 full drives (
/dev/sd? as opposed to /dev/sd?1 and /dev/sd?2). Will I have the same problems with booting? I like the idea of not having to partition the drives but not if it is going to cause hassles. I realize that there could be a potential problem if I need to replace a drive with a slightly different model that is slightly smaller.
That's the reason I ended up re-creating the array from backup, using partitions.
You _can_ use raw disks, but it's not as easy. I worked out that I was originally having problems because my mdadm.conf file had the right drives (/dev/sdc ...) in the ARRAY line, but didn't have the same drives listed in the DEVICES line.
I would suggest you do use partitions.
Ruth
Quoted 7 lines · Ruth Ivimey-Cook
Steve,
Quoted 1 line
The recent "Messed up creating new array..." thread has someone who started by using the whole drives but she now wants to use partitions because the array is not starting automatically on boot (I think that was the symptom). I'm guessing this is because there is no partigion ID of "fd" since there isn't even a partition.
Yes, that's right.
Thanks Ruth.
Neil (or others), what is the recommended way to have the array start up if you use whole drives instead of partitions? Do you put mdadm -A etc. in rc.local?
Thanks,
Steve
Quoted 4 lines · On Thursday September 14, [email protected] wrote:
Neil (or others), what is the recommended way to have the array start up if you use whole drives instead of partitions? Do you put mdadm -A etc. in rc.local?
I would use
mdadm -As
is rc.local (or /etc/init.d/mdadm or whatever) whether using partitions or not, but maybe that is just me.
This combined with correct information in mdadm.conf gets it reliably right every time.
NeilBrown
Quoted 10 lines · Steve Cousins
Quoted 6 lines · Ruth Ivimey-Cook
Steve,
Quoted 1 line
The recent "Messed up creating new array..." thread has someone who started by using the whole drives but she now wants to use partitions because the array is not starting automatically on boot (I think that was the symptom). I'm guessing this is because there is no partigion ID of "fd" since there isn't even a partition.
Quoted 7 lines
Quoted 1 line
Yes, that's right.
Thanks Ruth.
Neil (or others), what is the recommended way to have the array start up if you use whole drives instead of partitions? Do you put mdadm -A etc. in rc.local?
I think you want it earlier than that, unless you want to do the whole mounting process by hand. It's distribution dependent, but doing it early allows the array to be handled like any other block device.
Signature · 3 lines
bill davidsen <[email protected]> CTO TMR Associates, Inc Doing interesting things with small computers since 1979
Quoted 6 lines · Steve Cousins
The recent "Messed up creating new array..." thread has someone who started by using the whole drives but she now wants to use partitions because the array is not starting automatically on boot (I think that was the symptom). I'm guessing this is because there is no partigion ID of "fd" since there isn't even a partition.
Quoted 6 lines
I'm on the verge of re-doing this array with 11 full drives (
/dev/sd? as opposed to /dev/sd?1 and /dev/sd?2). Will I have the same problems with booting? I like the idea of not having to partition the drives but not if it is going to cause hassles. I realize that there could be a potential problem if I need to replace a drive with a slightly different model that is slightly smaller.
From personal experience, partitions would be much easier. I've still got an issue on my RAID5 where one of the hard disks has a bogus/fake partition table on it (simply due to the data on the RAID appearing like a partition table). It causes problems with lilo and other processes at boot time (all non-fatal except for lilo). Perhaps with time I'll get lucky and the data in that particular part of the drive will be changed to something that looks nothing like a partition table :)
Lem.