GairyS

Thanks itimpi and JorgeB. Back up and running with no issues using the new config steps. Also no issues with the cache pool after the new config. And thank you JorgeB for letting me know about the firmware version and the steps you provided. It worked perfectly and I couldn't believe I bought those cards that long ago. After the firmware and bios were updated on the LSI card, I went ahead and rebooted and the drives came back still using the "short" format.

I've been running 6.9.2 since initial release on this same hardware, so no changes before upgrade today. I'm running on an HPE DL380Gen9 with current BIOS and SPP and all parity and data drives on my LSI HBA card (LSI SAS3008), while both cache SSDs are on the Smart Array P440ar running in HBA mode. All drives (Parity, data, and cache) after the update are now identified with the "short" names, whereas before the upgrade they were all using the "long" names. - v6.9.2 - Parity 1 - HGST_HUH721212AL_5PJ85ZNE_35000cca291dfe875 - 12.0 TB - v9.10.0 - Parity 1 - HGST_HUH721212AL600_5PJ85ZNE - 12.0 TB I had this happen before when I replaced my older PERC H310 card that was flashed, just the other way around. I know I'm going to have to run a "clean" config now, which will kick off a parity sync, but what happens with BTRFS since both SSDs are showing as wrong? Will unRAID right itself once the pool comes back online, or will I have to restore cache from a backup? Screenshot and diag file attached. tower20-diagnostics-20220520-1335.zip

Dockerman from unRAID is a great option for the users who need a "simple" solution and a GUI to accomplish "basic" docker tasks. I see a lot of people asking for a docker-compose GUI, and a few people mentioning docker-compose can be installed using nerd pack. The way I see it, after working in IT for over 15 years now, is there are a number of solutions available to resolve this. It really just boils down to comfort level. If you use an IDE like VSCodium, you can connect via SSH to run you commands and edit your docker-compose.yml file directly in the IDE. If you like git, you can integrate that into your IDE project. If you want to get "fancy", set up Code-Server in dockerman and set /mnt/user/appdata/docker-compose/ as a persistant volume, and edit your compose file directly in the web editor. A reasonable answer for a docker-compose GUI could also be to use dockerman to install Portainer, then use Portainer to deploy your stacks. Portainer stacks are compatible with docker-compose version 2. As of today, docker-compose in unRAID nerdpack is running version 1.23.2, build 1110ad01 and docker version 19.03.5, build 633a0ea838 on unRAID 6.8.0. So, if you need features from v2 you can use Portainer, but if you need v3 you will have to use another solution. Using version 2 will allow you to use extends, which will allow you to call several docker-compose files from another file, so you can make it function closely to Portainer stacks. But I think extends were dropped in v3, but there are other work arounds that can be used. Hope this helps a few people. https://docs.docker.com/compose/compose-file/compose-versioning/