linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* AW: RAID1 root - troubles booting in degraded mode
@ 2002-10-30 10:52 Martin Bene
  2002-10-30 11:10 ` Massimiliano Masserelli
  0 siblings, 1 reply; 5+ messages in thread
From: Martin Bene @ 2002-10-30 10:52 UTC (permalink / raw)
  To: Massimiliano Masserelli, linux-raid

Hi Massimiliano

> If I disconnect /dev/hda before booting, the kernel tries to 
> initialize the array, can't access /dev/hda1 (no wonder), marks it as 
> faulty, then refuses to initialize the array, 
> dieing with a kernel panic, unable to mount root.

This look like you're initializing the array from an initrd using raidstart.

Reason why it's not working: raidstart is stupid. it just reads the first
device from raidtab and tries to read the raid superblock from there. if the
first device listed in raidtab doesn't work, raidstart can't start the array.

What to do about it:

a) you could compile raid into your kernel (not as modules), set the
partition type of the raid partitions to 0xfd and have the kernel
automatically initialize the raid array. This works even if device name and
or device order of the raid devices has changed.

or 

b) use Neil Browns mdadm instead of raidstart in the initrd - it's a
replacement for the older raidtools and doesn't have any problem when the
first device is down.

Bye, Martin



^ permalink raw reply	[flat|nested] 5+ messages in thread
* RAID1 root - troubles booting in degraded mode
@ 2002-10-29 23:07 Massimiliano Masserelli
  2002-10-30 20:18 ` Emilio Gargiulo
  0 siblings, 1 reply; 5+ messages in thread
From: Massimiliano Masserelli @ 2002-10-29 23:07 UTC (permalink / raw)
  To: linux-raid

Hi folks! 

I've taken a look at the ML archives, and found an old thread (06/2002) 
on this subject, but found no solution.

I've a working setup with a two disks RAID1 root, which boots
flawlessly. Troubles arise when simulating hw failure. RAID setup is as
follows:

raiddev                 /dev/md0
raid-level              1
nr-raid-disks           2
nr-spare-disks          0
chunk-size              4

device                  /dev/hda1
raid-disk               0

device                  /dev/hdc1
raid-disk               1

If I disconnect /dev/hda before booting, the kernel tries to initialize
the array, can't access /dev/hda1 (no wonder), marks it as faulty, then
refuses to initialize the array, dieing with a kernel panic, unable to
mount root.

If I disconnect /dev/hdc before booting, the array gets started in
degraded mode, and the startup goes on without a glitch.

If I disconnect /dev/hda and move /dev/hdc to its place (so it's now
/dev/hda), the array gets started in degraded mode and the startup goes
on.

Actually, this is already a workable solution (if the first disk dies, I
just "promote" the second to hda and go looking for a replacement of the
broken disk), but I think this is not _elegant_. 8)

Could anyone help me shedding some light on the subject?

Tnx in advance.
-- 
Massimiliano Masserelli
-------------------------------------------------------------------------------
Mayor: "Uh... try to have her home by eleven."
	--Buffy the Vampire Slayer: Enemies

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2002-10-30 20:18 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-10-30 10:52 AW: RAID1 root - troubles booting in degraded mode Martin Bene
2002-10-30 11:10 ` Massimiliano Masserelli
  -- strict thread matches above, loose matches on Subject: below --
2002-10-29 23:07 Massimiliano Masserelli
2002-10-30 20:18 ` Emilio Gargiulo
2002-10-30 20:18   ` Massimiliano Masserelli

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).