Arch Linux

arch1bald1

Member

Registered: 2019-06-15

Posts: 13

[solved] How to mount encrypted root with data=journal

Hi,

I have moved the Journal of my encrypted root device on a second SSD (EXT-4).

Since then I get the following error:

dmesg -l err
[   10.833243] EXT4-fs (dm-0): Cannot change data mode on remount
[   10.858960] systemd[1]: Failed to start Remount Root and Kernel File Systems.
[   12.164076] EXT4-fs (dm-0): Cannot change data mode on remount
[   12.225256] EXT4-fs (dm-0): Cannot change data mode on remount
[   12.669632] EXT4-fs (dm-0): Cannot change data mode on remount

/etc/default/grub:

GRUB_CMDLINE_LINUX="noresume cryptdevice=/dev/disk/by-uuid/77a2412d-7af8-4865-9d40-e5951de7b08e:root"
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
GRUB_ENABLE_CRYPTODISK="y"
GRUB_TIMEOUT="5"
GRUB_DISABLE_OS_PROBER="true"
GRUB_DISABLE_LINUX_RECOVERY="true"
GRUB_DISABLE_RECOVERY="true"
GRUB_CMDLINE_LINUX_DEFAULT="noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off mitigations=off nowatchdog acpi_sleep=s3_bios iommu=soft snd_hda_intel.dmic_detect=0 ivrs_ioapic[9]=00:14.0 ivrs_ioapic[10]=00:00.1"
GRUB_DEFAULT=saved
GRUB_SAVEDEFAULT=true

fstab:

UUID=6ed31cff-cdeb-46a3-84ba-91148cc1d54f /boot ext2 rw,noatime 0 0
UUID=e78e5dca-0fe8-4181-88a0-fc7f6f6b6995 / ext4 rw,noatime,data=journal,journal_checksum,journal_async_commit 0 0

How / ist actually mounted:

/dev/mapper/root on / type ext4 (rw,relatime)

So how can I specify mount options (especially data=journal) for the encrypted root device?

Last edited by arch1bald1 (2020-03-01 18:54:37)

Lone_Wolf

Administrator

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 15,096

Re: [solved] How to mount encrypted root with data=journal

On gpt drives systemd tries to mount many things before it processes fstab .
https://www.freedesktop.org/software/sy … rator.html

Check https://linux.die.net/man/8/tune2fs , you may be able to override the default options on filesystem level using -o

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky