[opensuse] MD5 Raid array does not start
Hi all, I need help with a raid5 array, that does not start. System has booted in maintenance mode, prompt says "repair filesystem". There are 3 raid5 arrays, one of them is not coming up. It is a data volume, used for backups. Messages after boot is as follows: fsck.ext3: Invalid argument while trying to open /dev/md0 /dev/md0: 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> When I do cat /proc/mdstat it says /dev/md0 is inactive. How can I activate it, and read/repair fs?? -- L. de Braal BraHa Systems NL - Terneuzen T +31 115 649333 F +31 115 649444 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 19 July 2009 18:12:31 Leen de Braal wrote:
When I do cat /proc/mdstat it says /dev/md0 is inactive. How can I activate it, and read/repair fs??
In the boot log, don't you have any messages from mdadm that say why it won't start up md0? If the raid is degraded (e.g. if a disk is broken), it will refuse to start up the raid automatically. Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Leen de Braal wrote:
Hi all,
I need help with a raid5 array, that does not start. System has booted in maintenance mode, prompt says "repair filesystem".
[snip]
When I do cat /proc/mdstat it says /dev/md0 is inactive. How can I activate it, and read/repair fs??
Let us see the output from "cat /proc/mdstat". -- Per Jessen, Zürich (20.8°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Leen de Braal wrote:
Hi all,
I need help with a raid5 array, that does not start. System has booted in maintenance mode, prompt says "repair filesystem".
[snip]
When I do cat /proc/mdstat it says /dev/md0 is inactive. How can I activate it, and read/repair fs??
Let us see the output from "cat /proc/mdstat".
md0: inactive sdc1[4](S) sde1[3](S) sda1[0](S) 2930279424 blocks super 1.0 and then md1 and md2, both ok.
-- Per Jessen, Zürich (20.8°C)
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-- L. de Braal BraHa Systems NL - Terneuzen T +31 115 649333 F +31 115 649444 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, Jul 19, 2009 at 12:12, Leen de Braal
Hi all,
I need help with a raid5 array, that does not start. System has booted in maintenance mode, prompt says "repair filesystem".
There are 3 raid5 arrays, one of them is not coming up. It is a data volume, used for backups.
Messages after boot is as follows:
fsck.ext3: Invalid argument while trying to open /dev/md0 /dev/md0: 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>
When I do cat /proc/mdstat it says /dev/md0 is inactive. How can I activate it, and read/repair fs??
-- L. de Braal BraHa Systems NL - Terneuzen T +31 115 649333 F +31 115 649444
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
No, it is not possible. MD RAID does not work well and honestly shouldn't be used even for testing. -- Med Vennlig Hilsen, A. Helge Joakimsen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi! Am Montag 20 Juli 2009 schrieb Andrew Joakimsen:
I need help with a raid5 array, that does not start. System has booted in maintenance mode, prompt says "repair filesystem".
There are 3 raid5 arrays, one of them is not coming up. It is a data volume, used for backups.
Did you try to assemble the array by hand?
Messages after boot is as follows:
fsck.ext3: Invalid argument while trying to open /dev/md0 /dev/md0: 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>
This is because /dev/md0 does not exists (is not backed by the actual disk). Once your MD is up again this should vanish.
No, it is not possible. MD RAID does not work well and honestly shouldn't be used even for testing.
I have been using MD RAID for a long time now, and only time I had problems was after a power outage that left my disk with different timestamps. A forced reassambly solved that. Regards, Matthias -- Matthias Bach www.marix.org „Der einzige Weg, die Grenzen des Möglichen zu finden, ist ein klein wenig über diese hinaus in das Unmögliche vorzustoßen.“ - Arthur C. Clarke
Andrew Joakimsen wrote:
No, it is not possible. MD RAID does not work well and honestly shouldn't be used even for testing.
On the contrary - MD raid works very well indeed. /Per -- Per Jessen, Zürich (17.9°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Anders Johansson -
Andrew Joakimsen -
Leen de Braal -
Matthias Bach -
Per Jessen