For context, I have a HL15 with 15 x 10TB WD Purples to be used as surveillance storage. Currently have 14 drives set up wtih raidZ2. 1 not set up yet for misc photo and file storage.
I am having some trouble with 45Drives ZFS not showing pools after creation. Followed startup guide to the T. Creates a pool and under 45Drive Disks it hows 14 Drives in a RaidZ2. If I run ‘zpool list’ it shows the pool as being active and total disk space.
I also had it connected to the Axis Server as a storage location directly from cameras. However, after a restart it lost connection and it now refuses to reconnect. Says it cannot find the share even though nothing has changed. All services are running. It took 2 hours of entering the same username and password as well as \address\share and then miraculously just worked… the first time it was set up
See photo for the errors recieved.
ALSO the service error is for ‘tuned’… not able to get it to started.
Clearly I have set something up incorrectly lol. Especially since no pools show up under the ‘45Drives ZFS’ tab only through terminal. My system is up to date as well.
Besides posting here you might also send a note to info@45homelab.com for support. Based on the post you linked and a couple others, they seem to be having problems with cockpit-zfs. See if you can figure out if cockpit-zffs or cockpit-zffs-manager is installed and which version.
I don’t have the full build, so aren’t sure exactly what’s in the startup guide, but did the ZFS tab arrive not working? Or did it stop working after some change?
Hey @AlexD
The ZFS module has been giving us some issues, Do you know if removing cockpit-zfs and downloading cockpit-zfs-manager has the pool show up?
Also for the SMB config, how are you setting up the smb server to the camera? Can they access the server if you use an IP rather than an allias? For example \192.168.x.x\ACSRecording\WPRC vs. \servername\ACSRecording\WPRC
Do you mind sending over the SMB config?
I see now that the ZFS tab is working after removing Cockpit-zfs and installing manager. I was creating the pools under “45Drives ZFS”. The actual ‘ZFS’ Tab was not present at the initial installation. I can see my pool as well.
Thank you for sharing the screenshots; they were very helpful. Based on what you’ve provided, it looks like there’s a configuration conflict involving your SMB shares.
It appears you have an SMB share defined in both the ZFS tab and the File-Sharing tab. We strongly recommend against using the SMB share option within the older ZFS tab, as this can cause unexpected behaviour. The latest 45Drives ZFS implementation has removed this option in favour of using the dedicated File-Sharing tab.
To resolve this:
Remove the SMB share from the ZFS tab.
Retain the configuration in the File-Sharing tab.
Restart the SMB service.
Ensure firewall ports are open for SMB.
Next, create a user on the server and set an SMB password for that user. This password is different from the Linux user password. You can set the SMB password using either the Identities tab or via the CLI using:
smbpasswd -a USERNAME
Finally, ensure the user has access to the shared folder location:
Use Navigator to assign ownership or group membership.
Confirm that the folder permissions include read, write, and execute.
Once everything is set up, you should be prompted to log in with the new SMB credentials when accessing the share from your client.
Please let me know if you run into any issues or need further assistance, I’m happy to help!
Hey Hutch,
Thank you for this. I am a little lost about using Navigator to assign ownership. I used Identities to assign to root group (should i assign to samba group?) I can hit the address from windows but it says password is incorrect.. Tried changing smb password but no luck.
This is where you want to set the SMB password for your user.
Once the password is set, the last thing we need to do is make sure you user has access to the data in Navigato.r
To do this, you will want to go to your ZFS pool in Navigator and find your Filesystem/Dataset you created (NOTE: if you did not create one, go back to the ZFS tab and do so first)
Now, change the permissions of the filesystem like the image below
Hey Hutch, I tried all of the above, i ensured that the group had permissions in the dataset. I even tried changing the user to owner. See screenshots. Sorry for all the back and forth.
Have you tried connecting through just the IP rather than the entire path?
For example
\ \192.168.15.80
rather than
\ \192.168.15.80\ACSRecordings\WRPC
Instead of the back and forth I would like to ask for a few things all at once and a few things to try!
Do you mind sending a screenshot of your Networking tab in Houston?
Do you mind showing what happens when you try to go to the specific IP
Can we also see your ZFS tab where you made the dataset for WPRC.
I did a little testing on my side. Can you make sure that SELinux is set to permissive mode. You can do this by going to the SELinux tab under tools and clicking the button that says enforcing and change that to permissive. Hopefully this should resolve the issue!
Hey @AlexD
That should stop it from ever turning back on! If it persists through reboot you can use the command sed -i ‘s/^(SELINUX=).*$/\1permissive/’ /etc/selinux/config
I am glad that we finally got it all figured out.
If you ever run into anymore issues please let us know
