Re: lilo on raid5 root doesn't work
From: Greg Lee (greg_at_ling.lll.hawaii.edu)
Date: 12/05/04
- Next message: Jean-David Beyer: "Re: The guts of /dev/* ?"
- Previous message: Mark Mitchell: "Palm pilot stopped syncing via usb."
- In reply to: Peter T. Breuer: "Re: lilo on raid5 root doesn't work"
- Next in thread: Peter T. Breuer: "Re: lilo on raid5 root doesn't work"
- Reply: Peter T. Breuer: "Re: lilo on raid5 root doesn't work"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 5 Dec 2004 02:09:27 GMT
Peter T. Breuer <ptb@lab.it.uc3m.es> wrote:
> Greg Lee <greg@ling.lll.hawaii.edu> wrote:
> > Michael Heiming <michael+USENET@www.heiming.de> wrote:
> > > In comp.os.linux.misc Greg Lee <greg@ling.lll.hawaii.edu>:
> > > > I moved my root filesystem from an ordinary parition
> > > > onto a raid5 array and lilo stopped working. It complains
> > > > "Fatal: Only RAID1 devices are supported for boot images".
> > > [..]
> >
> > > > I don't see what I'm doing wrong. Do you think it's
> > > > a bug in lilo? I compiled a lilo 22.6.1 and got the
> > > > same result.
> >
> > > Why should there be a bug in lilo? It told you exactly the
> > > problem, it can't have /boot on raid 5, nor can grub (IIRC).
> >
> > But /boot is not on raid5. It's on an ordinary partition.
> > I said that.
> No it isn't. Lilo is telling you that. Or something else of yours
> apart from the boot image and boot map is on a raid5 partition, like the
> lilo boot message file, or the boot splash background. Anyway, you
> know what it is! We don't.
I know what it is? No, I don't know what it is. It's not the
boot message file, as you can see by examining the lilo.conf
I posted a short time ago.
> But it SAYS it is the boot image. So check. Run with -v -v -v.
Here is the result of running with -v -v -v. Maybe it will tell
you something:
root@moore579:~# lilo -t -v -v -v
LILO version 22.5.9 (test mode), Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2004 John Coffman
Released 08-Apr-2004 and compiled at 00:18:50 on May 21 2004.
raid_setup returns offset = 00000000 ndisk = 0
BIOS VolumeID Device
Reading boot sector from /dev/sda
pf_hard_disk_scan: ndevs=8
0800 4D387FF3 /dev/sda
0810 1C9F709F /dev/sdb
0820 495F1051 /dev/sdc
0830 2D66E1FE /dev/sdd
0840 5C619BE8 /dev/sde
0850 5357D297 /dev/sdf
0860 29C21572 /dev/sdg
0870 4589FAF8 /dev/sdh
Resolve invalid VolumeIDs
Resolve duplicate VolumeIDs
0800 4D387FF3 /dev/sda
0810 1C9F709F /dev/sdb
0820 495F1051 /dev/sdc
0830 2D66E1FE /dev/sdd
0840 5C619BE8 /dev/sde
0850 5357D297 /dev/sdf
0860 29C21572 /dev/sdg
0870 4589FAF8 /dev/sdh
device codes (user assigned pf) = 0
device codes (user assigned) = 0
device codes (BIOS assigned) = FF
device codes (canonical) = FF
Device 0x0800: BIOS drive 0x80, 255 heads, 4427 cylinders,
63 sectors. Partition offset: 0 sectors.
Using Volume ID 4D387FF3 on bios 80
Fatal: Only RAID1 devices are supported for boot images
---------
sda and sdb are not in raid arrays. sdc-sdh are.
-- Greg Lee <greg@ling.lll.hawaii.edu>
- Next message: Jean-David Beyer: "Re: The guts of /dev/* ?"
- Previous message: Mark Mitchell: "Palm pilot stopped syncing via usb."
- In reply to: Peter T. Breuer: "Re: lilo on raid5 root doesn't work"
- Next in thread: Peter T. Breuer: "Re: lilo on raid5 root doesn't work"
- Reply: Peter T. Breuer: "Re: lilo on raid5 root doesn't work"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|