Date: Wed, 08 Feb 2017 14:35:43 +0200 From: Toomas Soome <tsoome@me.com> To: FreeBSD-current@freebsd.org Subject: Re: gptzfsboot trouble Message-ID: <CB018A6C-75F9-476F-A656-DC598DF00685@me.com> In-Reply-To: <op.yvccuojgkndu52@53556c9c.cm-6-6b.dynamic.ziggo.nl> References: <000d01d2815c$74f1be60$5ed53b20$@btinternet.com> <op.yvccuojgkndu52@53556c9c.cm-6-6b.dynamic.ziggo.nl>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 8. veebr 2017, at 14:26, Ronald Klop <ronald-lists@klop.ws> wrote: >=20 > On Tue, 07 Feb 2017 17:08:44 +0100, Thomas Sparrevohn = <Thomas.Sparrevohn@btinternet.com> wrote: >=20 >> Hi all >>=20 >>=20 >> 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 >>=20 >>=20 >> 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 >>=20 >>=20 >> I have some images - but they are 2 bit for the mailing list ;-) >=20 >=20 > Can it be related to this issue? > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D144234 >=20 > 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. >=20 > As you say UFS works, the bug might be in the gptzfsboot code, because = that is not used for UFS. >=20 There is another possible test scenario - to create pool on BSD labeled = disk, so we can see if it is just about the zfs code itself or rather = related to GPT. Or vice versa, try ufs on GPT labeled disk. rgds, toomas
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CB018A6C-75F9-476F-A656-DC598DF00685>