You are not logged in.
Good hello everyone,
I've installed a fresh Arch with F2FS today. Then after the base installation I came up with a failure on
systemctl --status
So I checked if what's wrong with the systemd-remount-fs.service and run
LC_ALL=C journalctl -u systemd-remount-fs.service --no-pager --since=today
and the output was like below:
Apr 12 04:56:40 ArchByte systemd-remount-fs[217]: mount: /: mount point not mounted or bad option.
Apr 12 04:56:40 ArchByte systemd-remount-fs[217]: dmesg(1) may have more information after failed mount system call.
-- Boot ad3a7fa7313446e88ba8a5a2de3c4d3a --
Apr 12 04:57:59 ArchByte systemd-remount-fs[217]: mount: /: mount point not mounted or bad option.
Apr 12 04:57:59 ArchByte systemd-remount-fs[217]: dmesg(1) may have more information after failed mount system call.
And here's my fstab:
# Static information about the filesystems.
# See fstab(5) for details.
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/sda2 LABEL=mylabel
UUID=93cbd622-dfec-43a3-ae1f-ba9c9caf424a / f2fs rw,relatime,lazytime,background_gc=on,gc_merge,discard,no_heap,inline_xattr,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6,whint_mode=fs-based,alloc_mode=default,checkpoint_merge,fsync_mode=posix,compress_algorithm=zstd:6,compress_log_size=2,compress_chksum,compress_mode=fs,atgc,discard_unit=block 0 0
# /dev/sda1
UUID=6E2E-B5C2 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2
I'd like to know If anyone could tell me the which part is causing the service fail.
Offline
Apr 12 04:57:59 ArchByte systemd-remount-fs[217]: dmesg(1) may have more information after failed mount system call.
Does it?
Offline
It's already a month late, I don't know if you have fixed it or have decided to give up. But since I havn't saw any good answers to this specific problem on the Internet, I an posting my answer here:
metebyte wrote:Apr 12 04:57:59 ArchByte systemd-remount-fs[217]: dmesg(1) may have more information after failed mount system call.
Does it?
It should be. I have encountered the same problem just now, and in dmesg it reads:
[5.294536] F2FS-fs (sdb1): switch atgc option is not allowed.
It's a problem that happens when the systemd-remount-fs.service tries to remount rootfs (mounted by the kernel without atgc option)with the option atgc set in your fstab, but is disallowed by the F2FS kernel module. F2FS filesystems cannot be remounted with atgc option added/cleared later. When systemd-remount-fs failed to remount rootfs, it leave the rootfs read-only, which then caused multiple problems for other services that requires a read-write rootfs.
To solve this problem, one have to either:
1) remove atgc mount option from fstab.
or
2) add kernel parameter
rootflags=atgc
into your bootloader configuration.
Offline