Hey guys,
I will quickly describe my situation here, that led to a very exciting morning ;-)
This post is intentionally a separate one as the others found here (like https://forums.freebsd.org/threads/cant-read-mos-of-pool-zroot.71517/ or https://forums.freebsd.org/threads/zfs-cant-read-mos-of-pool-rpool.57183/) seem to have another cause.
So the storyline to get things started:
I will quickly describe my situation here, that led to a very exciting morning ;-)
This post is intentionally a separate one as the others found here (like https://forums.freebsd.org/threads/cant-read-mos-of-pool-zroot.71517/ or https://forums.freebsd.org/threads/zfs-cant-read-mos-of-pool-rpool.57183/) seem to have another cause.
So the storyline to get things started:
- FreeBSD 12.1-RELEASE server, added current patches with
freebsd-update fetch install
. - Server has a ZFS mirrored setup as "rpool".
- Reboot
- During services startup FreeBSD panicked (I have no clue why that happened. Haven't seen that before).
- Stack trace getting written to zpool
- FreeBSD reboots
- I switched to single user mode, checked zpool. Everything looks fine at
zpool status
. - So I rebooted
- This lead to the mentioned error of "Can't read MOS of pool rpool"