LILO not working with root-LVM-RAID setup

Bug #111406 reported by Greg Turnquist
6
Affects Status Importance Assigned to Milestone
lilo (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: lilo

I am running Feisty on a 32-bit system, with root-on-LVM2-on-RAID1.

A detailed description is located at http://ubuntuforums.org/showthread.php?p=2560360#post2560360. It lists various checks I have done. Though the problem is manifested through LILO, I'm not convinced this is necessarily LILO's fault.

Revision history for this message
Greg Turnquist (gregturn) wrote : Detailed LILO output
Download full text (4.1 KiB)

I re-reran LILO with "-v5" to get more details about this failure to run on Feisty.
[code]
gregturn@startrek:/boot$ sudo lilo -v5
LILO version 22.6.1, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2004 John Coffman
Released 17-Nov-2004, and compiled at 13:54:18 on Mar 7 2007
Ubuntu

Warning: LBA32 addressing assumed
raid_setup: dev=0011 rdev=0900
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=00022E56 name=/dev/hdc
geo_query_dev: device=1600
lookup_dev: number=1600
lookup_dev: number=0300
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=0003CA77 *PT=080778B6
bios_dev: (0x80) vol-ID=00022E56 *PT=0807786E
bios_dev: PT match found 1 match (0x80)
pf_hard_disk_scan: (22,64) /dev/hdd
pf_hard_disk_scan: (22,65) /dev/hdd1
lookup_dev: number=1640
lookup_dev: number=1640
pf: dev=1640 id=0003CA77 name=/dev/hdd
geo_query_dev: device=1640
lookup_dev: number=1640
exit geo_query_dev
bios_dev: device 1640
lookup_dev: number=1640
bios_dev: masked device 1640, which is /dev/hdd
bios_dev: geometry check found 0 matches
bios_dev: (0x81) vol-ID=0003CA77 *PT=080778B6
bios_dev: (0x80) vol-ID=00022E56 *PT=0807786E
bios_dev: PT match found 1 match (0x81)
pf_hard_disk_scan: (9,0) /dev/md0
pf_hard_disk_scan: (254,0) /dev/dm-0
lookup_dev: number=FE00
Caching device /dev/evms/.nodes/hdd1 (0xFE00)
Warning: '/proc/partitions' does not match '/dev' directory structure.
    Name change: '/dev/dm-0' -> '/dev/evms/.nodes/hdd1'
pf_hard_disk_scan: (254,1) /dev/dm-1
lookup_dev: number=FE01
Caching device /dev/evms/.nodes/hdc1 (0xFE01)
    Name change: '/dev/dm-1' -> '/dev/evms/.nodes/hdc1'
pf_hard_disk_scan: (254,2) /dev/dm-2
lookup_dev: number=FE02
Caching device /dev/evms/lvm2/startrekvg/boot (0xFE02)
    Name change: '/dev/dm-2' -> '/dev/evms/lvm2/startrekvg/boot'
pf_hard_disk_scan: (254,3) /dev/dm-3
lookup_dev: number=FE03
Caching device /dev/evms/lvm2/startrekvg/root (0xFE03)
    Name change: '/dev/dm-3' -> '/dev/evms/lvm2/startrekvg/root'
pf_hard_disk_scan: (254,4) /dev/dm-4
lookup_dev: number=FE04
Caching device /dev/evms/lvm2/startrekvg/swap (0xFE04)
    Name change: '/dev/dm-4' -> '/dev/evms/lvm2/startrekvg/swap'
pf_hard_disk_scan: (254,5) /dev/dm-5
lookup_dev: number=FE05
Caching device /dev/mapper/startrekvg-swap (0xFE05)
    Name change: '/dev/dm-5' -> '/dev/mapper/startrekvg-swap'
pf_hard_disk_scan: (254,6) /dev/dm-6
lookup_dev: number=FE06
Caching device /dev/mapper/startrekvg-boot (0xFE06)
    Name change: '/dev/dm-6' -> '/dev/mapper/startrekvg-boot'
pf_hard_disk_scan: (254,7) /dev/dm-7
lookup_dev: number=FE07
Caching device /dev/mapper/startrekvg-root (0xFE07)
    Name change: '/dev/dm-7' -> '/dev/mapper/startrekvg-root'
  1600 00022E56 /dev/hdc
  1640 0003CA77 /dev/hdd
pf_hard_disk_scan: ndevs=2
  1600 00022E56 /dev/hdc
  1640 0003CA77 /dev/hdd
Resolve invalid VolumeIDs
Resolve duplicate VolumeIDs
  1600 00022E56 /dev/hdc
  1640 0003CA77 /dev/hdd
device cod...

Read more...

Revision history for this message
Andreas Moog (ampelbein) wrote : Old standing report

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thank you for taking the time to report this bug and helping to make
Ubuntu better. You reported this bug a while ago and there hasn't been
any activity in it recently. We were wondering is this still an issue
for you? Can you try with latest Ubuntu release? Thanks in advance.

 status incomplete
 assignee <email address hidden>
 subscribe

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkit5DcACgkQ06FgkPZwicSA6gCgirp2el/jXrNpjtYzEFnG5mmr
96gAn1jWbVjRkegHNUswvu6+CCyHgx7o
=k3uh
-----END PGP SIGNATURE-----

Changed in lilo:
assignee: nobody → andreas-moog
status: New → Incomplete
Revision history for this message
Greg Turnquist (gregturn) wrote : Re: [Bug 111406] Old standing report

I haven't run into this problem since.

Greg

-----Original Message-----
>From: Andreas Moog <email address hidden>
>Sent: Aug 21, 2008 5:55 PM
>To: <email address hidden>
>Subject: [Bug 111406] Old standing report
>
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Thank you for taking the time to report this bug and helping to make
>Ubuntu better. You reported this bug a while ago and there hasn't been
>any activity in it recently. We were wondering is this still an issue
>for you? Can you try with latest Ubuntu release? Thanks in advance.
>
> status incomplete
> assignee <email address hidden>
> subscribe
>
>
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.4.9 (GNU/Linux)
>Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
>iEYEARECAAYFAkit5DcACgkQ06FgkPZwicSA6gCgirp2el/jXrNpjtYzEFnG5mmr
>96gAn1jWbVjRkegHNUswvu6+CCyHgx7o
>=k3uh
>-----END PGP SIGNATURE-----
>
>** Changed in: lilo (Ubuntu)
> Assignee: (unassigned) => Andreas Moog (andreas-moog)
> Status: New => Incomplete
>
>--
>LILO not working with root-LVM-RAID setup
>https://bugs.launchpad.net/bugs/111406
>You received this bug notification because you are a direct subscriber
>of the bug.

Revision history for this message
Andreas Moog (ampelbein) wrote : Closing your Bug since its fixed.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This bug report is being closed due to your last comment regarding this
being fixed. For future reference you can manage the status of your own
bugs by clicking on the current status in the yellow line and then
choosing a new status in the revealed drop down box. You can learn more
about bug statuses at https://wiki.ubuntu.com/Bugs/Status . Thank you
again for taking the time to report this bug and helping to make Ubuntu
better. Feel free to submit any future bugs you may find.

 status invalid
 assignee nobody

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkiuep4ACgkQ06FgkPZwicQu9ACgrd4F9ujkRmIhdSN0rJsuIDU4
TwsAoM/7rWvGs/FVdfVRxUaJ2Zmf5wb/
=uRm2
-----END PGP SIGNATURE-----

Changed in lilo:
assignee: andreas-moog → nobody
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.