[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#409075: marked as done (lilo: major error on lvm root on cciss raid)

Your message dated Thu, 15 Feb 2007 16:04:44 -0700
with message-id <[🔎] 20070215230443.GC28967@colo>
and subject line fixed
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Subject: lilo: major error on lvm root on cciss raid
Package: lilo
Version: 1:22.6.1-9
Severity: important

I believe this bug qualifies as an RC bug.

I have a machine with a cciss raid device in it. Prior versions of lilo
seemed to work. While installing udev and hal, the installation fails.
Manually running lilo produces the following.

test:/home/wt# lilo
Warning: COMPACT may conflict with LBA32 on some systems
Fatal: geo_query_dev HDIO_GETGEO (dev 0x6800): No such device or address
test:/home/wt#

This is really bad as it could leave a system in an unbootable state.
Please let me know what other info I can provide to help.

Thanks,
wt

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages lilo depends on:
ii  debconf                      1.5.11      Debian configuration management 
sy
ii  libc6                        2.3.6.ds1-8 GNU C Library: Shared libraries
ii  libdevmapper1.02             2:1.02.08-1 The Linux Kernel Device Mapper 
use
ii  mbr                          1.1.9-2     Master Boot Record for IBM-PC 
comp

lilo recommends no packages.

-- debconf information:
  liloconfig/fstab_broken:
  liloconfig/banner:
  liloconfig/liloconf_incompatible:
  lilo/bad_bitmap:
  liloconfig/use_lba32: true
  lilo/upgrade:
  liloconfig/liloconf_exists:
  liloconfig/configuring_base:
  lilo/runme: false
  liloconfig/use_current_lilo: true
  liloconfig/wipe_old_liloconf: false
  liloconfig/instruction:
  liloconfig/activate_error:
  liloconfig/select_bitmap: /boot/coffee.bmp
  liloconfig/lilo_error:
  lilo/new-config:
  liloconfig/odd_fstab:
  liloconfig/install_from_root_device: true
  liloconfig/make_active_partition: true
  liloconfig/maintitle:
  liloconfig/mbr_error:
  liloconfig/lilo_warning:
  liloconfig/install_mbr: false
  liloconfig/no_changes:

--- End Message ---
--- Begin Message --- 
Version: 2.6.18.dfsg.1-9

I could reproduce w/ 2.6.17-7 and 2.6.18-8 but not with
2.6.18.dfsg.1-10. I'm pretty sure that this was fixed by one of the
cciss backports i did in -9 (though I didn't test it explicitly), so
marking as closed in that version.

-- 
dann frazier

--- End Message ---
Reply to: