I had a similar experience and got around it using:
ckraid --force-check --fix /dev/md0
I attributed to immature software that errs on the side of caution...
If I recall I had a similar situation with ext2 in the early days.
On Tue, 6 Apr 1999, Linux SMP Mlist wrote:
> Hi,
>
> i have /d
Hi,
i have /dev/sda3 a /dev/sdb3 in RAID1 array.
I've run raidadd /dev/md0, raidrun /dev/md0 - OK.
mount /dev/md0 - OK
raidstop /dev/md0 - OK
mount /dev/sda3 /mnt/ OK
umount /mnt OK
Now i've tried to start raid device but ...
raidadd /dev/md0 OK
raidrun /dev/md0 - > "raid1: detected m
