fsck not running at all on reboot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
After upgrading some servers from 16.04 to 18.04 I'm met with a MOTD that says:
*** /dev/xvda1 should be checked for errors ***
I added "fsck.mode=force" to GRUB_CMDLINE_
Surprisingly I was met with the same error message in MOTD when logging in. I then ran tune2fs to see when the last check was performed and this is the output:
$ sudo tune2fs -l /dev/xvda1 | grep checked
Last checked: Wed Sep 12 16:17:00 2018
I then tried to change mount count to 1 with tune2fs -c 1 /dev/xvda1, but after another reboot I was still met with the same error message and the timestamp for last checked was unchanged.
I have the same problem on all the servers that was upgraded from 16.04 to 18.04, but also on a new server installed directly with 18.04.
In should be mentioned that the servers are AWS EC2 instances, so I have no way of trying to run fsck from a liveusb.
Another user has reported the same issue here:
https:/
I'm not quite sure what information is needed, but attached are some basic information about the system.
Please let me know if you need any any other outputs or logs.
Edit1: I tested fsck.mode=force on my laptop running Ubuntu 18.04.1 LTS (Xubuntu) and it works fine. Seems to be related to the server edition.
summary: |
- fsck not running on reboot when fsck.mode=force is set + Ubuntu 18.04 Server: fsck not running at all on reboot |
summary: |
- Ubuntu 18.04 Server: fsck not running at all on reboot + fsck not running at all on reboot |
description: | updated |
affects: | ubuntu → e2fsprogs (Ubuntu) |
Changed in systemd (Ubuntu): | |
status: | Expired → Confirmed |
I am having this issue also.
fsck is not running on my root drive on Ubuntu 18.04 LTS server edition
I have tried fsck.mode=force in grub on the kernel command line to no success.
I have set the mount count to 1 with tune2fs -c 1 /dev/sda2 and rebooted and still no fsck. Instead I just get a text message saying you need to do a fsck on /dev/sda2.
------- ------- ------- ------- ------- ------- ------- -
one@localhost:~$ sudo tune2fs -l /dev/sda2
tune2fs 1.44.1 (24-Mar-2018) c6ab-11e8- 93a6-7085c27cfa ec directory_ hash 2b26-4b50- 97e1-21952c171d 2b
Filesystem volume name: <none>
Last mounted on: /
Filesystem UUID: 36589912-
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent 64bit flex_bg sparse_super large_file huge_file dir_nlink extra_isize metadata_csum
Filesystem flags: signed_
Default mount options: user_xattr acl
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 6160384
Block count: 24641536
Reserved block count: 1232076
Free blocks: 19441110
Free inodes: 5417720
First block: 0
Block size: 4096
Fragment size: 4096
Group descriptor size: 64
Reserved GDT blocks: 1024
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Flex block group size: 16
Filesystem created: Tue Oct 2 20:25:28 2018
Last mount time: Tue Oct 9 22:14:49 2018
Last write time: Tue Oct 9 22:13:35 2018
Mount count: 25
Maximum mount count: 1
Last checked: Tue Oct 2 20:25:28 2018
Check interval: 0 (<none>)
Lifetime writes: 179 GB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 32
Desired extra isize: 32
Journal inode: 8
First orphan inode: 1591485
Default directory hash: half_md4
Directory Hash Seed: 5dcfe344-
Journal backup: inode blocks
Checksum type: crc32c Checksum: 0x305a8ddb
I am not running on cloud, just a home PC with AMD Ryzen 5
------- ------- ------- ------- ------- ------- -
Linux localhost 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic