On Sun, Mar 24, 2002 at 08:11:51PM +0100, Seth Mos wrote:
> At 13:02 24-3-2002 -0600, Eric Sandeen wrote:
> >On Sun, 24 Mar 2002, Paul Blazejowski wrote:
> > > Yes, my LILO resides on /dev/sda2 which is the root partition with XFS
> > > filesystem.And i've been doing that for past 2 years or so without any
> > > problems.My MBR has NTLOADER and to avoid conflicts with it, i choose
> > to use
> > > lilo on my / partition.
> > >
> > > LILO version is 21.7.5 that shipped with Slackware 8.0.It always worked
> > and i
> > > knew about the FAQ entry but it never applied in my case until recently.My
> > > guess is that there's been either a change in XFS or LILO that don't play
> > > together anymore and i get corrupted superblock on my root....Any
> > > comments?
> >My only comment is that I don't know how this ever worked... if it did, I
> >think you were just lucky. :) The XFS superblock signature / magic
> >number should be "XFSB" in the first 4 bytes on the partition, and they're
> >not there in your image - lilo has overwritten it. I'm afraid that
> >you'll have to find another way to boot, XFS and lilo want to put data in
> >the same place.
> He could try putting it onto the swap partition.
bad plan, the bootloader will be overwritten as soon as swap is
activated, and you will probably end up crashing your system when you
scribble part of the active swap with lilo.
his only options are put lilo in the MBR, or create a small ext2
partition to hold lilo (such as /boot). i recommend MBR it will not
cause problems with dual booting, just read the lilo.conf man page.
lilo should really have a check added to see if the partition its
going to install on has an XFS superblock, as far as linux filesystems
go XFS is unique in that it doesn't have 1K of space left alone at the
start of the partition for bootblocks. should be a trivial 2 or 3
line change to lilo which would save a few people a lousy day i imagine.
Description: PGP signature