martin f krafft wrote:
> also sprach lrhorer <lrho...@satx.rr.com> [2011.02.02.1923 +0100]:
>> I rather suspected that might be the case. Taking a quick look at
>> the /dev directory, the drive targets have changed from /hdX to
>> /sdX, and are now way at the end of the list, rather than "a" and
>> "b". Now that really shouldn't give mdadm any grief, but I think
>> it is.
>
> Should not.
> Show me your mdadm.conf!
'Very straightforward:
DEVICE partitions
HOMEHOST <system>
ARRAY /dev/md0 level=raid6 num-devices=10 metadata=01.2 name=Backup:0
UUID=431244d6:45d9635a:e88b3de5:92f30255
ARRAY /dev/md1 level=raid1 num-devices=2 metadata=0.90
UUID=4cde286c:0687556a:4d9996dd:dd23e701
ARRAY /dev/md2 level=raid1 num-devices=2 metadata=01.2 name=Backup:2
UUID=d45ff663:9e53774c:6fcf9968:21692025
ARRAY /dev/md3 level=raid1 num-devices=2 metadata=01.2 name=Backup:3
UUID=51d22c47:10f58974:0b27ef04:5609d357
>> Mdstat and dmadm -D both show all the arrays inactive, but if
>> I try to assemble them, it says they are all in use.
>
> How do you assemble them?
I have to stop them (mdadm -S /dev/mdX), at which point assembly works
via `mdadm --assemble --scan`, or of course I can specify the array to
assemble.
> And what does /proc/mdstat contain at this point.
Before I stop and re-start the arrays, all four show inactive. After
I manually assemble the arrays, they all show active (auto-read-only).
> Also, show
>
> ls -l /dev/md* /dev/sd*
Something is also wrong with this busybox's implementation of `more`,
so it's hard to see all of any sufficiently verbose output. Suffice to
say the block devices (md0 - 3, sda - k, and sdl1 -3 plus sdm1 - 3) are
all there.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/vf-dnrsi1pnckdtqnz2dnuvz5okdn...@giganews.com
