Re: [gentoo-user] fixing raid1 /boot

[Kevin Haddock <kevinhaddock@yahoo.com>]

beta ~ # mdadm --manage --stop /dev/md0
mdadm: stopped /dev/md0
beta ~ # mdadm -A /dev/md0 /dev/sda1
mdadm: cannot open device /dev/sda1: Device or resource busy
mdadm: /dev/sda1 has no superblock - assembly aborted
beta ~ # mdadm -A /dev/md0 /dev/sda 
mdadm: cannot open device /dev/sda: Device or resource busy
mdadm: /dev/sda has no superblock - assembly aborted
beta ~ # mount
/dev/evms/slash on / type xfs (rw,noatime)
proc on /proc type proc (rw,nosuid,nodev,noexec)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec)
udev on /dev type tmpfs (rw,nosuid,size=10240k,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,gid=5,mode=620)
shm on /dev/shm type tmpfs (rw,noexec,nosuid,nodev)
usbfs on /proc/bus/usb type usbfs (rw,noexec,nosuid,devmode=0664,devgid=85)
securityfs on /sys/kernel/security type securityfs (rw,noexec,nosuid,nodev)
nfsd on /proc/fs/nfsd type nfsd (rw,noexec,nosuid,nodev)

-Kevin

-----

People originally thought the eternal question was:

      "Why am I here?"

But now we know the question is actually:

      "Why is THAT THERE?"

-Me


--- On Wed, 8/19/09, Mike Kazantsev <mk.fraggod@gmail.com> wrote:

> From: Mike Kazantsev <mk.fraggod@gmail.com>
> Subject: Re: [gentoo-user] fixing raid1 /boot
> To: gentoo-user@lists.gentoo.org
> Date: Wednesday, August 19, 2009, 4:17 PM
> On Wed, 19 Aug 2009 15:30:46 -0700
> (PDT)
> Kevin Haddock <kevinhaddock@yahoo.com>
> wrote:
> 
> > beta ~ # /sbin/mdadm /dev/md0 --fail /dev/sdb1
> --remove /dev/sdb1
> > mdadm: cannot get array info for /dev/md0
> > beta ~ # cat /proc/mdstat 
> > Personalities : [raid0] [raid1] [raid6] [raid5]
> [raid4] [raid10] 
> > md0 : inactive dm-0[0](S)
> >       104320 blocks super
> non-persistent
> 
> If you have /dev/sda1 and /dev/sdb1 in raid1, "md0 :
> inactive
> dm-0[0](S)" line is obviously wrong, it should be something
> like
> "md0 : active raid1 sda1[0] sdb1[1]".
> 
> So, what's this dm-0 device?
> Prehaps you had sda/sdb linked via device mapper during
> boot?
> 
> Try removing md0 (by "--manage --stop") and re-assemble the
> raid,
> specifying the correct devices.
> 
> Try to remove md0 and re-create it, specifying the right
> devices (or
> just /dev/sda1, then add sdb1).
> Alternatively, you can try --assemble --scan, maybe it'll
> just work
> now, then I guess something wrong should be happening
> during boot.
> 
> -- 
> Mike Kazantsev // fraggod.net
>