Hi Michael
Try a mkraid --really-force /dev/md0
Greetings, Dietmar
Michael Rothwell wrote:
>
> mkraid does this:
>
> [root@penguin rothwell]# mkraid /dev/md0
> handling MD device /dev/md0
> analyzing super-block
> disk 0: /dev/sda2, 8369865kB, raid superblock at 8369792kB
> /dev/sda2 appears to contain an ext2 filesystem -- use -f to override
> mkraid: aborted
>
> [root@penguin rothwell]# mkraid --really-force /dev/md0
> DESTROYING the contents of /dev/md0 in 5 seconds, Ctrl-C if unsure!
> handling MD device /dev/md0
> analyzing super-block
> disk 0: /dev/sda2, 8369865kB, raid superblock at 8369792kB
> disk 1: /dev/sdb2, 8369865kB, raid superblock at 8369792kB
> disk 2: /dev/sdc2, 8369865kB, raid superblock at 8369792kB
> disk 3: /dev/sdd2, 8369865kB, raid superblock at 8369792kB
> mkraid: aborted
> [root@penguin rothwell]#
>
> [root@penguin rothwell]# cat /etc/raidtab
> # Sample raid-5 configuration
> raiddev /dev/md0
> raid-level 5
> nr-raid-disks 4
> chunk-size 128
> #persistent-superblock 1
>
> # Parity placement algorithm
> parity-algorithm left-symmetric
> #parity-algorithm left-asymmetric
> #parity-algorithm right-asymmetric
> #parity-algorithm right-symmetric
>
> # Spare disks for hot reconstruction
> #nr-spare-disks 0
>
> device /dev/sda2
> raid-disk 0
>
> device /dev/sdb2
> raid-disk 1
>
> device /dev/sdc2
> raid-disk 2
>
> device /dev/sdd2
> raid-disk 3
>
>
> -- why?
>
> Thanks!
>
> Michael Rothwell
> Director, Internet Application Development
> InterLan Technologies
> 111 Corning Road #150
> Cary, NC 27513
> v: (919) 852-0690
> f: (919) 852-0501
> e: [EMAIL PROTECTED]
--
A guess may be one solution but not the only one ;-)
Dietmar Stein, Systemadministrator UNIX/Linux
[EMAIL PROTECTED], [EMAIL PROTECTED]
