Skip to content
This repository has been archived by the owner. It is now read-only.

fsck never runs on the ESP #2245

Closed
bgilbert opened this issue Nov 10, 2017 · 1 comment
Closed

fsck never runs on the ESP #2245

bgilbert opened this issue Nov 10, 2017 · 1 comment

Comments

@bgilbert
Copy link
Member

@bgilbert bgilbert commented Nov 10, 2017

Issue Report

Bug

Container Linux Version

$ cat /etc/os-release
NAME="Container Linux by CoreOS"
ID=coreos
VERSION=1590.0.0+2017-11-09-0113
VERSION_ID=1590.0.0
BUILD_ID=2017-11-09-0113
PRETTY_NAME="Container Linux by CoreOS 1590.0.0+2017-11-09-0113 (Ladybug)"
ANSI_COLOR="38;5;75"
HOME_URL="https://coreos.com/"
BUG_REPORT_URL="https://issues.coreos.com"
COREOS_BOARD="amd64-usr"

Environment

Any

Expected Behavior

fsck is run on the ESP when necessary.

Actual Behavior

fsck never runs on OS filesystems other than /. On every subsequent boot after an unclean shutdown, the kernel says:

[   38.087266] FAT-fs (vda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.

Reproduction Steps

  1. Forcibly power off the system.
  2. Boot and check dmesg.

Other Information

/usr/share/oem is journaled, so there's less of a problem in that case. /boot is not journaled.

The fix should be as simple as adding a dependency to boot.mount in init.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.