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:57:06 +0100 [thread overview]
Message-ID: <20041109195706.GA21202@middle.of.nowhere> (raw)
In-Reply-To: <41911F09.2070403@skybuilders.com>
From: Jesse Burkhardt <jesse@skybuilders.com>
Date: Tue, Nov 09, 2004 at 02:48:25PM -0500
> What happens in failure mode is that the computer succeeds in completing
> its POST (power on self test) cycle but never goes on to load the OS.
>
> PS - Another user, [1]olchansk@sam.triumf.ca, says that kernel 2.6 is
> broken as to raid1, but it has been patched, but not yet in the Fedora
> version.
>
I'm not sure if current BIOS code still requires a single 'active'
partition on a single drive to boot. If it still does, that would
explain what happens to you.
As for the kernel being at fault - perhaps, I never noticed anything,
but if even grub doesn't come on, it surely isn't the kernel's fault.
Good luck,
Jurriaan
--
REAL LIFE MANAGEMENT 'DILBERT QUOTATIONS':
5: Doing it right is no excuse for not meeting the schedule. No one will
believe you solved this problem in one day! We've been working on it
for months. Now, go act busy for a few weeks and I'll let you know
when it's time to tell them. (R&D supervisor, Minnesota Mining and
Manufacturing/3M Corp.)
Debian (Unstable) GNU/Linux 2.6.9-mm1 2x6078 bogomips load 1.17
next prev parent reply other threads:[~2004-11-09 19:57 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
[not found] ` <41911F09.2070403@skybuilders.com>
2004-11-09 19:57 ` Jurriaan [this message]
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=20041109195706.GA21202@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.