Date: Wed, 23 Jul 2025 01:21:10 +0100 From: void <void@f-m.fm> To: freebsd-current@freebsd.org Subject: Re: zfs panic VERIFY3U Message-ID: <aIAq9t0LKFhOu5iV@int21h> In-Reply-To: <CAOtMX2jvORU-_s4xLtgRFum9BD3mWsMRzRTVfDD1yvFa2%2BhC7g@mail.gmail.com> References: <aH7pM0iZ-XMihOrn@int21h> <aH7rrH8ISou9vN4k@int21h> <aH-I4-FpfLJgKp3M@int21h> <CAOtMX2jvORU-_s4xLtgRFum9BD3mWsMRzRTVfDD1yvFa2%2BhC7g@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
On Tue, Jul 22, 2025 at 11:46:11AM -0600, Alan Somers wrote: >Is this still a problem for you, or is it all solved? Now it is. The fix, for the benefit of archives: 0. pull the "failing" disk from the array 1. comment zfs out of /boot/loader.conf 2. reboot machine, complete make buildworld kernel installkernel world etc 3. add hw.ciss.expose_hidden_physical="1" to loader.conf 4. if this is in sysctl.conf, comment it out 5. poweroff now && unplug from wall socket, wait a few mins 6. turn on & boot machine 7. insert the "failing" disk. See it in /dev if it needs resilvering, it'll resilver automatically. Run a zpool scrub afterwards. --help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?aIAq9t0LKFhOu5iV>