Hi there

 

I'm having a persistent issue with my server becoming completely unresponsive. I've lost track of how many unclean shutdowns this has caused and the last one required a rebuild which itself was interrupted - so I'm hoping someone can help point me in the right direction.

 

At first I thought it was a bug with my NIC, but it appears as though the server enters a sleep mode and becomes unresponsive. I think it happens once the server is idle  - it usually happens within 24 hrs from when the server is booted. The lights are on, but I can't get it to wake and become responsive. I'm not sure what might be causing it to go into a sleep mode - or if this is a misdiagnosis and the issue is something else entirely.

 

I'm guessing it's a hardware issue - but I'm pretty new to all of this and I haven't been able to get to the bottom of it.

 

I've installed the Realtek driver.

I've set WOL in BIOS and through ethtool and added to the go file.

I've also gone down a few rabbit holes with forum and reddit posts to no avail.

 

Would appreciate any help before I ditch the hardware and start from scratch 🙏

 

Thank you!

tower-diagnostics-20240221-2150.zip

Check filesystem on disk1, also one of the cache devices dropped offline in the past, see here for more info.

 

For the crashing, make sure you run memtest, and one other thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one. 

Thanks for the reply Jorge

 

I'm waiting for the rebuild to finish and will recheck - but I checked and fixed the filesystem on the previous rebuild. Cache check is showing errors.

 

Will run memtest. I don't think it's dockers/VMs, as they all disappeared on the previous rebuild and the issue still happened. I'll try in safe mode to be sure.

 

Do the logs indicate a crash? I couldn't tell if it was crashing or more of a network card issue. 

Oof, so the rebuild completed. Everything looked like it worked, but I seem to have lost most of the files on the drives. Shortly after the rebuild, it appeared to be successful, but after looking around the drives, most of the contents is missing.

 

Now the array has been stopped (not by me), and disk 1 is showing as disabled. It says if I start the array, all existing data will be overwritten. 

 

I thought the rebuild would have been successful as it was from the parity drive?

 

I've attached the latest diagnostics - do you have any ideas for next steps? Would really like to recover the data that has gone missing.

tower-diagnostics-20240222-1433.zip

Disk1 is showing as wrong because the ID changed, this happened because it's using USB, we really don't recommend using USB for array or pool devices, but doing a new config and trusting parity should fix it for now

Thanks so much Jorge - appreciate your help. I will give that a go. 

 

One last question if its ok:

The hardware is getting an upgrade, and the HDDs will be on SATA so hopefully the issues go away. Its essentially a brand new system, but using the same Unraid usb.

 

Would you recommend that I try and restore using my current system via USB connected drives before swapping them in the new system, or is it ok to just install the drives on the new hardware and try doing it there?

If you can wait until the new hardware that would be preferable, but note that some USB bridges are not transparent, i.e., disks may not mount using SATA, but the majority don't have that problem.

I'll do that - thanks very much for your help!