LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
* LILO fatal error after going from 2.6.22 to 2.6.24.2
@ 2008-02-19  7:02 Rasmus Andersen
  2008-02-19 17:22 ` H. Peter Anvin
  0 siblings, 1 reply; 3+ messages in thread
From: Rasmus Andersen @ 2008-02-19  7:02 UTC (permalink / raw)
  To: linux-kernel

Hello,

I have just upgraded from 2.6.22 to 2.6.24.2 and after booting into the
new kernel and seeing that everything went right, I wanted to make the
new kernel the default boot kernel. But running LILO I got

   Fatal: Linux experimental device 0x04x needs to be defined.
   Check 'man lilo.conf' under 'disk=' and 'max-partitions='

(Full output from lilo -v 5 below). Apart from setting 2.6.24.2 as
default this is the same lilo config as 2.6.22 was able to write fine.
Can anyone tell me what I (or the kernel) am/is doing wrong?

Thanks,
  Rasmus



LILO version 22.7.3, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2006 John Coffman
Released 11-Aug-2006 and compiled at 17:06:40 on Jan 17 2007

raid_setup: dev=000C  rdev=0340
raid_setup returns offset = 00000000  ndisk = 0
 BIOS   VolumeID   Device
Reading boot sector from /dev/hdb
geo_get: device 0340, all=1
pf_hard_disk_scan: (7,0) /dev/loop0
pf_hard_disk_scan: (3,64) /dev/hdb
pf_hard_disk_scan: (3,65) /dev/hdb1
lookup_dev:  number=0340
lookup_dev:  number=0340
pf:  dev=0340  id=B661B661  name=/dev/hdb
geo_query_dev: device=0340
lookup_dev:  number=0340
exit geo_query_dev
bios_dev:  device 0340
lookup_dev:  number=0340
bios_dev:  masked device 0340, which is /dev/hdb
bios_dev: geometry check found 0 matches
bios_dev: (0x82)  vol-ID=17FF01F9  *PT=08070AD0
bios_dev: (0x81)  vol-ID=7C4DC2CA  *PT=08070A88
bios_dev: (0x80)  vol-ID=B661B661  *PT=08070A40
bios_dev: PT match found 1 match (0x80)
pf_hard_disk_scan: (3,66) /dev/hdb2
pf_hard_disk_scan: (8,0) /dev/sda
pf_hard_disk_scan: (8,1) /dev/sda1
lookup_dev:  number=0800
lookup_dev:  number=0800
pf:  dev=0800  id=7C4DC2CA  name=/dev/sda
geo_query_dev: device=0800
lookup_dev:  number=0800
lookup_dev:  number=0300
exit geo_query_dev
bios_dev:  device 0800
lookup_dev:  number=0800
bios_dev:  masked device 0800, which is /dev/sda
bios_dev: geometry check found 0 matches
bios_dev: (0x82)  vol-ID=17FF01F9  *PT=08070AD0
bios_dev: (0x81)  vol-ID=7C4DC2CA  *PT=08070A88
bios_dev: (0x80)  vol-ID=B661B661  *PT=08070A40
bios_dev: PT match found 1 match (0x81)
pf_hard_disk_scan: (8,16) /dev/sdb
pf_hard_disk_scan: (8,17) /dev/sdb1
lookup_dev:  number=0810
lookup_dev:  number=0810
pf:  dev=0810  id=17FF01F9  name=/dev/sdb
geo_query_dev: device=0810
lookup_dev:  number=0810
lookup_dev:  number=0300
exit geo_query_dev
bios_dev:  device 0810
lookup_dev:  number=0810
bios_dev:  masked device 0810, which is /dev/sdb
bios_dev: geometry check found 0 matches
bios_dev: (0x82)  vol-ID=17FF01F9  *PT=08070AD0
bios_dev: (0x81)  vol-ID=7C4DC2CA  *PT=08070A88
bios_dev: (0x80)  vol-ID=B661B661  *PT=08070A40
bios_dev: PT match found 1 match (0x81)
pf_hard_disk_scan: (9,0) /dev/md0
pf_hard_disk_scan: (253,0) /dev/dm-0
Caching device /dev/dm-0 (0xFD00)
pf_hard_disk_scan: (253,1) /dev/dm-1
Caching device /dev/dm-1 (0xFD01)
pf_hard_disk_scan: (253,2) /dev/dm-2
Caching device /dev/dm-2 (0xFD02)
pf_hard_disk_scan: (253,3) /dev/dm-3
Caching device /dev/dm-3 (0xFD03)
pf_hard_disk_scan: (253,4) /dev/dm-4
Caching device /dev/dm-4 (0xFD04)
pf_hard_disk_scan: (253,5) /dev/dm-5
Caching device /dev/dm-5 (0xFD05)
pf_hard_disk_scan: (253,6) /dev/dm-6
Caching device /dev/dm-6 (0xFD06)
  0340  B661B661  /dev/hdb
  0800  7C4DC2CA  /dev/sda
  0810  17FF01F9  /dev/sdb
pf_hard_disk_scan: ndevs=3
  0340  B661B661  /dev/hdb
  0800  7C4DC2CA  /dev/sda
  0810  17FF01F9  /dev/sdb
Resolve invalid VolumeIDs
Resolve duplicate VolumeIDs
  0340  B661B661  /dev/hdb
  0800  7C4DC2CA  /dev/sda
  0810  17FF01F9  /dev/sdb
device codes (user assigned pf) = 0
device codes (user assigned) = 0
device codes (BIOS assigned) = 3
Filling in '/dev/sdb' = 0x82
device codes (canonical) = 7
geo_query_dev: device=0340
lookup_dev:  number=0340
exit geo_query_dev
bios_dev:  device 0340
lookup_dev:  number=0340
bios_dev:  masked device 0340, which is /dev/hdb
bios_dev: geometry check found 0 matches
bios_dev: (0x82)  vol-ID=17FF01F9  *PT=08070AD0
bios_dev: (0x81)  vol-ID=7C4DC2CA  *PT=08070A88
bios_dev: (0x80)  vol-ID=B661B661  *PT=08070A40
bios_dev: PT match found 1 match (0x80)
Device 0x0340: BIOS drive 0x80, 255 heads, 9729 cylinders,
               63 sectors. Partition offset: 0 sectors.
registering bios=0x80  device=0x0340
Using Volume ID B661B661 on bios 80
geo_get: device FD06, all=1
geo_query_dev: device=FD06
lookup_dev:  number=FD06
Fatal: Linux experimental device 0x04x needs to be defined.
Check 'man lilo.conf' under 'disk=' and 'max-partitions='

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: LILO fatal error after going from 2.6.22 to 2.6.24.2
  2008-02-19  7:02 LILO fatal error after going from 2.6.22 to 2.6.24.2 Rasmus Andersen
@ 2008-02-19 17:22 ` H. Peter Anvin
  2008-02-19 19:55   ` Rasmus Andersen
  0 siblings, 1 reply; 3+ messages in thread
From: H. Peter Anvin @ 2008-02-19 17:22 UTC (permalink / raw)
  To: Rasmus Andersen; +Cc: linux-kernel

Rasmus Andersen wrote:
> Hello,
> 
> I have just upgraded from 2.6.22 to 2.6.24.2 and after booting into the
> new kernel and seeing that everything went right, I wanted to make the
> new kernel the default boot kernel. But running LILO I got
> 
>    Fatal: Linux experimental device 0x04x needs to be defined.
>    Check 'man lilo.conf' under 'disk=' and 'max-partitions='
> 
> (Full output from lilo -v 5 below). Apart from setting 2.6.24.2 as
> default this is the same lilo config as 2.6.22 was able to write fine.
> Can anyone tell me what I (or the kernel) am/is doing wrong?
> 

You have at least one file on a device mapper device (possibly an LVM 
module), and LILO doesn't understand it.

	-hpa

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: LILO fatal error after going from 2.6.22 to 2.6.24.2
  2008-02-19 17:22 ` H. Peter Anvin
@ 2008-02-19 19:55   ` Rasmus Andersen
  0 siblings, 0 replies; 3+ messages in thread
From: Rasmus Andersen @ 2008-02-19 19:55 UTC (permalink / raw)
  To: H. Peter Anvin; +Cc: linux-kernel

On Tue, Feb 19, 2008 at 09:22:27AM -0800, H. Peter Anvin wrote:
> Rasmus Andersen wrote:
[...]
> You have at least one file on a device mapper device (possibly an LVM 
> module), and LILO doesn't understand it.

Hi Peter, and thanks for your reply. That was indeed the issue, my /boot
was not mounted and my / is on a LVM partition. So this was merely a
user issue, my specialty.

Thanks for your time.

Cheers,
  Rasmus

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2008-02-19 19:55 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-02-19  7:02 LILO fatal error after going from 2.6.22 to 2.6.24.2 Rasmus Andersen
2008-02-19 17:22 ` H. Peter Anvin
2008-02-19 19:55   ` Rasmus Andersen

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).