ModemManager is installed, has a
systemd unit, and the unit was
disabled.
I have
enabled the unit so we'll see if that gets rid of that error. The
ModemManager is a required dependency of
Gnome 3.
I am looking at this
fsck set of messages:
Code: Select all
~ $ sudo journalctl -xb | grep -i fsck
Sep 14 09:28:48 bench6 systemd[1]: Starting system-systemd\x2dfsck.slice.
Sep 14 09:28:48 bench6 systemd[1]: Created slice system-systemd\x2dfsck.slice.
-- Subject: Unit systemd-fsck-root.service has finished start-up
-- Unit systemd-fsck-root.service has finished starting up.
-- Subject: Unit systemd-fsck@dev-disk-by\x2dlabel-bench8raid.service has begun with start-up
-- Unit systemd-fsck@dev-disk-by\x2dlabel-bench8raid.service has begun starting up.
-- Subject: Unit systemd-fsck@dev-disk-by\x2dlabel-benchboot8.service has begun with start-up
-- Unit systemd-fsck@dev-disk-by\x2dlabel-benchboot8.service has begun starting up.
Sep 14 09:28:48 bench6 systemd-fsck[1692]: /sbin/fsck.btrfs: BTRFS file system.
-- Subject: Unit systemd-fsck@dev-disk-by\x2dlabel-bench8raid.service has finished start-up
-- Unit systemd-fsck@dev-disk-by\x2dlabel-bench8raid.service has finished starting up.
Sep 14 09:28:48 bench6 systemd-fsck[1693]: benchboot8: clean, 325/80320 files, 38628/321268 blocks
-- Subject: Unit systemd-fsck@dev-disk-by\x2dlabel-benchboot8.service has finished start-up
-- Unit systemd-fsck@dev-disk-by\x2dlabel-benchboot8.service has finished starting up.
-- Subject: Unit systemd-fsck@dev-disk-by\x2dlabel-bench8raid.service has begun shutting down
-- Unit systemd-fsck@dev-disk-by\x2dlabel-bench8raid.service has begun shutting down.
-- Subject: Unit systemd-fsck@dev-disk-by\x2dlabel-bench8raid.service has finished shutting down
-- Unit systemd-fsck@dev-disk-by\x2dlabel-bench8raid.service has finished shutting down.
-- Subject: Unit systemd-fsck@dev-disk-by\x2dlabel-bench8raid.service has begun with start-up
-- Unit systemd-fsck@dev-disk-by\x2dlabel-bench8raid.service has begun starting up.
-- Subject: Unit systemd-fsck@dev-disk-by\x2dlabel-bench8raid.service has finished start-up
-- Unit systemd-fsck@dev-disk-by\x2dlabel-bench8raid.service has finished starting up.
Sep 14 09:28:48 bench6 systemd-fsck[1791]: /sbin/fsck.btrfs: BTRFS file system.
It looks like
btrfs.fsck is being invoked by
systemd twice, and is left on? Can anyone confirm this from these logs?
On pastebin.
But I have also found this:
Code: Select all
Sep 14 09:28:48 bench6 mount[1708]: mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
Sep 14 09:28:48 bench6 mount[1708]: missing codepage or helper program, or other error
Sep 14 09:28:48 bench6 mount[1708]: In some cases useful info is found in syslog - try
Sep 14 09:28:48 bench6 mount[1708]: dmesg | tail or so.
Sep 14 09:28:48 bench6 systemd[1]: mnt-backup.mount mount process exited, code=exited status=32
Sep 14 09:28:48 bench6 systemd[1]: Failed to mount /mnt/backup.
-- Subject: Unit mnt-backup.mount has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mnt-backup.mount has failed.
--
This is the mount point
/mnt/backup for the
bench8raid which is mounted after the system boots where I have to type CONTROL-D.
If its mounting correctly after it's filesystem check, why is it failing here and apparently triggering 'maintenance mode'? Here's the output of
blkid and the mount line from
fstab.
Code: Select all
# blkid | grep bench8raid
/dev/sdb1: LABEL="bench8raid" UUID="b65b2adf-8b40-457d-b59a-8d4c50d46967" UUID_SUB="7fc2c41e-ec19-4cee-8d3c-73964dd1c954" TYPE="btrfs" PARTLABEL="bench8_sdb1" PARTUUID="b5178a75-fa17-40c5-bd14-a881cef5a86e"
/dev/sdc1: LABEL="bench8raid" UUID="b65b2adf-8b40-457d-b59a-8d4c50d46967" UUID_SUB="2399e27b-1f2f-4b99-bdc2-6acf3ebb9220" TYPE="btrfs" PARTLABEL="bench8_sdc1" PARTUUID="f29c9f08-064d-43e8-8745-63d495cd4a8a"
/dev/sdd1: LABEL="bench8raid" UUID="b65b2adf-8b40-457d-b59a-8d4c50d46967" UUID_SUB="8220677b-8389-4633-96f8-ca14800fd2a8" TYPE="btrfs" PARTLABEL="bench8_sdd1" PARTUUID="b3c37ae9-be1e-4e7d-870a-70e8073a919f"
/dev/sde1: LABEL="bench8raid" UUID="b65b2adf-8b40-457d-b59a-8d4c50d46967" UUID_SUB="0230d173-c1ab-45b5-9097-f8aeb99344f0" TYPE="btrfs" PARTLABEL="bench8_sde1" PARTUUID="3a7a1b14-66e4-4c94-b4f6-f5b3e1aec0dd"
Code: Select all
# grep bench8raid /etc/fstab
LABEL="bench8raid" /mnt/backup btrfs defaults,noatime,compress=zlib 1 2
I seriously wonder what's going on here.
I dropped to single user and used
fstab based instructions to unmount and remount this array, and it works fine.
Code: Select all
# unmount /mnt/backup
# mount /mnt/backup
with no errors.
Does anyone know if there are more than one default units that attempt to mount
fstab filesystems? It's doing it twice, failing the first time, and (I'm guessing) triggering 'maintenance mode' because of the first failure.
Code: Select all
-- Subject: Unit mnt-backup.mount has begun with start-up
-- Unit mnt-backup.mount has begun starting up.
Sep 14 09:28:48 bench6 systemd[1]: mnt-backup.mount mount process exited, code=exited status=32
-- Subject: Unit mnt-backup.mount has failed
-- Unit mnt-backup.mount has failed.
Sep 14 09:28:48 bench6 systemd[1]: Unit mnt-backup.mount entered failed state.
-- Subject: Unit mnt-backup.mount has begun with start-up
-- Unit mnt-backup.mount has begun starting up.
-- Subject: Unit mnt-backup.mount has finished start-up
-- Unit mnt-backup.mount has finished starting up.
I guess I'll try commenting out
/mnt/backup in my
fstab and see if that changes this scenario. I'm also searching for multiple units ending in '.mount'.
Well there's smoke, but that damned old lady is still standing on her balcony threatening to jump:
Code: Select all
# systemctl list-units | grep .mount
proc-sys-fs-binfmt_misc.automount loaded active waiting Arbitrary Executable File Formats File System Automount Point
-.mount loaded active mounted /
boot.mount loaded active mounted /boot
dev-mqueue.mount loaded active mounted POSIX Message Queue File System
mnt-backup.mount loaded active mounted /mnt/backup
run-user-1000.mount loaded active mounted /run/user/1000
sys-fs-fuse-connections.mount loaded active mounted FUSE Control File System
sys-kernel-config.mount loaded active mounted Configuration File System
sys-kernel-debug.mount loaded active mounted Debug File System
tmp.mount loaded active mounted Temporary Directory
var-lib-nfs-rpc_pipefs.mount loaded active mounted RPC Pipe File System
var-tmp-portage.mount loaded active mounted /var/tmp/portage
systemd-remount-fs.service loaded active exited Remount Root and Kernel File Systems
