October 1, 20178 yr Community Expert Is your case setup to allow installation of a fan in the side of the case that you removed to take these pictures? If so, I would suggest installing one in that side. (Of course, it should be sucking air of of the case...) I hope you picked those fans as much for their CFM capacity (preferably against a 'head') as for their 'quietness'! Unfortunately, all of those 5-in-5.25 drive enclosure present notorious issues to get enough air flow through to keep the drives cool. You really have to think about cooling in every step of your component selection.
October 1, 20178 yr Author I did a fair amount of research in the past (2013). I never tried installing the side fan, but I did test parity check with the opening taped up or without taping, and taping it up improved cooling in general... I choose those fans as the best for cooling, with quietness in mind. The original norcos fans cooled the best, but boy they really the noise got under my skin. This is a good compromise, I only run parity check once in a while, and in that case I stick a fan in front and we have temperatures around 30C for all the disks.
October 1, 20178 yr Author If I built the server again, I would use these caddies http://www.icydock.com/goods.php?id=175 Large front fan generates better cooling, and less noise. You lose space for an additional hard disk but that is a small price to pay for better cooling. You can swivel the fan out of the way and slide the hard disks in and out, very slick compared to my original coolermaster stack cages, which had a fan at the front but you had to remove the plastic pins and unscrew the hard disk every time you wanted to replace one. Pain in the a$$ that was...
October 2, 20178 yr The question is now: Are the freezes and crashes gone now? BTW: Your signature still says "Celeron D"
October 2, 20178 yr Author Freezes and crashes still occurred, but since I installed a cheap spare network card, it happened much less often.
October 2, 20178 yr Author 3 hours ago, Zonediver said: The question is now: Are the freezes and crashes gone now? BTW: Your signature still says "Celeron D" Mmh, updated the signature but I can' actually see it in the posts...
October 2, 20178 yr Author 1 hour ago, Zonediver said: Try to install a Cache-Drive and test it again. I don't have a cache-drive, how would that be beneficial when I am trying to play files on one of the other drives?
October 4, 20178 yr Author Temperatures are max 36C after 9 hours parity calculation. London temperature is 9C minimum and 16 max today.
October 4, 20178 yr Author Previous parity check took place on Wed 16 Aug 2017 finding 0 errors.Duration: 20 hours, 47 minutes, 29 seconds. Average speed: 53.5 MB/s Yesterday's parity check finished and found 258 errors.Duration: 13 hours, 43 seconds. Average speed: 85.4 MB/s This is interesting. A faster CPU cut down parity calculation by 30% in time. I will look into the errors, and see if they are connected to the hardware changes.
October 5, 20178 yr Author I cannot see any mention of parity errors in the syslog or any errors showing for any of the disks in the UI. SO why is the email alert telling me that there were 258 errors? How can I investigate further?
October 5, 20178 yr Community Expert Was the parity check a correcting one? If so they should have been corrected. (If you found not errors in your SMART reports and nothing in the syslog, the errors probably are on the parity disk data-- not on the data disks. At least, that is what has usually been found to be the case in the past.)
October 5, 20178 yr Author Yes correct, no errors on the drives SMART reports. If i lost a drive, whilst I have errors on the parity drive, what would happen? Would I be able to rebuild the drive?
October 5, 20178 yr Community Expert 16 minutes ago, gnollo said: I cannot see any mention of parity errors in the syslog They have to be there if it's the syslog from the check.
October 5, 20178 yr Community Expert In my opinion, yes, you would be able to rebuilt the drive but it would have errors on it because parity did not agree with the data actually on ALL of the data disks. (Now if the parity data was actually correct that would mean that ONE of the data disks has errors on it. But which one? IF it was the failed one, then no foul. HOWEVER, if it was another disk, then there would be now two disks with errors...) That is why you should continue to run correcting parity checks until you get one with zero errors. It might be wise to post up the diagnostics file ('Tools' >>>> 'Diagnostics') and let the real experts have a look at it.
October 5, 20178 yr Author They have to be there if it's the syslog from the check.I opened the syslog and searched for parity, nothing found, will post the actual syslog. not long and date jumps from January to a few days ago.Sent from my Nexus 5 using Tapatalk
October 6, 20178 yr Community Expert Here are the sync errors, they look like genuine sync errors, any unclean shutdown since last check? Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067688 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067696 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067704 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067712 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067720 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067728 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067736 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067744 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067752 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067760 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067768 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067776 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067784 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067792 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067800 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067808 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067816 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067824 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067832 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067840 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067848 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067856 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067864 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067872 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067880 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067888 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067896 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067904 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067912 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067920 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067928 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067936 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067944 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067952 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067960 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067968 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067976 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067984 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067992 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068000 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068008 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068016 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068024 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068032 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068040 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068048 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068056 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068064 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068072 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068080 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068088 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068096 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068104 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068112 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068120 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068128 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068136 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068144 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068152 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068160 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068168 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068176 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068184 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068192 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068200 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068208 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068216 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068224 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068232 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068240 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068248 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068256 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068264 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068272 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068280 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068288 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068296 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068304 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068312 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068320 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068328 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068336 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068344 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068352 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068360 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068368 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068376 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068384 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068392 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068400 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068408 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068416 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068424 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068432 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068440 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068448 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068456 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068464 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068472 Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068480 Oct 4 06:15:34 Tower kernel: md: recovery thread: stopped logging
October 6, 20178 yr Author Here are the sync errors, they look like genuine sync errors, any unclean shutdown since last check? Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067688Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067696Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067704Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067712Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067720Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067728Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067736Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067744Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067752Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067760Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067768Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067776Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067784Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067792Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067800Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067808Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067816Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067824Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067832Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067840Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067848Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067856Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067864Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067872Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067880Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067888Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067896Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067904Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067912Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067920Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067928Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067936Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067944Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067952Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067960Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067968Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067976Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067984Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519067992Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068000Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068008Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068016Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068024Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068032Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068040Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068048Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068056Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068064Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068072Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068080Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068088Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068096Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068104Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068112Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068120Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068128Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068136Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068144Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068152Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068160Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068168Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068176Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068184Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068192Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068200Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068208Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068216Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068224Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068232Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068240Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068248Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068256Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068264Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068272Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068280Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068288Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068296Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068304Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068312Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068320Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068328Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068336Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068344Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068352Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068360Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068368Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068376Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068384Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068392Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068400Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068408Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068416Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068424Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068432Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068440Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068448Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068456Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068464Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068472Oct 4 06:15:34 Tower kernel: md: recovery thread: P corrected, sector=3519068480Oct 4 06:15:34 Tower kernel: md: recovery thread: stopped logging It's a possibility. I rebooted a few times when I was upgrading the CPU and I was trying to update the bios. I'll run another parity check next week, if it comes out clean then it must have been an unclean shutdown.Sent from my Nexus 5 using Tapatalk
October 12, 20178 yr Author Run another parity check, came back with zero errors, case close I think it must have been a dodgy shutdownSent from my Nexus 5 using Tapatalk
Archived
This topic is now archived and is closed to further replies.