On 1/25/2021 2:37 PM, Toomas Soome via freebsd-current wrote: > >> On 25. Jan 2021, at 21:31, Michael Butler via freebsd-current >> <freebsd-current@freebsd.org> wrote: >> >> I have a few machines on which I've been hesitant to run 'zpool upgrade' as >> I'm not sure of the (boot?) implications. They report like this .. >> >> imb@toshi:/home/imb> uname -a >> FreeBSD toshi.auburn.protected-networks.net 14.0-CURRENT FreeBSD >> 14.0-CURRENT #25 main-eb61de5b78: Fri Jan 22 10:03:02 EST 2021 >> r...@toshi.auburn.protected-networks.net:/usr/obj/usr/src/amd64.amd64/sys/TOSHI >> amd64 >> >> imb@toshi:/home/imb> zpool status >> pool: zroot >> state: ONLINE >> status: Some supported features are not enabled on the pool. The pool can >> still be used, but some features are unavailable. >> action: Enable all features using 'zpool upgrade'. Once this is done, >> the pool may no longer be accessible by software that does not support >> the features. See zpool-features(5) for details. >> >> Is it safe to upgrade the root pool? >> >> imb > We can not boot from encrypted pool and draid. Rest is all ok. Please note, > you may need to update the bootblocks. > last Friday on zoo.freebsd.org, m...@freebsd.org and I could not boot again because v2 bookmarks were on the boot pool. I had to boot from another disk, remove the bookmarks and then boot. This was on RELENG_13 (stable/13-c256203-g51d73a3e46c)
---Mike _______________________________________________ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
