(In reply to Franck Bui from comment #49) > *** Bug 1060226 has been marked as a duplicate of this bug. *** OMG! This issue is known since 2017-09-25 and the culprit found just a few days later by Jonathan Cottrill <novell@jonathancottrill.net>. And the bugowner of that bug is in Cc of this bug ... (JFYI, the workaround in this bugreport is not really a workaround; it can only be applied after a new installation, i.e. after you had the complete data loss) Ludwig, I'm not sure what another entry in our release notes would help here. One of the systemd update was the culprit here. What we need here is another systemd Online update. ASAP.