> my lilo.conf:
> disk=/dev/hda
> bios = 0x80
> sectors = 63
> heads = 128
> cylinders = 779
> partition = /dev/hda1
> start = 63
>
> boot=/dev/hda
> map=/boot/map
> install=/boot/boot.b
> prompt
> timeout=50
> default=linux
> image=/boot/bzImage
> label=linux
> read-only
> root=/dev/md0
> append="ether=0,0,0,0,eth1"
>
> Note the disk paragraph, My setup is hda1 as boot-disk (32mb) and the rest
> of my 2 hd's as raid0. Why
> exactly this is needed, i don't know. But without it, i also got the 0x0900
> from lilo.
In the context of booting from RAID, the disk geometry is only needed if the
boot-loader is trying to read from or write to a file on a RAID-1 array that
contains that partition. But in that case, the disk= and partition= lines would
point to RAID arrays, not normal disks and partitions (see Harald
Nordgård-Hansen's message to the list of 22 August on the "Booting Root RAID 1
Directly _Is_ Possible" thread). You may need this section in your lilo.conf to
enable booting, but it has nothing to do with RAID, nor should it be a cure for
the "Sorry, don't know how to handle device 0x0900" error, particularly as I
believe your /dev/md0 is RAID-0, which cannot be read by lilo whatever
parameters you pass to it.
The lines in lilo.conf that could produce this error by pointing lilo at
/dev/md0 are the "boot=", "map=", "install=", "loader=" or "image=" lines. In
this case, it is clearly not the "boot=/dev/hda" line, as that is a
straightforward installation of the boot-loader to the MBR on the first IDE
disk. The "map=", "install=" and "image=" lines all point to files in /boot, and
the absent "loader=" line defaults to /boot/chain.b as well, so if this is
really the error message you are receiving, your problem is clearly something to
do with /boot. You say that /dev/hda1 is your "boot-disk". Do you mean by this
that /dev/hda1 is mounted on /boot? If so and you have all the normal files in
/boot, I don't understand why you get the error message. If not, that is why you
get the error. But even then, I still don't understand how adding disk geometry
for /dev/hda has solved the problem.
Something is not right with your description. Are you really saying that
removing the disk geometry lines from your lilo.conf results in a "Sorry, don't
know how to handle device 0x0900" error when you run lilo? The device number is
particularly crucial. Could you try it again and check? Be careful that the only
change you make it is to remove the geometry lines. And if you get an error, see
if it is _exactly_ as stated above. Because as it stands, your solution doesn't
make sense, as you yourself recognize.
Cheers,
Bruno Prior [EMAIL PROTECTED]
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Kelina
> Sent: 26 October 1999 18:04
> To: Marcos Lopez; Egon Eckert
> Cc: [EMAIL PROTECTED]
> Subject: Re: Root RAID and unmounting /boot
>
>
> At 09:07 26/10/99 -0600, Marcos Lopez wrote:
> >Egon Eckert wrote:
> > >
> > > > syslogd 378 root 5w REG 9,1 8548 192396
> > > > /var/log/boot.log
> > > > klogd 389 root 2r REG 8,1 191102 12
> > > > /boot/System.map-2.2.12-20
> > > >
> > > > Is it safe to kill these?
> > >
> > > These are loggers, so I guess nothing terrible would happen. But I
> > > wouldn't kill them anyway.. I would fix the problem, not make it worse.
> > >
> > > > Also i would be quite grateful if someone could explain to me why I must
> > > > unmount /boot inorder for the lilo -r /mnt/newroot to work?
> > >
> > > I don't unmount anything before running lilo.
> >
> >Okay tired performing that function without doing the umount. I tried
> >doing it without coping the files in /boot over to /mnt/newroot/boot but
> >it couldn't find /boot/boot.b. So i copied over all the files in /boot
> >to /mnt/newroot/boot. Then after running "lilo -r /mnt/newroot" I get
> >the following error:
> >"Sorry, don't know how to handle device 0x0900"
> >
> >What does the above mean and how to i fix it?
>
> Okay bear with me here... i'm doing this from memory and some of my own
> configs (if u have the time to search the
> archives, u'll find something abt this in august i think)
>
> my lilo.conf:
> disk=/dev/hda
> bios = 0x80
> sectors = 63
> heads = 128
> cylinders = 779
> partition = /dev/hda1
> start = 63
>
> boot=/dev/hda
> map=/boot/map
> install=/boot/boot.b
> prompt
> timeout=50
> default=linux
> image=/boot/bzImage
> label=linux
> read-only
> root=/dev/md0
> append="ether=0,0,0,0,eth1"
>
> Note the disk paragraph, My setup is hda1 as boot-disk (32mb) and the rest
> of my 2 hd's as raid0. Why
> exactly this is needed, i don't know. But without it, i also got the 0x0900
> from lilo. The sectors, heads
> and cylinder's line are taken directly from fdisk -l /dev/hda. The start as
> far as i remember, is the same
> as the sector, since it's on the beginning of the disk. (correct me if i'm
> wrong) And the partition is the
> boot partition obviously. The reasons for why this is neccesary u have to
> ask some of the greater linux-
> god's around here, but this worked for me. Also, i think this comes up
> often enough to be added to the
> Software-Raid-HOWTO (i don't remember seeing it there). Anyone agree on this??
>
> Surge
>
>
> >I also have a extra small /boot partition but I just have the regular
> >stuff that is in /boot in there. Should I put some more stuff in
> >there. My end goal is to have a system that boots off RAID if i can
> >figure it out, but right now i need to get this machine into out
> >environment and i would really like to have Root on RAID before letting
> >it get hammered. I think i am close just have to figure out this lilo
> >thing.
>
>
>
