Samba that was installed on the base HL15 – I was one of the first to purchase when it was available to the public – which is current at 4.19.4-9.el8_10_45d
Rocky 8.10 wants to use 4.19.4-12.el8_10.
My question is the version that 45Drive made/installed/forked going to be updated?
I was going to have this node join a REALM within my home lab but that package would like to see samba to upgrade
given that Samba/NFS with the HL15 has unique behavior including the cockpit/houston UI for File Sharing using this library.
I don’t want to upgrade and move away from this build. Has anyone who has the first units using Rocky 8 seen this issue?
I would like to move to Rocky 9 but if cockpit does not have similar updates on Rocky 9 I don’t mind to wait. But I did not see anything in the forum when I was searching .
Hutch, Thank you for the response. You answer comes at the right time too. I am planning some home on the homelab during my holiday PTO work (in the US).
I can upgrade Rocky on the HL15
Install the “Dust Filter (Black)” key
Install the Rail rail cable management arm
As well as to start the outdoor decor Christmas Lights.
Coming back to the base HL15 itself, I have tried to keep my original HL15 box’s OS and its default configuration. Can I assume it would be a simple straightforward upgrade from Rocky 8 to Rocky 9.6 similar to how I would upgrade debian from its major releases? Is there anything I would watch out? ZFS should be upgraded without any issues? IS the “file sharing” module working the same way?
Is there anything special for the houston UI needed for the install script?
I shared some of the images to show how normal this HL15 box (was kept) – my homelab / home network has a whole FQDN as well
Braeden,
Thank you for the response. I did do a full reinstall and before I did that I also clone the old Rocky 8 on the NVMe that came with the unit. After the clean Rocky 9.6 install, I am now seeing the cockpit-file-sharing, maybe I missed it earlier. I have this motherboard “X11SPH-nCTPF” and forced Rocky 9 to load mpt3sas.
The hardware was fully recognized and detected all the drive as I reused the old /etc/vdev_id.conf
I asked about the file-sharing as the spool status has an issue with a samba share that was created on Rocky 8.
As I write this follow-up, these were the two things I noticed.
Hey @pcHome, sorry for the delays. Could you share the 2 issues you noticed or are still having
For the SMB shares in the file-sharing tab, you could have exported your existing SMB.conf file and then reimported it into the Rocky9 OS. If you still have the Rocky8 backup, you could boot back into that and grab that export to then use on Rocky9
This will keep all your shares and permissions the same as they were before the upgrade
I have resolved the issue once I got cockpit-file-sharing installed. I might have missed it initially as I was doing much of the install using a manual process. I am working on a bash script to automate the process.z
The first message experience is what I anticipated due to the Rocky 9 having a different version of zfs status: Some supported and requested features are not enabled on the pool. The pool can still be used, but some features are unavailable. action: Enable all features using 'zpool upgrade'. Once this is done, the pool may no longer be accessible by software that does not support the features. See zpool-features(7) for details. scan: resilvered 10.7M in 00:00:01 with 0 errors on Mon Nov 24
This zpool was created using a server called Chenbro NR12000. Moving the zpool over to HL15 was simple and easy. I did a similar zpool upgrade as I moved away from FreeNas/TrueNas to have HL15 host the zpool using Rocky 8 and cockpit.
After the clean install to Rocky 9 and after I loaded the module mpt3sas, I noticed this zpool message:
cannot share ‘zpoolName/HPScans: system error’: SMB share creation failed
I used this command to remove it:
zfs set sharesmb=off zpoolName/HPScans
At the moment all of the services are running including zfs-share.service
8:46 AM Finished ZFS file system shares. systemd
8:46 AM Starting ZFS file system shares… systemd
As of this post, I am not having any issues. I did notice samba 4.21 changes from samba 4.1x as the new version does disable older protocols (SMB1, NTLMv1, and LANMAN).
@Hutch-45Drives
would it be possible to know what might be forked within the samba version that is shipped with 45drives_enterprise than from Rocky 9.6 version? The versions seems close
samba-4.21.3-14.el9_6_45d is 45drives &
samba-4.21.3-14.el9_6 is the version from Rocky
is there anything changed in a manner that would break what samba and FreeIPA interact as samba will use:
SSD for imapd
keytabs from FreeIPA
verify Kerberos PAC from AD
follow Red Hat IdM guidance
I am asking because I wanted to have FreeIPA be a true IDP within my homelab.
I have samba working using the local accounts, but I wanted to change security current set as user to ads and then add idmap config settings to use the realm managed by FreeIPA.
just curious if anyone reported issues with FreeIPA and the forked version of samba
The version of SMB we provide is primarily designed for our clustered environments, as it includes compatibility with CTDB, which we use for high-availability SMB.
For a single-server setup, those clustering features are not required, so either version of SMB will work for you.
