You are not logged in.
My system updated to the latest Linux release today. Since then I'm unable to boot my system, which consists of a setup of LVM on top of LUKS.
Here's the journalctl -xb: pastebin link
For me it's hard to see what's the problem here. /home/ doesn't get mounted and then things seem to break.
Feb 03 21:57:11 hubert systemd[1]: home.mount: Mount process exited, code=exited status=32
Feb 03 21:57:11 hubert systemd[1]: Failed to mount /home.
...
Feb 03 21:57:11 hubert systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'.
Feb 03 21:57:11 hubert systemd[1]: local-fs.target: Triggering OnFailure= dependencies.
Feb 03 21:57:11 hubert systemd[1]: home.mount: Unit entered failed state.
Feb 03 21:57:11 hubert kernel: EXT4-fs (dm-3): can't mount with data=, fs mounted w/o journal
Feb 03 21:57:11 hubert systemd[1]: Stopped target Graphical Interface.Interestingly, booting linux-lts works just fine.
I've checked my partitions for filesystem errors and rebuilt /boot/vmlinuz-linux with no success.
Any idea and help is appreciated, thanks!
Last edited by Duxon (2016-02-11 10:38:53)
Offline
Hello Duxon ![]()
Do you have no default mount options in fstab (data, commit)? My ext4 system only boot with default mount options after kernel update.
Offline
Excellent, Beauvoir!
I've used the option data=ordered in my /etc/fstab, which was actually mentioned in my error abstract, but I didn't understand it. Now I do.
Thanks, solved!
Offline
I ran into the same issue here today. I first suspected lvm to cause the problem and downgraded to a previous version without success.
After downgrading to linux 4.3 the issue was resolved.
Is this a kernel bug then? I couldn't find anything in kernel bugzilla.
Offline
Why not simply editing your /etc/fstab?
Offline
I don't understand your question. I did the downgrades before I read your post.
If this is a bug it should get fixed.
Or is data=ordered not a valid option anymore?
Last edited by georgnix (2016-02-05 08:02:55)
Offline
Sorry, the question was not well put. I didn't really depend on data=ordered and therefore just removed it without a lot of further thought and without the need of downgrading.
I can't find any documentation on whether or not this option is now deprecated either, so my guess is it's a kernel bug.
Offline
I finally got around creating a bug report: FS#48135
@Duxon: maybe you could remove [SOLVED] from the title. It's really not.. ;-)
Offline
To document this here: The problem was that the filesystem did indeed not have a journal in contrast to my assumption.
That's the meaning of the follwing kernel error msg:
EXT4-fs (dm-3): can't mount with data=, fs mounted w/o journal
Sent a patch to clarify it.
Last edited by georgnix (2016-02-12 13:42:29)
Offline