Date: Fri, 28 Apr 2023 08:30:33 +0200 From: "Dave Cottlehuber" <dch@skunkwerks.at> To: stable@freebsd.org, "Miroslav Lachman" <000.fbsd@quip.cz> Subject: Re: etcupdate created empty files = system unbootable Message-ID: <bae5d97b-42af-48a6-abf8-ff88ac19c62e@app.fastmail.com> In-Reply-To: <312ae63f-4fab-e194-c603-a85fd11f6edd@quip.cz> References: <312ae63f-4fab-e194-c603-a85fd11f6edd@quip.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 27 Apr 2023, at 11:21, Miroslav Lachman wrote: > Yesterday I upgraded one machine from 12.3 to 13.2 with source upgrade=20 > (installkernel & installworld). > Then I run "etcupdate" (about 100 changes listed, mainly U and A, only= 2=20 > C), "etcupdate resolve" to solve conflicts in newsyslog.conf and=20 > sshd_config, then "etcupdate status" to be sure everything is OK, it=20 > just said: "Modified regular file remains: /etc/motd" > > After this I updated bootcode with gpart and rebooted the machine but = it=20 > does not come up, cannot login via ssh. Accessing this remote machine=20 > with remote mamagement / IPMI was a nightmare. It took me almost 5 hou= rs=20 > because of java etc. but it's a different story. > > The machine in question is all ZFS based. Ouch. I don=E2=80=99t wish java remote console on anybody. I have heard = a very small number of vaguely similar complaints but nothing concrete. Do you still have the zfs snapshot this was upgraded from? It would be g= ood to know if this issue is reproducible, and even better to work out w= hat=E2=80=99s happening. Please log a PR for this issue Dave
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bae5d97b-42af-48a6-abf8-ff88ac19c62e>