Re: lilo on raid5 root doesn't work
From: Greg Lee (greg_at_ling.lll.hawaii.edu)
Date: 12/05/04
- Next message: Michael Heiming: "Re: lilo on raid5 root doesn't work"
- Previous message: Bill Unruh: "Re: The guts of /dev/* ?"
- In reply to: Robert Heller: "Re: lilo on raid5 root doesn't work"
- Next in thread: Michael Heiming: "Re: lilo on raid5 root doesn't work"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 5 Dec 2004 00:38:14 GMT
Robert Heller <heller@deepsoft.com> wrote:
> Greg Lee <greg@ling.lll.hawaii.edu>,
> In a message on 4 Dec 2004 17:20:11 GMT, wrote :
> GL> I moved my root filesystem from an ordinary parition
> GL> onto a raid5 array and lilo stopped working. It complains
> GL> "Fatal: Only RAID1 devices are supported for boot images".
> GL> But I don't have a boot image on any sort of raid device.
> GL> Only my root is on raid5. I know that I can boot up to a
> GL> root on raid5, because I'm running that way now. And I can
> GL> still run lilo by using "lilo -r /old-root", where
> GL> /old-root is on an ordinary partition (/dev/sda2).
> GL>
> GL> On my new raid5 root, /etc/lilo.config is the same
> GL> as the one on the old, non-raid root, except it refers
> GL> to image files on /old-root/boot/. I'm running
> GL> lilo 22.5.9, linux 2.6.9, software raid arrays made
> GL> with mdadm, Slackware 10.
> GL>
> GL> I don't see what I'm doing wrong. Do you think it's
> GL> a bug in lilo? I compiled a lilo 22.6.1 and got the
> GL> same result.
> Not a problem with lilo. You need to update your /etc/modules.conf to
> include the raid driver modules and re-build your initrd file (if
> needed).
I have the raid stuff compiled into the kernel. I don't need extra
modules. I'm running right now with the root on raid5. That's not
the problem. Lilo can get the kernel image from where I put it
and boot me up with my raid5 root, because it's doing so now.
I just can't run lilo when my current root is on raid5. So long
as I don't have to re-run lilo, I'm fine. But I don't want to
keep the old root around forever, just for the sake of re-running
lilo at some time in the future.
> Also, you need to have your /old-root/boot available as a
> normal file system, accessible via the *BIOS*.
It is. It's on /dev/sda2. It's mounted. (Otherwise "lilo -r /old-root"
wouldn't work.) As I said, though my root is on raid5, the boot
files are not. They're on a filesystem on /dev/sda2, and my lilo.conf
file says to put the boot on /dev/sda.
> /old-root/boot *must*
> be a regular partition (eg /dev/sda2), it cannot be part of the RAID5
> array. ...
It's not part of the raid5 array, which is built from /dev/sdc2,
/dev/sdd2, /dev/sde2, /dev/sdf2, /dev/sdg2, and /dev/sdh2.
-- Greg Lee <greg@ling.lll.hawaii.edu>
- Next message: Michael Heiming: "Re: lilo on raid5 root doesn't work"
- Previous message: Bill Unruh: "Re: The guts of /dev/* ?"
- In reply to: Robert Heller: "Re: lilo on raid5 root doesn't work"
- Next in thread: Michael Heiming: "Re: lilo on raid5 root doesn't work"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
