From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Fwd: Re: Grub not working under software RAID
Date: Fri, 01 Apr 2011 18:43:11 +0200 [thread overview]
Message-ID: <4D96009F.9030309@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]
Forwarding for reference.
-------- Original Message --------
Subject: Re: Grub not working under software RAID
Date: Fri, 01 Apr 2011 11:23:37 -0400
From: Sean Porth <sporth@tortus.com>
To: Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com>
On 04/01/11 11:07, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> On 01.04.2011 16:59, Sean Porth wrote:
>> backup:~# cat /proc/mdstat
>>>> Personalities : [linear] [raid1]
>>>> md1 : active raid1 sdb3[1] sda3[0]
>>>> 945513536 blocks [2/2] [UU]
>>>>
>>>> md0 : active raid1 sdb1[1] sda1[0]
>>>> 29294400 blocks [2/2] [UU]
>>
> How do you access those disks? Do you have /dev/sd[ab][13]. Is it some
> kind of VM? If none of /dev/sd[ab][13] /dev/sd[ab] exist it probably
> means that there is a bug in udev. Mdraid detection is probably done in
> kernel and so presence of nodes under /dev is irrelevant. But any action
> attempted with devices from userspace is obviously bound to fail.
>
I manually created the device nodes for /dev/sda and /dev/sdb. I then
reran grub-mkdevicemap and now the device.map had devices in it.
Rerunning grub-install /dev/md0 now reports no errors.
So it does seem to be a bug with udev and the squeeze upgrade so I'll
move this over to a Debian bug.
Thanks for your help!
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
reply other threads:[~2011-04-01 16:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4D96009F.9030309@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.org \
/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.