From: Jurriaan <thunder7@xs4all.nl>
To: Jesse Burkhardt <jesse@skybuilders.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Fedora 2.0 - raid1 not working
Date: Tue, 9 Nov 2004 20:41:27 +0100 [thread overview]
Message-ID: <20041109194127.GA17963@middle.of.nowhere> (raw)
In-Reply-To: <41911ACB.2070604@skybuilders.com>
From: Jesse Burkhardt <jesse@skybuilders.com>
Date: Tue, Nov 09, 2004 at 02:30:19PM -0500
> Hi Jurriaan,
>
> Your interpretation of my scenerio is correct. Boot is successful when
> both drives A and B are present; also when just drive B is present, but
> not when just drive A is present.
>
> I am using a grub loader which ennumerates thusly:
>
> /boot/grub/menu.lst
>
> default=0
> timeout=10
> splashimage=(hd0,0)/grub/splash.xpm.gz
> title Fedora Core (2.6.5-1.358)
> root (hd0,0)
> kernel /vmlinuz-2.6.5-1.358 ro root=/dev/md1 rhgb quiet
> initrd /initrd-2.6.5-1.358.img
>
I'm still not clear on what happens when boot isn't succesful. Do you
get error messages from grub? If so, what do they say?
Also note that while my menu.lst works fine and lets me boot from both
drives, I haven't tested disconnecting one. I know where my data is, and
my backup, and in case of trouble, I can (and have tested that I can)
boot from a Knoppix-cd.
Kind regards,
Jurriaan
--
and even as Pug spoke, he knew the answer to his question.
"Whom must I seek?"
The girl's eyes seemed to pierce his soul. Calmly she said,
"You must find Macros the Black."
Raymond E Feist - A Darkess at Sethanon
Debian (Unstable) GNU/Linux 2.6.9-mm1 2x6078 bogomips load 0.32
next prev parent reply other threads:[~2004-11-09 19:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 19:08 Fedora 2.0 - raid1 not working Jesse Burkhardt
2004-11-09 19:22 ` Jurriaan
[not found] ` <41911ACB.2070604@skybuilders.com>
2004-11-09 19:41 ` Jurriaan [this message]
[not found] ` <41911F09.2070403@skybuilders.com>
2004-11-09 19:57 ` Jurriaan
2004-11-09 22:14 ` More: " Jesse Burkhardt
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=20041109194127.GA17963@middle.of.nowhere \
--to=thunder7@xs4all.nl \
--cc=jesse@skybuilders.com \
--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).