2.4.0 -> 2.4.1 Update Failed
-
No, that's the same one I used on that box, I'm fairly certain. I spot checked a few systems here running ZFS and I don't see that on any of them. One of them is a single disk the other is a mirror.
What other ZFS options did you choose? Do you remember?
-
I don't have any setup for it, but it looks like maybe that can end up that way with GELI encryption for the disk
-
You might have to refresh my memory on what options there were. I deleted the swap partition if I remember correctly. I didn't enable encryption.
-
Looks like MBR can also result in a bootpool (looking at the source, haven't tested it, no time today)
What does "zpool list" show? Do you see bootpool there?
-
: zpool list NAMEĀ Ā SIZEĀ ALLOCĀ FREEĀ EXPANDSZĀ FRAGĀ Ā CAPĀ DEDUPĀ HEALTHĀ ALTROOT zrootĀ 5.34GĀ 481MĀ 4.87GĀ Ā Ā Ā -Ā Ā 8%Ā Ā 8%Ā 1.00xĀ ONLINEĀ - -
I finally had some time to look into this today and it turns out that in those cases (Using MBR or geli), the zfs pool called "bootpool" isn't getting imported due to a fun chicken-and-egg scenario with the zfs cache file. The zfs pool cache tells the OS what pools to mount, but that cache file is in /boot/, so it doesn't get read at boot time because the file isn't there.
https://redmine.pfsense.org/issues/8063
I just pushed a fix. Once that is in snapshots you can upgrade to a 2.4.2 snapshot, you will need to run "zpool import bootpool" first and then it should proceed from there.
-
Am I running with install options that are untested and/or in beta? I just want to be able to click the update button and have it update without issues every time. What do you recommend? This isn't the first time I have had updating issues.
-
ZFS support as a whole is new and still considered experimental. People are excited about it, but it's not something we recommend yet. That said, it works fine for the majority of those using it.
Even more rare are those that need MBR support in ZFS, most people that can run 2.4 can run GPT which does not have this problem.
ZFS Encryption is also new and rarely used, and not practical to test since it requires a lot of manual intervention and direct console access.
If you install using the default ZFS options (which is GPT, no encryption) then you'll be OK.
-
Like I said before, the options I used were GPT and no encryption.
-
If you ended up with /bootpool, that cannot be true. It only gets activated for MBR or encrypted drives in the installer code.
-
Is there a way to verify without reinstalling?
-
gpart list | grep schemeIf it says MBR/BSD then it's MBR, if it's says GPT/GPT then it's GPT
Either way though, once the bootpool fix is in snapshots it will be fine no matter what you chose.
-
Ok, you are right, it's MBR. I had installed it twice and the first go-around I had chosen GPT. I thought I had the second time too but I guess not.
