Date: Wed, 8 Feb 2017 11:48:50 -0000 From: "Thomas Sparrevohn" <Thomas.Sparrevohn@btinternet.com> To: "'Steven Hartland'" <killing@multiplay.co.uk>, <freebsd-current@freebsd.org> Subject: RE: gptzfsboot trouble Message-ID: <002801d28201$50cf3260$f26d9720$@btinternet.com> In-Reply-To: <001e01d28166$9eac3960$dc04ac20$@btinternet.com> References: <000d01d2815c$74f1be60$5ed53b20$@btinternet.com> <26D78147-119E-4BB7-B567-2B2C09C321BE@me.com> <78739e6c-a645-25a6-a65b-968941fc4864@multiplay.co.uk> <001e01d28166$9eac3960$dc04ac20$@btinternet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Getting more and more weird - Installed a vanilla 11-RELEASE using UFS =
rather ZFS and it issues no errors. Tried to roll back an older snapshot =
but getting issues as the pool is build using 11-CURRENT. Looking at the =
part - the LBA complained about is an empty sector (did a dd =
if=3D/dev/zero of=3D/dev/ada1) and then read the blocks but they are =
empty.=20
Both the UFS and ZFS was installed using GPT - and UFS does not =
complain. The disks are old and so is the host and should most likely be =
replaced anyhow but I am not sure if it will help.=20
-----Original Message-----
From: owner-freebsd-current@freebsd.org =
[mailto:owner-freebsd-current@freebsd.org] On Behalf Of Thomas =
Sparrevohn
Sent: 07 February 2017 17:21
To: 'Steven Hartland' <killing@multiplay.co.uk>; =
freebsd-current@freebsd.org
Subject: RE: gptzfsboot trouble
I will check but I don't think so - The system has worked for years =
without any trouble and I did a full wipe e.g. "dd if=3D/dev/zero =
of=3D/dev/ada1" but let me check again - for ease - I think I am going =
to do a vanilla single drive pool=20
-----Original Message-----
From: owner-freebsd-current@freebsd.org =
[mailto:owner-freebsd-current@freebsd.org] On Behalf Of Steven Hartland
Sent: 07 February 2017 16:41
To: freebsd-current@freebsd.org
Subject: Re: gptzfsboot trouble
On 07/02/2017 16:33, Toomas Soome wrote:
>
>> On 7. veebr 2017, at 18:08, Thomas Sparrevohn =
<Thomas.Sparrevohn@btinternet.com> wrote:
>>
>> Hi all
>>
>>
>>
>> Last week I decided to upgrade my FreeBSD installation - it's been a=20
>> while (September 16 was last time). Unfortunately CURRENT does not=20
>> boot and cash in a weird way. Both 11-RELEASE and 12 CURRENT boot=20
>> loader seems to attempt to read blocks that exceeds the physical=20
>> disk. Initially I through it was a hard disk error - but after a "oh"
>> experience I realised that the
>> "gptzfsboot: error 4 lba 921592" is actually beyond the physical=20
>> boundaries of the disk (300GB disk). In order to rule out different=20
>> options - I installed a vanilla 11-RELEASE on the 300G with a simple=20
>> stripe - it also gives the error but does boot - the LBA of the error =
>> is slightly different on 11 CURRENT and comes up with LBA 921600
>>
>>
>>
>> I have scanned all the disks for physical faults and there seems to=20
>> be none and I have tried doing a single disk installation on each=20
>> disk - they give the same error - Does anybody have any idea?
>> Included Photos as sometimes it get through to the actual boot menu=20
>> but then crash in another place
>>
>
> The gptzfsboot does read the backup label from the disk and the GPT=20
> backup label is stored at the end of the disk. The location of the=20
> backup label is in the primary GPT table, alternate sector field. I=20
> wonder if that location is somehow set to bad value=E2=80=A6
>
>
Booting from a live CD and inspecting the label with gpart show should =
be able to confirm that.
Regards
Steve
_______________________________________________
freebsd-current@freebsd.org mailing list =
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to =
"freebsd-current-unsubscribe@freebsd.org"
_______________________________________________
freebsd-current@freebsd.org mailing list =
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to =
"freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?002801d28201$50cf3260$f26d9720$>