Re: lilo on raid5 root doesn't work
From: Robert Heller (heller_at_deepsoft.com)
Date: 12/05/04
- Next message: KJ: "Re: How does Linux inform me when a RAID disk has failed?"
- Previous message: Jean-David Beyer: "Re: The guts of /dev/* ?"
- In reply to: Peter T. Breuer: "Re: lilo on raid5 root doesn't work"
- Next in thread: Greg Lee: "Re: lilo on raid5 root doesn't work"
- Reply: Greg Lee: "Re: lilo on raid5 root doesn't work"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 05 Dec 2004 03:54:57 +0100
Greg Lee <greg@ling.lll.hawaii.edu>,
In a message on 5 Dec 2004 02:09:27 GMT, wrote :
GL> Peter T. Breuer <ptb@lab.it.uc3m.es> wrote:
GL> > Greg Lee <greg@ling.lll.hawaii.edu> wrote:
GL> > > Michael Heiming <michael+USENET@www.heiming.de> wrote:
GL> > > > In comp.os.linux.misc Greg Lee <greg@ling.lll.hawaii.edu>:
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> > > > [..]
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.
GL> > >
GL> > > > Why should there be a bug in lilo? It told you exactly the
GL> > > > problem, it can't have /boot on raid 5, nor can grub (IIRC).
GL> > >
GL> > > But /boot is not on raid5. It's on an ordinary partition.
GL> > > I said that.
GL>
GL> > No it isn't. Lilo is telling you that. Or something else of yours
GL> > apart from the boot image and boot map is on a raid5 partition, like the
GL> > lilo boot message file, or the boot splash background. Anyway, you
GL> > know what it is! We don't.
GL>
GL> I know what it is? No, I don't know what it is. It's not the
GL> boot message file, as you can see by examining the lilo.conf
GL> I posted a short time ago.
GL>
GL> > But it SAYS it is the boot image. So check. Run with -v -v -v.
GL>
GL> Here is the result of running with -v -v -v. Maybe it will tell
GL> you something:
GL>
GL> root@moore579:~# lilo -t -v -v -v
GL> LILO version 22.5.9 (test mode), Copyright (C) 1992-1998 Werner Almesberger
GL> Development beyond version 21 Copyright (C) 1999-2004 John Coffman
GL> Released 08-Apr-2004 and compiled at 00:18:50 on May 21 2004.
GL>
GL> raid_setup returns offset = 00000000 ndisk = 0
GL> BIOS VolumeID Device
GL> Reading boot sector from /dev/sda
GL> pf_hard_disk_scan: ndevs=8
GL> 0800 4D387FF3 /dev/sda
GL> 0810 1C9F709F /dev/sdb
GL> 0820 495F1051 /dev/sdc
GL> 0830 2D66E1FE /dev/sdd
GL> 0840 5C619BE8 /dev/sde
GL> 0850 5357D297 /dev/sdf
GL> 0860 29C21572 /dev/sdg
GL> 0870 4589FAF8 /dev/sdh
GL> Resolve invalid VolumeIDs
GL> Resolve duplicate VolumeIDs
GL> 0800 4D387FF3 /dev/sda
GL> 0810 1C9F709F /dev/sdb
GL> 0820 495F1051 /dev/sdc
GL> 0830 2D66E1FE /dev/sdd
GL> 0840 5C619BE8 /dev/sde
GL> 0850 5357D297 /dev/sdf
GL> 0860 29C21572 /dev/sdg
GL> 0870 4589FAF8 /dev/sdh
GL> device codes (user assigned pf) = 0
GL> device codes (user assigned) = 0
GL> device codes (BIOS assigned) = FF
GL> device codes (canonical) = FF
GL> Device 0x0800: BIOS drive 0x80, 255 heads, 4427 cylinders,
GL> 63 sectors. Partition offset: 0 sectors.
GL> Using Volume ID 4D387FF3 on bios 80
GL> Fatal: Only RAID1 devices are supported for boot images
What does /etc/fstab look like? Somehow, one of the file systems lilo
is going after for something IS on the RAID5 disks. One thing that is
*probably* the problem is the file system /boot lives on. You are
either going to need a pile of additional lilo options
(foo=/old-root/boot/foo) or you really should make life easy for
yourself and create a small (about 5-10 meg, not on the RAID5 array)
/boot partition and mount it under /boot, since that is the default
place lilo looks for stuff.
LILO 101: there is not enough room in the MBR to store all of lilo, only
the start. Lilo *first* loads additional pieces of itself from /boot/
(by default):
chain.b, boot.b, and map
You are going to need (at least) in your RAID5 lilo.conf:
map=/old-root/boot/map
loader=/old-root/boot/chain.b
And *maybe* (I am not sure if these are accessed at boot time or lilo
install time):
install=/old-root/boot/boot.b
backup=/old-root/boot/boot.0800
Like I said, it will be easier if you just create and mount a /boot file
system.
GL>
GL> ---------
GL> sda and sdb are not in raid arrays. sdc-sdh are.
GL> --
GL> Greg Lee <greg@ling.lll.hawaii.edu>
GL>
\/
Robert Heller ||InterNet: heller@cs.umass.edu
http://vis-www.cs.umass.edu/~heller || heller@deepsoft.com
http://www.deepsoft.com /\FidoNet: 1:321/153
- Next message: KJ: "Re: How does Linux inform me when a RAID disk has failed?"
- Previous message: Jean-David Beyer: "Re: The guts of /dev/* ?"
- In reply to: Peter T. Breuer: "Re: lilo on raid5 root doesn't work"
- Next in thread: Greg Lee: "Re: lilo on raid5 root doesn't work"
- Reply: Greg Lee: "Re: lilo on raid5 root doesn't work"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
