I apologize if this is in the wrong area.
I have an HL15 and I initially installed Unraid. I am currently testing Rocky 8.10 with Houston UI. I need guidance creating the server info JSON so that my drives will map in the Houston interface. I believe the issue may be that I have a SAS HBA connected to the backplane. How might I go about creating the JSON so dmap sees the drives?
Thanks in advance!
Hi @sinewaverx,
I will make an attempt here as I am using a fully build HL15 with Rocky 8.10. As I am not used UNRAID, I share what packages I installed on multiple servers (my proxmox servers, a development haproxy server, etc)
here is the list of packages that were installed on my fully built HL15 (back when it was first offered):
dnf list --installed | grep cockpit
cockpit.x86_64 310.4-1.el8_10 @baseos
cockpit-45drives-hardware.noarch 2.3.6-2.el8 @45drives_stable
cockpit-benchmark.noarch 2.1.1-1.el8 @45drives_stable
cockpit-bridge.x86_64 310.4-1.el8_10 @baseos
cockpit-file-sharing.noarch 3.3.7-1.el8 @45drives_stable
cockpit-identities.noarch 0.1.12-1.el8 @45drives_stable
cockpit-machines.noarch 310.3-3.el8_10 @appstream
cockpit-navigator.noarch 0.5.10-1.el8 @45drives_stable
cockpit-packagekit.noarch 250.1.1-1.el8 @45drives_stable
cockpit-pcp.x86_64 250.1.1-1.el8 @45drives_stable
cockpit-storaged.noarch 250.1.1-1.el8 @45drives_stable
cockpit-system.noarch 310.4-1.el8_10 @baseos
cockpit-ws.x86_64 310.4-1.el8_10 @baseos
cockpit-zfs-manager.noarch 1.3.1-1.el8 @45drives_stable
The cockpit package storaged does the following:
https://cockpit-project.org/guide/latest/feature-storaged
here is a snippet to serve as the TL:DR
If available on the system, Cockpit uses storaged to configure and monitor storage, disks, mounts etc. on the system. This functionality is present in the Cockpit storaged package.
The storaged project is originally based on a project called udisks and added support for many more features such as LVM, iSCSI, Multipath, and BTRFS. The same tools and backwards compatible API are available between storaged and udisks the projects. Cockpit can use udisks but disables many of it's storage related features, including updating /etc/fstab and /etc/crypttab for stability reasons.
For non root users, storaged controls access to its APIs via Policy Kit and a user logged into Cockpit will have the same permissions as they do from the command line.
To perform similar tasks from the command line, use the storagedctl command:
$ udisksctl dump
...
To perform LVM tasks, you may use the various LVM commands, such as vgcreate, lvresize and so on. Cockpit will detect such changes made at the command line.
Cockpit recognizes devices with multiple paths and can start the multipathd service in case it is not running. On the command line, you can control multipath features with the mpathconf, multipathd, and multipath commands.
To manage iSCSI initiators from the command line, you can use iscsiadm and related tools.
In my experience with these cockpit* packages, the drives were recognized (I have a fully built HL15). I did not have to do anything extra.
From what I read online, cockpit-storaged will install dependencies that include a package called clevis.x86_64 (and clevis will load its dependencies).
here is how I normally attempt to install cockpit on any rocky linux system:
dnf install cockpit-bridge.x86_64 cockpit-composer.noarch cockpit-doc.noarch cockpit-ostree.noarch cockpit-packagekit.noarch cockpit-podman.noarch cockpit-session-recording.noarch cockpit-storaged.noarch cockpit-system.noarch cockpit-ws.x86_64 subscription-manager-cockpit.noarch
I hope any of the information helps you. I was attempting to look at dmap the comamnd itself, but I need to cut my post short (at this moment).