Veah

Are you using the assigned port in the address? 192.168.1.155:#### That can be found in docker setting. Also if you open it from within unraid using WebUI, that should get you there. Also be sure the containers are running.

On the regular PC, try using a different browser to access the webgui. Browser can cause trouble occasionally. If that works then you should be able to get a log posted for the pros to gloss over.

It's really sus that multiple young drives would fail so soon... Hard for me to accept that. Let's see, you eliminated SAS controller, you spared off both data and power cables. There's only one long shot I can think of with HW and that would be the PSU actual. Any chance you have an old one laying around? If not that, maybe Jorge (or another pro) can see something in the logs. I'm pretty bad at reading through those unfortunately.

Is it possible to get all the hdd on mb sata to test it? Eliminate the LSI card sort of thing.

Check Settings > Notification Settings > Unraid OS update notification: _____

Since this all started after renaming shares, I think you should be able to verify all your paths in VMs to correct. Changing from upper case to lower case letters would be the same as moving your data to a different location so your vms just got lost.

I wonder if your address got reassigned to a different nic. Try connecting different ports to your switch and look for (ping) that .10 IP.

I assign those containers their own IP and use router to send the data to whichever VPN path.

I have had symptoms 1, 2, 5 and 7 while flash drive was failing.

Does the problem continue if you put back the old GPU?

If it's happening at the same time daily, that makes me think some sort of scheduled event. If not scheduler, perhaps a script, or something within a docker container or a vm. The big brains may stop and have a look if you get diagnostics attached. They are real good at ciphering all that data quickly.

In hindsight, I should have mentioned I am running an HA Core VM vice Unraid container. Sounds like you got it nailed down so that's cool.

Something in the scheduler?

My solution was to setup a virtual eth port within HA. I set one port to be accessible in the iot subnet, and the other to my main subnet.

https://m.youtube.com/c/SpaceinvaderOne ^^ This guy

Many issues like this turn out to be power delivery. Bad power connection or too many splits of a cable. Did you check those?

Have you checked for updated firmware? It would be manufacturer specific so caution advised.

This IS your path forward. Get yourself the largest drive you intend to use as you upgrade the individual drives. The physical size (2.5" or 3.5") is only limited by your case. Take a picture of your disk info under Main for reference. Shut down array. Use that large drive to replace the parity drive. Boot system up. Go into Tools > New Config. Check Preserve Pool slots and Uncheck Preserve Array slots. Now assign all the disks in the previous spots according to the pic you tooke except parity. Assign the new large drive in the parity spot instead of the original. This should leave you with big parity drive + 4 original 1TB data drives. Finish array creation and it will initiate a parity check. Your data will be preserved. Later on... Swapping out data drives will require some data shuffling. My suggestion would be to add a new large drive, migrate all your data to that new drive, then use New Config to remove all the old empty drives by simply not assigning them during the process above. That will leave you with 1 parity and 1 data drive. You can if course expand that at your convenience. Good luck.

I do not see anything in documentation about ASM1166 airflow requirements, I am guessing it will be ok in any reasonably vented case. The one I mentioned is intended to be used in a proper server chassis with front to rear airflow of the loud persuasion. Since I am in a Fractal (normal tower style) case, I needed to supplement the airflow by mounting a fan on it.

I use an Adaptec ASR 71605 and it's great. But used on eHay or whatever it's called. If you go that route, you NEED to be sure it's cool. A 40mm fan screwed to the heatsink plugged into mb header is how I do it. If it gets hot, it lets you know. https://www.ebay.com/itm/225006187962?mkcid=16&mkevt=1&mkrid=711-127632-2357-0&ssspo=mkjc0LRXS1S&sssrc=4429486&ssuid=KFg1X26QQay&var=&widget_ver=artemis&media=SMS

Data will stay there on disks 1-4. Disk 5 is is just being removed so that unraid is not looking for it anymore.

Check Preserve Pool Slots. The array slots you need to assign manually (don't check) Basically use your image and assign all but disk 5 so it is left unassigned.

I do not recall the options exactly, but be sure to read the checkbox choices. You want to keep all your array and cache drive data intact.

I think you meant to make new without the missing drive. You can add it later on when you have the part you mentioned waiting for. The idea is to put you back where you started before adding that last drive.

Oh. I assumed you had a generic build that uses 1 or 2 drives for parity. If you don't use it, then it would not apply. BTW, if any of the big brains pass through, they will likely ask you to post diagnostics. They are able to clean a ton from that.