Steve,
> 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 partigio
Folks,
I messed up slightly when creating a new 6-disk raid6 array, and am wondering
if there is a simple answer. The problem is that I didn't partition the drives,
but simply used the whole drive. All drives are of the same type and using the
Supermicro SAT2-MV8 controller.
This is a problem bec
Folks,
> I'm currently using a Promise Technologies TX4300 SATA II
> 3.0GB/s controller, to which are connected 4 Seagate
> Barracuda 7200.10 ST3320620AS 320GB drives. I've only had
> this setup for
> 2 weeks but so far I'm happy with it. The controller is PCI
> and costs about $66. the drive
Hi,
I've a file server running on an Athlon XP 3200+ motherboard, currently using a
mixture of PATA and SATA-150 drives and Fedora Core 5 Linux. 5x 120GB Seagate
drives form a single raid-5 volume. One of those drives has failed, the rest
are old, and I'm looking to replace all of them. I'd appre
9 and hda9
removed.
which wasn't part of an array but couldn't be added to one. Nothing
particularly interesting.
Ok. I'll just re-add the drive and see what happens.
Thanks
Ruth
--
Ruth Ivimey-Cook
Software engineer and technical writer.
-
To unsubscribe from this list: send th
thoughts on why this happened?
Ruth
--
Ruth Ivimey-Cook <[EMAIL PROTECTED]>
-
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
Hi,
I've just spent a couple of hours sorting out my server after it, for an
unknown reason, threw a wobbly and froze.
One of the stranger aspects of this is that once I got it more-or-less
working, I found that the raid5 array on the server was being switched to
readonly mode very early on in th
ync, md%d has
>overlapping physical units with md%d!\n", mdidx(mddev), mdidx(mddev2));
>+ printk(KERN_INFO "md: serializing resync, md%d has
>shares one or more physical units with md%d!\n", mdidx(mddev), mdidx(mddev2));
> serialize = 1;
>
