also sprach Tito <farmatito@tiscali.it> [2008.05.07.2027 +0100]:
> 1) using the script in /usr/share/mdadm/mkconf (which uses mdadm --examine --scan --config=partitions) i get
>
> # definitions of existing MD arrays
> ARRAY /dev/md2 level=raid1 num-devices=2 UUID=95261952:6a58368f:9d4deba6:47ca997f
> ARRAY /dev/md0 level=raid1 num-devices=4 UUID=2928f68e:5d9adc5b:3fbebe5a:bce56b15
> ARRAY /dev/md1 level=raid1 num-devices=2 UUID=e16b4bf9:f0dbce60:04894333:532a878b spares=2
> ARRAY /dev/md1 level=raid5 num-devices=3 UUID=fd0b1c0e:f10deae6:11c6bfd4:055cd56a spares=1
This means that mdadm found two devices (or partitions) with
superblocks that set super-minor=1, thus /dev/md1. You probably want
to find the device/partition which defines the unwanted array and
call --zero-superblock on it, after making sure you know what you're
doing.
> 2) while with mdadm --detail --scan i get:
This actually inspects only arrays which are assembled. Therefore,
it's logical you don't find the /dev/md1 raid1.
> So seems that i did something stupid (forgot to delete an array?)
> that i don't know how to fix at the moment. :-(
You can try
mdadm -Esvcpartitions
and see which devices have the unwanted superblock, then zero it on
each.
--
.''`. martin f. krafft <madduck@debian.org>
: :' : proud Debian developer, author, administrator, and user
`. `'` http://people.debian.org/~madduck - http://debiansystem.info
`- Debian - when you have better things to do than fixing systems
god is real, unless declared integer.
(dedicated to gabriel gómez)
Attachment:
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)