DeanJanscak

I am able to start up the array in safe mode with no apparent problems. Does that point to it maybe being a plugin that has caused the issue? I have attached last night's diagnostic. tower-diagnostics-20231010-2153.zip

I have this same issue starting yesterday. The GUI became inaccessible as soon as I started the array after a reboot. All my dockers started up and were accessible, SSH and MC were usable. I have connected with Unraid Connect, and get "request to http://127.0.0.1/graphql failed, reason: connect ECONNREFUSED 127.0.0.1:80" under Storage, Docker Apps, and Vitual Machines. I haven't tried safe mode yet. I will post diagnostics later if I can. Any other help or suggestions would be appreciated.

I'm pretty sure all I have are Western Digital... All the drives in the array, and the two devices I tested with are definitely all WD, and the one other naked drive I have around is also WD. Just really old. I'll see if I can dig up something different just to test with, and come back.

Hi Guys, I seem to be having a similar problem to Peter. I have a generic ASMedia card ASM1061, and cannot seem to get it running in my server. Whenever I have a drive connected I get a kernel panic during the boot into UNRAID. BIOS shows the drive connected, and I have taken it out of the boot order. System boots into UNRAID perfectly fine when there is no drive connected, but thats just defeating the purpose. I have tried two different drives, kernel panic seems to occur at the same time with each. If anyone has suggestions for fixes troubleshooting I would be grateful. Thanks.