Re: raid software troubles (long)

[Hal <selvone@ngi.it>]

Now I'm doing some tests with another server that uses raid software 
(mdadm - v2.5.2)
I am able to stop an array and bring it back with:

tux:~# mdadm --misc -S /dev/md0	--> stop the array
mdadm: stopped /dev/md0

tux:~# mdadm --assemble /dev/md0  --> restart the array
mdadm: /dev/md0 has been started with 2 drives.

All perfect...



In my server:
srv:/var/log# mdadm --assemble /dev/md2
mdadm: no devices found for /dev/md2

No devices ??

If I put "--uuid" parameters, it's just the same...
The only way to get the array back is the command
"mdrun".
Yah, You said me not to use it, but it's the only way ...



Then, talking about my startup errors
--
fsck.ext3: Invalid argument while trying to open /dev/mdX
/dev/mdX:
The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

i noticed that it is the same as the output of:
fsck.ext3 -a -C0 /dev/mdX
if I launch when array is not started.

So I make my silly question:  -_-
.... !!
Is it possible that "some init.d script" in the boot process
launch the command "fsck.ext3 ..."
automatically
BEFORE array run,
causing the startup error ??