Login always shows partitions to be fsck-ed, even after reboot.
Bug #1817496 reported by
Kevin O'Gorman
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| systemd (Ubuntu) |
Expired
|
Undecided
|
Unassigned | ||
Bug Description
This system reports /dev/sda5 will be checked on the next reboot. Maybe it is (it's EXT4 on as SSD drive, so it could be too fast to notice), but the message persists even after such a reboot.
I would expect it to go away.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: login 1:4.5-1ubuntu1
ProcVersionSign
Uname: Linux 4.15.0-45-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Sun Feb 24 17:27:50 2019
SourcePackage: shadow
UpgradeStatus: No upgrade log present (probably fresh install)
Revision history for this message
| Kevin O'Gorman (kogorman-pacbell) wrote | #1 |
Revision history for this message
| Serge Hallyn (serge-hallyn) wrote | #2 |
| affects: | shadow (Ubuntu) → systemd (Ubuntu) |
| Changed in systemd (Ubuntu): | |
| status: | New → Incomplete |
Revision history for this message
| Serge Hallyn (serge-hallyn) wrote | #3 |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #4 |
| Changed in systemd (Ubuntu): | |
| status: | Incomplete → Expired |
To post a comment you must log in.
You should be able to manually do
fsck /dev/sda5
If the filesystem on sda5 is listed in /etc/fstab, then sixth fstab field for that filesystem should be '2'. If it is 0, then indeed it won't be fsck'd on reboot.
fstab is owned by util-linux, but system bringup belongs to systemd, so I'm assigning this to the systemd package. However I suspect fstab lists '0' for the sixth field, and the system is doing what it is told.