F3nris

I have had this issue for awhile now and it recently ended up ophraning all of my docker images (Not the cause, just attributing it to what happened). When I either attempt to update 1 or all docker images, or plug-ins, even unraid itself. I often run into the pop-up window stalling on me. It will stop providing updates and I never know if it completed or not. I just wait and wait. Eventually, I will check whatever it is in a different tab to see if the docker is running or whatever the install was for. However, I would like to know if I can fix this very annoying issue with the window. Anyone have any idea's? Added an example screenshot of a plug-in I was installing. It never reached "done" in the window after 30+ minutes.

Over the years, I've had 3 different USB drives fail. I had them plugged into the back of the server and I think the heat just killed them over time. My current one has been in for over a year plugged into the front with fresh air and I have had no issues. I would second the advice above and maybe think about getting a new drive since they are so cheap.

Not much to go on with the screen shots. NIC's going into promiscuous is normal behavior with docker/vms. Do you have any dockers running, scripts, VM's or machines that are connected to your shares? Maybe get a diagnostics log uploaded?

I ran across this looking for something else, but out of curiosity, did you find the problem? It would appear the memory modules you are using (BL8G32C16U4B.M8FE) are not qualified on the MB. edit: Also, you are running a release candidate. I would suggest staying on stable versions.

I just ran across this guide when I was looking into the possibility of doing this as well. I have not tried it. https://www.rootisgod.com/2020/ESXi-On-Unraid/

Just FYI for anyone getting this error: 16:48:32:ERROR:WU01:FS01:Failed to start core: OpenCL device matching slot 1 not found, make sure the OpenCL driver is installed or try setting 'opencl-index' manually Had this problem for a week now. Somehow I was missing "--runtime=nvidia" after it had been working for several weeks before. /shrug.

Good points. Right now the usb has been in the back of the case at the IO. Considering your points, maybe I will get a usb IO cable for the mobo and mount it inside the case for airflow to help the longevity.

Possibly, this is the second time its happened to me when doing an upgrade. I have been using 32gb sandisk ultra fit's to allow for lots of space in the hope this would reduce the overall wear to it. Maybe move to 64gb? The last time this happened was over a year ago. The drive was not being seen by any of the partition tools I quickly tried last night. It did not have any warnings before the upgrade. Maybe if I get bored over the weekend I will pull out a linux laptop with some forensic tools to see if I can pull some info from it. However, being so cheap, not really worth the effort. On a side note... Since I encrypted all of my disks, recovering the config was a bit more cumbersome this time around. I had a backup.... in a encrypted share.... Wouldn’t have been so bad if I had a recent screen cap of the drive assignments. The two parity drives will be finished rebuilding in little over an hour from now. I think I might add a old drive to mirror the flash backup to in the future.

Upgrade bricked my USB key. Went from 6.7.2 > 6.8.2. I am unable to read the key on a PC or MAC....