From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Cc: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Subject: Re: grub-probe seems to be having problems
Date: Thu, 01 Mar 2012 21:07:34 +0100 [thread overview]
Message-ID: <4F4FD706.7030204@gmail.com> (raw)
In-Reply-To: <20120301194758.GE22241@caffeine.csclub.uwaterloo.ca>
On 01.03.2012 20:47, Lennart Sorensen wrote:
> root@rceng03new:~# /usr/sbin/grub-probe --device /dev/md1 --target=partmap
> /usr/sbin/grub-probe: error: disk `mduuid/dc00bd3a0e9491bb0b66fa8b9246c2e8' not found.
Is the uuid correct?
> That seems wrong.
>
> So does:
>
> root@rceng03new:~# /usr/sbin/grub-probe --device /dev/md0 --target=partmap
> /usr/sbin/grub-probe: error: Couldn't find physical volume `(null)'. Check your device.map.
The problem is that code stops scanning as soon as it detects enough
devices to read from RAID.
> root@rceng03new:~# cat /proc/mdstat
> Personalities : [raid1] [raid6] [raid5] [raid4]
> md1 : active raid5 sdd3[4] sdc3[3](F) sda3[0] sdb3[1]
> 284773376 blocks super 1.2 level 5, 512k chunk, algorithm 2 [3/3] [UUU]
>
> md0 : active raid1 sdd2[2] sda2[0] sdb2[1]
> 976884 blocks super 1.2 [3/3] [UUU]
>
> unused devices:<none>
>
> grub-install never seems to generate a device.map file anymore either,
> although --recheck happily deletes it for me.
>
> What is supposed to generate the /boot/grub/device.map these days?
Nothing, it's not used by default anymore and its main use is manual
override.
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
next prev parent reply other threads:[~2012-03-01 20:07 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 19:47 grub-probe seems to be having problems Lennart Sorensen
2012-03-01 20:04 ` Lennart Sorensen
2012-03-01 20:07 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2012-03-01 20:15 ` Lennart Sorensen
2012-03-01 20:19 ` Lennart Sorensen
2012-03-03 22:00 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-05 20:07 ` Lennart Sorensen
2012-03-05 23:10 ` Lennart Sorensen
2012-03-08 17:46 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-08 19:01 ` Lennart Sorensen
2012-03-08 19:14 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-08 20:15 ` Lennart Sorensen
2012-03-08 23:37 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-09 14:53 ` Lennart Sorensen
2012-03-09 0:11 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-09 15:39 ` Lennart Sorensen
2012-03-09 15:43 ` Lennart Sorensen
2012-03-09 15:47 ` Lennart Sorensen
2012-03-09 15:48 ` Vladimir 'φ-coder/phcoder' Serbinenko
[not found] ` <20120309160538.GA14853@caffeine.csclub.uwaterloo.ca>
2012-03-09 18:15 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-09 18:39 ` Lennart Sorensen
2012-03-09 20:37 ` Lennart Sorensen
2012-03-19 21:28 ` Lennart Sorensen
2012-03-20 10:28 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-20 19:02 ` Lennart Sorensen
2012-03-20 19:10 ` Vladimir 'φ-coder/phcoder' Serbinenko
2012-03-20 19:13 ` Lennart Sorensen
2012-03-20 19:14 ` Lennart Sorensen
2012-03-20 19:41 ` Lennart Sorensen
2012-03-20 19:11 ` Lennart Sorensen
2012-03-22 2:27 ` Fwd: " jlcenter
2012-03-22 2:46 ` NeilBrown
2012-03-22 17:52 ` Fwd: " jlcenter
2012-03-09 0:24 ` Vladimir 'φ-coder/phcoder' Serbinenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F4FD706.7030204@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.org \
--cc=lsorense@csclub.uwaterloo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.