Date: Wed, 16 Mar 2022 00:41:57 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 262580] fsck fails system startup if USB disk is not yet configured Message-ID: <bug-262580-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D262580 Bug ID: 262580 Summary: fsck fails system startup if USB disk is not yet configured Product: Base System Version: 13.1-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: misc Assignee: bugs@FreeBSD.org Reporter: karels@freebsd.org I have a USB disk listed in /etc/fstab on a Raspberry Pi 4 system; the USB = disk is not root. When booting 13.1-BETA1, the system startup fails because fsck cannot open the disk device; the disk then configures shortly thereafter. I discovered that this setup worked in 13.0-RELEASE because fsck failed to op= en the disk, but then exited with status 3, causing /etc/rc.d/fsck to invoke root_hold_wait() from /etc/rc.subr. Once the USB bus and disk configured, = fsck was re-run successfully. In 13.1-BETA1, fsck exits with a status of 8 after failing to open the disk, aborting the startup. I verified that the releva= nt change was in fsck by copying fsck* from 13.0 onto the 13.1 system; that combination works. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-262580-227>