Date: Sat, 1 Feb 2020 19:35:38 +0100 From: =?utf-8?Q?Peter_Rap=C4=8Dan?= <peter.rapcan@savba.sk> To: Allan Jude <allanjude@freebsd.org> Cc: freebsd-hackers@freebsd.org Subject: Re: How do I tell gptzfsboot NOT to analyze other disks (or specify which disks to analyze)? Message-ID: <66180BBD-AB88-4DA0-9F0E-815578AA6925@savba.sk> In-Reply-To: <48f04506-b5bf-03b6-2ef8-9d8853961b07@freebsd.org> References: <EC3F4FDB-7186-4F24-9EC9-771ED239510D@savba.sk> <CANCZdfqieUhT=H_1k6DRw4fcX2nwSP-hx4kL8Y-9L12-ZZDnTw@mail.gmail.com> <F3A0D37D-8DAD-4249-ADED-54C505F9E701@savba.sk> <48f04506-b5bf-03b6-2ef8-9d8853961b07@freebsd.org>
index | next in thread | previous in thread | raw e-mail
Dear Allan, Thanks for your reply. Assuming the said 512 is in bytes, the 512*some_block_number are less then the size of the disk. The disk is a 12TB one and the “some_block_numbers" shown are 32, 544, 2929720352, 2929720864, 1. Additional information: - the same disk(s) worked in the same system without errors previously (prior version of freeNAS with less disks of the same type) - I have not been able to revert to the errorless configuration though (I think I tried all versions of freeNAS I think I could have used and seen working, with the original number of the harddrives). - when putting the harddrives in a different PC, the gptzfsboot: error 128 lba some_block_number changed into gptzfsboot: error 32 [if I remeber the number correctly] lba some_block_number The whole situation seems mysterious to me, given the system was working without the error messages previously... Best, Peter > On 31 Jan 2020, at 18:39, Allan Jude <allanjude@freebsd.org> wrote: > > On 2020-01-30 10:09, Peter Rapčan wrote: >> Thanks for your reply! >> >> I believe it is some kind of bug (maybe related to to https://forums.freebsd.org/threads/gptzfsboot-error-128-after-adding-new-disks.65677/ but the solution provided there makes no difference in my case). >> >> The funny thing is that the same system with the same type of disks worked before (with 3 data HDDS and freeNAS [11.2-Ux]) there were no gptzfsboot errors and the boot time was fast. After I added a 4th data drive and upgraded the system (freeNAS) to new version, only then I started getting the "gptzfsboot: error 128 lba some_block_number” errors. However I was not able revert to the state without the errors, altough I tried the original version of freeNAS, with 3, 2, or 1 data HDD(s), I tried wiping the HDDS, removing the partition table, creating a new one, etc…. I even tried installing freeBSD instead of freeNAS :-). >> >> I am new to freeBSD… could you perhaps give me some advice how to troubleshoot this error? >> >> Best, >> Peter >> >> > Is the 'some_block_number' at or past the end of the disk? > > Multiply the number by 512 and compare it to the size of the disk. > > -- > Allan Judehelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?66180BBD-AB88-4DA0-9F0E-815578AA6925>