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:


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to