From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: The development of GRUB 2 <grub-devel@gnu.org>,
Marco d'Itri <md@Linux.IT>
Subject: Re: grub-probe seems to be having problems
Date: Tue, 20 Mar 2012 11:28:18 +0100 [thread overview]
Message-ID: <4F685BC2.1030008@gmail.com> (raw)
In-Reply-To: <20120319212850.GE10301@caffeine.csclub.uwaterloo.ca>
On 19.03.2012 22:28, Lennart Sorensen wrote:
> On Fri, Mar 09, 2012 at 03:37:57PM -0500, Lennart Sorensen wrote:
>> Interestingly after poking at reading all the disks and poking mdadm
>> --examine and --detail, now grub-prob likes md1, but still dislikes md0.
>>
>> root@rceng03new:/tmp# /usr/sbin/grub-probe --device-map= --target=abstraction --device /dev/md1
>> diskfilter mdraid1x raid5rec
>> root@rceng03new:/tmp# /usr/sbin/grub-probe --device-map= --target=abstraction --device /dev/md0
>> /usr/sbin/grub-probe: error: Couldn't find physical volume `(null)'. Check your device.map.
>>
>> md1 was failing before with the same grub code.
>>
>> I don't get it. I wonder if there is any known issues in 2.6.32 kernel
>> and/or mdadm - v3.1.4 - 31st August 2010
> Any suggestion for how to try and debug this myself, like which
> file/function to start debuging at? I would like to put this machine
> in to production use soon, but I would also like to take this chance to
> fix the bug in grub first.
There is no need to debug. I know exactly why GRUB is confused: because
as far as my understanding goes the superblock makes no sense (details
in previous mail). What we need is that someone familiar with md tells
me how this sector should be interpreted.
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
next prev parent reply other threads:[~2012-03-20 10:28 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
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 [this message]
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=4F685BC2.1030008@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.org \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=md@Linux.IT \
/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.