On Mon, 18 Oct 1999, Florian Lohoff wrote:
> I created 2 Raid 5s with 6 Disks each. I created them one after another
> alwas disconnecting the other disks - Both raid 5s were created as
> /dev/md1 - Afterwards i duplicated the md1 entry and created an md2
> attaching all 12 Disks.
>
> On sta
i suspect this is what happened:
md: md0, array needs 12 disks, has 7, aborting.
raid0: disks are not ordered, aborting!
raidstart was still using the old raidtab to start up the array. It has
found an old array's superblock and tried to start it up. Some disks were
not available so the raid0
does it work if you mark all partitions as autostart? raidstart cannot
find all partitions in the system (obviously) and so weird things might
happen if the SCSI chain is shuffled around without raidtab being updated.
-- mingo
On Mon, 18 Oct 1999, Jakub Jelinek wrote:
> Hi!
>
> Until now I w
On Mon, Oct 18, 1999 at 12:38:22PM +0200, Jakub Jelinek wrote:
> Hi!
>
> Until now I was using non-persistant superblocks, a few days ago I changed a lot
> of small (4 disk) md devices into a few big ones with persistant
> superblocks and I must say I'm quite disappointed by totally loosing contr
Hi!
Until now I was using non-persistant superblocks, a few days ago I changed a lot
of small (4 disk) md devices into a few big ones with persistant
superblocks and I must say I'm quite disappointed by totally loosing control
over what's going on and kernel doing weird things.
The arrays work fi
