DavidIrwin Posted February 5, 2017 Share Posted February 5, 2017 Hi, Not sure if my server has an issue or not, and I am not sufficiently skilled in reading the log files to work it out. I have the FCP plugin running, and when I logged in this morning it warned me: Your server has issued one or more call traces. This could be caused by a Kernel Issue, Bad Memory, etc. You should post your diagnostics and ask for assistance on the unRaid forums As a result this is my post, and here are the diagnostics. I have not suffered any problems with the server, noticed any dockers crashing or anything like that. Thank you in advance davidserver-diagnostics-20170205-0838.zip Link to comment
allanp81 Posted February 5, 2017 Share Posted February 5, 2017 I was getting similar and I did a xfs_repair on all disks in maintenance mode and it seemed to help but ultimately it was faulty memory that was causing this. I wasn't getting any errors as such but I was getting intermittent crc fails when copying to my unraid box from other sources. Link to comment
John_M Posted February 22, 2017 Share Posted February 22, 2017 In response to the OP, your server has several problems. I see segfaults reported, Quote Dec 24 12:47:30 DavidServer kernel: python[7241]: segfault at 2b91ad147ff8 ip 00002b91a519bd9b sp 00002b91ad148000 error 6 in libpython2.7.so.1.0[2b91a512c000+341000] several call traces, and your parity disk is disabled Quote Jan 15 16:25:40 DavidServer kernel: md: disk0 write error, sector=6445719760 ... Jan 20 23:02:33 DavidServer root: Fix Common Problems: Error: parity (ST8000AS0002-1NA17Z_Z840BRKX) is disabled Segfaults could mean memory problems so I recommend rebooting your server and selecting MemTest from the boot menu and letting it run for 48 hours. Your parity disk's SMART report looks good so you can re-introduce it to the array. I recommend you turn on Notifications so problems don't go unnoticed in future. Link to comment
DavidIrwin Posted February 22, 2017 Author Share Posted February 22, 2017 Thank you for the advice. I reintroduced the parity drive with no problems (SMART was all clean) and will run the memtest as soon as I can shut the server down for a few days. My Plex users are not going to be happy about that! Link to comment
John_M Posted February 22, 2017 Share Posted February 22, 2017 You've got a lot of memory related issues in your syslog. Your should reboot at the very least. You might want to consider updating to unRAID 6.3.2 as it has newer kernel and libraries and includes security fixes. Link to comment
marcoNLD Posted February 22, 2017 Share Posted February 22, 2017 sorry confusing treat my bad Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.