Questions that googling/scanning the forums aren't helping.

[kdcampo]

So, I have a few questions. 

1. My server, an old 170z system  32 gig ram 1070 gpu, likes to randomly "freeze". It wont show up on the network, I cant ssh into it, and, as far as i can tell, the keyboard becomes unresponsive. The only thing i can do is a hard shutdown, which i do not like doing because its running off 4 nas HDD's and I know a hard shut down is not a fun thing for them. I'm sure its a hardware issue since my mobo is an old msi gaming z, that has the problem that it will thermal throttle the cpu even if its below 70C. I had to disable the temp monitoring in bios and it works good as "new". I'm wondering if this is an issue that is common or just something my system is doing. 

2. Is there a way to get the system to show a display after the monitor turns off. My system shows a display when it first turns on, but as soon as i shut off the monitor and turn it back on; it will not display a picture until it is rebooted. I did a test today and shut off the monitor and turned it right back on and no signal. 

3. If i buy a remote management pcie card can i hook it up to a laptop to monitor the system instead of having to ssh into it using command line? In tech youtuber videos they just walk up to their rack, open a laptop, and off they go doing stuff in their server. I only ask because of issue #1. with the system in headless mode; I cannot see what it is trying to do when it "freezes". I would like a way to be able to give it a command to restart. 

[PsychoWards]

Hey, 

Not sure if your 170Z is a typo and should be an AMD 1700 CPU.

If it is, there is a bug concerning AMD Ryzen 1000-3000 CPUs which is causing exactly those random freezes. You have to disable all the C-states in the BIOS to stop this from happening.

 

You could use something like uptime kuma to easily see if the server is still running or not, but you would need to install it on another server/pc and have it running there to get proper tracking. 

[Azureblood2]

Honestly, if there are known hardware issues you should probably be looking for another machine to host your NAS

[kdcampo]

18 hours ago, PsychoWards said:

Hey, 

Not sure if your 170Z is a typo and should be an AMD 1700 CPU.

If it is, there is a bug concerning AMD Ryzen 1000-3000 CPUs which is causing exactly those random freezes. You have to disable all the C-states in the BIOS to stop this from happening.

 

You could use something like uptime kuma to easily see if the server is still running or not, but you would need to install it on another server/pc and have it running there to get proper tracking. 

Sorry ment z170. Old intel i5 6600. And I'll look into that and see what goes into it

[kdcampo]

10 hours ago, Azureblood2 said:

Honestly, if there are known hardware issues you should probably be looking for another machine to host your NAS

Yes, I need to find something else to host it on, just don't have the funds right now. Trying to find some server grade mobo for my 6600 i5 to try to save some money. But might just have to go with a xeon something to have less of a head ache when I get the proper funds. 

 

This is mainly to get my feet wet and learn truenas and self hosting. 

[Mobius]

yeah it might be time for new hardware.

I would also suggest not keeping your only copy of important data on this machine if you intend to keep using it as is.

xeons are excessive if the only reason you are picking them is for less of a headache.
for most users a used cpu and mobo is good enough. heck in your case i might even look for a replacement motherboard on the cheap.