Date: Mon, 05 Dec 2022 05:32:16 +0000 From: bugzilla-noreply@freebsd.org To: fs@FreeBSD.org Subject: [Bug 268157] /etc/rc.d/zpool runs too early, before usb disks available Message-ID: <bug-268157-3630-WVVPd4CYHy@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-268157-3630@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268157 Graham Perrin <grahamperrin@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|freebsd-arm@FreeBSD.org |usb@FreeBSD.org Hardware|arm64 |Any --- Comment #4 from Graham Perrin <grahamperrin@freebsd.org> --- Thanks, now I might have a clearer idea of what you're describing. (In reply to Barney Wolff from comment #3) > … a vital pool that's on a permanently-attached internal disk > fails to get imported because an unimportant pool on a usb disk has > vanished. For me, occasionally, boot (from OpenZFS on adao) fails in the presence of some combination of external USB devices. IIRC multi-user mode either (a) is not reached, or (b) does not progress. The 'offending' device is not necessarily one that contains a pool. Sometimes it might be a cache device; other times IIRC it might be not storage-related. Sometimes, randomness – a failure to boot with a particular set of USB devices might be followed by a successful boot with the same set, with no change to connections. When the bug bites: I remove the device, boot continues. There might be an existing bug report for this type of thing. -- You are receiving this mail because: You are on the CC list for the bug.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-268157-3630-WVVPd4CYHy>