At 09:51 AM 9/17/1999 -0400, Daniel Bidwell wrote:
> > I have found that you need to re-partition the disks so you only have
> > partition 1 and 3...
> > 3 is whole disk, 1 is type FD and starts at cyl 1, not 0
> > Raidtools doesn't like any other partitions.
>
>I don't think that this is correct. I am running 2.2.12 with the 0.90
>raid tools and I have a set of 5 18G disks with 7 partitions on each
>disk and 7 different RAID5 spread across the disk set. They are all
>configured and running just fine.
I was running Kernel 2.2.5-22 from RH 6 on Sparc. Regardless what
partitoon I specified (/dev/sdc7 was what I tried first... plus partition 7
on the next 5 disks) it said /dev/sdc1 not found, mkraid aborting. Made a
small partition 1 and tried again, still didn't like it. Went to the final
configuration (next to final) with partitions 1 and 3, set up ok, but on
next boot, it said the superblocks were corrupt... One of the readme's or
how to's said cyl 0 is where it put those, so I changed partition 1 to
start at cyl1 and all has been well.
Some weirdness I am having now though is I installed a second SCSI
controller... I broke up my 2 md devices so now each ones drives are on a
seperate controller (6 on SCSI1, 6 on SCSI2).
It won't use both SCSI controllers for md devices... It will start and
mount the raid for the drives on SCSI 1, but fails for SCSI2... if I put
all 12 drives back on one controller (either one... tested to ensure
controller was good!) it will make both.
The Kernel see's all 12 regardless of config, and /proc/partition has all
12 listed. It just won't use them. I upgraded to kernel 2.2.11, applied
the raid patch and compiled/installed the latest raidtools for it... same
result.
===========================================================
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!
===========================================================
