Date: Mon, 29 Apr 2019 07:38:16 -0400 From: Thomas Laus <lausts@acm.org> To: Ian Lepore <ian@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Question about 'gptzfsboot' Message-ID: <a6e9953f-6ed9-1d60-893c-6dcedb05895c@acm.org> In-Reply-To: <5de29e0b5228d7eb0aac8e0eec116896f11ea862.camel@freebsd.org> References: <f2f43092-4417-2683-04f1-724d12eed1e9@acm.org> <op.z0yhbhqykndu52@sjakie> <01d10a11-49b2-2982-01cb-b49a0831d30b@acm.org> <5de29e0b5228d7eb0aac8e0eec116896f11ea862.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2019-04-28 22:27, Ian Lepore wrote: > > If you're using gptzfsboot, I guess you're using zfs? I just fixed a > problem with probing disks for zfs volumes a few days ago (r346675). > There is even some small chance it fixes this problem, because one of > the things I noticed was that in one of the disk structures in loader, > the "slice offset" value was sometimes a bit random-looking, like it > was being initialized with whatever garbage was laying around in > memory. It actually makes some sense that the "garbage" might be > different between a firstboot after power-on and a reboot. > > So all in all, it wouldn't hurt to update both gptzfsboot and loader > (gpart bootcode -b and -p) to see if there's a fix lurking in my zfs > probe changes. > I'll build and update my laptop OS this morning and report back to this thread if I have any additional issues. Thanks Tom -- Public Keys: PGP KeyID = 0x5F22FDC1 GnuPG KeyID = 0x620836CF
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a6e9953f-6ed9-1d60-893c-6dcedb05895c>