From: Goswin von Brederlow <goswin-v-b@web.de>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Raid5 regression
Date: Wed, 04 May 2011 13:23:40 +0200 [thread overview]
Message-ID: <871v0ebtfn.fsf@frosties.localnet> (raw)
In-Reply-To: <4DC067F1.4060901@cfl.rr.com> (Phillip Susi's message of "Tue, 03 May 2011 16:39:13 -0400")
Phillip Susi <psusi@cfl.rr.com> writes:
> After enabling raid debug output and then loading mdraid09.mod, I can
> see that it is scanning and detecting the superblock on both (hdx) and
> (hdx,msdos1).
>
> On 5/3/2011 10:33 AM, Phillip Susi wrote:
>> After upgrading an Ubuntu server from Maverick to Natty ( grub2 version
>> 1.99-rc1-13ubuntu3 ) the system no longer will boot. Grub complains
>> about the raid5 array:
>>
>> error: Found two disks with the index 0 for RAID md0
>> error: Found two disks with the index 1 for RAID md0
>> error: Found two disks with the index 2 for RAID md0
>> error: Superfluous RAID member (4 found)
>> error: Unknown filesystem
>>
>> This is a 4 disk raid5 array that mdadm still recognizes and looks fine,
>> with each disk having IDs 0 through 3 respectively. Despite the fact
>> that it complains about the raid, it still shows the LVM logical volumes
>> in the output of ls. The array is the sole LVM PV.
>>
>> Bug filed at https://launchpad.net/bugs/776422. Any hints on how to
>> proceed with debugging this? Is there a way to check what modules are
>> built into the core image from the rescue shell?
That is a problem mdadm has (had?) too. The problem arises when the
alignment of the partition and its size causes the metadata of the
partition to be also valid for the disk (as in the partition ends
exactly at the end of the disk).
One of the reasons not to use metadata at the end of the disk.
MfG
Goswin
next prev parent reply other threads:[~2011-05-04 11:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-03 14:33 Raid5 regression Phillip Susi
2011-05-03 15:30 ` Phillip Susi
2011-05-03 20:39 ` Phillip Susi
2011-05-03 21:15 ` Jérôme Poulin
2011-05-04 6:17 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-05-04 11:23 ` Goswin von Brederlow [this message]
2011-05-04 13:49 ` Phillip Susi
2011-05-04 15:09 ` Phillip Susi
2011-05-04 15:21 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-05-04 18:37 ` Phillip Susi
2011-05-04 19:01 ` Goswin von Brederlow
2011-05-04 20:23 ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-05-05 14:38 ` Phillip Susi
2011-05-05 16:57 ` Goswin von Brederlow
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=871v0ebtfn.fsf@frosties.localnet \
--to=goswin-v-b@web.de \
--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.