FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian User

 
 
LinkBack Thread Tools
 
Old 06-05-2011, 07:30 PM
Felix Natter
 
Default 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@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>
---------------------

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@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 87r578t6tg.fsf@smail.inf.fh-brs.de">http://lists.debian.org/87r578t6tg.fsf@smail.inf.fh-brs.de
 
Old 06-05-2011, 11:59 PM
Tom H
 
Default Problems installing grub/lilo with RAID1 on /

On Sun, Jun 5, 2011 at 3:30 PM, Felix Natter
<felix.natter@smail.inf.fh-brs.de> wrote:


> I am trying to install squeeze (from live DVD[1]) with a RAID1 root
> filesystem (/dev/md0).
>
> There is an error when running grub-install:
> Jun 5 18:38:18 grub-installer: error: Running 'grub-install --no-floppy --force "/dev/sda"' failed.
>
> 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>

Does "/target/etc/mtab" exist and is it correct?


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

On both Debian and Ubuntu, I used to be able to run "dpkg-reconfigure
grub-pc", choose md0, sda, and sdb, and grub would be installed on all
three. For a while now (I can't remember for how long), installing to
md0's failed.


> 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:22:00 in-target: Running lilo...
> 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)

What do RV and GAI mean? I've googled both and not foudn anything to
help. "0.90" and "1.2" are mdraid metadata versions. Were these disks
previously in another array and do you now have two types of metada on
them?


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: BANLkTimN946v25ZojXqTGFZMERDtnCCRvg@mail.gmail.com ">http://lists.debian.org/BANLkTimN946v25ZojXqTGFZMERDtnCCRvg@mail.gmail.com
 
Old 06-06-2011, 06:16 PM
Felix Natter
 
Default Problems installing grub/lilo with RAID1 on /

Tom H <tomh0665@gmail.com> writes:

hello Tom,

> On Sun, Jun 5, 2011 at 3:30 PM, Felix Natter
> <felix.natter@smail.inf.fh-brs.de> wrote:
>
>
>> I am trying to install squeeze (from live DVD[1]) with a RAID1 root
>> filesystem (/dev/md0).
>>
>> There is an error when running grub-install:
>> Jun 5 18:38:18 grub-installer: error: Running 'grub-install --no-floppy --force "/dev/sda"' failed.
>>
>> 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>
>
> Does "/target/etc/mtab" exist and is it correct?

Seems like it's correct:
----------------------
/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
----------------------

>
>> 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 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.
>
> On both Debian and Ubuntu, I used to be able to run "dpkg-reconfigure
> grub-pc", choose md0, sda, and sdb, and grub would be installed on all

This results in the same error.

> three. For a while now (I can't remember for how long), installing to
> md0's failed.

Is this a known bug or unsupported?

>
>> 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:22:00 in-target: Running lilo...
>> 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)
>
> What do RV and GAI mean? I've googled both and not foudn anything to
> help. "0.90" and "1.2" are mdraid metadata versions. Were these disks
> previously in another array and do you now have two types of metada on
> them?

No, I did not change any hardware config before reinstalling with
squeeze. I also had a RAID1 root fs with those two disks before.

I think it is justified to file a bug against debian-installer.

Thanks,
--
Felix Natter


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 87zkluddvb.fsf@smail.inf.fh-brs.de">http://lists.debian.org/87zkluddvb.fsf@smail.inf.fh-brs.de
 
Old 06-06-2011, 06:59 PM
"tv.debian@googlemail.com"
 
Default Problems installing grub/lilo with RAID1 on /

Hi,

06/06/2011 20:16, Felix Natter wrote:
> Tom H <tomh0665@gmail.com> writes:
>
> hello Tom,
>
>> On Sun, Jun 5, 2011 at 3:30 PM, Felix Natter
>> <felix.natter@smail.inf.fh-brs.de> wrote:
>>
>>
>>> I am trying to install squeeze (from live DVD[1]) with a RAID1 root
>>> filesystem (/dev/md0).
>>>
>>> There is an error when running grub-install:
>>> Jun 5 18:38:18 grub-installer: error: Running 'grub-install --no-floppy --force "/dev/sda"' failed.
>>>
>>> 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>
>>
>> Does "/target/etc/mtab" exist and is it correct?
>
> Seems like it's correct:
> ----------------------
> /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
> ----------------------
>
>>
>>> 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 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.
>>
>> On both Debian and Ubuntu, I used to be able to run "dpkg-reconfigure
>> grub-pc", choose md0, sda, and sdb, and grub would be installed on all
>
> This results in the same error.
>
>> three. For a while now (I can't remember for how long), installing to
>> md0's failed.
>
> Is this a known bug or unsupported?

There have been a longstanding non-reliability of grub-pc with /boot on
raid1, have a look at the bug tracker and you'll find several reports
revolving around /boot or / on raid1 (#624232 is mine). Problem is
solved with the recent "mduuid" patch that went into grub-pc 1.99 (is in
Wheezy/Testing). But I don't know if your problem is related to this or
due to the metadata weirdness (see below).


>
>>
>>> 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:22:00 in-target: Running lilo...
>>> 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)
>>
>> What do RV and GAI mean? I've googled both and not foudn anything to
>> help. "0.90" and "1.2" are mdraid metadata versions. Were these disks
>> previously in another array and do you now have two types of metada on
>> them?
>
> No, I did not change any hardware config before reinstalling with
> squeeze. I also had a RAID1 root fs with those two disks before.
>
> I think it is justified to file a bug against debian-installer.
>
> Thanks,

Since the different metadata were not stored at the place, it may be
possible that your disks retained the old metadata (0.90) together with
the new ones (1.2). Did you "mdadm --zero-superblock" your volumes et
some point before doing a new install ? What does "mdadm --examine"
$(raid_member) tell you ?


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4DED238A.8020402@googlemail.com">http://lists.debian.org/4DED238A.8020402@googlemail.com
 
Old 06-06-2011, 10:08 PM
Tom H
 
Default Problems installing grub/lilo with RAID1 on /

>Tom H <tomh0665@gmail.com> writes:
>> On Sun, Jun 5, 2011 at 3:30 PM, Felix Natter
>> <felix.natter@smail.inf.fh-brs.de> wrote:
>>>
>>> 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:22:00 in-target: Running lilo...
>>> 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)
>>
>> What do RV and GAI mean? I've googled both and not foudn anything to
>> help. "0.90" and "1.2" are mdraid metadata versions. Were these disks
>> previously in another array and do you now have two types of metada on
>> them?

> No, I did not change any hardware config before reinstalling with
> squeeze. I also had a RAID1 root fs with those two disks before.

There may be more to your problem than this but you definitely have a metadata problem.

Some more googing yielded RV and GAI as "raid version" and "get array info" so your previous mdraid metadata must've been v0.90 and you're new metadata's the Squeeze d-i default, v1.2.

Since they're written to different parts of the HD, they can co-exist and must be confusing grub and lilo.

I only know how to remove all metadata (with "--zero-superblock") so I have no idea how to fix your problem short of backing up your install, recreating your array, and restoring the install... Sorry.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: DE3B97F0-5140-4C39-A2F2-B7B9D2C664AD@gmail.com">http://lists.debian.org/DE3B97F0-5140-4C39-A2F2-B7B9D2C664AD@gmail.com
 
Old 06-07-2011, 07:52 PM
Felix Natter
 
Default Problems installing grub/lilo with RAID1 on /

Tom H <tomh0665@gmail.com> writes:

>>Tom H <tomh0665@gmail.com> writes:
>>> On Sun, Jun 5, 2011 at 3:30 PM, Felix Natter
>>> <felix.natter@smail.inf.fh-brs.de> wrote:
>>>>
>>>> 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:22:00 in-target: Running lilo... 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)
>>>
>>> What do RV and GAI mean? I've googled both and not foudn anything to
>>> help. "0.90" and "1.2" are mdraid metadata versions. Were these
>>> disks previously in another array and do you now have two types of
>>> metada on them?
>
>> No, I did not change any hardware config before reinstalling with
>> squeeze. I also had a RAID1 root fs with those two disks before.

hi Tom,

> There may be more to your problem than this but you definitely have a
> metadata problem.
>
> Some more googing yielded RV and GAI as "raid version" and "get array
> info" so your previous mdraid metadata must've been v0.90 and you're
> new metadata's the Squeeze d-i default, v1.2.
>
> Since they're written to different parts of the HD, they can co-exist
> and must be confusing grub and lilo.
>
> I only know how to remove all metadata (with "--zero-superblock") so I
> have no idea how to fix your problem short of backing up your install,
> recreating your array, and restoring the install... Sorry.

No change after I called:
mdadm --zero-superblock /dev/sda2
mdadm --zero-superblock /dev/sdb2

Next I tried to create the array directly with mdadm and bypassing
partman (d-i partitioner). That way, I can install grub when creating
the array with old metadata:

$ mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sda2
/dev/sdb2 --metadata=0.9

However, when I reboot the system, I get:
-----------
Gave up waiting for root device. Common Problems:
- Boot args (cat /proc/cmdline): check root=, rootdelay=
- Missing modules (cat /proc/modules; ls /dev)
- ALERT! /dev/md0 does not exist. Dropping to a shell!
-----------

Here is the fstab from the installed system:
-----------
# /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=0a94e4b3-9b3b-4290-9fa3-9e8ed167136a / ext3 errors=remount-ro 0 1
# swap was on /dev/sdb1 during installation
UUID=ce46b046-fce5-4298-a06e-2b3680406eaa 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
-----------

Could it be that the /dev/md0 I created manually is not permanent
because d-i didn't create it (although the manually created /dev/md0
could be seen in partman)?

Thank you!
--
Felix Natter


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 87ei35wh9g.fsf@smail.inf.fh-brs.de">http://lists.debian.org/87ei35wh9g.fsf@smail.inf.fh-brs.de
 
Old 06-08-2011, 07:27 PM
Felix Natter
 
Default Problems installing grub/lilo with RAID1 on /

"tv.debian@googlemail.com" <tv.debian@googlemail.com> writes:

> Hi,
>
> 06/06/2011 20:16, Felix Natter wrote:
>> Tom H <tomh0665@gmail.com> writes:
>>
>> hello Tom,
>>
>>> On Sun, Jun 5, 2011 at 3:30 PM, Felix Natter
>>> <felix.natter@smail.inf.fh-brs.de> wrote:
>>>
>>>
>>>> I am trying to install squeeze (from live DVD[1]) with a RAID1 root
>>>> filesystem (/dev/md0).
>>>>
>>>> There is an error when running grub-install:
>>>> Jun 5 18:38:18 grub-installer: error: Running 'grub-install --no-floppy --force "/dev/sda"' failed.
>>>>
>>>> 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>
>>>
>>> Does "/target/etc/mtab" exist and is it correct?
>>
>> Seems like it's correct:
>> ----------------------
>> /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
>> ----------------------
>>
>>>
>>>> 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 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.
>>>
>>> On both Debian and Ubuntu, I used to be able to run "dpkg-reconfigure
>>> grub-pc", choose md0, sda, and sdb, and grub would be installed on all
>>
>> This results in the same error.
>>
>>> three. For a while now (I can't remember for how long), installing to
>>> md0's failed.
>>
>> Is this a known bug or unsupported?
>
> There have been a longstanding non-reliability of grub-pc with /boot on
> raid1, have a look at the bug tracker and you'll find several reports
> revolving around /boot or / on raid1 (#624232 is mine). Problem is
> solved with the recent "mduuid" patch that went into grub-pc 1.99 (is in
> Wheezy/Testing). But I don't know if your problem is related to this or
> due to the metadata weirdness (see below).

Thanks for the suggestion, it all works fine with today's testing
(net) installer!

Best Regards!
--
Felix Natter


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 8762og86on.fsf@smail.inf.fh-brs.de">http://lists.debian.org/8762og86on.fsf@smail.inf.fh-brs.de
 

Thread Tools




All times are GMT. The time now is 08:42 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org