February 11, 201511 yr Hi I'm new to Unraid, this is my first NAS build i have ever made. I built it with parts from on old HTPC and and a newly bought PSU + 2x3TB HDD Red. NAS BUILD Mobo: Asus M2A-VM HDMI CPU: AMD Athlon X2 5600+ RAM: Kingston 2x2GB DDR2 800Mhz PSU: beQuiter 430 Watt Modular NIC: Intel PRO/1000 GT Desktop Adapter HDD1 (Pairity): 3TB WD Green HDD2 (Data): 3TB WD Red HDD3 (Data): 3TB WD Red So the issues here is that sometime my Unraid server suddenly "dies", what i mean by that is that i can't connect to it. WebGUI - No response Telnet - No response/Black Screen Monitor connected directly to NAS - Black Screen, monitor goes to sleep. Max time i reached is 6days of uptime but i mostly only makes 1day of uptime. This uptime is checked trough telnet by using uptime command. So when the server "dies" i need to hardreset myself holding the powerbutton down and the restart it. But the system seems running, all the fans and so on is spinning. How will i go about creating a syslog if i can't access it when it "dies"? I was planning to buy a Pro license for using a Cache drive but if i can't get it stable then it's no use. What i have done is trying to solve this is: Switching to a brand new Cat6 Ethernet Cable Switching the NIC to a Intel Pro 1000 GT Ran memtest86+ for 8hours Reset CMOS When the NAS is running, everything works flawlessly. Please help me fix this, when Unraid works it's perfect and it has all the functions i need.
February 12, 201511 yr Author So basically i followed this: "In cases where the system hangs, you can set up a system log monitoring telnet session by typing this command: tail -f /var/log/syslog Messages will get displayed in your telnet window as they are generated. If the system hangs, please select/copy/paste the contents of your telnet window, put into a txt file, and attach to your post." So i have to keep the telnet session active till when the system hangs, then the syslog from telnet will show what actually happened at the time of the crash?
February 12, 201511 yr So i have to keep the telnet session active till when the system hangs, then the syslog from telnet will show what actually happened at the time of the crash? Yes. If the computer running telnet goes to sleep, resets, or shuts off then the command terminates. Alternatively, you can also hook up a keyboard and monitor to the unRaid server, log in, and enter the following command: tail -f /var/log/syslog >/boot/syslogtail.txt This will accomplish the same thing, but continually save the file to your flashdrive.
February 12, 201511 yr Author I was just about to write that i found that command on another topic. I just used the command using a monitor and keyboard connected to my Unraid server. I checked the flashdrive via the WebGui and the syslogtail.txt is there and is writing everything that occurs. Right now the server has been up and running for over 24 hours. So now i have to basically wait for it to crash and post the syslogtail.txt here to get additional help?
February 12, 201511 yr Author So the Unraid server just crashed while i was wathcing a tv show, i checked the syslogtail.txt but there seems to be nothing wrong?? I will attach the syslogtail.txt here. syslogtail.txt
February 13, 201511 yr Author What i did today was: Reapplying thermal-paste on my CPU because the CPU is pretty old and has been running before in my HTPC for a few years. Switched Ram sticks to my Kingmax 2x1GB because the ones i used was bought from eBay and was a small form factor like this I have had trouble with these before when using them in my HTPC without Overvolting so i tought maybe that could be an issue. I think this is hardware related because Unraid crashes without any error in the syslog as you saw. I got on offer from a Swedish PC forum for these parts: AMD A10-5800K Asus F2A85-M LE HyperX 2133mhz 2x4gb Cooler Master EVO 212 All this for 1500 SEK which is like 180 USD. I'm thinking of buying these parts but do you guys think i'm suffering from HW issues or is it SW issues with Unraid itself?
February 16, 201511 yr Author I think the small form factor RAM sticks was the culprit in my sever repeatedly crashing. I have now 3 days of uptime since switching back to regular sized ram sticks. As my record was 6 days of uptime (which only happened once, otherwise it would crash after 1 day of uptime),i will have to wait before i can mark this case solved.
February 20, 201511 yr Author I think i can conclude this case solved. Over 7 days of uptime. I think that weird small factor ram got to hot and failed. I'm very happy now that my server is now stable.
Archived
This topic is now archived and is closed to further replies.