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 module refused to run and aborted in a safe
manner.
the behavior you saw is normal (unless my analysis is wrong, i do not
claim that there might not be bugs left). The only way we can guarantee
protection against device reordering is marking RAID-enabled partitions as
autostartable. For that to work on Sparc you'll have to introduce a new
partition type (really small amount of hacking), only MSDOS partitions can
currently be used as autostart. (because this is what i'm using)
of course the worst thing that should happen with this are arrays not
getting started up. If anything else happens (messed up superblocks or
corrupted data) then that is a bug.
-- mingo
