January 25, 201214 yr Server shuts itself down randomly, ie crashes after just a few minutes. Previously ran well for about 3 months with no problems. Hardware list and syslog attached. Can't run parity check as server crashes during the process. Biostar TH67+ Intel I3-2100 4GB RAM Onboard ethernet and video Corsair AX750 PSU Update: tried remounting the RAM. No effect. Also, unRaid version 4.7 on a Sandisk Cruzer 4gb flashdrive. syslog-2012-01-26.txt syslog-2012-01-26_after_crash.txt
January 26, 201214 yr Author Another update: Tried swapping both sticks of RAM. Still no luck. Please provide suggestions.
January 27, 201214 yr Author Could not complete memtest. The server shuts down during testing. Therefore, I can't confirm that the memory is bad. Could bad RAM be the most likely culprit?
January 27, 201214 yr You more than likely have another problem. At this point you are going to have to eliminate one piece at a time and see if you can figure out what it might be. If you have another PSU you can at least try I would start there. Just connect it to the motherboard and not the Hard drives. Boot unRAID and run Memtest if possible.
January 31, 201214 yr Author Replaced with new RAM, ran memtest overnight (and then some) with zero errors. Proceeded to run parity check. Apparently the server crashed while I was at work because the server was OFF when I returned. I don't know if the parity check completed.
February 2, 201214 yr Author Update - System booted up and functioned property for about an hour of typical office use (opening files, saving documents, etc.). So, I decided to run parity check which was very very slow. After 30 minutes of running parity check, it was only about 1% complete. The server then abruptly shut down.
February 2, 201214 yr I would suspect a bad power supply. A parity check spins up all disks, which can cause a faulty power supply to fail and shut down. The slow parity check indicates that one or more hard drives may also be having issues. Posting a syslog and SMART report for each drive would be very helpful, but of course I know that can be difficult when your server is randomly shutting down.
February 2, 201214 yr Author Interesting... swapped out my Corsair AX750 with a new Seasonic x760. Proceeded to run parity check, which went for about 30 minutes (about 30% complete) at which time the server shut itself down. I'd call this a slow crash. lol Anyways, the syslog from right after the crash is attached. I've now definitely rules out the PSU, RAM. syslog-2012-02-02.txt
February 2, 201214 yr Author Ok maybe bad cables or a failing drive(s)? I think the server finally managed to complete a parity check. Didn't do anything, it just seemed to run parity overnight. The attached syslog shows major errors. Can anyone tell me what it means? syslog-2012-02-02_unknown.txt
February 2, 201214 yr 1. Run a smart test on ata3/SAMSUNG HD502IJ 2. Check cable connections. Replace or swap cables as part of the troubleshooting. http://lime-technology.com/wiki/index.php?title=The_Analysis_of_Drive_Issues Line 494: Feb 2 13:56:29 Tower kernel: ata3: SATA max UDMA/133 abar m2048@0xfe505000 port 0xfe505200 irq 31 Line 509: Feb 2 13:56:29 Tower kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Line 517: Feb 2 13:56:29 Tower kernel: ata3.00: ATA-7: SAMSUNG HD502IJ, 1AA01117, max UDMA7 Line 518: Feb 2 13:56:29 Tower kernel: ata3.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA Line 521: Feb 2 13:56:29 Tower kernel: ata3.00: configured for UDMA/133 Line 549: Feb 2 13:56:29 Tower kernel: ata3.00: exception Emask 0x50 SAct 0x1 SErr 0x280900 action 0x6 frozen Line 550: Feb 2 13:56:29 Tower kernel: ata3.00: irq_stat 0x08000000, interface fatal error Line 551: Feb 2 13:56:29 Tower kernel: ata3: SError: { UnrecovData HostInt 10B8B BadCRC } Line 552: Feb 2 13:56:29 Tower kernel: ata3.00: failed command: READ FPDMA QUEUED Line 553: Feb 2 13:56:29 Tower kernel: ata3.00: cmd 60/08:00:00:00:00/00:00:00:00:00/40 tag 0 ncq 4096 in Line 555: Feb 2 13:56:29 Tower kernel: ata3.00: status: { DRDY } Line 556: Feb 2 13:56:29 Tower kernel: ata3: hard resetting link
February 4, 201214 yr My similar issue was a cpu fan that was unlatched and partially dislodged from the cpu.
February 7, 201214 yr Author Thanks for the tip. Unfortunately, my CPU fan assembly is solid so I have no idea what to troubleshoot next. I doubt this is the culprit, but I ordered a Supermicro AOC-SASLP-MV8 in the hopes that the onboard SATA controller is buggy. Can anyone comment if the new controller card might speed up transfers some? I think writes were peaking out at ~12MB/s before all this insanity. Also read somewhere to try disconnecting all drives. Will try this to see how long the darn thing will stay on as I wait for the new controller card. Not sure what it will prove as there will be no system activity but I'll do it anyways.
February 10, 201214 yr Author WOW... i finally figured out why my server kept crashing. It was a faulty POWER button. The crashes were absolutely random reboots. That's why non of the efforts to isolate the CPU, PSU, RAM,HD's, etc. didn't work. Fortunately the Biostar TH67+ mobo has an onboard button for power on and restart. I disconnected the power on, restart, and LED wires from the mobo and have not experienced a random reboot since. Maybe this will help.
February 10, 201214 yr Glad to hear you solved it! I've definitely seen a few faulty power buttons before, they can be some of the most difficult hardware failures to identify. My favorite story was from the unRAID user who's server would power down randomly for no reason - until he figured out that his 2 year old daughter loved to press the shiny blue power button when he wasn't in the room!
Archived
This topic is now archived and is closed to further replies.