Drive Mapping help

I am like a lot of people that when I got my HL-15 I went and put a different OS on it. I have came back to Rocky with Houston UI, I have everything working except for 45Drives Disks section. I get this error “dmap is not compatible with HomeLab-HL15 Servers. You can perform device mapping manually using ‘dalias’ Try running: 'sudo dalias -t HL15”

When I run that it wants me to put in my drives and I have tried that. I dont have all the drives populated and I dont know how to make it go to the next line. Is there anything I can do to get this to work again like when I first got it?

Have you seen this thread;

I don’t have a full build, but I think you are supposed to be able to use a single drive and I think the tool is automatically supposed to iterate through each slot as the drive is detected.

Maybe be sure you have the latest version of the utility, or if you can follow it try the process @pxpunx describes at the end to build and reload the config file manually?

I have searched for days but never found this article. Thank you so much for pointing this out following @pxpunx I got everything working correctly.

My only issue now is when I click on a disk it says not part of a zpool. It is in a pool I have tried to remove the zpool and then re create it. But for some reason I am unable to completely destroy the zpool. But I am happy just having it show the drives.

Did you have data from an old ZFS pool that you are trying to use in Rocky/Houston? Or are you starting the pool from scratch after the Rocky install? If you had an existing pool on the disks, did you “export” it before fiddling with the OS, and did you “import” it to get it into Rocky?

This isn’t exactly your issue, but maybe installing the cockpit-storage module (it might be cockpit-storaged) would help;

Hopefully someone more versed in Houston than me can help.

Houston is a pretty good solution but, in my opinion, doesn’t do a good job exposing to the user details about errors. When I was playing around with it on my HL15, I often found I had to drop to the command line to figure out a generic error from Houston.

I suspect there is a mismatch between the aliasing and your zpool. What do you see when you run zpool list -v POOLNAME on the command line? You should see the aliases listed under the pool in this output. If you see anything else then that would be why Houston isn’t associating the drive with the pool.

I got everything working i just deleted the pool i had and re created one and it works. I agree i have to go to command line a lot to figure out things and try to fix issues. I am going to play around with it a lot before i decide to put any data on it, have to make sure it is going to work without any issues.

Great to hear you got it working. I’m pretty sure I had this same problem at one point and it was that I imported or created a zpool using device names or uuids instead of the aliases.

In the event you end up starting over again on your HL15, you should be able to avoid the dalias program by backing up and restoring these files:

  • /etc/45drives/server_info/server_info.json
  • /etc/vdev_id.conf
  • /usr/lib/udev/rules.d/68-vdev.rules
  • /usr/lib/udev/vdev_id_45drives

Also, a big update for Houston is coming out soon. Might be worth your time to enable 45Drives testing repo to check that out while you’re playing around.

Thanks for all the information. I was thinking about installing proxmox on it, but maybe I will hold off until the update comes out and see how I like it.