Am 18.12.2015 um 13:34 schrieb Frank B. Brokken: >> I'm a bit confused by those logs. They show that sda5 have been mounted. >> >> Dec 17 15:44:29 localhost.localdomain kernel: EXT4-fs (sda5): mounting >> ext3 file system using the ext4 subsystem >> Dec 17 15:44:29 localhost.localdomain kernel: EXT4-fs (sda5): mounted >> filesystem with ordered data mode. Opts: (null) > > I seem to remember that message, in particular the Opts: (null) remark, and I > think at that point /usr was mounted by me fron the systemd shell. Also, > couldn't it be that initramfs *did* do the mount, but that remounting it rw, > als reported in the error message is the problem? Also, to me it appears
The verbose debug log from the initramfs and systemd can maybe tell us more. But looking at https://www.icce.rug.nl/systemd/journalctl, the sda5 mount happens at line 773, the first errors start at line 785 and the remount is at line 802. So it looks like /usr is not mounted at the time systemd-remount-fs.service is run. What's also curious is, that the log doesn't seem to be complete. Usually systemd's first log line is something like > Dez 18 07:03:47 pluto systemd[1]: systemd 228 running in system mode. (+PAM > +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT > +GNUTLS +ACL +X > Dez 18 07:03:47 pluto systemd[1]: Detected architecture x86-64. Those early boot messages seem to be missing completely. Btw, you mentioned that this happened after an upgrade. Which previous version did you run which worked fine? Which other packages were upgraded along with it? If you downgrade systemd/udev, does the problem go away? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
