Daniel Pielmeier schrieb am 23.02.19 um 16:37: > Daniel Pielmeier schrieb am 23.02.19 um 16:25: >> Holger Hoffstätte schrieb am 23.02.19 um 15:15: >>> >>> Last night openrc was updated to ~0.41, supposedly fixing [1]. >>> >>> Unfortunately it seems it had the opposite effect and made things worse >>> compared to the previous 0.42.3 - the deptree is broken, rc-status >>> remains confused and a reboot results in a read-only root fs because >>> (I think) the runlevels are all mixed up, esp. /etc/runlevels/boot. >>> >>> Restoring /etc/runlevels from backup & downgrade to 0.40.3 fixed it. >>> >>> If someone can reproduce this in a VM (I cannot do so right now) please >>> file a bug with more information. >>> >>> hth, >>> Holger >>> >>> [1] https://bugs.gentoo.org/659906 >>> >>> >>> >> >> Same here! However I am still on sys-apps/openrc-0.38.3-r1. I think the >> culprit is sys-fs/udev-init-scripts-33 which got an upgrade from version >> 32 on the day before this started happening! >> > > What's to add is that restarting from the semi booted state always > resulted in the same partial boot with the rootfs mounted read-only. > After fixing this by manually starting all services everything was fine > after the next boot. Today when booting again the same happened. I am > writing this now from the manually started system. I will try restarting > over and check if I can reproduce this issue reliable. >
Rebooting a few times always resulted in a failed boot! Maybe the other time I was just lucky. Downgrading to sys-fs/udev-init-scripts-32 seems to fix the issue. I opened bug 678638 [1] about this issue. [1] https://bugs.gentoo.org/678638 -- Regards Daniel
