Problems installing grub/lilo with RAID1 on /

hello,

I am trying to install squeeze (from live DVD[1]) with a 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@xxxxxxx>
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@xxxxxxx>
---------------------

Should I report this as d-i bug?

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 grub-bug?

Is there a way to tell grub-install that this is a ext3 filesystem?

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)
---------------------

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)
---------------------

Please tell me if you need additional information.

Thank you!
--
Felix Natter


--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
Archive: http://lists.debian.org/87r578t6tg.fsf@xxxxxxxxxxxxxxxxxxx

Relevant Pages

  • Re: A newbie question - trying to resize a given 15GB vdi file to a bigger one
    ... Therefore - went ahead and read about resizing partitions.. ... A "folder" may represent a directory in a filesystem, ... but it is not needed by the kernel. ... Although most newbies opt to install everything in a single root ...
    (comp.os.linux.setup)
  • Re: Newbie how do I designate a disk to install software from the DVD?
    ... You do not install software "on other disks". ... Digital Research's CP/M operating system, ... sitting on the root filesystem - i.e. the main filesystem. ... directories in the root directory (or of nested directories in those ...
    (comp.os.linux.misc)
  • Re: /var corrupted.....
    ... I may have totally destroyed my /var filesystem at this point. ... I've seen plenty of threads from folks having lost theirs in some form or fashion, and the solution always seems to be "reinstall everything". ... I go to the port dir and `make install`, thinking it would reinstall it and all its deps. ...
    (freebsd-questions)
  • Re: Advice on Partitioning
    ... I have not yet decided which distribution to install and at ... directories in the encrypted data filesystem. ... With regards to the bootloader, my preference is to have each linux ...
    (alt.os.linux)
  • Re: Rebuilding kernel (2.6.14.4)
    ... > install of FC4. ... > Mounted /proc filesystem ... > Mounting root filesystem ...
    (Fedora)