Date: Fri, 31 Jan 2020 12:39:31 -0500 From: Allan Jude <allanjude@freebsd.org> To: freebsd-hackers@freebsd.org Subject: Re: How do I tell gptzfsboot NOT to analyze other disks (or specify which disks to analyze)? Message-ID: <48f04506-b5bf-03b6-2ef8-9d8853961b07@freebsd.org> In-Reply-To: <F3A0D37D-8DAD-4249-ADED-54C505F9E701@savba.sk> References: <EC3F4FDB-7186-4F24-9EC9-771ED239510D@savba.sk> <CANCZdfqieUhT=H_1k6DRw4fcX2nwSP-hx4kL8Y-9L12-ZZDnTw@mail.gmail.com> <F3A0D37D-8DAD-4249-ADED-54C505F9E701@savba.sk>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --RrsvURNOlSpCXzsfFTDsxJYMg0BU6LbkN Content-Type: multipart/mixed; boundary="9NtOgVpiPkRUp7uR7PWvhnJ2wO3XgNAmK"; protected-headers="v1" From: Allan Jude <allanjude@freebsd.org> To: freebsd-hackers@freebsd.org Message-ID: <48f04506-b5bf-03b6-2ef8-9d8853961b07@freebsd.org> Subject: Re: How do I tell gptzfsboot NOT to analyze other disks (or specify which disks to analyze)? References: <EC3F4FDB-7186-4F24-9EC9-771ED239510D@savba.sk> <CANCZdfqieUhT=H_1k6DRw4fcX2nwSP-hx4kL8Y-9L12-ZZDnTw@mail.gmail.com> <F3A0D37D-8DAD-4249-ADED-54C505F9E701@savba.sk> In-Reply-To: <F3A0D37D-8DAD-4249-ADED-54C505F9E701@savba.sk> --9NtOgVpiPkRUp7uR7PWvhnJ2wO3XgNAmK Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable On 2020-01-30 10:09, Peter Rap=C4=8Dan wrote: > Thanks for your reply! >=20 > I believe it is some kind of bug (maybe related to to https://forums.fr= eebsd.org/threads/gptzfsboot-error-128-after-adding-new-disks.65677/ but = the solution provided there makes no difference in my case). >=20 > The funny thing is that the same system with the same type of disks wor= ked before (with 3 data HDDS and freeNAS [11.2-Ux]) there were no gptzfsb= oot 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 gettin= g the "gptzfsboot: error 128 lba some_block_number=E2=80=9D errors. Howev= er 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 wi= ping the HDDS, removing the partition table, creating a new one, etc=E2=80= =A6. I even tried installing freeBSD instead of freeNAS :-). >=20 > I am new to freeBSD=E2=80=A6 could you perhaps give me some advice how = to troubleshoot this error? >=20 > Best, > Peter >=20 >=20 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. --=20 Allan Jude --9NtOgVpiPkRUp7uR7PWvhnJ2wO3XgNAmK-- --RrsvURNOlSpCXzsfFTDsxJYMg0BU6LbkN Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJeNGZWAAoJEBmVNT4SmAt+OUgP/2ZCMCP2OoPIyukflWJG8R92 dER6za2+rLWBulPL4UCLqk1VZtgMwUsmcKbsFjY5IfZd2zxaxoHK1HaHGr4fNyOZ lv+FvWbpw939aVPMKe9Hc8apjhHGJia0Xt3XHyVLbF+ybvOmkdMSa2Y2R71vkaZR VcGVi+MgrVIoUYrutl3OBMLzHYbXRVECw6mlC6fMA5RWRSaKysZMkebcTJhbOImh d8cJYU9X5Vc5ZuHW0qIXSKFb2KCfAWcxtXkr0nL48o0hFTLkc+kDbDbfj9KjJ9QQ m/QYMSr8CX3QnzilZdvALYTJTRb3Cs5CDWzymYYjy5wH+fW2LbK+EgD7esBbmQhk m1W+JESHdsylOq0bKrEcRFNoS+2vDjmEUgB2ytb+DM3s48VWKJPlsCNaU3l1qhbh kiRqilS1RfzHCaAiTBC7DNBEv6aslTxJsRGZ4kUphA8bpmFvzdTZlj3Tgj/MKFVP Bha/nIzWVOPVVKwUjEblUCim57IAPGM1Ll7bLRHq6fvpsnRpFjUAyPkFSJMyL/El +Gw38nnw7nPduPd8ZlbVDDVJGz99AxIfDlg+1fQhz/gdIfOAoQ+8OdibVHHNfo6V rCw7y3vMZmMBOVvlGYOAhTJvpZ0aVgO+EReSFaRYwDFtBlKFfpMc/APXeMy4sZJ/ /6wzR7lFuMF+644jeE0E =wEKe -----END PGP SIGNATURE----- --RrsvURNOlSpCXzsfFTDsxJYMg0BU6LbkN--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48f04506-b5bf-03b6-2ef8-9d8853961b07>