.org/archives/freebsd-bugs
List-Help: <mailto:freebsd-bugs+help@freebsd.org>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Subscribe: <mailto:freebsd-bugs+subscribe@freebsd.org>
List-Unsubscribe: <mailto:freebsd-bugs+unsubscribe@freebsd.org>
Sender: owner-freebsd-bugs@FreeBSD.org
MIME-Version: 1.0

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D278993

            Bug ID: 278993
           Summary: fsck not checking disk if sysctl
                    kern.boottrace.enabled=3D1 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).=20

After troubleshooting, I was able to find a root cause - it was
kern.boottrace.enabled=3D1 in the /boot/loader.conf. This is caused by miss=
ing
"$autoboot" variable in the /etc/rc.d/fsck when that script is running, so =
it
does not run correctly.=20

To reproduce on the clean system:

1. Add kern.boottrace.enabled=3D1 to the /boot/loader.conf
2. Add background_fsck=3D"NO" to the /etc/rc.conf
3. Reset system and check logs. Fsck will not be started.

--=20
You are receiving this mail because:
You are the assignee for the bug.=