I know very well the ro-fsck-rw-killall-ro sequence and have performed it manually many times.
lsof shows that plymouth is writing to boot.log: # lsof -p 352 plymouthd 352 root 12w REG 8,4 4944 280966 /var/log/boot.log Is this an unusual configuration? In any case, if plymouth is supposed to remain alive to the end, and NOT write to /, then perhaps /etc/init/plymouth-stop is misleading. To quote: # This job ensures that only one service stops the plymouth splash screen This comment seems to imply that plymouth needs to be stopped. -- plymouthd alive when umountroot runs (prevents clean unmount) https://bugs.launchpad.net/bugs/665195 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
