linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roberto Spadim <roberto@spadim.com.br>
To: Chris Murphy <lists@colorremedies.com>
Cc: Linux RAID <linux-raid@vger.kernel.org>
Subject: Re: GPT Table broken on a Raid1
Date: Mon, 24 Sep 2012 15:17:47 -0300	[thread overview]
Message-ID: <CABYL=Try-XyEEXe37RWt4Py8_ewh-mU2kAn1X_75FjrLFcACeQ@mail.gmail.com> (raw)
In-Reply-To: <8AB64122-6198-4A2E-BA49-76BD6AFE7907@colorremedies.com>

i used some disks one or two years ago of 1.5TB, when i boot the disk
for the first time the bios recognized it as a 1TB disk, i change some
bios parameters (removed from automatic) and i could put it to work
with 1.5TB could you check if it´s a bios problem? in my case the disk
appears as 1TB when it booted wrong, and after changing bios options
it goes nice with 1.5TB


2012/9/24 Chris Murphy <lists@colorremedies.com>
>
>
> On Sep 24, 2012, at 3:37 AM, John Robinson wrote:
>
> > On 23/09/2012 19:53, Chris Murphy wrote:
> > [...]
> >> Upon creating a GPT on /dev/md/vol0, identical structures at identical byte offsets are created on /dev/sd[bc] and /dev/md/vol0.
> >>
> >> The primary GPT header says the alternate header is at 0xffdfff.
> >> The alternate GPT header is at 0xffdfff., or sector 16769023, right where it should be.
> >>
> >> Regardless of whether the kernel sees the disk as Intel RAID or a bare disk, it finds the alternate GPT header, and doesn't complain about anything.
> >
> > Yes, it does. It finds the alternate header just fine, according to the offset in the primary header, but warns that it's not at the end of the disc, which is where it expected to find it:
>
> Not for me, is what I meant. Linux 3.5.3-1.fc17 does not complain about the alternate GPT header not being at the end of the disk. However, parted 3.0 does. And gdisk 0.8.5 does not.
>
> Further, it seems increasingly clear as I'm reading the UEFI spec on GPT, that IMSM is incompatible with GPT. The GPT alternate header by spec is expected at the end of the disk, but then IMSM also demands to be in basically the exact same location. And yet Intel is shipping UEFI hardware, which require GPT disks, with IMSM on board that also requires metadata in the same location? How is this not a WTF moment?
>
> I'm still wondering why parted reports Günther's disks have hybrid MBRs. That's weird, even if unrelated. And I wonder why his kernel complains about the GPTs not being at the end of the disk, but my kernel doesn't. Both are 3.5 kernels.
>
>
> Chris Murphy--
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html




--
Roberto Spadim
Spadim Technology / SPAEmpresarial
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-09-24 18:17 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-19 11:03 GPT Table broken on a Raid1 Günther J. Niederwimmer
2012-09-20  2:39 ` Chris Murphy
2012-09-20 11:05   ` Günther J. Niederwimmer
2012-09-20 17:34     ` Chris Murphy
2012-09-21 11:42       ` Günther J. Niederwimmer
2012-09-21 19:35         ` Chris Murphy
2012-09-21 22:43           ` Chris Murphy
2012-09-22  8:37             ` Günther J. Niederwimmer
2012-09-22 18:30               ` Chris Murphy
2012-09-23  6:47                 ` Hello,Re: " Günther J. Niederwimmer
2012-09-23  7:17                   ` Chris Murphy
2012-09-24  7:28                     ` Günther J. Niederwimmer
2012-09-24 17:21                       ` Chris Murphy
2012-09-24 19:06                         ` Günther J. Niederwimmer
2012-09-24 20:18                           ` Chris Murphy
2012-09-24 21:06                             ` Günther J. Niederwimmer
2012-09-24 21:12                               ` Chris Murphy
2012-09-25  8:27                                 ` Günther J. Niederwimmer
2012-09-25  9:28                                   ` John Robinson
2012-09-25 16:55                                   ` Chris Murphy
2012-09-26 12:17                                     ` Günther J. Niederwimmer
2012-09-26 19:33                                       ` Chris Murphy
2012-09-27  2:43                                         ` NeilBrown
2012-09-22 15:31             ` John Robinson
2012-09-22 18:45               ` Chris Murphy
2012-09-22 21:58                 ` NeilBrown
2012-09-22 22:07                 ` John Robinson
2012-09-22 22:30                   ` Chris Murphy
2012-09-23 12:00                     ` John Robinson
2012-09-23 17:44                       ` Chris Murphy
2012-09-23 18:53                         ` Chris Murphy
2012-09-24  9:37                           ` John Robinson
2012-09-24 17:35                             ` Chris Murphy
2012-09-24 18:17                               ` Roberto Spadim [this message]
     [not found]                               ` <CABYL=ToFtzXv95At54=jSCaD0QVSB+bdxbssda1AMw5gNBqvhg@mail.gmail.com>
2012-09-24 18:55                                 ` Chris Murphy
2012-09-25  7:33                               ` Miquel van Smoorenburg
2012-09-21 21:30         ` Chris Murphy
2012-09-21 21:49           ` Chris Murphy

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='CABYL=Try-XyEEXe37RWt4Py8_ewh-mU2kAn1X_75FjrLFcACeQ@mail.gmail.com' \
    --to=roberto@spadim.com.br \
    --cc=linux-raid@vger.kernel.org \
    --cc=lists@colorremedies.com \
    /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).