From: "Robert L. Harris" <Robert.L.Harris@rdlg.net>
To: danci@agenda.si
Cc: Linux-Raid <linux-raid@vger.kernel.org>
Subject: Re: "failed-disk" ?
Date: Mon, 24 Mar 2003 09:34:58 -0500 [thread overview]
Message-ID: <20030324143458.GB683@rdlg.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0303210828520.10546-100000@duplo.agenda.si>
[-- Attachment #1: Type: text/plain, Size: 4652 bytes --]
I'm trying to rebuild a system with a non-mirrored root. I
intentionally killed /dev/sda by yanking it (hotswap disk) and let the
machine croak. I put the replacement disk in and rebooted, rebuilt (we
have a system similar to jumpstart that makes this very fast and clean).
I'm at the point of trying to restart /dev/md0 with one mirror dead.
My raidtab looks like this:
raiddev /dev/md0
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
chunk-size 16
persistent-superblock 1
device /dev/lvm-vg1/lvm1
raid-disk 0
device /dev/lvm-vg2/lvm2
raid-disk 1
I changed the first raid-disk line to be:
failed-disk 0
and then tried:
root@rharris-build2.acs:~# raidstart /dev/md0
/dev/md0: Invalid argument
md: could not lock [dev 9e:0e], zero-size? Marking faulty.
md: could not import [dev 9e:0e]!
md: autostart [dev 9e:0e] failed!
At this point /dev/lvm-vg1/lvm1 doesn't exist and will need to be
rebuilt but I'd like to get the machine up and running with /dev/md0
intact.
Any idea what's wrong here?
Robert
Thus spake danci@agenda.si (danci@agenda.si):
> On Thu, 20 Mar 2003, Robert L. Harris wrote:
>
> >
> >
> > No but according to the RAID HOWTO it says it's a valid keyword for when
> > you need to build a mirror with a failed/missing disk (i.e. converting
> > root to raid and can't kill your existing /)
>
> It is, but:
>
> 'failed-disk' replaces 'raid-disk' to inform the md driver, that a device
> '/dev/sda1' should not be automatically synchronized.
>
> This gives you an operative array in degraded mode, so you can copy files
> from your current root to your new degraded array.
>
> You have to change the file /etc/fstab (on the NEW filesystem) to use
> /dev/md0 for root, arrange the boot manager (lilo, grub, whatever) to boot
> with the new root (/dev/md0), reboot and 'un-fail' :) (or add) /dev/sda1
> to the array (using mdadm or raidhotadd).
>
>
> D.
>
>
> >
> >
> > Thus spake Lars Marowsky-Bree (lmb@suse.de):
> >
> > > On 2003-03-20T16:22:50,
> > > "Robert L. Harris" <Robert.L.Harris@rdlg.net> said:
> > >
> > > > I'm trying to "mkraid /dev/md1" with the following:
> > > >
> > > > raiddev /dev/md1
> > > > raid-level 1
> > > > nr-raid-disks 2
> > > > nr-spare-disks 0
> > > > chunk-size 16
> > > > persistent-superblock 1
> > > > device failed-disk
> > > > raid-disk 0
> > > > device /dev/sdb1
> > > > raid-disk 1
> > > >
> > > > I'm trying to convert this machine to raid1 on root. Don't ask about
> > > > the md1, long story. At any rate when I do the mkraid I get this:
> > > >
> > > > root@rharris-build2:~# mkraid /dev/md1
> > > > handling MD device /dev/md1
> > > > analyzing super-block
> > > > couldn't call stat() on device failed-disk -- No such file or directory
> > > > mkraid: aborted, see the syslog and /proc/mdstat for potential clues.
> > >
> > > Does your system have a device named 'failed-disk' ? I would assume not ;-)
> > >
> > >
> > > Sincerely,
> > > Lars Marowsky-Br?e <lmb@suse.de>
> > >
> > > --
> > > SuSE Labs - Research & Development, SuSE Linux AG
> > >
> > > "If anything can go wrong, it will." "Chance favors the prepared (mind)."
> > > -- Capt. Edward A. Murphy -- Louis Pasteur
> >
> > :wq!
> > ---------------------------------------------------------------------------
> > Robert L. Harris | PGP Key ID: E344DA3B
> > @ x-hkp://pgp.mit.edu
> > DISCLAIMER:
> > These are MY OPINIONS ALONE. I speak for no-one else.
> >
> > Diagnosis: witzelsucht
> >
> > IPv6 = robert@ipv6.rdlg.net http://ipv6.rdlg.net
> > IPv4 = robert@mail.rdlg.net http://www.rdlg.net
> >
>
> --
> ___________________________________________________________________
> | Danilo Godec | Agenda d.o.o. | ISP for business |
> | jr. Syst. Admin | Gosposvetska 84 | WAN networks |
> | danci@agenda.si | si-2000 Maribor | Internet/Intranet |
> | tel:+386.2.2340860 | Slovenija | Application servers |
> | fax:+386.2.2340854 | http://www.agenda.si | Caldera OpenLinux |
>
:wq!
---------------------------------------------------------------------------
Robert L. Harris | PGP Key ID: E344DA3B
@ x-hkp://pgp.mit.edu
DISCLAIMER:
These are MY OPINIONS ALONE. I speak for no-one else.
Diagnosis: witzelsucht
IPv6 = robert@ipv6.rdlg.net http://ipv6.rdlg.net
IPv4 = robert@mail.rdlg.net http://www.rdlg.net
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-03-24 14:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-20 21:22 "failed-disk" ? Robert L. Harris
2003-03-20 21:29 ` Lars Marowsky-Bree
2003-03-20 21:32 ` Robert L. Harris
2003-03-21 7:38 ` danci
2003-03-24 14:34 ` Robert L. Harris [this message]
2003-03-25 14:12 ` danci
2003-03-25 14:16 ` Robert L. Harris
2003-03-20 21:32 ` Wolfram Schlich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030324143458.GB683@rdlg.net \
--to=robert.l.harris@rdlg.net \
--cc=danci@agenda.si \
--cc=linux-raid@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).