danioj

If there is nothing in your nas log's, perhaps the cause of the restart is unrelated. hardware failure, heat tolerance levels exceeded etc ... I had a server I was running for ages start dying on me when I had recently installed something new and thought it was related. Turns out I had neglected cleaning the thing for so long it was dusty etc and by moving it to install something new I must have disturbed things and suddenly it started over heating ... Might be way off, but something to consider!

@ trurl - My understanding is that the parity is calculated initially "automatically" on a new install of blank drives (at least that is my experience here as I certainly didn't initiate it) I have no data on them anyway so is all good. When I format and create the FS I imagine it will be updated again. . @matguy & Joe L - I completely agree that the drive could have failed, but I am finding it hard to believe right now. Given the discovery of the drive is intermittent. I am at work now but will check the connections again when I get home and run another preclear on the drive in question. I havent migrated any data from my existing nas yet so all is good. Thank you all for your quick responses! I will post back when I have an update. Daniel

A bit of an update. Parity sync is still running and the errors, writes and reads on this disk are increasing: My syslog is showing masses of the following entries: Feb 6 05:48:38 nas kernel: handle_stripe read error: 16230248/2, count: 1 Feb 6 05:48:38 nas kernel: md: disk2 read error Weird thing, I tried to do: smartctl -a -d ata /dev/sdd OR smartctl -a -A /dev/sdd and get: Smartctl open device: /dev/sdd failed: No such device Very weird (to me anyway) given the web GUI is showing that the system recognizes it and also that preclear run on it. Hmm, cant be anything daft like a loose cable can it!?

Hello Limetech Community, I built my new server on Saturday. MBoard: Asus P8B75-M-LX CPU: Intel G550 Memory: G.Skill 1666 Ripjaws 4 GB Case & PSU: Antec P183 V3 & Antec Neo Eco 620 HDD: 5 x WD Red NAS drives 3TB (1 for parity, 1 for cache, 3 for storage) Unraid version: Pro Well, I started the simultaneous (different pty's) preclear process on my drives at 3pm on Saturday. It finished on Monday morning at 10am. All was ok before I had to go on overnight business. Everything passed, no errors all good. Came back last night, did some bios tweaks that I read about (e.g. enable AHCI, disable sound, serial, parallel ports etc) and then installed the Pro key. Added my devices into an array and the parity sync started. Now boom: Disk2 is showing: Reads: 4294967239 Writes: 17314587057 Errors: 11671800 I am confused because preclear gave the drives a workout and returned no issue, but Unraid now tells me there are problems. The parity sync is continuing as I type and the reads, writes and errors are increasing. The parity disk, cache disk and the two other disks in the array seem fine. I have attached a screenshot of my server MAIN window as of 2 mins before posting. Can I please ask for some support from this forum. Am I missing something, have I really got a dud disk here or have I done something wrong? Thank you in advance. Daniel [EDIT] Was a loose cable. Doh, *Slaps Forehead*