ronald-lists at klop.ws
Wed Feb 8 12:53:48 UTC 2017
On Wed, 08 Feb 2017 13:35:22 +0100, Thomas Sparrevohn
<Thomas.Sparrevohn at btinternet.com> wrote:
> What would help? Takes a little while as I have to rebuild to 11-RELEASE
> each time? 12-CURRENT cashed either before the boot menu or immediately
> after which could be unrelated - I have photos but they are quite big
> 4 MB
You can't mail them as attachment, but you might put them on Dropbox or
something else and link to them.
> I suggest -
> 1) Single disk ZFS pool on the 320GB disks should allow for faster
> dd wipes if needed
> 2) Run 11-RELEASE initially in case the 12-CURRENT issues are
> I send
> Dmesg output
> Gpart show
> Gpart list
> Zpool status
> Camcontrol devlist
> Anything else?
That is a really good start for people to look further on.
Did you update your boot blocks while updating?
> -----Original Message-----
> From: owner-freebsd-current at freebsd.org
> [mailto:owner-freebsd-current at freebsd.org] On Behalf Of Ronald Klop
> Sent: 08 February 2017 12:27
> To: FreeBSD-current at freebsd.org; Thomas Sparrevohn
> <Thomas.Sparrevohn at btinternet.com>
> Subject: Re: gptzfsboot trouble
> On Tue, 07 Feb 2017 17:08:44 +0100, Thomas Sparrevohn
> <Thomas.Sparrevohn at btinternet.com> wrote:
>> Hi all
>> Last week I decided to upgrade my FreeBSD installation - it's been a
>> while (September 16 was last time). Unfortunately CURRENT does not
>> boot and cash in a weird way. Both 11-RELEASE and 12 CURRENT boot
>> loader seems to attempt to read blocks that exceeds the physical 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
>> boundaries of the disk (300GB disk). In order to rule out different
>> options - I installed a vanilla 11-RELEASE on the 300G with a simple
>> 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 be
>> none and I have tried doing a single disk installation on each disk -
>> they give the same error - Does anybody have any idea? Included Photos
>> as sometimes it get through to the actual boot menu but then crash in
>> another place
>> I have some images - but they are 2 bit for the mailing list ;-)
> Can it be related to this issue?
> Would be nice if you tell more about the system. CPU? dmesg?
> The 11-RELEASE did that boot from the same disk? In the mentioned issue
> there is the case that gptzfsboot does recognize a secondary disk (can be
> configured as mirror), but not the first.
> As you say UFS works, the bug might be in the gptzfsboot code, because
> is not used for UFS.
> freebsd-current at freebsd.org mailing list
> To unsubscribe, send any mail to
> "freebsd-current-unsubscribe at freebsd.org"
More information about the freebsd-current