When I first set up my Raid 5, I made the partitions with Fdisk, and
started /dev/hdc1 at block 0, the end was the end of the disk (single
partition per drive except /dev/hdc5 is type whole disk).
It ran fine until I rebooted, when it came up and said there was no valid
superblock. I re-fdisked the drives and re-ran mkraid and all was well
until I rebooted. I read somewhere (can't remember where though) that
block 0 had to be isolated as the superblock was written there... I
re-fdisked all my drives so partition /dev/hdx1 started at block 1 instead
of zero and haven't had a problem since.
I'm running Kernel 2.2.12 with raidtools 0.90 and all the patches..
At 04:17 PM 11/4/1999 +0100, Jakob �stergaard wrote:
>On Thu, Nov 04, 1999 at 10:01:41AM -0500, David Cooley wrote:
>...
> >
> > Does this mean we no longer have to start raid partitions at block 1
> > instead of block zero?
>
>I'm sorry, but I have no idea of what you're referring to...
>
>When accessing the RAID device you can't see that there is a superblock
>at all. You can't access the superblock via valid accesses to the MD
>device.
>
>I might be misunderstanding your question... When did you ever have to
>start anything at block 1 instead of block 0 ?
>
>(Gee, I hope this isn't in the HOWTO as well ;)
>
>--
>................................................................
>: [EMAIL PROTECTED] : And I see the elder races, :
>:.........................: putrid forms of man :
>: Jakob �stergaard : See him rise and claim the earth, :
>: OZ9ABN : his downfall is at hand. :
>:.........................:............{Konkhra}...............:
===========================================================
David Cooley N5XMT Internet: [EMAIL PROTECTED]
Packet: N5XMT@KQ4LO.#INT.NC.USA.NA T.A.P.R. Member #7068
We are Borg... Prepare to be assimilated!
===========================================================
