Package: lilo
Version: 1:22.6.1-9.3
Severity: important

I replaced a faulty disk and after i am not able to restart the 
system with shutdown -r or reboot. Lilo hangs an on the Lilo Screen.

After power off/on the system starts perfectly.

Its not the first disk that i replaced. Its a System with 2 Disk
and Softraid on a partitoned disk (no LVM)

Here is my lilo.conf:
root=/dev/md0
raid-extra-boot=mbr
map=/boot/map
delay=20
default=Linux
image=/vmlinuz
        label=Linux
        read-only
        initrd=/initrd.img
image=/vmlinuz.old
        label=LinuxOLD
        optional
        initrd=/initrd.img.old

-- System Information:
Debian Release: 4.0
  APT prefers oldstable
  APT policy: (500, 'oldstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-5-686
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro (charmap=ISO-8859-15)

Versions of packages lilo depends on:
ii  debconf            1.5.11etch2           Debian configuration management sy
ii  libc6              2.3.6.ds1-13etch10+b1 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:
  liloconfig/use_current_lilo: true
  lilo/runme: false
  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