Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 09 May 2012 19:14:23 +0700
From:      Adam Strohl <adams-freebsd@ateamsystems.com>
To:        "Andrey V. Elsukov" <bu7cher@yandex.ru>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: FreeBSD 9 "gptboot: invalid backup GPT header" error (boots fine though)
Message-ID:  <4FAA5F9F.1080203@ateamsystems.com>
In-Reply-To: <4FA15C0D.2050107@yandex.ru>
References:  <4F9EE487.6020609@ateamsystems.com> <4FA0CCF0.5000607@FreeBSD.org> <4FA0F872.4040008@ateamsystems.com> <CAMXt9NbdnmsJH33iCFW91ycTO2wM1dqstFcEL1f=-krqk1Graw@mail.gmail.com> <4FA13C48.8010700@ateamsystems.com> <4FA15C0D.2050107@yandex.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
On 5/2/2012 23:08, Andrey V. Elsukov wrote:
> On 02.05.2012 17:53, Adam Strohl wrote:
>>> % gpart recover da0
>>
>> Good thought, but no dice:
>>
>> $ gpart recover da0
>> da0 recovering is not needed
>
> I already saw several reports about gptboot's complains on 3ware
> controllers, but don't know what is the problem.
> The only guess is that a controller incorrectly handles BIOS requests,
> when gptboot tries to read GPT header from the end of a large virtual disk.


Thanks for your input on this Andrey.  Just to clarify I am assuming 
that "da0 recovering is not needed" means that gpart has no problem 
reading and verifying the backup GPT header?

(which is why its probably the BIOS for the RAID controller as the GPT 
is actually intact)



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FAA5F9F.1080203>