I had used my Windows 11 install for general use as it is installed to a m.2 which also runs in Windows 11 vm install. I have come to use unraid, and I have noted that i get array starting stuck at the bottom of the screen. But i can access shares and Plex works. But then later on, the web ui stops working and plex stops working. I did find it strange that on boot, i had to bind the Windows 11 m.2 drive for it to be selectable in the Windows 11 vm. I have been able to get a diagnostics file.

Furthermore, I have NEVER had such an issue like this before. I have booted into windows natively without issue beforehand and then booted into unraid all without issue.

maincomputer-diagnostics-20250930-1219.zip

Edited September 30, 2025Sep 30 by Goldmaster

1 hour ago, Goldmaster said:

and I have noted that i get array starting stuck at the bottom of the screen.

Can you still access the GUI normally when this happens? Before it gets unresponsive.

6 minutes ago, JorgeB said:

Can you still access the GUI normally when this happens? Before it gets unresponsive.

yes i can. i can access the web ui. just to make its not me being inpatient, i have just left it running. It still says starting array even when the system has been on for 40 minutes. so there is something bugged out. when i look at the display text when unraid boots, the screen just hangs and does not show anything. but the main display is blank. When i try to shut down from the web ui it just hangs and does not shut down.

I am able to boot to safe mode and start the array in maintenance mode and then mount the drives. so it may be something to do with a plugin. but the whole system does seam very slow such as laoding the web ui and plex loading

Edited September 30, 2025Sep 30 by Goldmaster
can start in safe mode and mount drives

1 hour ago, Goldmaster said:

so it may be something to do with a plugin.

That's a strong possibility. Remove them all, then install them one by one and retest.

58 minutes ago, JorgeB said:

That's a strong possibility. Remove them all, then install them one by one and retest.

could i just move the plugins folder off the usb stick then start? Does not seam to matter what I do and there should be something in the log the WHY the system does not fully start, i frankly cannot believe that a system has been working fine could jsut stop like this. the usb and drives had been unplugged when i had used windows.

Ok, I have moved the plugin's folder off the usb and the system starts so I am looking in the right place. Just got to now work out WHICH plugin it is. unless something in the logs may be able to narrow it down?

Edited September 30, 2025Sep 30 by Goldmaster

28 minutes ago, Goldmaster said:

Just got to now work out WHICH plugin it is. unless something in the logs may be able to narrow it down?

You can post a syslog to see if there's something logged there, but it's probably easier to just reinstall them one by one, or a few at a time, and retest.

10 minutes ago, JorgeB said:

You can post a syslog to see if there's something logged there

Thank you. But the web ui still steams sto stop responding as i can get to the web ui. but if then click on say tools tab or such. Then the web ui just sits waiting to load for ages. So i close the tab. but if i go to web ui again. it just sits and sits and does not show any sign of wanting to load. The only way is to open an incognito window and then go from there. But even shutting is down is not possible, as clicking shut down brings up the stopping services and just sits and does not shut down. only way is to pull the plug.

I wonder if to try the usb or such in another system and see how it behaves there.

Edited September 30, 2025Sep 30 by Goldmaster
system not shutting down

44 minutes ago, Goldmaster said:

But the web ui still steams sto stop responding as i can get to the web ui.

You can enable the syslog server and post that.

On 9/30/2025 at 5:37 PM, JorgeB said:

You can enable the syslog server and post that.

Right, i think i have narrowed it right down to when trying to bind the Windows 11 m.2 to unraid. I never had such a problem as this. This is where somehow the issue of the system not mounting drives starts to happen. I have fortunately had a previous backup of the usb stick before upgrading from version 7 to the latest version. I frankly have zero clue how after all this time I seam to suddenly have issues with unraid and the passing though a m.2 drive with windows installed to unraid and causing this much trouble. But here is the syslog after i had bind the m.2 drive to then be able to pass though

syslog

Oct 2 13:02:29 MainComputer nginx: 2025/10/02 13:02:29 [emerg] 13875#13875: bind() to 127.0.0.1:80 failed (98: Address already in use)

Oct 2 13:02:29 MainComputer nginx: 2025/10/02 13:02:29 [emerg] 13875#13875: bind() to 192.168.1.3:80 failed (98: Address already in use)

Oct 2 13:02:29 MainComputer nginx: 2025/10/02 13:02:29 [emerg] 13875#13875: bind() to 100.74.35.109:80 failed (98: Address already in use)

Oct 2 13:02:29 MainComputer nginx: 2025/10/02 13:02:29 [emerg] 13875#13875: bind() to 127.0.0.1:443 failed (98: Address already in use)

Oct 2 13:02:29 MainComputer nginx: 2025/10/02 13:02:29 [emerg] 13875#13875: bind() to 192.168.1.3:443 failed (98: Address already in use)

Oct 2 13:02:29 MainComputer nginx: 2025/10/02 13:02:29 [emerg] 13875#13875: bind() to 100.74.35.109:443 failed (98: Address already in use)

Any idea what is trying to bind to port 98? Does it do it in safe mode?

2 hours ago, JorgeB said:

Any idea what is trying to bind to port 98? Does it do it in safe mode?

Well im not sure but the only thing it should be is the Samsung m.2 drive that has Windows 11 installed on. i have never had such an issue like this. i will have a look in safe mode once parity check is done

37 minutes ago, Goldmaster said:

Well im not sure but the only thing it should be is the Samsung m.2 drive that has Windows 11 installed on.

That should be completely unrelated, I suspect it's more like a plugin, like Tailscale, for example.

.

13 minutes ago, JorgeB said:

That should be completely unrelated, I suspect it's more like a plugin, like Tailscale, for example.

Right, but it does not explain how binding the m.2 drive can cause the array to get on array starting on the next boot. Or is it something to do with talescale or quite what that when binding the m.2 drive causes the array to get stuck on starting and cause instability.

And the problem never occurs without binding the m.2 device?

20 minutes ago, JorgeB said:

And the problem never occurs without binding the m.2 device?

That is correct, yes. The system runs fine. But as soon as I bind the m.2 drive in the vfio settings and then reboot, that's when the system gets stuck on array starting and becomes quite unstable, such as the web UI taking ages to load anything other than the main screen and does not shut down or restart cleanly. This then forces me to have to restore the previous usb stick backup using the unraid usb creator tool. I have never had such an issue like in all the time of running unraid. I currently have mirror syslog to usb and set the log not to rotate so I can see if there is anything that would point to the cause of the issue.

In that case please do this, with the device unbound, reboot the server, start the array and grab diags, then stop the array, bind the device, reboot, and post rne diags. Comparing both hopefully will help.

syslog before binding syslog-previous before binding syslog afterbinding syslog-previous after binding

Complete diagnostics would be better, but the syslog afterbindind shows the array started. Is it still working for now?

17 hours ago, JorgeB said:

but the syslog afterbindind shows the array started. Is it still working for now?

Well here is something strange and that is after binding the m.2 drive, the array decided to then work and start successfully. However, issues then seamed to start when I tried to tick to add the drive to the VM. but I did notice some additional devices ticked under other pci devices, such as something relating to Matisse and something to do with tpm2 security. So it may be that upon binding, those devices were getting bonded as well as the m.2 drive. It was only upon removing them. That the system decided to work. The only devices that should be showing up under other pci devices is the hard drive, disc drive and Bluetooth module.


So for anyone else with similar issues, ensure there are no other random devices to begin with in the other pci devices and remove them. Then try binding again. Not sure how this came to be, but hopefully a bug fix could be done to prevent such an issue like this.

Edited October 4, 2025Oct 4 by Goldmaster