If you already have that as a zfs dataset, then do a full snapshot of that, send receive it. Destroy the original. send/receive it back and restore it.
"Concurrent coexistence of Windows, Linux and UNIX..." || Ubuntu user # 33563, Linux user # 533637 Sticky: Graphics Resolution | UbuntuForums 'system-info' Script | Posting Guidelines | Code Tags
/boot is part of the / dataset, not its own dataset. I think I'll keep it all under / for now because ZBM cannot be used if /boot is its own dataset. Simplest way forward for me, minimize changes. I may do something else when I consider moving to 24.04 later this year. I don't think making it its own dataset would help anything, based on the bug reports, the issue seems to be with the pool, others say that even deleting all snapshots from the pool doesn't help. It seems that it needs to be its own bpool, fresh, no snapshots.
Last edited by tkubnt; January 16th, 2024 at 11:47 PM.
My experience with "ZFS Boot Menu" is fairly limited, I tried it about a year ago, to see how it worked and how it did. Installed it on a few VM's I had in my test-suite to play with it. So maybe about a week of testing... Other than that, it's been a while. Please tell me how that goes for you. If it works okay, (LOL! Even if it doesn't...) please share with others (here) how you fixed your issue with it here, so other's might benefit from that. That is how we all benefit from sharing are experiences with each other.
Last edited by MAFoElffen; January 17th, 2024 at 04:07 AM.
I have successfully moved to ZFSBootMenu and I'm happy with it, fine piece of software to pair with ZFS. So many features in a bootloader! fzf, ssh, tailscale even, booting from snapshots, etc. It's a mini OS. A few tips for others: - you can use the portable version from a flash drive to help you boot if the system doesn't otherwise have other issues - /boot must be in the same dataset as /, it cannot be in its own "bpool" pool or even dataset. But this is easy to fix, you can use the ZBM recovery shell, import both pools and rsync /boot to the / dataset (then later on when happy destroy the previous boot pool/dataset) - some discussion on how to go from Grub to ZBM: https://github.com/zbm-dev/zfsbootme...omment-8150472 - reading the docs really helps - the help from the authors is outstanding
Thank you for sharing that. I created a portable ZBM USB and am exploring it again... So this is "Solved" now? If so, then we mark our own threads that we start, as solved. Select the "Thread Tools" link in hte upper right , then "Solved". That will help other looking to solved their similar problems find what helped you.
Last edited by MAFoElffen; January 19th, 2024 at 04:11 PM.
I encountered this issue too and documented my workaround here: https://bugs.launchpad.net/ubuntu/+s...73/comments/10 In summary replace the ubuntux64.efi on the ESP with one extracted from the Debian sid package and contains the necessary fix.
After this thread, it was found that there was a related Bug with Grub2. Reported at OpenZFS & GNU's Savannah (look at the last linked thread). Grub2 12.2 has ZFS patches that fix it. The patches are presently being back-ported for Mantic and Jammy. Bug Report for this problem: https://bugs.launchpad.net/ubuntu/+s...d/+bug/2051999 Three workarounds. Working on an accepted fourth work-aroud with a different PPA, until the patches get back-ported to Jammy... RE: https://ubuntuforums.org/showthread.php?t=2495131 For anything further... Please reply to the last linked thread, where we are addressing this, and keeping the status updated for the Forum there.
View Tag Cloud
Ubuntu Forums Code of Conduct