Hi everyone,
Has anyone had success installing and using the 45D Drive Map Plugin in Unraid with an HL15 1.0 model system?
Currently the plugin does not function and complains about ZFS pools, directing the user to a 45Drives Cockpit ZFS repo that does not have any documentation for Unraid users.
Neither the plugin details in the Unraid CA App catalog, nor the README.md for the Plugin GitHub repo indicate the HL15 1.0 is unsupported.
Error message being reported:
ZFS status displayed by this module for zpool 'rust' may be incomplete.
This module can only display zfs status information for devices that are created using a device alias.
This can be done using the 45Drives cockpit-zfs-manager package: https://github.com/45Drives/cockpit-zfs-manager/releases/
I am using a Prebuilt HL15 1.0 purchased directly from 45drives/45homelab.
Chassis, Supermicro Motherboard, Intel CPU, RAM and PSU are all from 45drives/45homelab included as part of the fully built HL15 1.0 model.
If only they didn’t explicitly mention the HL15 in the summary and description of the plugin template in unraid though (see attached screenshot).
The messaging in the error seems to point to the issue being with how ZFS pools are discovered. This would lead me to believe there are underlying dependencies that are missing, which the error seems to be indicating.
I imagine it may be that 45Drives is shipping X15’s with the dependencies preinstalled since those units arrive with unraid preloaded.
My experience with the 45Drives Cockpit ZFS Manager plugin on my X15 is that the warning seems to be about how ZFS pool members are referenced.
My regular HDDs show up as /dev/sdX and display fine, but those are XFS array disks. The warning only appears on my ZFS pools where the vdev members are shown as raw NVMe names like nvme0n1p1 instead of stable alias paths like /dev/disk/by-id/... or /dev/disk/by-vdev/....
So I do not think this is Cockpit having a general problem with /dev/sdX or /dev/nvmeXnY device names. It seems specific to the 45Drives ZFS plugin expecting ZFS vdevs to use alias-based references for full status reporting.
In my case, Unraid presents the ZFS pool members using the raw nvmeXnYpZ names, and that is what triggers the incomplete-status warning for my setup on a X15 using Unraid 7.3.1.
I am not sure which is more likely, Unraid changing how it creates/imports ZFS pools to use stable aliases, or the 45Drives plugin being updated to better handle ZFS pools that use raw device names.
I’m running the latest stable version of Unraid, v7.3.1.
Over on the GitHub page for the plugin, we’ve received some traction there, indicating that the HL15 indeed should be supported, though which iteration (1.0 or 2.0) is still unclear and awaiting confirmation.
Indeed, it does become a question of who is going to make the changes necessary for ZFS pools created in Unraid on systems that did not ship with Unraid preinstalled by 45Drives.
Though my suspicions lean toward this being a bug rather than a fundamental issue. I.e., if you needed to install a clean version of Unraid on an existing X15 system, it would not contain any configuration tweaks implemented by 45Drives.
If anyone has an X15 and wants to test this theory, the results, particularly if the plugin does not work on a clean install of Unraid on an X15 system, would certainly help pinpoint where the problem is.
