lilo hangs at "Resolve invalid VolumeIDs" ?!

From: Allan Houston (ahouston-debian_at_blueyonder.co.uk)
Date: 02/10/04

  • Next message: Strop Alexander: "Newbie: Back to installation part...dselect" 
    To: <debian-user@lists.debian.org>
Date: Tue, 10 Feb 2004 12:24:27 -0000

    Hi,

    Having a few hassles with lilo 22.5.8 - I first noticed the problem after building a new kernel. Was just about ready to boot it, ran lilo to complete off the upgrade and it just hangs there.

    System is running debian-unstable, 2.4.20 kernel , two 80 gig IDE disks.
    So far I've tried :

    - comparing the lilo.conf to a similarly built box for any silly mistakes
    - deleting the lilo package and reinstalling (with config file purge)
    - upgrading the lilo package

    .. all to no avail.

    When running it with -v :

    zulu:/# lilo -v
    LILO version 22.5.8, Copyright (C) 1992-1998 Werner Almesberger
    Development beyond version 21 Copyright (C) 1999-2003 John Coffman
    Released 10-Oct-2003, and compiled at 20:07:39 on Feb 1 2004
    Debian GNU/Linux

    Warning: LBA32 addressing assumed
    Reading boot sector from /dev/hda3
    <hangs here>

    Followed the advice in /usr/share/doc/lilo/README.common.problems regarding problems after booting, and checked the geometry :

    zulu:/# lilo -t -v5
    LILO version 22.5.8 (test mode), Copyright (C) 1992-1998 Werner Almesberger
    Development beyond version 21 Copyright (C) 1999-2003 John Coffman
    Released 10-Oct-2003, and compiled at 20:07:39 on Feb 1 2004
    Debian GNU/Linux

    Warning: LBA32 addressing assumed
    raid_setup: dev=0303 rdev=0303
    raid_setup returns offset = 00000000 ndisk = 0
     BIOS VolumeID Device
    Reading boot sector from /dev/hda3
    geo_get: device 0303, all=1
    pf_hard_disk_scan: (22,0) /dev/hdc
    pf_hard_disk_scan: (22,1) /dev/hdc1
    lookup_dev: number=1600
    lookup_dev: number=1600
    pf: dev=1600 id=00000000 name=/dev/hdc
    geo_query_dev: device=1600
    lookup_dev: number=1600
    lookup_dev: number=0300
    lookup_dev: number=0340
    exit geo_query_dev
    bios_dev: device 1600
    lookup_dev: number=1600
    bios_dev: masked device 1600, which is /dev/hdc
    bios_dev: geometry check found 0 matches
    bios_dev: (0x81) vol-ID=00000000 *PT=08076D76
    bios_dev: (0x80) vol-ID=57B5AE33 *PT=08076D2E
    bios_dev: PT match found 1 match (0x81)
    pf_hard_disk_scan: (3,0) /dev/hda
    pf_hard_disk_scan: (3,1) /dev/hda1
    lookup_dev: number=0300
    lookup_dev: number=0300
    pf: dev=0300 id=57B5AE33 name=/dev/hda
    geo_query_dev: device=0300
    lookup_dev: number=0300
    exit geo_query_dev
    bios_dev: device 0300
    lookup_dev: number=0300
    bios_dev: masked device 0300, which is /dev/hda
    bios_dev: geometry check found 0 matches
    bios_dev: (0x81) vol-ID=00000000 *PT=08076D76
    bios_dev: (0x80) vol-ID=57B5AE33 *PT=08076D2E
    bios_dev: PT match found 1 match (0x80)
    pf_hard_disk_scan: (3,2) /dev/hda2
    pf_hard_disk_scan: (3,3) /dev/hda3
      1600 00000000 /dev/hdc
      0300 57B5AE33 /dev/hda
    pf_hard_disk_scan: ndevs=2
      0300 57B5AE33 /dev/hda
      1600 00000000 /dev/hdc
    Resolve invalid VolumeIDs
    <hangs here>

    zulu:/# lilo -Tgeom

        bios=0x00, cylinders=80, heads=2, sectors=18
            ( 1.44Mb 2,880 sectors) C:H:S supported (IBM PC bios)

    BIOS reports 2 hard drives
        bios=0x80, cylinders=1023, heads=255, sectors=63 vol-ID: 57B5AE33
            ( 81.96Gb 160,086,528 sectors) LBA32 supported (EDD bios)
        bios=0x81, cylinders=1023, heads=255, sectors=63
            ( 81.96Gb 160,086,528 sectors) LBA32 supported (EDD bios)

    Using -Tgeom completes OK.

    Anyone have any ideas on this one ?

    Thanks,
    Allan.

    lilo.conf
    --------------

    # Generated by liloconfig

    # This allows booting from any partition on disks with more than 1024
    # cylinders.
    lba32

    # Specifies the boot device
    boot=/dev/hda3

    # Specifies the device that should be mounted as root.
    # If the special name CURRENT is used, the root device is set to the
    # device on which the root file system is currently mounted. If the root
    # has been changed with -r , the respective device is used. If the
    # variable ROOT is omitted, the root device setting contained in the
    # kernel image is used. It can be changed with the rdev program.
    root=/dev/hda3

    # Enables map compaction:
    # Tries to merge read requests for adjacent sectors into a single
    # read request. This drastically reduces load time and keeps the map
    # smaller. Using COMPACT is especially recommended when booting from a
    # floppy disk.
    # compact

    # Default menu for Debian. (Using the images from debian-bootscreen)
    # from Philipp Wolfer <phil@newswriter.org>.
    bitmap=/usr/share/lilo/contrib/debian.bmp
    bmp-colors=1,,0,2,,0
    bmp-table=120p,173p,1,15,17
    bmp-timer=254p,432p,1,0,0

    # Install the specified file as the new boot sector.
    # LILO supports built in boot sectory, you only need
    # to specify the type, choose one from 'text', 'menu' or 'bitmap'.
    # new: install=bmp old: install=/boot/boot-bmp.b
    # new: install=text old: install=/boot/boot-text.b
    # new: install=menu old: install=/boot/boot-menu.b or boot.b
    # default: 'menu' is default, unless you have a bitmap= line
    # Note: install=bmp must be used to see the bitmap menu.
    # install=menu
    install=bmp

    # Specifies the number of _tenths_ of a second LILO should
    # wait before booting the first image. LILO
    # doesn't wait if DELAY is omitted or if DELAY is set to zero.
    # delay=20

    # Prompt to use certaing image. If prompt is specified without timeout,
    # boot will not take place unless you hit RETURN
    prompt
    timeout=50

    # Specifies the location of the map file. If MAP is
    # omitted, a file /boot/map is used.
    map=/boot/map

    # Specifies the VGA text mode that should be selected when
    # booting. The following values are recognized (case is ignored):
    # NORMAL select normal 80x25 text mode.
    # EXTENDED select 80x50 text mode. The word EXTENDED can be
    # abbreviated to EXT.
    # ASK stop and ask for user input (at boot time).
    # <number> use the corresponding text mode. A list of available modes
    # can be obtained by booting with vga=ask and pressing [Enter].
    vga=normal

    # These images were automagically added. You may need to edit something.

    image=/boot/vmlinuz-2.4.20-P4SMP
            label="DEB 2.4.20-1"
            read-only

    image=/boot/vmlinuz-2.4.20-P4SMP-Highmem
            label="DEB 2.4.20-2"
            read-only

    image=/boot/vmlinuz-2.6.2-SMP
            label="DEB 2.6.2-5"
            read-only

    # If you have another OS on this machine (say DOS),
    # you can boot if by uncommenting the following lines
    # (Of course, change /dev/hda2 to wherever your DOS partition is.)
    # other=/dev/hda2
    # label=dos 

    -- 
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
  • Next message: Strop Alexander: "Newbie: Back to installation part...dselect"

    Relevant Pages

    • Re: lilo hangs at "Resolve invalid VolumeIDs" ?!
      ... Try with lilo -T vol-ID. ... > # Specifies the device that should be mounted as root. ... > # Install the specified file as the new boot sector. ...
      (Debian-User)
    • Re: lost password Please HELP
      ... > enter the "single" user input at the LiLo prompt. ... > Have no Linux boot disc. ... > recover from a lost root password. ...
      (comp.os.linux.security)
    • Re: getting LILO to boot windows
      ... >> If LILO or Grub is installed in MBR, ... >Here's what happens when I try to use the windows tools to get it to boot. ... This is where Lilo installs its boot ... ># Specifies the device that should be mounted as root. ...
      (comp.os.linux.misc)
    • lost password Please HELP
      ... enter the "single" user input at the LiLo prompt. ... Have no Linux boot disc. ... recover from a lost root password. ...
      (comp.os.linux.security)
    • lilo hangs at "Resolve invalid VolumeIDs" ?!
      ... Having a few hassles with lilo 22.5.8 - I first noticed the problem after building a new kernel. ... Was just about ready to boot it, ran lilo to complete off the upgrade and it just hangs there. ... # Specifies the device that should be mounted as root. ...
      (Debian-User)