From: NeilBrown <neilb@suse.de>
To: jlcenter@comcast.net
Cc: linux-raid@vger.kernel.org
Subject: Re: grub-probe seems to be having problems
Date: Thu, 22 Mar 2012 13:46:44 +1100 [thread overview]
Message-ID: <20120322134644.4ab6aa3a@notabene.brown> (raw)
In-Reply-To: <529358656.324923.1332383237382.JavaMail.root@sz0019a.westchester.pa.mail.comcast.net>
[-- Attachment #1: Type: text/plain, Size: 1888 bytes --]
On Thu, 22 Mar 2012 02:27:17 +0000 (UTC) jlcenter@comcast.net wrote:
> Any takers? -John
Without the "details in the previous mail", there isn't much to take...
NeilBrown
>
> ----- Forwarded Message -----
> 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>
> Sent: Tuesday, March 20, 2012 6:28:18 AM
> Subject: Re: grub-probe seems to be having problems
>
> 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.
>
>
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2012-03-22 2:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4F685BC2.1030008@gmail.com>
2012-03-22 2:27 ` Fwd: grub-probe seems to be having problems jlcenter
2012-03-22 2:46 ` NeilBrown [this message]
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=20120322134644.4ab6aa3a@notabene.brown \
--to=neilb@suse.de \
--cc=jlcenter@comcast.net \
--cc=linux-raid@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).