Re: raid software troubles (long)

Hal wrote: 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 ?? Maybe it wasn't a silly question and raid system was functioning well... I found th

Re: raid software troubles (long)

Hal wrote: In my server: srv:/var/log# mdadm --assemble /dev/md2 mdadm: no devices found for /dev/md2 I am drunk O-o the command is: #:/var/log# mdadm --assemble /dev/md2 /dev/sda6 /dev/sdb6 mdadm: /dev/md2 has been started with 2 drives. And, as you can see, It works... -- To UNSUBSCRIBE

Re: raid software troubles (long)

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 st

Re: raid software troubles (long)

martin f krafft wrote: also sprach Hal <[EMAIL PROTECTED]> [2006.12.27.2120 +0100]: I didn't tried modifying that file, because I didn't want to get into troubles. ;-) Make a backup and try using /usr/share/mdadm/mkconf once the system is up and running the way you like it to create a new one.

Re: raid software troubles (long)

also sprach Hal <[EMAIL PROTECTED]> [2006.12.27.2120 +0100]: > I didn't tried modifying that file, because I didn't want to get into > troubles. ;-) Make a backup and try using /usr/share/mdadm/mkconf once the system is up and running the way you like it to create a new one. Some stuff has change

Re: raid software troubles (long)

martin f krafft wrote: [..] It would help to see the contents of /proc/mdstat at this point, and also the output of mdadm -Es and mdadm -Asa yes I cannot do that now because I'm not in front of the server, now only ssh connection is available... I remember that I tried to 'cat /proc/mdst

Re: raid software troubles (long)

also sprach Hal <[EMAIL PROTECTED]> [2006.12.26.2205 +0100]: > fsck.ext3 invalid argument while trying to open /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 fs (and not swap or > ufs or something

raid software troubles (long)

Hi, many days ago my Debian server stopped working because one hard disk broke down. So I attached a new disk and rebuilded the array successfully. The server came back up online and I decided to make a reboot. During bootup phase, the shell returned this message and the process stopped, suggesti