fedora-kde / SIG

#649 on reboot failed unmounting /etc (LUKS encrypted disk)
Opened by antonin. Modified

Open
Close Issue

Hi,

I noticed that after rebooting the computer, I have a log entry that the /etc directory was not unmounted correctly:

$ journalctl -b -1 | grep mount.*etc
systemd[1]: Unmounting etc.mount - /etc...
umount[6375]: umount: /etc: target is busy.
systemd[1]: Failed unmounting etc.mount - /etc.

Antonin

We need more info and more logs to be able to help here. What's your fstab, etc.

Hi,
it is Fedora Kinoite with full disk encryption. And my /etc/fstab was created during installation:

UUID=6c02f6b7-f7db-4ec2-a1d7-02d243547e74 /boot ext4 defaults 1 2
UUID=A96C-504D /boot/efi vfat umask=0077,shortname=winnt 0 2
UUID=89b0bd2e-5f55-4b2e-8f08-419869a23aa5 / btrfs subvol=root,compress=zstd:1,x-systemd.device-timeout=0,ro 0 0
UUID=89b0bd2e-5f55-4b2e-8f08-419869a23aa5 /home btrfs subvol=home,compress=zstd:1,x-systemd.device-timeout=0 0 0
UUID=89b0bd2e-5f55-4b2e-8f08-419869a23aa5 /var btrfs subvol=var,compress=zstd:1,x-systemd.device-timeout=0 0 0

Every time I shut down my computer, a message appears briefly saying that the /etc directory failed to unmount.
To investigate this further, I created a new installation in a virtual machine in QEMU. This problem also occurred in this new installation, but only(!) if I specified that I wanted an encrypted disk during installation. If I did not use full disk encryption, the problem with unmounting the /etc directory did not occur.

Antonin
Edited by antonin

If this is for Kinoite, then this is likely https://github.com/ostreedev/ostree/issues/3513
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.