Just finally got my HL15 setup and after I created my ZFS Pool it pops up with success! When I clicked the refresh it doesn’t show anything.
However if I goto the Overview or 45Drives Disks it shows that the ZFS Pools and file system are there.
Anyone know how to troubleshoot this? When I purchased the HL15 it was burned in so I assumed this would just work out of box.
I don’t use Cockpit/Houston, but there have been a few posts here like the following suggesting switching between the cockpit-zfs and cockpit-zfs-manager modules due to some sort of bug, or perhaps those bugs are resolved and you can upgrade cockpit-zfs.
Perhaps @Braeden-45Drives can reply with how you should proceed.
https://forum.45homelab.com/t/45drives-zfs-shows-no-pools-network-path-connection-issues/3338/3
You could also try export the pool via CLI and see if it appears in the GUI to import.
I am a novice to this so I’ll have to search online to figure out how to do that but atleast it’s something to try.
You can also send a note to info@45homelab.com for support.
You can export a pool with;
zpool export <poolname>
If it doesn’t show up in the UI that way, the reverse command is;
zpool import <poolname>
To manage packages on Rocky Linux I think you use the dnf command.
I did send them a note at support. Will probably be talking to them later today for additional steps.
Hey @Bonnifur
Did you get in contact with a support specialist already for this?
Unfortunately we have removed the cockpit-zfs-manager from our repos so this sort of fix does not work anymore.
I see that creation of the pool went through. Are you still running into issues?
No yet. Just received an email that I should be in contact with someone later today.
Update: Support will look into the cockpit-zfs module not showing the zpool and get with R&D about the updates on. But besides that the ZFS is created and running fine. I will update this whenever I get any updates.
Update: I finally have a fix to my issue, I would like to thank again the support team for all the time they poured into looking at this. The fix that worked was to set the default python3 to 3.6, since I am running Rockylinux8.
"To do this you would use the update-alternatives --config python3 command.
From there it will ask you to select a version of python.
It should look something like this.
Mine showed the following:
So once I changed it to 3.6 it fixed the issue.
