Date: Mon, 29 Apr 2019 21:58:06 +0300 From: Toomas Soome <tsoome@me.com> To: lausts@acm.org Cc: Ian Lepore <ian@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: Question about 'gptzfsboot' Message-ID: <1AE55D88-B509-44B9-953E-A5BFBF383102@me.com> 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 29 Apr 2019, at 21:47, Thomas Laus <lausts@acm.org> wrote: >=20 > 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. >>=20 >> 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. >>=20 > Ian: >=20 > I re-activated the r346885 BEADM snapshot and booted from my > 'kernel.old' from r346544 and everything came up OK including 'X'. >=20 > 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. >=20 It means you have different issues - one is about gptzfsboot causing = boot problems and apparently it got fixed when you did update the = bootcode (the boot partition is global). But also you got bitten by DRM = update, and since you had old BE around, you were able to load old = kernel. Now the question is, is that gptzfsboot issue really fixed or is it just = the =E2=80=9Cwarm boot=E2=80=9D fix you were seeing earlier too. rgds, toomas > Tom >=20 >=20 > --=20 > Public Keys: > PGP KeyID =3D 0x5F22FDC1 > GnuPG KeyID =3D 0x620836CF > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to = "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1AE55D88-B509-44B9-953E-A5BFBF383102>