How do I tell gptzfsboot NOT to analyze other disks (or specify which disks to analyze)?

[Allan Jude]

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 Jude

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 834 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-hackers/attachments/20200131/70f9792e/attachment.sig>