teitur

When my Unraid server boots back up after unscheduled power off the eth0 interface is missing. Any ideas what can cause this? It fixes itself by gracefully powering down the server and turning it back on again. tower-diagnostics-20240228-1419.zip

How do I troubleshoot that? Please tell me there is some app or some way to stress the system from within Unraid so I don't have to install and do this in Windows? Im very familiar with Windows, but not at all with Linux.

I powered off again. there seems to be nothing logged by syslog before poweron that surprises me somewhat. syslog.txt tower-diagnostics-20240224-1809.zip.crdownload

It very simply seems to power off. its rock solid stable running 2 VMs all of the time and 3 VMs some of the time, 1 of them in a work environment used for 6 hours a day. And I used the computer for about a week on windows 11 before committing it to Unraid. No issues. Even used it for games. How does Unraid behave when BSOD happens? And if it powers off, would it log that?

Im using an old Nvidia 970. it performed just fine in a Windows machine. But might Unraid have problems with it and how do I go about testing for that? However im not doing anything GPU intensive at all.

Ran this for over 30 minutes. Its not overheating CPU. If its a memory issue then the server should simply crash/reboot/flaky, right? Used something called CoreFreq for the CPU stress test.

its on a UPS with another computer that was fine. Must be hardware. is there a stress test that you can recommend for Unraid?

I got the brilliant idea of looking at the windows client log file. The time I estimated seems to be correct. (That windows error is repetitive, not related to the problem in Unraid).

Did I not remove anything. I could only find those two files. are there any others in another location? The time is based on when the woman working on the server messaged me and let me know it went offline. She told me it just happened.

And diagnostics log again if there is anything there. tower-diagnostics-20240222-1408.zip

This is the power on syslog

This seems to be it. its a syslog from flash. it powered off sometime this morning 22.02.2024 between 9-10. I think its between 9:50-9:57. syslog

Im having problems when I convert to the QCOW2 format. The disk is reporting the wrong size and unallocated 142.58GB that should be 250gb. And does not boot. it works fine with KVM on Debian. Is there a problem for the Unraid KVM using QCOW2 converted with qemu-img.

My Unraid server has turned off about 3 times now, it might be a controlled shutdown but I don't know what log to read to see if it was or not. it seems to be completely random and I cannot see any reason for it. I have not been able to get a temperature APP working to monitor CPU and other heat readings, so I guess it might be that. But Windows had no problems when running on the computer. Can anyone please tell me what log to read and perhaps see if there is any reason for the shutdown or power off. tower-diagnostics-20240221-1045.zip

Thank you for your help. I unplugged the unraid USB. that's why it had those errors I guess. The case fans are to loud, cannot hear the disks. I installed windows and the disks did not show up there either. So it seems the solution was that have to have a SATA cable plugged into both SATA ports at the back of the adapter for the drive bay to work. I'm currently looking for another adapter that only needs one sata for two drives...

I bought a U4 case from Inter-Tech, the 4U 4410. But unraid does not seem to pick up the drive bays. At least the disks are not appearing in unraid. Is there a special way to initialize the drives in the bays? Nvme disks are showing up just fine and I can use them in an array, but not in a pool without a array disk for some reason I don't understand. unraid-diagnostics-20240208-1048.zip