Arakus

Still no luck, but I did have a new development. When I turn off the SATA controller on the board I'm not getting any crashes with spin down, however, now I'm down 6 sata ports to use and i'm dependent on my M.2 - SATA adapters. Is this likely a hardware issue then? or is there a known issue related to this?

Yes, I can recreate a crash each time by just starting the array and then stopping it, which triggers the spin down. Otherwise it's about 15 minutes of being idle for the spin down. That's also why I guess the system is stable while a parity check is occuring. Yes, I ran a memtest this morning and got a pass. Should I be running it longer than 1 pass?

Well, still having an issue but here's the updates This processor is an Intel Celeron N100 and the bios does not have anything specific to c6 states. However I've disabled and enabled multiple options related to power conservation and still the issue persists. I can pinpoint the crash to when the disks spin down, it's immediately after that. I logged the syslog to my thumb drive and attached to this thread, as you can see it stops with no further logging as soon as the spin down completes. Is it somehow related to the nginx errors that I see in the logs? Thanks for any further help and suggestions. syslog

Thanks for any help in advance, I have an issue where unraid crashes and becomes unresponsive/freezes after some time when a parity check is complete, or it is paused or cancelled. Within about 15 minutes of a parity check not being performed it will freeze up requiring a hard reboot. I have done the following: Started in safe mode with no plugins Replaced my USB thumb drive Updated all dockers Still the same issue. Note that I did recently upgrade my hardware around the same time this all started. I upgraded to an N100 CPU with new motherboard. My father recently did the exact same upgrade but has had no issues. Would really appreciate some insight on what's causing this so I don't have to keep re-running 48 hours with of parity checking just to have a functional system. Thanks! tower-diagnostics-20250318-1913.zip

Thanks for the suggestion @JorgeB. I troubleshooted the issue and began removing config files to see what was causing it and eventually narrowed it down to the ident.cfg, machine-id & network.cfg file, plus I removed the pools folder. Deleting all those allowed for the startup of UNRAID and nothing seems to be affected from my previous config. Still not sure what happened during the upgrade to 7.0 that would have caused this issue though, it's pretty concerning.

Hi, I recently updated from 6.12 to 7.0 and I have since been unable to connect to Unraid. When booting up I can access the Unraid GUI option but it just appears to be linux. When trying to access unraid itself at localhost from this GUI I get 'unable to connect' on the firefox browser. I have tried 3 things: 1. Manually added the bz* files and changes file from the 7.0 zip file. 2. Downgraded manually by following step 1 but with the 6.12 files. 3. Deleted network.cfg file. Neither has worked and leads to the same issue. Help with this would be greatly appreciated! The attached diagnostics file was taken after installing and booting up into the 7.0 version. tower-diagnostics-20250216-2120.zip