Bug#629451: debian-installer: grub/lilo-Problems with (SW-)RAID1 root fs
Package: debian-installer
Version: 20110106+squeeze1
Severity: important
Tags: d-i
hello,
I am trying to install squeeze (from live DVD[1]) with a software-RAID1 root
filesystem (/dev/md0).
[1] http://cdimage.debian.org/cdimage/release/current-live/i386/iso-hybrid/debian-live-6.0.1-i386-gnome-desktop.iso
There is an error when running grub-install:
---------------------
Jun 5 18:38:08 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/90linux-distro
Jun 5 18:38:08 50mounted-tests: debug: running subtest /usr/lib/os-probes/mounted/90solaris
Jun 5 18:38:16 grub-installer: info: Installing grub on '/dev/sda'
Jun 5 18:38:16 grub-installer: info: grub-install supports --no-floppy
Jun 5 18:38:16 grub-installer: info: Running chroot /target grub-install --no-floppy --force "/dev/sda"
Jun 5 18:38:18 grub-installer: /usr/sbin/grub-probe: error: no such disk.
Jun 5 18:38:18 grub-installer: Auto-detection of a filesystem of /dev/md0 failed.
Jun 5 18:38:18 grub-installer: Please report this together with the output of "/usr/sbin/grub-probe --device-map=/boot/grub/device.map --target=fs -v /boot/grub" to <bug-grub@gnu.org>
Jun 5 18:38:18 grub-installer: error: Running 'grub-install --no-floppy --force "/dev/sda"' failed.
Jun 5 18:39:51 init: starting pid 361, tty '/dev/tty3': '-/bin/sh'
---------------------
I tried to run it manually:
---------------------
chroot /target grub-install --no-floppy --force /dev/sda
/usr/sbin/grub-probe: error: no such disk.
Auto-detection of a filesystem of /dev/md0 failed.
Please report this together with the output of "/usr/sbin/grub-probe --device-map=/boot/grub/device.map --target=fs -v /boot/grub" to <bug-grub@gnu.org>
---------------------
The output of grub-probe is as follows:
---------------------
chroot /target /usr/sbin/grub-probe --device-map=/boot/grub/device.map --target=fs -v /boot/grub
/usr/sbin/grub-probe: info: the size of hd0 is 488397168.
/usr/sbin/grub-probe: info: the size of hd0 is 488397168.
/usr/sbin/grub-probe: info: the size of hd0 is 488397168.
/usr/sbin/grub-probe: info: the size of hd0 is 488397168.
/usr/sbin/grub-probe: info: the size of hd1 is 488397168.
/usr/sbin/grub-probe: info: the size of hd1 is 488397168.
/usr/sbin/grub-probe: info: the size of hd1 is 488397168.
/usr/sbin/grub-probe: info: the size of hd1 is 488397168.
/usr/sbin/grub-probe: info: the size of hd1 is 488397168.
/usr/sbin/grub-probe: info: the size of hd0 is 488397168.
/usr/sbin/grub-probe: info: the size of hd0 is 488397168.
/usr/sbin/grub-probe: info: the size of hd0 is 488397168.
/usr/sbin/grub-probe: info: the size of hd0 is 488397168.
/usr/sbin/grub-probe: info: the size of hd1 is 488397168.
/usr/sbin/grub-probe: info: the size of hd1 is 488397168.
/usr/sbin/grub-probe: info: the size of hd1 is 488397168.
/usr/sbin/grub-probe: info: the size of hd1 is 488397168.
/usr/sbin/grub-probe: info: the size of hd1 is 488397168.
/usr/sbin/grub-probe: info: changing current directory to /dev.
/usr/sbin/grub-probe: info: changing current directory to mapper.
/usr/sbin/grub-probe: info: opening md0.
/usr/sbin/grub-probe: error: no such disk.
---------------------
Should I report this to bug-grub@gnu.org?
Here is /target/fstab:
---------------------
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# / was on /dev/md0 during installation
<UUID=602edfeb-17c2-4904-a972-ffaa89496418 / ext3 errors=remount-ro 0 1
# swap was on /dev/sdb1 during installation
UUID=5c3c731c-0183-4131-ac01-ffab7b5600d9 none swap sw 0 0
/dev/scd1 /media/cdrom0 udf,iso9660 user,noauto 0 0
/dev/scd0 /media/cdrom1 udf,iso9660 user,noauto 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto 0 0
---------------------
"chroot /target mount" produces:
---------------------
rootfs on / type rootfs (rw)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
none on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
/dev/md0 on /target type ext3 (rw,relatime,errors=remount-ro,data=ordered)
tmpfs on /target/dev type tmpfs (rw,relatime,mode=755)
none on /target/proc type proc (rw,relatime)
/dev/sr1 on /cdrom type iso9660 (ro,relatime)
/dev/sdg1 on /media type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=utf8,shortname=mixed,errors=remount-ro)
---------------------
/target/etc/mtab:
----------------------
/dev/md0 / ext3 rw,relatime,errors=remount-ro,data=ordered 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
none /proc proc rw,relatime 0 0
----------------------
When trying to install lilo (with the debian-installler), I get
"inconsistent raid information" (but the RAID1 (2x 208G) was created
with debian-installer):
---------------------
Jun 5 19:21:57 in-target: Vormals abgewähltes Paket lilo wird gewählt.
Jun 5 19:21:57 in-target: Entpacken von lilo (aus .../lilo/lilo_1%3a22.8-10_i386.deb) ...
Jun 5 19:21:57 in-target: Trigger für man-db werden verarbeitet ...
Jun 5 19:21:58 in-target: Trigger für menu werden verarbeitet ...
Jun 5 19:22:00 in-target: mbr (1.1.10-2) wird eingerichtet ...
Jun 5 19:22:00 in-target: lilo (1:22.8-10) wird eingerichtet ...
Jun 5 19:22:00 in-target: WARNING: Added large-memory option, please run lilo before you reboot
Jun 5 19:22:00 in-target: Running lilo...
Jun 5 19:22:00 in-target: Warning:
Jun 5 19:22:00 in-target: LBA32 addressing assumed
Jun 5 19:22:00 in-target:
Jun 5 19:22:01 in-target: Fatal:
Jun 5 19:22:01 in-target: Inconsistent Raid version information on /dev/md0 (RV=0.90 GAI=1.2)
Jun 5 19:22:01 in-target:
Jun 5 19:22:01 in-target: dpkg: Fehler beim Bearbeiten von lilo (--configure):
Jun 5 19:22:01 in-target: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
Jun 5 19:22:01 in-target: configured to not write apport reports
Jun 5 19:22:01 in-target: Trigger für menu werden verarbeitet ...
Jun 5 19:22:02 in-target: Fehler traten auf beim Bearbeiten von:
Jun 5 19:22:02 in-target: lilo
Jun 5 19:22:02 in-target: E
Jun 5 19:22:02 in-target: :
Jun 5 19:22:02 in-target: Sub-process /usr/bin/dpkg returned an error code (1)
---------------------
I did not change any hardware config before reinstalling with
squeeze. In Lenny, I also had a RAID1 root fs with the same two disks.
The complete logs are here (they are taken from a different installation
attempt compared to the above logs):
http://www2.inf.fh-brs.de/~fnatte2s/syslog
http://www2.inf.fh-brs.de/~fnatte2s/hardware-summary
http://www2.inf.fh-brs.de/~fnatte2s/partman
-- System Information:
Debian Release: 6.0.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.32-5-486
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Please tell me if you need additional information.
Thank You!
--
Felix Natter
Reply to: