[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

AW: Discarding improperly nested partition ?

From: Sebastian Lemke [infoworxx]
Subject: AW: Discarding improperly nested partition ?
Date: Mon, 30 Jan 2012 11:51:10 +0100


that´s right - sda2 is the first member of md0. So your explanation is
completely right.

Even if I could ignore the error - the question is : Is there a way to do it
better ?
It´s is a "fresh" system - at the moment there is no problem to change the


> -----Ursprüngliche Nachricht-----
> Von: address@hidden [mailto:help-grub-
> address@hidden Im Auftrag von Jordan Uggla
> Gesendet: Samstag, 28. Januar 2012 01:22
> An: Sebastian Lemke [infoworxx]
> Cc: address@hidden
> Betreff: Re: Discarding improperly nested partition ?
> On Fri, Jan 27, 2012 at 12:57 AM, Sebastian Lemke [infoworxx]
> <address@hidden> wrote:
> > /usr/sbin/grub-probe: warn: Discarding improperly nested partition
> > (hd0,gpt2,gpt4)
> This means that grub is detecting that (hd0,gpt2) (the second gpt
partition on
> the first disk, or "sda2") contains a GPT label which defines partitions
> sda2 is a partition itself, this is a "nested partition table"). It also
sees that one
> of the partitions in the nested partition table, the fourth gpt partition,
> improperly nested. My guess would be that "improper" here means that the
> partition ends (or starts and ends) beyond the size of sda2. This is
> explained by further output quoted below:
> > "blkid" output:
> >
> ________________________________________________________________
> > Device           UUID                                   TYPE
> > /dev/md0p1       4d377ecd-4d50-4a46-a836-a70eba197f1e   ext2
> > /dev/md0p2       d7652bab-a7eb-408d-ab76-346b89ba6642   swap
> > /dev/md0p3       a5bf88f4-7fd6-44e9-b26c-df5de3557367   ext3
> Since your have an array which itself is partitioned (in addition to being
> up of member partitions, these are two different things which can be
> with each other) my guess is that since sda2 is the first member of this
> and presumably the mdraid metadata is not stored at the beginning of the
> member partitions, the GPT label (minus the backup) is contained entirely
> within the beginning of sda2.
> This makes it appear as though sda2 is itself partitioned, when it's
really just
> one member of a partitioned array. This partition table is
> *not* valid for sda2, only for md0, hence grub correctly finding something
> wrong.
> In short, grub is seeing something that would normally be a sign of
> in most cases, but in your case is probably fine. Grub is discarding the
> data (and should have no problem reading the valid data) so nothing should
> wrong. I believe you can safely ignore this warning.
> --
> Jordan Uggla
> _______________________________________________
> Help-grub mailing list
> address@hidden

Attachment: smime.p7s
Description: S/MIME cryptographic signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]