grslc

Could you clarify this a bit? I ran through a new config with preserve pool and array slots selected, and preserved parity, thinking maybe that would flush some sort of bad config setting, but no dice. Are you saying I should rebuild parity?

I recently migrated my drives and Mobo into a Supermicro 4U case with BPN-SAS2-846EL2 backplane. 8 Disks were previously connected through HBA and breakout cables, with the remaining 3 on SATA. On initial startup, the array hung when started. Server was showing the 'array is starting' notification, docker and VMs hang, nothing happened when I clicked 'stop array.' Booted server in safe mode, traced it to Unassigned Devices, and uninstalled, server functions normally. I tried deleting the plugin folders from the config folder and reinstalling, reissuing UUID, and probably a couple of other things mentioned in threads and help. After reinstalling plugin, the array mounts normally, but all array disks show up in UD, with greyed out Array bar, as well in the Array Devices list. The array is functional, and docker and VM's load, but won't spin down with UD installed, and the log stops if I issue the stop array command. The issue seems to be that the sdx drive assignments are in disagreement between Unraid and UD. I see reference to this in the instructions, but can't find any instruction on how to fix it. I'm getting the same device id error on all of the backplane disks. device /dev/sdo problem getting id Nov 10 23:53:23 emhttpd: error: hotplug_devices, 1710: No such file or directory (2): tagged device HUH72808CLAR8000_VKGU950X_35000cca2542dfeac was (sdu) is now (sdl) kernel: emhttpd[4685]: segfault at 67c ip 000000000041816d sp 00007ffefb3a4d10 error 4 in emhttpd[404000+1a4000] likely on CPU 9 (core 3, socket 0) Any advice is appreciated. diagnostics-20241111-1505.zip

I had the same problem, and solved it the same way. However, I noticed My Home Assistant VM and one of my docker containers were no longer available from WebUI after making the change. I figured the update must have caused a port conflict somewhere, but haven't been able to figure it out. Possibly Healthcheck? Rolled back to my previous version of Gluetun, and logs show that it is healthy now, but I still can't access the docker containers I had routed through...