Mailinglist Archive: opensuse (1606 mails)

< Previous Next >
Re: [opensuse] Recover md RAID-1.
  • From: "Andrew Joakimsen" <joakimsen@xxxxxxxxx>
  • Date: Sat, 6 Sep 2008 17:10:39 -0400
  • Message-id: <23fd749a0809061410q6b39a9a2j68d5e30c77526f9b@xxxxxxxxxxxxxx>
What is the command? Because mdadm /dev/md0 --fail /dev/sdb2 does not
work. It says set device faulty failed for /dev/sdb2: no such
device.... but cat /dev/sdb2 shows there is a device there!

I have a 2nd system with the same config, I shut it down correctly
with the 'halt" command and when I bring it back up I get the same
problems due to the crappy RAID.

On Sat, Aug 30, 2008 at 3:41 AM, Rodney Baker <rodney.baker@xxxxxxxxxxxx> wrote:
On Sat, 30 Aug 2008 08:30:52 Andrew Joakimsen wrote:
How do I recover a broken MD RAID-1.... Since there is no way to make
a backup with easy restore? I boot the system and it says:

md: radi5 personality registered
md: raid4 personality registered
md: md0 stopped.
md: bind<sdb1>
md: bind<sda1>
md: md0: raid array is not clean -- starting background reconstruction
raid1: raid set md0 active with 2 out of 2 mirrors
md0: bitmap file is out of date (8 < 9) -- forcing full recovery
md0: bitmap file is out of date, doing full recovery
md0: bitmap initialisation failed: -5
md0: failed to create bitmap (-5)
md: peers -> run() failed...
mdadm: failed to RUN_ARRAY /dev/md0: Input/output error
mdadm: device /dev/md0 already active - cannot assemble it
Trying manual resume from /dev/sdb2
Invoking userspace resume from /dev/sdb2
boot/ line 48: /proc/splash: No such file or
directory resume: libgcrypt version: 1.4.0
Trying manual resume from /dev/sdb2
Invoking in-kernel resume from /dev/sdb2
PM: starting manual resum from disk
Waiting for device /dev/md0 to appear: ok
/dev/md0: unknown volume type
invalid root filesystem -- exiting to /bin/sh

Before this system was working fine. I shut it down correctly with the
'halt' command. I plugged in a USB KVM that makes the system hang at
boottime (to provide needed info for Bug # 412476) after the system
hung I powered it off, unplugged the kVM and then booted it back, only
to get the above messages.

First thing I would do is to mark /dev/sdb2 as failed and remove it from the
array. Then try booting the array with just /dev/sdb1 as a member. Once the
array is started, reassemble the array and let it rebuild the mirror. I am
assuming that /dev/sdb2 is the partition with the problem - it may in fact
be /dev/sdb1 (in which case do the above for /dev/sdb1).

Reading man mdadm may be useful.

Rodney Baker VK5ZTV

A [golf] ball hitting a tree shall be deemed not to have hit the tree.
Hitting a tree is simply bad luck and has no place in a scientific
game. The player should estimate the distance the ball would have
traveled if it had not hit the tree and play the ball from there,
preferably atop a nice firm tuft of grass.
-- Donald A. Metz

To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups