Date: Mon, 29 Apr 2019 13:24:45 -0600 From: Ian Lepore <ian@freebsd.org> To: lausts@acm.org, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Question about 'gptzfsboot' Message-ID: <6e0db2b2130555acb64c9016a33da07bb0d16f96.camel@freebsd.org> In-Reply-To: <9ed708cc-8b16-12e7-9119-aeebb412317c@acm.org> References: <f2f43092-4417-2683-04f1-724d12eed1e9@acm.org> <op.z0yhbhqykndu52@sjakie> <01d10a11-49b2-2982-01cb-b49a0831d30b@acm.org> <5de29e0b5228d7eb0aac8e0eec116896f11ea862.camel@freebsd.org> <a6e9953f-6ed9-1d60-893c-6dcedb05895c@acm.org> <5bf88341-80f0-3aff-f51a-0b1975530f2e@acm.org> <0848043e68641ea47b918b8480ac8a5a3bb773e0.camel@freebsd.org> <940cbef4-67a9-1f8e-2bca-35b41e4a08f9@acm.org> <9ed708cc-8b16-12e7-9119-aeebb412317c@acm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2019-04-29 at 14:47 -0400, Thomas Laus wrote: > On 2019-04-29 14:27, Thomas Laus wrote: > > It was more than a broken console. All of the other 2 computers > > that I > > upgraded to r346885 were essentially 'dead'. I could not even > > remotely > > login to them via ssh. All of them required a hard power button > > reset > > to get into single user mode to let me comment out the rc.conf line > > that > > loads the DRM driver. The computer could successfully boot without > > DRM > > activation but would go to a black console screen again with > > 'startx'. > > This also required a hard power button shutdown. I rolled back to > > r346544 and everything worked again like before. > > > > My disastrous update to r346885 included installing a new > > gptzfsboot and > > pmbr in the drive boot record. I did not try booting an older > > kernel > > using the new gptzfsboot. I was concerned about the lack of ssh > > login > > when the computers lost their console, so I just rolled back my > > system > > to the last snapshot made a week ago. > > > > Ian: > > I re-activated the r346885 BEADM snapshot and booted from my > 'kernel.old' from r346544 and everything came up OK including 'X'. > > I don't know what that means. It might be that I have a DRM issue > instead of a gptzfsboot problem? Everything except for the kernel is > now running CURRENT r346885. I am not using the updated > drm-current-kmod because I am using the r346544 kernel.old. > > Tom > > I can't say anything at all about drm or other video driver issues, I'm just not knowledgeable about that stuff at all. The only thing I was getting at was that the changes I made in r346675 might make this error stop happening: gptzfsboot: error 1 LBA 18446744072709551608 gptzfsboot: error 1 LBA 1 gptzfsboot: No ZFS pools located, can't boot Emphasis on the "might"... that appears to be an error during probing for zfs, and I made some fixes related to probing for zfs. -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6e0db2b2130555acb64c9016a33da07bb0d16f96.camel>