On Mittwoch, 26. August 2020 10:53:23 CEST Robert Munteanu wrote:
Hi John,
On Wed, 2020-08-26 at 10:30 +0200, John Janus wrote:
Good Morning. After I updated my system the day before yesterday to this snapshot and shut it down afterwards, it did not really come up correctly today. At first, only the graphical environment (plasma) did not start. After rebooting again, logind did not start and the root-filesystem was mounted ro, no /tmp and other weirdness. I could remount the root fs as rw but i was not able to determine the issue, let alone fix it. I rolled back to the snapshot before this update and everything works fine here. Yesterday at work, I did install the same update without problems, so it may be related to the differences between the two systems. NotWorkinkSystem WorkingSystem /tmp not in fstab old tmp setup as subvol root on nvme ssd root on sata ssd amd ryzen 7 2700 older intel core i5
rpmconfigcheck did not report files I'd link to the issue (postfix master.cf and the like) I will file a Bug later today, now I have to work (I will probably need to create a new account...)
Is this the same as https://lists.opensuse.org/opensuse-support/2020-08/msg00083.html ? Robert
May be. I did not check most stuff after the first boot. Now, after rollback, there is no symlink related to tmp.mount in /etc/systemd/system (or anywhere in /etc), but in the other snapshots, there is. Interestingly, there is /etc/systemd/system/tmp.mount (symlink to /usr/share/ systemd/tmp.mount) in the ro snapshot of the fs from the rollback. I'll try the dist-upgrade again later today. Thank you, Robert. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org