[Bug 278993] fsck not checking disk if sysctl kern.boottrace.enabled=1 is set
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 278993] fsck not checking disk if sysctl kern.boottrace.enabled=1 is set"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 278993] fsck not checking disk if sysctl kern.boottrace.enabled=1 is set"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 278993] fsck not checking disk if sysctl kern.boottrace.enabled=1 is set"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 278993] fsck not checking disk if sysctl kern.boottrace.enabled=1 is set"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 278993] fsck not checking disk if sysctl kern.boottrace.enabled=1 is set"
- Reply: bugzilla-noreply_a_freebsd.org: "[Bug 278993] fsck not checking disk if sysctl kern.boottrace.enabled=1 is set"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 15 May 2024 05:58:52 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=278993
Bug ID: 278993
Summary: fsck not checking disk if sysctl
kern.boottrace.enabled=1 is set
Product: Base System
Version: 14.0-RELEASE
Hardware: Any
OS: Any
Status: New
Severity: Affects Some People
Priority: ---
Component: conf
Assignee: bugs@FreeBSD.org
Reporter: samm@FreeBSD.org
Recently I found that some of my VPS-s fsck is not running (what is causing
failed mount root in case of hard reset).
After troubleshooting, I was able to find a root cause - it was
kern.boottrace.enabled=1 in the /boot/loader.conf. This is caused by missing
"$autoboot" variable in the /etc/rc.d/fsck when that script is running, so it
does not run correctly.
To reproduce on the clean system:
1. Add kern.boottrace.enabled=1 to the /boot/loader.conf
2. Add background_fsck="NO" to the /etc/rc.conf
3. Reset system and check logs. Fsck will not be started.
--
You are receiving this mail because:
You are the assignee for the bug.