zoggy

joe, did the syslog confg file get updated with 1.6?

yay 1.6 -- http://lime-technology.com/forum/index.php?topic=27051.0

looks much nicer. fyi, you should remove the 'body' css in those .cgi since it will mess up the unmenu up top...

All the other "disk" related informational messages are in 'teal', and lime-tech lines in 'green', so I added your match for the error handler, but in teal. (hope you'll understand why I changed the color) I've incorporated your other css upgrades to the .cgi "shell" scripts. I'll be uploading them to the google.code site once I merge in some very interesting .css changes from mvdzwaan. Thanks so much for helping improve unMENU. It was designed to be easily modified and is remarkably impressive for an "awk" script pretending to be a web-server. no worries. glad to help in anyway i can. I forgot to mention that on the .cgi network one I changed the refresh from 1sec to 2sec and forgot to change it back. i tried upgrading a few packages with newer versions but kept running into issues... i cant seem to figure out why upgrading to newer gcc versions result in it just not working.. and then trying to add g++ seems like other dependencies are needed but i cant track it down.. will dig around some more tonight but so far i've not had much luck.

since this is a one liner, I'll just post the update here rather than the whole file. in syslog_match.conf find the line: match_case||"HPA detected: current [0-9]*168,"||black and add this right afterwards: match_case||"dev error handler"||green I was scared seeing that popping up all the time as a new user.. but after researching I found that its just wrongly being assumed it's an error because of the 'error' pattern and figure this would save some others some anxiety when digging through the logs with unmenu.

same css applied to the disk perf page this time, image and file (cgi->txt) attached. 15-unmenu-disk_perf.txt

@Joe , I looked into customizing the bwm-ng page.. sadly they do not produce valid html (they don't close their TR tags, they dont use TH for headers.. etc) which ends up making it hard to apply some CSS styles to improve the look easily. Noticed that also it currently does not support network bonded devices as well as the code is from 2007! So prob no chance of this really being worked on anymore. but I did what I could using some css3 selectors.. attached a screen shot of what it looks like and the udpated file (note due to forum security I had to rename the extension from cgi to txt) 15-unmenu-network_perf.txt

fyi looks like the Nexus Prominent 9 is out of stock everywhere..

alright, pre-cleared the WD 2tb drive that has been the problem.. ================================================================== 1.13 = unRAID server Pre-Clear disk /dev/sdg = cycle 1 of 1, partition start on sector 64 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 35C, Elapsed Time: 29:32:24 ========================================================================1.13 == WDC WD20EARS-00S8B1 WD-WCAVY4386698 == Disk /dev/sdg has been successfully precleared == with a starting sector of 64 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdg /tmp/smart_finish_sdg ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 117 120 0 ok 35 No SMART attributes are FAILING_NOW 1 sector was pending re-allocation before the start of the preclear. 1 sector was pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, a change of -1 in the number of sectors pending re-allocation. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. now i guess i'll put it back in the array then check parity to see if it messes it up again. Parity check completed.. no problems. Running another non-correcting check just to be safe. Alright, another parity check.. no problems. so looks like i *should* be good now. so long story short.. replace the cable if you have doubts!

It is apparently downloading to /.cpan/..... Do you have enough memory? for that is an in RAM file-system. If filled, you would find all kinds of things having problems. I installed the "perl" package here a few minutes ago, and I had no issues at all. It does download a lot of files under /root/.cpan (over 25 Meg ) and over 35 Meg under /usr/lib/perl5 Joe L. This has only happened twice, so far.. most startups it d/ls just fine and moves along to the next package. I have 4gb of ram.. syslog shows: Apr 9 23:41:02 husky kernel: 3706MB HIGHMEM available. (System) Apr 9 23:41:02 husky kernel: 891MB LOWMEM available. (System) To me it's like when you go to download from a file and the server for whatever reason just stops sending.. but the app is just keeps looping waiting for the next piece of data and never times out even though its been 0 bytes xfer after <insert whatever timespan>. digging into wget manual http://unixhelp.ed.ac.uk/CGI/man-cgi?wget I see the default timeout is 15mins with 20 retries.. "The only timeout enabled by default is a 900-second (15 mins!) read timeout. Setting a timeout to 0 disables it altogether." "The default is to retry 20 times, with the exception of errors like "connection refused" or "not found" (404), which not retried.". So with that said.. 15mins x 20 times would end up being a really long time waiting for a package part to install during unmenu startup. So maybe change some of the default settings like (-T 45 -t 5) so we retry 5 times with 45 sec timeouts... Like I said before, this package normally installs.. just randomly twice (prob out of 40 restarts) it's "hung".. I'm sure it would have worked after 15mins on the next retry attempt if I was more patient. So the timeout just seems a bit too high for me as I was trying to test something / watching it startup. Maybe make it a configurable option for those that want to change it?

just started up my unraid box.. it went through the installing process for all the packages like normal.. it hung on the PERL one again.. so it's just sitting there incrementing the download part.. the last few lines of the screen show: --2013-04-09 23:20:16-- http://www.cpan.org/modules/02packages.details.txt.gz Resolving www.cpan.org (www.cpan.org)... 199.15.176.140, 207.171.7.177, 2a01:608:2:4:2, ... Connecting to www.cpan.org (www.cpan.org)|199.15.176.140|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 1407546 (1.3M) [application/x-gzip] Saving to: '/.cpan/sources/modules/02packages.details.txt.tmp1877' 26% [=======> ] 371,213 --.-K/s eta 10m 17s just checked back in on the screen.. still 26% and eta is 34m 49s. so yeah its stuck no key combination will exit out of it. I can however remote into the box via ssh / access the webui and started unmenu. went to package manager and told it not to reinstall perl on startup.. since this seems to always be the problem package for me.

okay, shutdown array and replaced the SAS breakout cable from the 1st AOC-SAS2LP-MV8 card (2nd port) with a brand new one. So this will hopefully prove out if the cable was the issue. Already at 4% on pre-clear step 1 (which is 2% further than last run before it started to go crazy). update: alright this drive pre-cleared without any problems on this port with new cable. ================================================================== 1.13 = unRAID server Pre-Clear disk /dev/sdg = cycle 1 of 1, partition start on sector 63 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 32C, Elapsed Time: 3:50:05 ========================================================================1.13 == WDC WD1600JS-55MHB1 WD-WCANM8565748 == Disk /dev/sdg has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdg /tmp/smart_finish_sdg ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Seek_Error_Rate = 100 200 51 ok 0 Airflow_Temperature_Cel = 69 72 45 In_the_past 31 Temperature_Celsius = 115 119 0 ok 32 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. so now i guess i'll try putting the old disk back in and pre-clear it again.

Joe, is there an unmenu irc channel? Wanted to talk to you/people about some things about it. For right now I'll just toss some stuff up here, but don't want to clutter this thread if there is a better spot for it. On the package manage page: Segment visually the 4.x and 5.x stuff.. add last updated, show if it requires d/ling things from the internet (which could result in delayed/hung startup of unraid if something goes wrong -- i've had it happen with the PERL package) The visual changes also could be further expanded with the ability to allow packages to be disabled (beta/bad) or hidden (for example cxxlibs-6.0.9-i486.tgz library accidentally left out of unRAID 4.4-beta2 through 4.5beta5 shows up.. not really needed for most?) on the pkgmgr page. Allow packages to be installed dependent of their unraid version (4.x or 5.x or even more specific) ex: ('compiler' installs cxxlibs, assume its for the 4.4b2-b5 users.. not needed for others)? Reinstall / Remove package Proper way to update a package / submit it to unraid / what actually needs to be changed.. I've seen a few updates floating around on websites/forums for packages but none of them seemed to have made it back to the actual trunk.. is there any rules about packages.. try to keep them as lean as possible? built for the lowest common denominator? For example the 'compiler' package only includes GCC not G++.. should we extend it to include it or make it a separate package? or add option to a package and relay that back and use during install.. like 'x - include g++' About bwm-ng: noticed that it needs to be a little wider so that the values don't word wrap when the network/disk values are in the double digits or even tripple digits.. it only shows in one fixed format (kb?) or does it have the ability to adjust to b/kb/mb/gb/tb? Additionally, I plan on updating the md5deep package, as the currently installed version is 3.6 and there has been a bit of upgrades to it. Some highlights (for me) for the difference between 3.6 (23 Mar 2010) and 4.3 (24 Oct 2012): The old 3.6 version md5deep package only installed md5deep* sha1deep* sha256deep* tigerdeep* whirlpooldeep*, it didn't copy hashdeep (there was some peoples forked installs that did) However now md5deep 4.x requires g++ which lead me down the path of wanting to update the compiler package as well. 4.4 beta of md5deep includes SHA3 with sha3deep, but as dev moved to github I'm uncertain if 4.4 will be on sourceforge to grab from or if they will post once its out of beta (also I found a bug on windows for them to fix) dev: https://github.com/jessek/hashdeep changelog: https://github.com/jessek/hashdeep/blob/master/NEWS

already tried the local master. doesnt do anything.. since smb doesnt run until the array starts.

removed sdg from the array. reset array config. reassigned disks back to their spots and started array.. letting it rebuild parity now. will run parity check once its completed to make sure. so with that disk remove, parity check is clean. so now i guess i'll try out another disk in that spot to see if the problem returns to see if maybe its the sas port/cable/norco cage shutdown unraid and swapped the disk14 spot with another disk to test with.. only 160gb so figure'd it would make for easier testing. started the pre-clear.. checked back and the syslog was 2gb... -rw-r--r-- 1 root root 2.0G 2013-04-09 16:40 syslog with the same sort of repeating message: Apr 9 16:40:53 husky kernel: sd 0:0:4:0: [sdg] CDB: cdb[0]=0x28: 28 00 12 a1 9e 70 00 00 08 00 (Drive related) Apr 9 16:40:53 husky kernel: end_request: I/O error, dev sdg, sector 312581744 (Errors) Apr 9 16:40:53 husky kernel: sd 0:0:4:0: [sdg] Unhandled error code (Errors) Apr 9 16:40:53 husky kernel: sd 0:0:4:0: [sdg] Result: hostbyte=0x04 driverbyte=0x00 (System) looking at the syslog for when it started, I see: Apr 9 16:32:10 husky kernel: NTFS driver 2.1.30 [Flags: R/W MODULE]. Apr 9 16:35:23 husky kernel: sdg: sdg1 Apr 9 16:36:31 husky kernel: sd 0:0:4:0: [sdg] command f4b55900 timed out Apr 9 16:36:31 husky kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1 Apr 9 16:36:31 husky kernel: sas: ata11: end_device-0:4: cmd error handler Apr 9 16:36:31 husky kernel: sas: ata7: end_device-0:0: dev error handler Apr 9 16:36:31 husky kernel: sas: ata8: end_device-0:1: dev error handler Apr 9 16:36:31 husky kernel: sas: ata9: end_device-0:2: dev error handler Apr 9 16:36:31 husky kernel: sas: ata10: end_device-0:3: dev error handler Apr 9 16:36:31 husky kernel: sas: ata11: end_device-0:4: dev error handler Apr 9 16:36:31 husky kernel: ata11.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 Apr 9 16:36:31 husky kernel: ata11.00: failed command: READ DMA Apr 9 16:36:31 husky kernel: ata11.00: cmd c8/00:00:80:55:64/00:00:00:00:00/e0 tag 0 dma 131072 in Apr 9 16:36:31 husky kernel: res 51/84:cf:b1:55:64/00:00:00:00:00/e0 Emask 0x10 (ATA bus error) Apr 9 16:36:31 husky kernel: ata11.00: status: { DRDY ERR } Apr 9 16:36:31 husky kernel: ata11.00: error: { ICRC ABRT } Apr 9 16:36:31 husky kernel: ata11: hard resetting link Apr 9 16:36:32 husky kernel: ata11.00: both IDENTIFYs aborted, assuming NODEV Apr 9 16:36:32 husky kernel: ata11.00: revalidation failed (errno=-2) Apr 9 16:36:37 husky kernel: ata11: hard resetting link Apr 9 16:36:37 husky kernel: ata11.00: both IDENTIFYs aborted, assuming NODEV Apr 9 16:36:37 husky kernel: ata11.00: revalidation failed (errno=-2) Apr 9 16:36:42 husky kernel: ata11: hard resetting link Apr 9 16:36:42 husky kernel: ata11.00: both IDENTIFYs aborted, assuming NODEV Apr 9 16:36:42 husky kernel: ata11.00: revalidation failed (errno=-2) Apr 9 16:36:42 husky kernel: ata11.00: disabled Apr 9 16:36:42 husky kernel: ata11: EH complete Apr 9 16:36:42 husky kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 Apr 9 16:36:42 husky kernel: sd 0:0:4:0: [sdg] Unhandled error code Apr 9 16:36:42 husky kernel: sd 0:0:4:0: [sdg] Result: hostbyte=0x04 driverbyte=0x00 Apr 9 16:36:42 husky kernel: sd 0:0:4:0: [sdg] CDB: cdb[0]=0x28: 28 00 00 64 55 80 00 01 00 00 Apr 9 16:36:42 husky kernel: end_request: I/O error, dev sdg, sector 6575488 Apr 9 16:36:42 husky kernel: Buffer I/O error on device sdg, logical block 821936 Apr 9 16:36:42 husky kernel: Buffer I/O error on device sdg, logical block 821937 Apr 9 16:36:42 husky kernel: Buffer I/O error on device sdg, logical block 821938 Apr 9 16:36:42 husky kernel: Buffer I/O error on device sdg, logical block 821939 Apr 9 16:36:42 husky kernel: Buffer I/O error on device sdg, logical block 821940 Apr 9 16:36:42 husky kernel: Buffer I/O error on device sdg, logical block 821941 Apr 9 16:36:42 husky kernel: Buffer I/O error on device sdg, logical block 821942 Apr 9 16:36:42 husky kernel: Buffer I/O error on device sdg, logical block 821943 Apr 9 16:36:42 husky kernel: Buffer I/O error on device sdg, logical block 821944 Apr 9 16:36:42 husky kernel: sd 0:0:4:0: [sdg] Unhandled error code Apr 9 16:36:42 husky kernel: sd 0:0:4:0: [sdg] Result: hostbyte=0x04 driverbyte=0x00 Apr 9 16:36:42 husky kernel: sd 0:0:4:0: [sdg] CDB: cdb[0]=0x28: 28 00 00 64 55 80 00 00 08 00 Apr 9 16:36:42 husky kernel: end_request: I/O error, dev sdg, sector 6575488 Apr 9 16:36:42 husky kernel: Buffer I/O error on device sdg, logical block 821936 Apr 9 16:36:42 husky kernel: sd 0:0:4:0: [sdg] Unhandled error code Apr 9 16:36:42 husky kernel: sd 0:0:4:0: [sdg] Result: hostbyte=0x04 driverbyte=0x00 Apr 9 16:36:42 husky kernel: sd 0:0:4:0: [sdg] CDB: cdb[0]=0x28 Apr 9 16:36:42 husky kernel: sd 0:0:4:0: [sdg] Unhandled error code Apr 9 16:36:42 husky kernel: sd 0:0:4:0: [sdg] Result: hostbyte=0x04 driverbyte=0x00 Apr 9 16:36:42 husky kernel: sd 0:0:4:0: [sdg] CDB: cdb[0]=0x28: 28 00 00 64 55 80 00 00 08 00 Apr 9 16:36:42 husky kernel: end_request: I/O error, dev sdg, sector 6575488 Apr 9 16:36:42 husky kernel: : 28 00 00 64 56 80 00 01 00 00

Apr 7 06:31:03 husky kernel: ata11.00: exception Emask 0x0 SAct 0x7fffffff SErr 0x0 action 0x6 frozen (Errors) Apr 7 06:31:03 husky kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Apr 7 06:31:03 husky kernel: ata11.00: cmd 60/38:00:b0:50:e9/00:00:91:00:00/40 tag 0 ncq 28672 in (Drive related) Apr 7 06:31:03 husky kernel: res 40/00:04:88:9e:02/00:00:8c:00:00/40 Emask 0x4 (timeout) (Errors) Apr 7 06:31:03 husky kernel: ata11.00: status: { DRDY } (Drive related) Apr 7 06:31:03 husky kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Apr 7 06:31:03 husky kernel: ata11.00: cmd 60/28:00:e8:50:e9/00:00:91:00:00/40 tag 1 ncq 20480 in (Drive related) Apr 7 06:31:03 husky kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Apr 7 06:31:03 husky kernel: ata11.00: status: { DRDY } (Drive related) Apr 7 06:31:03 husky kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Apr 7 06:31:03 husky kernel: ata11.00: cmd 60/40:00:f0:52:e9/00:00:91:00:00/40 tag 2 ncq 32768 in (Drive related) Apr 7 06:31:03 husky kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Apr 7 06:31:03 husky kernel: ata11.00: status: { DRDY } (Drive related) Apr 7 06:31:03 husky kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Apr 7 06:31:03 husky kernel: ata11.00: cmd 60/38:00:28:55:e9/01:00:91:00:00/40 tag 3 ncq 159744 in (Drive related) Apr 7 06:31:03 husky kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Apr 7 06:31:03 husky kernel: ata11.00: status: { DRDY } (Drive related) Apr 7 06:31:03 husky kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Apr 7 06:31:03 husky kernel: ata11.00: cmd 60/38:00:38:51:e9/00:00:91:00:00/40 tag 4 ncq 28672 in (Drive related) Apr 7 06:31:03 husky kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Apr 7 06:31:03 husky kernel: ata11.00: status: { DRDY } (Drive related) Apr 7 06:31:03 husky kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Apr 7 06:31:03 husky kernel: ata11.00: cmd 60/90:00:38:4d:e9/00:00:91:00:00/40 tag 5 ncq 73728 in (Drive related) Apr 7 06:31:03 husky kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Apr 7 06:31:03 husky kernel: ata11.00: status: { DRDY } (Drive related) Apr 7 06:31:03 husky kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Apr 7 06:31:03 husky kernel: ata11.00: cmd 60/68:00:c8:4d:e9/00:00:91:00:00/40 tag 6 ncq 53248 in (Drive related) Apr 7 06:31:03 husky kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Apr 7 06:31:03 husky kernel: ata11.00: status: { DRDY } (Drive related) Apr 7 06:31:03 husky kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Apr 7 06:31:03 husky kernel: ata11.00: cmd 60/38:00:30:4e:e9/00:00:91:00:00/40 tag 7 ncq 28672 in (Drive related) Apr 7 06:31:03 husky kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Apr 7 06:31:03 husky kernel: ata11.00: status: { DRDY } (Drive related) Apr 7 06:31:03 husky kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Apr 7 06:31:03 husky kernel: ata11.00: cmd 60/20:00:48:4f:e9/00:00:91:00:00/40 tag 8 ncq 16384 in (Drive related) Apr 7 06:31:03 husky kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Apr 7 06:31:03 husky kernel: ata11.00: status: { DRDY } (Drive related) Apr 7 06:31:03 husky kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Apr 7 06:31:03 husky kernel: ata11.00: cmd 60/30:00:b8:4f:e9/00:00:91:00:00/40 tag 9 ncq 24576 in (Drive related) Apr 7 06:31:03 husky kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Apr 7 06:31:03 husky kernel: ata11.00: status: { DRDY } (Drive related) Apr 7 06:31:03 husky kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Apr 7 06:31:03 husky kernel: ata11.00: cmd 60/28:00:70:51:e9/00:00:91:00:00/40 tag 10 ncq 20480 in (Drive related) Apr 7 06:31:03 husky kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Apr 7 06:31:03 husky kernel: ata11.00: status: { DRDY } (Drive related) Apr 7 06:31:03 husky kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Apr 7 06:31:03 husky kernel: ata11.00: cmd 60/58:00:98:51:e9/00:00:91:00:00/40 tag 11 ncq 45056 in (Drive related) Apr 7 06:31:03 husky kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Apr 7 06:31:03 husky kernel: ata11.00: status: { DRDY } (Drive related) Apr 7 06:31:03 husky kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Apr 7 06:31:03 husky kernel: ata11.00: cmd 60/30:00:f0:51:e9/00:00:91:00:00/40 tag 12 ncq 24576 in (Drive related) Apr 7 06:31:03 husky kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Apr 7 06:31:03 husky kernel: ata11.00: status: { DRDY } (Drive related) Apr 7 06:31:03 husky kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Apr 7 06:31:03 husky kernel: ata11.00: cmd 60/50:00:48:52:e9/00:00:91:00:00/40 tag 13 ncq 40960 in (Drive related) Apr 7 06:31:03 husky kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Apr 7 06:31:03 husky kernel: ata11.00: status: { DRDY } (Drive related) Apr 7 06:31:03 husky kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Apr 7 06:31:03 husky kernel: ata11.00: cmd 60/28:00:98:52:e9/00:00:91:00:00/40 tag 14 ncq 20480 in (Drive related) Apr 7 06:31:03 husky kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Apr 7 06:31:03 husky kernel: ata11.00: status: { DRDY } (Drive related) Apr 7 06:31:03 husky kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Apr 7 06:31:03 husky kernel: ata11.00: cmd 60/30:00:c0:52:e9/00:00:91:00:00/40 tag 15 ncq 24576 in (Drive related) Apr 7 06:31:03 husky kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Apr 7 06:31:03 husky kernel: ata11.00: status: { DRDY } (Drive related) Apr 7 06:31:03 husky kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Apr 7 06:31:03 husky kernel: ata11.00: cmd 60/30:00:30:53:e9/00:00:91:00:00/40 tag 16 ncq 24576 in (Drive related) Apr 7 06:31:03 husky kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Apr 7 06:31:03 husky kernel: ata11.00: status: { DRDY } (Drive related) Apr 7 06:31:03 husky kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Apr 7 06:31:03 husky kernel: ata11.00: cmd 60/c8:00:60:53:e9/01:00:91:00:00/40 tag 17 ncq 233472 in (Drive related) Apr 7 06:31:03 husky kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Apr 7 06:31:03 husky kernel: ata11.00: status: { DRDY } (Drive related) Apr 7 06:31:03 husky kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Apr 7 06:31:03 husky kernel: ata11.00: cmd 60/28:00:68:4e:e9/00:00:91:00:00/40 tag 18 ncq 20480 in (Drive related) Apr 7 06:31:03 husky kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Apr 7 06:31:03 husky kernel: ata11.00: status: { DRDY } (Drive related) Apr 7 06:31:03 husky kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Apr 7 06:31:03 husky kernel: ata11.00: cmd 60/28:00:c8:4e:e9/00:00:91:00:00/40 tag 19 ncq 20480 in (Drive related) Apr 7 06:31:03 husky kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Apr 7 06:31:03 husky kernel: ata11.00: status: { DRDY } (Drive related) Apr 7 06:31:03 husky kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Apr 7 06:31:03 husky kernel: ata11.00: cmd 60/28:00:68:4f:e9/00:00:91:00:00/40 tag 20 ncq 20480 in (Drive related) Apr 7 06:31:03 husky kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Apr 7 06:31:03 husky kernel: ata11.00: status: { DRDY } (Drive related) Apr 7 06:31:03 husky kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Apr 7 06:31:03 husky kernel: ata11.00: cmd 60/38:00:e8:4f:e9/00:00:91:00:00/40 tag 21 ncq 28672 in (Drive related) Apr 7 06:31:03 husky kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Apr 7 06:31:03 husky kernel: ata11.00: status: { DRDY } (Drive related) Apr 7 06:31:03 husky kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Apr 7 06:31:03 husky kernel: ata11.00: cmd 60/30:00:20:50:e9/00:00:91:00:00/40 tag 22 ncq 24576 in (Drive related) Apr 7 06:31:03 husky kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Apr 7 06:31:03 husky kernel: ata11.00: status: { DRDY } (Drive related) Apr 7 06:31:03 husky kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Apr 7 06:31:03 husky kernel: ata11.00: cmd 60/38:00:50:50:e9/00:00:91:00:00/40 tag 23 ncq 28672 in (Drive related) Apr 7 06:31:03 husky kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Apr 7 06:31:03 husky kernel: ata11.00: status: { DRDY } (Drive related) Apr 7 06:31:03 husky kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Apr 7 06:31:03 husky kernel: ata11.00: cmd 60/98:00:60:56:e9/00:00:91:00:00/40 tag 24 ncq 77824 in (Drive related) Apr 7 06:31:03 husky kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Apr 7 06:31:03 husky kernel: ata11.00: status: { DRDY } (Drive related) Apr 7 06:31:03 husky kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Apr 7 06:31:03 husky kernel: ata11.00: cmd 60/38:00:90:4e:e9/00:00:91:00:00/40 tag 25 ncq 28672 in (Drive related) Apr 7 06:31:03 husky kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Apr 7 06:31:03 husky kernel: ata11.00: status: { DRDY } (Drive related) Apr 7 06:31:03 husky kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Apr 7 06:31:03 husky kernel: ata11.00: cmd 60/58:00:f0:4e:e9/00:00:91:00:00/40 tag 26 ncq 45056 in (Drive related) Apr 7 06:31:03 husky kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Apr 7 06:31:03 husky kernel: ata11.00: status: { DRDY } (Drive related) Apr 7 06:31:03 husky kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Apr 7 06:31:03 husky kernel: ata11.00: cmd 60/28:00:90:4f:e9/00:00:91:00:00/40 tag 27 ncq 20480 in (Drive related) Apr 7 06:31:03 husky kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Apr 7 06:31:03 husky kernel: ata11.00: status: { DRDY } (Drive related) Apr 7 06:31:03 husky kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Apr 7 06:31:03 husky kernel: ata11.00: cmd 60/28:00:88:50:e9/00:00:91:00:00/40 tag 28 ncq 20480 in (Drive related) Apr 7 06:31:03 husky kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Apr 7 06:31:03 husky kernel: ata11.00: status: { DRDY } (Drive related) Apr 7 06:31:03 husky kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Apr 7 06:31:03 husky kernel: ata11.00: cmd 60/28:00:20:52:e9/00:00:91:00:00/40 tag 29 ncq 20480 in (Drive related) Apr 7 06:31:03 husky kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Apr 7 06:31:03 husky kernel: ata11.00: status: { DRDY } (Drive related) Apr 7 06:31:03 husky kernel: ata11.00: failed command: READ FPDMA QUEUED (Minor Issues) Apr 7 06:31:03 husky kernel: ata11.00: cmd 60/28:00:10:51:e9/00:00:91:00:00/40 tag 30 ncq 20480 in (Drive related) Apr 7 06:31:03 husky kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Apr 7 06:31:03 husky kernel: ata11.00: status: { DRDY } (Drive related) Apr 7 06:31:03 husky kernel: ata11: hard resetting link (Minor Issues) Apr 7 06:31:04 husky kernel: drivers/scsi/mvsas/mv_sas.c 1521:mvs_I_T_nexus_reset for device[4]:rc= 0 (System) Apr 7 06:31:04 husky kernel: sas: sas_ata_task_done: SAS error 8a (Errors) Apr 7 06:31:04 husky kernel: sas: sas_ata_task_done: SAS error 8a (Errors) Apr 7 06:31:04 husky kernel: ata11.00: both IDENTIFYs aborted, assuming NODEV (Drive related) Apr 7 06:31:04 husky kernel: ata11.00: revalidation failed (errno=-2) (Minor Issues) Apr 7 06:31:04 husky kernel: mvsas 0000:01:00.0: Phy4 : No sig fis (Drive related) Apr 7 06:31:09 husky kernel: sas: sas_form_port: phy4 belongs to port4 already(1)! (Drive related) Apr 7 06:31:09 husky kernel: ata11: hard resetting link (Minor Issues) Apr 7 06:31:09 husky kernel: ata11.00: configured for UDMA/133 (Drive related) Apr 7 06:31:09 husky kernel: ata11.00: device reported invalid CHS sector 0 (Drive related) Apr 7 06:31:09 husky last message repeated 29 times Apr 7 06:31:09 husky kernel: ata11: EH complete (Drive related) Apr 7 06:31:09 husky kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 (Drive related) Apr 7 06:31:09 husky kernel: md: parity incorrect, sector=2447988984 (Errors) Apr 7 06:31:09 husky kernel: md: parity incorrect, sector=2447988992 (Errors) Apr 7 06:31:09 husky kernel: md: parity incorrect, sector=2447989000 (Errors) Apr 7 06:31:09 husky kernel: md: parity incorrect, sector=2447989008 (Errors) Apr 7 06:31:09 husky kernel: md: parity incorrect, sector=2447989016 (Errors) Apr 7 06:31:09 husky kernel: md: parity incorrect, sector=2447989024 (Errors) Apr 7 06:31:09 husky kernel: md: parity incorrect, sector=2447989032 (Errors) Apr 7 06:31:09 husky kernel: md: parity incorrect, sector=2447989040 (Errors) Apr 7 06:31:09 husky kernel: md: parity incorrect, sector=2447989048 (Errors) Apr 7 06:31:09 husky kernel: md: parity incorrect, sector=2447989056 (Errors) Apr 7 06:31:09 husky kernel: md: parity incorrect, sector=2447989064 (Errors) Apr 7 06:31:09 husky kernel: md: parity incorrect, sector=2447989072 (Errors) Apr 7 06:40:54 husky kernel: mdcmd (48): spindown 1 (Routine) Apr 7 06:40:54 husky kernel: mdcmd (49): spindown 2 (Routine) Apr 7 06:40:55 husky kernel: mdcmd (50): spindown 3 (Routine) should i be concern about the SAS stuff? or is it just a byproduct of the drive errors trickling up to the controller?

put the drive back into array.. it built pairty.. no problems. ran parity check (non-correcting), so far 12 errors.. some ugly stuff in the log though Apr 7 01:49:51 husky kernel: mdcmd (47): check NOCORRECT (unRAID engine) Apr 7 01:49:51 husky kernel: md: recovery thread woken up ... (unRAID engine) Apr 7 01:49:51 husky kernel: md: recovery thread checking parity... (unRAID engine) Apr 7 01:49:51 husky kernel: md: using 1536k window, over a total of 2930266532 blocks. (unRAID engine) Apr 7 06:31:02 husky kernel: sd 0:0:4:0: [sdg] command dfab2840 timed out (Drive related) Apr 7 06:31:02 husky kernel: sd 0:0:4:0: [sdg] command dfab2240 timed out (Drive related) Apr 7 06:31:02 husky kernel: sd 0:0:4:0: [sdg] command df56ff00 timed out (Drive related) Apr 7 06:31:02 husky kernel: sd 0:0:4:0: [sdg] command df95b540 timed out (Drive related) Apr 7 06:31:02 husky kernel: sd 0:0:4:0: [sdg] command df9c7780 timed out (Drive related) Apr 7 06:31:02 husky kernel: sd 0:0:4:0: [sdg] command f4a759c0 timed out (Drive related) Apr 7 06:31:02 husky kernel: sd 0:0:4:0: [sdg] command dfb50cc0 timed out (Drive related) Apr 7 06:31:02 husky kernel: sd 0:0:4:0: [sdg] command dfab26c0 timed out (Drive related) Apr 7 06:31:02 husky kernel: sd 0:0:4:0: [sdg] command dfab2480 timed out (Drive related) Apr 7 06:31:02 husky kernel: sd 0:0:4:0: [sdg] command df9c73c0 timed out (Drive related) Apr 7 06:31:02 husky kernel: sd 0:0:4:0: [sdg] command f4a75540 timed out (Drive related) Apr 7 06:31:02 husky kernel: sd 0:0:4:0: [sdg] command df571b40 timed out (Drive related) Apr 7 06:31:02 husky kernel: sd 0:0:4:0: [sdg] command df571f00 timed out (Drive related) Apr 7 06:31:02 husky kernel: sd 0:0:4:0: [sdg] command df571840 timed out (Drive related) Apr 7 06:31:02 husky kernel: sd 0:0:4:0: [sdg] command df9c7900 timed out (Drive related) Apr 7 06:31:02 husky kernel: sd 0:0:4:0: [sdg] command f4b75540 timed out (Drive related) Apr 7 06:31:02 husky kernel: sd 0:0:4:0: [sdg] command f4b756c0 timed out (Drive related) Apr 7 06:31:02 husky kernel: sd 0:0:4:0: [sdg] command df571900 timed out (Drive related) Apr 7 06:31:02 husky kernel: sd 0:0:4:0: [sdg] command dfb35c00 timed out (Drive related) Apr 7 06:31:02 husky kernel: sd 0:0:4:0: [sdg] command dfb61b40 timed out (Drive related) Apr 7 06:31:02 husky kernel: sd 0:0:4:0: [sdg] command dfa18cc0 timed out (Drive related) Apr 7 06:31:02 husky kernel: sd 0:0:4:0: [sdg] command dfb61900 timed out (Drive related) Apr 7 06:31:02 husky kernel: sd 0:0:4:0: [sdg] command dfb353c0 timed out (Drive related) Apr 7 06:31:02 husky kernel: sd 0:0:4:0: [sdg] command dfb35840 timed out (Drive related) Apr 7 06:31:02 husky kernel: sd 0:0:4:0: [sdg] command dfb35240 timed out (Drive related) Apr 7 06:31:02 husky kernel: sd 0:0:4:0: [sdg] command dfad9c00 timed out (Drive related) Apr 7 06:31:02 husky kernel: sd 0:0:4:0: [sdg] command dfb610c0 timed out (Drive related) Apr 7 06:31:02 husky kernel: sd 0:0:4:0: [sdg] command dfb61cc0 timed out (Drive related) Apr 7 06:31:02 husky kernel: sd 0:0:4:0: [sdg] command dfb61780 timed out (Drive related) Apr 7 06:31:02 husky kernel: sd 0:0:4:0: [sdg] command dfb61000 timed out (Drive related) Apr 7 06:31:02 husky kernel: sd 0:0:4:0: [sdg] command df9c7a80 timed out (Drive related) Apr 7 06:31:02 husky kernel: sas: Enter sas_scsi_recover_host busy: 31 failed: 31 (Drive related) Apr 7 06:31:02 husky kernel: sas: trying to find task 0xdf9a2640 (Drive related) Apr 7 06:31:02 husky kernel: sas: sas_scsi_find_task: aborting task 0xdf9a2640 (Drive related) Apr 7 06:31:02 husky kernel: sas: sas_scsi_find_task: task 0xdf9a2640 is aborted (Drive related) Apr 7 06:31:02 husky kernel: sas: sas_eh_handle_sas_errors: task 0xdf9a2640 is aborted (Errors) Apr 7 06:31:02 husky kernel: sas: trying to find task 0xdf9a3b80 (Drive related) Apr 7 06:31:02 husky kernel: sas: sas_scsi_find_task: aborting task 0xdf9a3b80 (Drive related) Apr 7 06:31:02 husky kernel: sas: sas_scsi_find_task: task 0xdf9a3b80 is aborted (Drive related) Apr 7 06:31:02 husky kernel: sas: sas_eh_handle_sas_errors: task 0xdf9a3b80 is aborted (Errors) Apr 7 06:31:02 husky kernel: sas: trying to find task 0xdf9a3400 (Drive related) Apr 7 06:31:02 husky kernel: sas: sas_scsi_find_task: aborting task 0xdf9a3400 (Drive related) Apr 7 06:31:02 husky kernel: sas: sas_scsi_find_task: task 0xdf9a3400 is aborted (Drive related) Apr 7 06:31:02 husky kernel: sas: sas_eh_handle_sas_errors: task 0xdf9a3400 is aborted (Errors) Apr 7 06:31:02 husky kernel: sas: trying to find task 0xdf9a2f00 (Drive related) Apr 7 06:31:02 husky kernel: sas: sas_scsi_find_task: aborting task 0xdf9a2f00 (Drive related) Apr 7 06:31:02 husky kernel: sas: sas_scsi_find_task: task 0xdf9a2f00 is aborted (Drive related) Apr 7 06:31:02 husky kernel: sas: sas_eh_handle_sas_errors: task 0xdf9a2f00 is aborted (Errors) Apr 7 06:31:02 husky kernel: sas: trying to find task 0xdf9a3e00 (Drive related) Apr 7 06:31:02 husky kernel: sas: sas_scsi_find_task: aborting task 0xdf9a3e00 (Drive related) Apr 7 06:31:02 husky kernel: sas: sas_scsi_find_task: task 0xdf9a3e00 is aborted (Drive related) Apr 7 06:31:02 husky kernel: sas: sas_eh_handle_sas_errors: task 0xdf9a3e00 is aborted (Errors) Apr 7 06:31:02 husky kernel: sas: trying to find task 0xdf9a3680 (Drive related) Apr 7 06:31:02 husky kernel: sas: sas_scsi_find_task: aborting task 0xdf9a3680 (Drive related) Apr 7 06:31:02 husky kernel: sas: sas_scsi_find_task: task 0xdf9a3680 is aborted (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_eh_handle_sas_errors: task 0xdf9a3680 is aborted (Errors) Apr 7 06:31:03 husky kernel: sas: trying to find task 0xdf9a2c80 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: aborting task 0xdf9a2c80 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: task 0xdf9a2c80 is aborted (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_eh_handle_sas_errors: task 0xdf9a2c80 is aborted (Errors) Apr 7 06:31:03 husky kernel: sas: trying to find task 0xdf9a2000 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: aborting task 0xdf9a2000 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: task 0xdf9a2000 is aborted (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_eh_handle_sas_errors: task 0xdf9a2000 is aborted (Errors) Apr 7 06:31:03 husky kernel: sas: trying to find task 0xdf9a28c0 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: aborting task 0xdf9a28c0 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: task 0xdf9a28c0 is aborted (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_eh_handle_sas_errors: task 0xdf9a28c0 is aborted (Errors) Apr 7 06:31:03 husky kernel: sas: trying to find task 0xdf9a2a00 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: aborting task 0xdf9a2a00 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: task 0xdf9a2a00 is aborted (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_eh_handle_sas_errors: task 0xdf9a2a00 is aborted (Errors) Apr 7 06:31:03 husky kernel: sas: trying to find task 0xdf9a37c0 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: aborting task 0xdf9a37c0 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: task 0xdf9a37c0 is aborted (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_eh_handle_sas_errors: task 0xdf9a37c0 is aborted (Errors) Apr 7 06:31:03 husky kernel: sas: trying to find task 0xdf9a3a40 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: aborting task 0xdf9a3a40 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: task 0xdf9a3a40 is aborted (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_eh_handle_sas_errors: task 0xdf9a3a40 is aborted (Errors) Apr 7 06:31:03 husky kernel: sas: trying to find task 0xdf9a2140 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: aborting task 0xdf9a2140 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: task 0xdf9a2140 is aborted (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_eh_handle_sas_errors: task 0xdf9a2140 is aborted (Errors) Apr 7 06:31:03 husky kernel: sas: trying to find task 0xdf9a2dc0 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: aborting task 0xdf9a2dc0 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: task 0xdf9a2dc0 is aborted (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_eh_handle_sas_errors: task 0xdf9a2dc0 is aborted (Errors) Apr 7 06:31:03 husky kernel: sas: trying to find task 0xdf9a3540 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: aborting task 0xdf9a3540 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: task 0xdf9a3540 is aborted (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_eh_handle_sas_errors: task 0xdf9a3540 is aborted (Errors) Apr 7 06:31:03 husky kernel: sas: trying to find task 0xdf9a23c0 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: aborting task 0xdf9a23c0 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: task 0xdf9a23c0 is aborted (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_eh_handle_sas_errors: task 0xdf9a23c0 is aborted (Errors) Apr 7 06:31:03 husky kernel: sas: trying to find task 0xdf9a2500 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: aborting task 0xdf9a2500 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: task 0xdf9a2500 is aborted (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_eh_handle_sas_errors: task 0xdf9a2500 is aborted (Errors) Apr 7 06:31:03 husky kernel: sas: trying to find task 0xf5336c80 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: aborting task 0xf5336c80 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: task 0xf5336c80 is aborted (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_eh_handle_sas_errors: task 0xf5336c80 is aborted (Errors) Apr 7 06:31:03 husky kernel: sas: trying to find task 0xf0913180 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: aborting task 0xf0913180 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: task 0xf0913180 is aborted (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_eh_handle_sas_errors: task 0xf0913180 is aborted (Errors) Apr 7 06:31:03 husky kernel: sas: trying to find task 0xf0930280 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: aborting task 0xf0930280 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: task 0xf0930280 is aborted (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_eh_handle_sas_errors: task 0xf0930280 is aborted (Errors) Apr 7 06:31:03 husky kernel: sas: trying to find task 0xf0912000 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: aborting task 0xf0912000 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: task 0xf0912000 is aborted (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_eh_handle_sas_errors: task 0xf0912000 is aborted (Errors) Apr 7 06:31:03 husky kernel: sas: trying to find task 0xf5336000 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: aborting task 0xf5336000 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: task 0xf5336000 is aborted (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_eh_handle_sas_errors: task 0xf5336000 is aborted (Errors) Apr 7 06:31:03 husky kernel: sas: trying to find task 0xf5336640 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: aborting task 0xf5336640 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: task 0xf5336640 is aborted (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_eh_handle_sas_errors: task 0xf5336640 is aborted (Errors) Apr 7 06:31:03 husky kernel: sas: trying to find task 0xf5337400 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: aborting task 0xf5337400 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: task 0xf5337400 is aborted (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_eh_handle_sas_errors: task 0xf5337400 is aborted (Errors) Apr 7 06:31:03 husky kernel: sas: trying to find task 0xf53368c0 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: aborting task 0xf53368c0 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: task 0xf53368c0 is aborted (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_eh_handle_sas_errors: task 0xf53368c0 is aborted (Errors) Apr 7 06:31:03 husky kernel: sas: trying to find task 0xf0913e00 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: aborting task 0xf0913e00 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: task 0xf0913e00 is aborted (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_eh_handle_sas_errors: task 0xf0913e00 is aborted (Errors) Apr 7 06:31:03 husky kernel: sas: trying to find task 0xf0913cc0 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: aborting task 0xf0913cc0 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: task 0xf0913cc0 is aborted (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_eh_handle_sas_errors: task 0xf0913cc0 is aborted (Errors) Apr 7 06:31:03 husky kernel: sas: trying to find task 0xf0913b80 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: aborting task 0xf0913b80 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: task 0xf0913b80 is aborted (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_eh_handle_sas_errors: task 0xf0913b80 is aborted (Errors) Apr 7 06:31:03 husky kernel: sas: trying to find task 0xf09123c0 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: aborting task 0xf09123c0 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: task 0xf09123c0 is aborted (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_eh_handle_sas_errors: task 0xf09123c0 is aborted (Errors) Apr 7 06:31:03 husky kernel: sas: trying to find task 0xf0912780 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: aborting task 0xf0912780 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: task 0xf0912780 is aborted (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_eh_handle_sas_errors: task 0xf0912780 is aborted (Errors) Apr 7 06:31:03 husky kernel: sas: trying to find task 0xf09128c0 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: aborting task 0xf09128c0 (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_scsi_find_task: task 0xf09128c0 is aborted (Drive related) Apr 7 06:31:03 husky kernel: sas: sas_eh_handle_sas_errors: task 0xf09128c0 is aborted (Errors) Apr 7 06:31:03 husky kernel: sas: ata11: end_device-0:4: cmd error handler (Errors) Apr 7 06:31:03 husky kernel: sas: ata7: end_device-0:0: dev error handler (Errors) Apr 7 06:31:03 husky kernel: sas: ata8: end_device-0:1: dev error handler (Errors) Apr 7 06:31:03 husky kernel: sas: ata9: end_device-0:2: dev error handler (Errors) Apr 7 06:31:03 husky kernel: sas: ata10: end_device-0:3: dev error handler (Errors) Apr 7 06:31:03 husky kernel: sas: ata11: end_device-0:4: dev error handler (Errors) continue in next post

no such thing as a 'dns section' in any of the areas I see. its fine, its just as i suspected.. if the array isnt started i have to use the ip address not the hostname because i rely on samba. ill just use the hosts hack for the one computer i care to mess with the unraid box..

SMART Extended Comprehensive Error Log Version: 1 (6 sectors) Device Error Count: 7 CR = Command Register FEATR = Features Register COUNT = Count (was: Sector Count) Register LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8 LH = LBA High (was: Cylinder High) Register ] LBA LM = LBA Mid (was: Cylinder Low) Register ] Register LL = LBA Low (was: Sector Number) Register ] DV = Device (was: Device/Head) Register DC = Device Control Register ER = Error register ST = Status register Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 7 [6] occurred at disk power-on lifetime: 23609 hours (983 days + 17 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 01 00 00 00 91 e9 47 38 40 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 01 00 00 00 00 00 91 e9 46 88 40 08 23:11:37.811 READ FPDMA QUEUED 60 01 00 00 08 00 00 91 e9 45 88 40 08 23:11:37.809 READ FPDMA QUEUED 60 01 00 00 00 00 00 91 e9 44 88 40 08 23:11:37.808 READ FPDMA QUEUED 60 01 00 00 08 00 00 91 e9 43 88 40 08 23:11:37.806 READ FPDMA QUEUED 60 01 00 00 00 00 00 91 e9 42 88 40 08 23:11:37.803 READ FPDMA QUEUED Error 6 [5] occurred at disk power-on lifetime: 23580 hours (982 days + 12 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 01 00 00 00 92 0c b8 10 40 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 01 00 00 18 00 00 92 0c b8 00 40 08 04:29:55.011 READ FPDMA QUEUED 60 01 00 00 10 00 00 92 0c b7 00 40 08 04:29:55.009 READ FPDMA QUEUED 60 01 00 00 18 00 00 92 0c b6 00 40 08 04:29:55.008 READ FPDMA QUEUED 60 01 00 00 10 00 00 92 0c b5 00 40 08 04:29:55.006 READ FPDMA QUEUED 60 01 00 00 18 00 00 92 0c b4 00 40 08 04:29:55.004 READ FPDMA QUEUED Error 5 [4] occurred at disk power-on lifetime: 23486 hours (978 days + 14 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 01 70 00 00 92 0c b8 10 40 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 10 00 40 00 00 92 0c f4 88 40 08 1d+10:02:23.329 READ FPDMA QUEUED 60 00 28 00 68 00 00 92 0c f4 60 40 08 1d+10:02:23.328 READ FPDMA QUEUED 60 00 a0 00 b8 00 00 92 0c f3 c0 40 08 1d+10:02:23.304 READ FPDMA QUEUED 60 00 b8 00 b0 00 00 92 0c f3 08 40 08 1d+10:02:23.304 READ FPDMA QUEUED 60 00 88 00 a8 00 00 92 0c f2 80 40 08 1d+10:02:23.304 READ FPDMA QUEUED Error 4 [3] occurred at disk power-on lifetime: 23486 hours (978 days + 14 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 01 70 00 00 92 0c b8 10 40 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 38 00 10 00 00 92 0c d6 08 40 08 1d+10:01:44.454 READ FPDMA QUEUED 60 00 28 00 00 00 00 92 0c d5 e0 40 08 1d+10:01:44.454 READ FPDMA QUEUED 60 00 08 00 b0 00 00 92 0c d5 d8 40 08 1d+10:01:44.429 READ FPDMA QUEUED 60 00 08 00 a0 00 00 92 0c d5 d0 40 08 1d+10:01:44.429 READ FPDMA QUEUED 60 00 38 00 90 00 00 92 0c d5 98 40 08 1d+10:01:44.429 READ FPDMA QUEUED Error 3 [2] occurred at disk power-on lifetime: 23486 hours (978 days + 14 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 01 70 00 00 92 0c b8 10 40 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 28 00 b8 00 00 92 0c c2 58 40 08 1d+10:01:06.417 READ FPDMA QUEUED 60 00 60 00 b0 00 00 92 0c c1 f8 40 08 1d+10:01:06.417 READ FPDMA QUEUED 60 00 50 00 10 00 00 92 0c c1 a8 40 08 1d+10:01:06.416 READ FPDMA QUEUED 60 00 50 00 78 00 00 92 0c c1 58 40 08 1d+10:01:06.416 READ FPDMA QUEUED 60 00 80 00 70 00 00 92 0c c0 d8 40 08 1d+10:01:06.416 READ FPDMA QUEUED Error 2 [1] occurred at disk power-on lifetime: 23445 hours (976 days + 21 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 01 00 00 00 92 0c b8 10 40 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 01 00 00 08 00 00 92 0c b7 50 40 08 22:10:44.250 READ FPDMA QUEUED 60 01 00 00 00 00 00 92 0c b8 50 40 08 22:10:44.250 READ FPDMA QUEUED ef 00 10 00 02 00 00 00 00 00 00 a0 08 22:10:44.250 SET FEATURES [Reserved for Serial ATA] 27 00 00 00 00 00 00 00 00 00 00 e0 08 22:10:44.250 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 00 00 00 00 00 a0 08 22:10:44.244 IDENTIFY DEVICE Error 1 [0] occurred at disk power-on lifetime: 23445 hours (976 days + 21 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 01 00 00 00 92 0c b8 10 40 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 01 00 00 00 00 00 92 0c b7 50 40 08 22:10:41.400 READ FPDMA QUEUED 60 01 00 00 08 00 00 92 0c b6 50 40 08 22:10:41.399 READ FPDMA QUEUED 60 01 00 00 00 00 00 92 0c b5 50 40 08 22:10:41.397 READ FPDMA QUEUED 60 01 00 00 08 00 00 92 0c b4 50 40 08 22:10:41.393 READ FPDMA QUEUED 60 01 00 00 00 00 00 92 0c b3 50 40 08 22:10:41.393 READ FPDMA QUEUED SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 23632 - # 2 Extended offline Aborted by host 90% 23625 - # 3 Extended offline Aborted by host 20% 23625 - # 4 Short offline Completed without error 00% 23619 - # 5 Short offline Completed without error 00% 23586 - # 6 Short offline Completed without error 00% 23586 - # 7 Short offline Aborted by host 50% 23586 - # 8 Short offline Aborted by host 20% 23586 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. SCT Status Version: 3 SCT Version (vendor specific): 258 (0x0102) SCT Support Level: 1 Device State: Active (0) Current Temperature: 37 Celsius Power Cycle Min/Max Temperature: 31/37 Celsius Lifetime Min/Max Temperature: ?/42 Celsius Under/Over Temperature Limit Count: 0/0 SCT Temperature History Version: 2 Temperature Sampling Period: 1 minute Temperature Logging Interval: 1 minute Min/Max recommended Temperature: 0/60 Celsius Min/Max Temperature Limit: -41/85 Celsius Temperature History Size (Index): 478 (330) Index Estimated Time Temperature Celsius 331 2013-04-06 09:41 35 **************** ... ..( 66 skipped). .. **************** 398 2013-04-06 10:48 35 **************** 399 2013-04-06 10:49 36 ***************** ... ..( 6 skipped). .. ***************** 406 2013-04-06 10:56 36 ***************** 407 2013-04-06 10:57 37 ****************** ... ..( 16 skipped). .. ****************** 424 2013-04-06 11:14 37 ****************** 425 2013-04-06 11:15 35 **************** ... ..( 61 skipped). .. **************** 9 2013-04-06 12:17 35 **************** 10 2013-04-06 12:18 36 ***************** ... ..(205 skipped). .. ***************** 216 2013-04-06 15:44 36 ***************** 217 2013-04-06 15:45 35 **************** ... ..(112 skipped). .. **************** 330 2013-04-06 17:38 35 **************** Warning: device does not support SCT Error Recovery Control command SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x0001 2 0 Command failed due to ICRC error 0x0002 2 0 R_ERR response for data FIS 0x0003 2 0 R_ERR response for device-to-host data FIS 0x0004 2 0 R_ERR response for host-to-device data FIS 0x0005 2 0 R_ERR response for non-data FIS 0x0006 2 0 R_ERR response for device-to-host non-data FIS 0x0007 2 0 R_ERR response for host-to-device non-data FIS 0x000a 2 2 Device-to-host register FISes sent due to a COMRESET 0x000b 2 0 CRC errors within host-to-device FIS 0x8000 4 168673 Vendor specific

ok long test finished.. posting results (2 parts) the current pending stayed the same, and multi zone error went up by one. 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 1 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 2 /boot/logs# smartctl -x /dev/sdg smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green (Adv. Format) family Device Model: WDC WD20EARS-00S8B1 Serial Number: WD-WCAVY4386698 Firmware Version: 80.00A80 User Capacity: 2,000,398,934,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Sat Apr 6 17:38:22 2013 CDT SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (40800) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3031) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 26 3 Spin_Up_Time 0x0027 157 143 021 Pre-fail Always - 9108 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 83 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 068 068 000 Old_age Always - 23632 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 71 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 32 193 Load_Cycle_Count 0x0032 189 189 000 Old_age Always - 35236 194 Temperature_Celsius 0x0022 115 110 000 Old_age Always - 37 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 1 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 2 General Purpose Logging (GPL) feature set supported General Purpose Log Directory Version 1 SMART Log Directory Version 1 [multi-sector log support] GP/S Log at address 0x00 has 1 sectors [Log Directory] SMART Log at address 0x01 has 1 sectors [summary SMART error log] SMART Log at address 0x02 has 5 sectors [Comprehensive SMART error log] GP Log at address 0x03 has 6 sectors [Ext. Comprehensive SMART error log] SMART Log at address 0x06 has 1 sectors [sMART self-test log] GP Log at address 0x07 has 1 sectors [Extended self-test log] SMART Log at address 0x09 has 1 sectors [selective self-test log] GP Log at address 0x10 has 1 sectors [NCQ Command Error] GP Log at address 0x11 has 1 sectors [sATA Phy Event Counters] GP/S Log at address 0x80 has 16 sectors [Host vendor specific log] GP/S Log at address 0x81 has 16 sectors [Host vendor specific log] GP/S Log at address 0x82 has 16 sectors [Host vendor specific log] GP/S Log at address 0x83 has 16 sectors [Host vendor specific log] GP/S Log at address 0x84 has 16 sectors [Host vendor specific log] GP/S Log at address 0x85 has 16 sectors [Host vendor specific log] GP/S Log at address 0x86 has 16 sectors [Host vendor specific log] GP/S Log at address 0x87 has 16 sectors [Host vendor specific log] GP/S Log at address 0x88 has 16 sectors [Host vendor specific log] GP/S Log at address 0x89 has 16 sectors [Host vendor specific log] GP/S Log at address 0x8a has 16 sectors [Host vendor specific log] GP/S Log at address 0x8b has 16 sectors [Host vendor specific log] GP/S Log at address 0x8c has 16 sectors [Host vendor specific log] GP/S Log at address 0x8d has 16 sectors [Host vendor specific log] GP/S Log at address 0x8e has 16 sectors [Host vendor specific log] GP/S Log at address 0x8f has 16 sectors [Host vendor specific log] GP/S Log at address 0x90 has 16 sectors [Host vendor specific log] GP/S Log at address 0x91 has 16 sectors [Host vendor specific log] GP/S Log at address 0x92 has 16 sectors [Host vendor specific log] GP/S Log at address 0x93 has 16 sectors [Host vendor specific log] GP/S Log at address 0x94 has 16 sectors [Host vendor specific log] GP/S Log at address 0x95 has 16 sectors [Host vendor specific log] GP/S Log at address 0x96 has 16 sectors [Host vendor specific log] GP/S Log at address 0x97 has 16 sectors [Host vendor specific log] GP/S Log at address 0x98 has 16 sectors [Host vendor specific log] GP/S Log at address 0x99 has 16 sectors [Host vendor specific log] GP/S Log at address 0x9a has 16 sectors [Host vendor specific log] GP/S Log at address 0x9b has 16 sectors [Host vendor specific log] GP/S Log at address 0x9c has 16 sectors [Host vendor specific log] GP/S Log at address 0x9d has 16 sectors [Host vendor specific log] GP/S Log at address 0x9e has 16 sectors [Host vendor specific log] GP/S Log at address 0x9f has 16 sectors [Host vendor specific log] GP/S Log at address 0xa0 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa1 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa2 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa3 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa4 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa5 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa6 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa7 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa8 has 1 sectors [Device vendor specific log] GP/S Log at address 0xa9 has 1 sectors [Device vendor specific log] GP/S Log at address 0xaa has 1 sectors [Device vendor specific log] GP/S Log at address 0xab has 1 sectors [Device vendor specific log] GP/S Log at address 0xac has 1 sectors [Device vendor specific log] GP/S Log at address 0xad has 1 sectors [Device vendor specific log] GP/S Log at address 0xae has 1 sectors [Device vendor specific log] GP/S Log at address 0xaf has 1 sectors [Device vendor specific log] GP/S Log at address 0xb0 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb1 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb2 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb3 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb4 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb5 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb6 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb7 has 1 sectors [Device vendor specific log] GP/S Log at address 0xc0 has 1 sectors [Device vendor specific log] GP Log at address 0xc1 has 93 sectors [Device vendor specific log] GP/S Log at address 0xe0 has 1 sectors [sCT Command/Status] GP/S Log at address 0xe1 has 1 sectors [sCT Data Transfer]

continue of output since i exceeded message limit SMART Extended Self-test Log Version: 1 (1 sectors) Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Aborted by host 20% 23625 - # 2 Short offline Completed without error 00% 23619 - # 3 Short offline Completed without error 00% 23586 - # 4 Short offline Completed without error 00% 23586 - # 5 Short offline Aborted by host 50% 23586 - # 6 Short offline Aborted by host 20% 23586 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. SCT Status Version: 3 SCT Version (vendor specific): 258 (0x0102) SCT Support Level: 1 Device State: DST executing in background (3) Current Temperature: 35 Celsius Power Cycle Min/Max Temperature: 31/36 Celsius Lifetime Min/Max Temperature: 31/42 Celsius Under/Over Temperature Limit Count: 0/0 SCT Temperature History Version: 2 Temperature Sampling Period: 1 minute Temperature Logging Interval: 1 minute Min/Max recommended Temperature: 0/60 Celsius Min/Max Temperature Limit: -41/85 Celsius Temperature History Size (Index): 478 (371) Index Estimated Time Temperature Celsius 372 2013-04-06 02:24 35 **************** ... ..( 92 skipped). .. **************** 465 2013-04-06 03:57 35 **************** 466 2013-04-06 03:58 31 ************ ... ..( 12 skipped). .. ************ 1 2013-04-06 04:11 31 ************ 2 2013-04-06 04:12 32 ************* ... ..( 9 skipped). .. ************* 12 2013-04-06 04:22 32 ************* 13 2013-04-06 04:23 33 ************** ... ..( 6 skipped). .. ************** 20 2013-04-06 04:30 33 ************** 21 2013-04-06 04:31 32 ************* ... ..( 7 skipped). .. ************* 29 2013-04-06 04:39 32 ************* 30 2013-04-06 04:40 31 ************ ... ..( 47 skipped). .. ************ 78 2013-04-06 05:28 31 ************ 79 2013-04-06 05:29 32 ************* 80 2013-04-06 05:30 32 ************* 81 2013-04-06 05:31 31 ************ ... ..( 22 skipped). .. ************ 104 2013-04-06 05:54 31 ************ 105 2013-04-06 05:55 32 ************* 106 2013-04-06 05:56 32 ************* 107 2013-04-06 05:57 32 ************* 108 2013-04-06 05:58 33 ************** ... ..( 6 skipped). .. ************** 115 2013-04-06 06:05 33 ************** 116 2013-04-06 06:06 34 *************** ... ..( 20 skipped). .. *************** 137 2013-04-06 06:27 34 *************** 138 2013-04-06 06:28 35 **************** ... ..(232 skipped). .. **************** 371 2013-04-06 10:21 35 **************** Warning: device does not support SCT Error Recovery Control command SATA Phy Event Counters (GP Log 0x11) ID Size Value Description 0x0001 2 0 Command failed due to ICRC error 0x0002 2 0 R_ERR response for data FIS 0x0003 2 0 R_ERR response for device-to-host data FIS 0x0004 2 0 R_ERR response for host-to-device data FIS 0x0005 2 0 R_ERR response for non-data FIS 0x0006 2 0 R_ERR response for device-to-host non-data FIS 0x0007 2 0 R_ERR response for host-to-device non-data FIS 0x000a 2 2 Device-to-host register FISes sent due to a COMRESET 0x000b 2 0 CRC errors within host-to-device FIS 0x8000 4 142492 Vendor specific

issued a long smart test for the drive since i'm still uncertain of where to go with this drive. will report back in 300 mins checked in on it using the smart status button in unraid.. didnt seem like anything was going on.. so issued another long test.. now i see it was only at 20% after like 5 hours.. then i googled and saw i should have disable spin down.. did that. output of smartctl -x on the drive, note that long test is suppose to be running now.. smartctrl -x /dev/sdg -bash: smartctrl: command not found root@husky:/boot/logs# smartctl -x /dev/sdg smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green (Adv. Format) family Device Model: WDC WD20EARS-00S8B1 Serial Number: WD-WCAVY4386698 Firmware Version: 80.00A80 User Capacity: 2,000,398,934,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Sat Apr 6 10:21:36 2013 CDT SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 249) Self-test routine in progress... 90% of test remaining. Total time to complete Offline data collection: (40800) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3031) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 26 3 Spin_Up_Time 0x0027 157 143 021 Pre-fail Always - 9108 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 83 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 068 068 000 Old_age Always - 23625 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 71 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 32 193 Load_Cycle_Count 0x0032 189 189 000 Old_age Always - 35236 194 Temperature_Celsius 0x0022 117 110 000 Old_age Always - 35 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 1 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 1 General Purpose Logging (GPL) feature set supported General Purpose Log Directory Version 1 SMART Log Directory Version 1 [multi-sector log support] GP/S Log at address 0x00 has 1 sectors [Log Directory] SMART Log at address 0x01 has 1 sectors [summary SMART error log] SMART Log at address 0x02 has 5 sectors [Comprehensive SMART error log] GP Log at address 0x03 has 6 sectors [Ext. Comprehensive SMART error log] SMART Log at address 0x06 has 1 sectors [sMART self-test log] GP Log at address 0x07 has 1 sectors [Extended self-test log] SMART Log at address 0x09 has 1 sectors [selective self-test log] GP Log at address 0x10 has 1 sectors [NCQ Command Error] GP Log at address 0x11 has 1 sectors [sATA Phy Event Counters] GP/S Log at address 0x80 has 16 sectors [Host vendor specific log] GP/S Log at address 0x81 has 16 sectors [Host vendor specific log] GP/S Log at address 0x82 has 16 sectors [Host vendor specific log] GP/S Log at address 0x83 has 16 sectors [Host vendor specific log] GP/S Log at address 0x84 has 16 sectors [Host vendor specific log] GP/S Log at address 0x85 has 16 sectors [Host vendor specific log] GP/S Log at address 0x86 has 16 sectors [Host vendor specific log] GP/S Log at address 0x87 has 16 sectors [Host vendor specific log] GP/S Log at address 0x88 has 16 sectors [Host vendor specific log] GP/S Log at address 0x89 has 16 sectors [Host vendor specific log] GP/S Log at address 0x8a has 16 sectors [Host vendor specific log] GP/S Log at address 0x8b has 16 sectors [Host vendor specific log] GP/S Log at address 0x8c has 16 sectors [Host vendor specific log] GP/S Log at address 0x8d has 16 sectors [Host vendor specific log] GP/S Log at address 0x8e has 16 sectors [Host vendor specific log] GP/S Log at address 0x8f has 16 sectors [Host vendor specific log] GP/S Log at address 0x90 has 16 sectors [Host vendor specific log] GP/S Log at address 0x91 has 16 sectors [Host vendor specific log] GP/S Log at address 0x92 has 16 sectors [Host vendor specific log] GP/S Log at address 0x93 has 16 sectors [Host vendor specific log] GP/S Log at address 0x94 has 16 sectors [Host vendor specific log] GP/S Log at address 0x95 has 16 sectors [Host vendor specific log] GP/S Log at address 0x96 has 16 sectors [Host vendor specific log] GP/S Log at address 0x97 has 16 sectors [Host vendor specific log] GP/S Log at address 0x98 has 16 sectors [Host vendor specific log] GP/S Log at address 0x99 has 16 sectors [Host vendor specific log] GP/S Log at address 0x9a has 16 sectors [Host vendor specific log] GP/S Log at address 0x9b has 16 sectors [Host vendor specific log] GP/S Log at address 0x9c has 16 sectors [Host vendor specific log] GP/S Log at address 0x9d has 16 sectors [Host vendor specific log] GP/S Log at address 0x9e has 16 sectors [Host vendor specific log] GP/S Log at address 0x9f has 16 sectors [Host vendor specific log] GP/S Log at address 0xa0 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa1 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa2 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa3 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa4 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa5 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa6 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa7 has 16 sectors [Device vendor specific log] GP/S Log at address 0xa8 has 1 sectors [Device vendor specific log] GP/S Log at address 0xa9 has 1 sectors [Device vendor specific log] GP/S Log at address 0xaa has 1 sectors [Device vendor specific log] GP/S Log at address 0xab has 1 sectors [Device vendor specific log] GP/S Log at address 0xac has 1 sectors [Device vendor specific log] GP/S Log at address 0xad has 1 sectors [Device vendor specific log] GP/S Log at address 0xae has 1 sectors [Device vendor specific log] GP/S Log at address 0xaf has 1 sectors [Device vendor specific log] GP/S Log at address 0xb0 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb1 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb2 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb3 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb4 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb5 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb6 has 1 sectors [Device vendor specific log] GP/S Log at address 0xb7 has 1 sectors [Device vendor specific log] GP/S Log at address 0xc0 has 1 sectors [Device vendor specific log] GP Log at address 0xc1 has 93 sectors [Device vendor specific log] GP/S Log at address 0xe0 has 1 sectors [sCT Command/Status] GP/S Log at address 0xe1 has 1 sectors [sCT Data Transfer] SMART Extended Comprehensive Error Log Version: 1 (6 sectors) Device Error Count: 7 CR = Command Register FEATR = Features Register COUNT = Count (was: Sector Count) Register LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8 LH = LBA High (was: Cylinder High) Register ] LBA LM = LBA Mid (was: Cylinder Low) Register ] Register LL = LBA Low (was: Sector Number) Register ] DV = Device (was: Device/Head) Register DC = Device Control Register ER = Error register ST = Status register Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 7 [6] occurred at disk power-on lifetime: 23609 hours (983 days + 17 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 01 00 00 00 91 e9 47 38 40 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 01 00 00 00 00 00 91 e9 46 88 40 08 23:11:37.811 READ FPDMA QUEUED 60 01 00 00 08 00 00 91 e9 45 88 40 08 23:11:37.809 READ FPDMA QUEUED 60 01 00 00 00 00 00 91 e9 44 88 40 08 23:11:37.808 READ FPDMA QUEUED 60 01 00 00 08 00 00 91 e9 43 88 40 08 23:11:37.806 READ FPDMA QUEUED 60 01 00 00 00 00 00 91 e9 42 88 40 08 23:11:37.803 READ FPDMA QUEUED Error 6 [5] occurred at disk power-on lifetime: 23580 hours (982 days + 12 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 01 00 00 00 92 0c b8 10 40 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 01 00 00 18 00 00 92 0c b8 00 40 08 04:29:55.011 READ FPDMA QUEUED 60 01 00 00 10 00 00 92 0c b7 00 40 08 04:29:55.009 READ FPDMA QUEUED 60 01 00 00 18 00 00 92 0c b6 00 40 08 04:29:55.008 READ FPDMA QUEUED 60 01 00 00 10 00 00 92 0c b5 00 40 08 04:29:55.006 READ FPDMA QUEUED 60 01 00 00 18 00 00 92 0c b4 00 40 08 04:29:55.004 READ FPDMA QUEUED Error 5 [4] occurred at disk power-on lifetime: 23486 hours (978 days + 14 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 01 70 00 00 92 0c b8 10 40 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 10 00 40 00 00 92 0c f4 88 40 08 1d+10:02:23.329 READ FPDMA QUEUED 60 00 28 00 68 00 00 92 0c f4 60 40 08 1d+10:02:23.328 READ FPDMA QUEUED 60 00 a0 00 b8 00 00 92 0c f3 c0 40 08 1d+10:02:23.304 READ FPDMA QUEUED 60 00 b8 00 b0 00 00 92 0c f3 08 40 08 1d+10:02:23.304 READ FPDMA QUEUED 60 00 88 00 a8 00 00 92 0c f2 80 40 08 1d+10:02:23.304 READ FPDMA QUEUED Error 4 [3] occurred at disk power-on lifetime: 23486 hours (978 days + 14 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 01 70 00 00 92 0c b8 10 40 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 38 00 10 00 00 92 0c d6 08 40 08 1d+10:01:44.454 READ FPDMA QUEUED 60 00 28 00 00 00 00 92 0c d5 e0 40 08 1d+10:01:44.454 READ FPDMA QUEUED 60 00 08 00 b0 00 00 92 0c d5 d8 40 08 1d+10:01:44.429 READ FPDMA QUEUED 60 00 08 00 a0 00 00 92 0c d5 d0 40 08 1d+10:01:44.429 READ FPDMA QUEUED 60 00 38 00 90 00 00 92 0c d5 98 40 08 1d+10:01:44.429 READ FPDMA QUEUED Error 3 [2] occurred at disk power-on lifetime: 23486 hours (978 days + 14 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 01 70 00 00 92 0c b8 10 40 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 28 00 b8 00 00 92 0c c2 58 40 08 1d+10:01:06.417 READ FPDMA QUEUED 60 00 60 00 b0 00 00 92 0c c1 f8 40 08 1d+10:01:06.417 READ FPDMA QUEUED 60 00 50 00 10 00 00 92 0c c1 a8 40 08 1d+10:01:06.416 READ FPDMA QUEUED 60 00 50 00 78 00 00 92 0c c1 58 40 08 1d+10:01:06.416 READ FPDMA QUEUED 60 00 80 00 70 00 00 92 0c c0 d8 40 08 1d+10:01:06.416 READ FPDMA QUEUED Error 2 [1] occurred at disk power-on lifetime: 23445 hours (976 days + 21 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 01 00 00 00 92 0c b8 10 40 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 01 00 00 08 00 00 92 0c b7 50 40 08 22:10:44.250 READ FPDMA QUEUED 60 01 00 00 00 00 00 92 0c b8 50 40 08 22:10:44.250 READ FPDMA QUEUED ef 00 10 00 02 00 00 00 00 00 00 a0 08 22:10:44.250 SET FEATURES [Reserved for Serial ATA] 27 00 00 00 00 00 00 00 00 00 00 e0 08 22:10:44.250 READ NATIVE MAX ADDRESS EXT ec 00 00 00 00 00 00 00 00 00 00 a0 08 22:10:44.244 IDENTIFY DEVICE Error 1 [0] occurred at disk power-on lifetime: 23445 hours (976 days + 21 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 01 00 00 00 92 0c b8 10 40 00 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 01 00 00 00 00 00 92 0c b7 50 40 08 22:10:41.400 READ FPDMA QUEUED 60 01 00 00 08 00 00 92 0c b6 50 40 08 22:10:41.399 READ FPDMA QUEUED 60 01 00 00 00 00 00 92 0c b5 50 40 08 22:10:41.397 READ FPDMA QUEUED 60 01 00 00 08 00 00 92 0c b4 50 40 08 22:10:41.393 READ FPDMA QUEUED 60 01 00 00 00 00 00 92 0c b3 50 40 08 22:10:41.393 READ FPDMA QUEUED

well it finished... ================================================================== 1.13 = unRAID server Pre-Clear disk /dev/sdg = cycle 1 of 1, partition start on sector 64 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Disk Post-Clear-Read completed DONE Elapsed Time: 22:55:02 ========================================================================1.13 == WDC WD20EARS-00S8B1 WD-WCAVY4386698 == Disk /dev/sdg has been successfully precleared == with a starting sector of 64 ============================================================================ ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ** Changed attributes in files: /tmp/smart_start_sdg /tmp/smart_finish_sdg ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 200 ok Spin_Up_Time = 157 ok Start_Stop_Count = 100 ok Reallocated_Sector_Ct = 200 ok Seek_Error_Rate = 200 ok Power_On_Hours = 68 ok Spin_Retry_Count = 100 ok Calibration_Retry_Count = 100 ok Power_Cycle_Count = 100 ok Power-Off_Retract_Count = 200 ok Load_Cycle_Count = 189 ok Temperature_Celsius = 118 ok Reallocated_Event_Count = 200 ok Current_Pending_Sector = 200 ok Offline_Uncorrectable = 200 ok UDMA_CRC_Error_Count = 200 ok Multi_Zone_Error_Rate = 200 ok No SMART attributes are FAILING_NOW 1 sector was pending re-allocation before the start of the preclear. 1 sector was pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. a change of -1 in the number of sectors pending re-allocation. 0 sectors had been re-allocated before the start of the preclear. a change of 0 in the number of sectors re-allocated. SMART overall-health status = so i guess it worked? not sure why preclear is having problems now with this disk.. ./preclear_disk.sh -t /dev/sdg Pre-Clear unRAID Disk /dev/sdg ################################################################## 1.13 Model Family: Western Digital Caviar Green (Adv. Format) family Device Model: WDC WD20EARS-00S8B1 Serial Number: WD-WCAVY4386698 Firmware Version: 80.00A80 User Capacity: 2,000,398,934,016 bytes Disk /dev/sdg: 2000.4 GB, 2000398934016 bytes 255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdg1 64 3907029167 1953514552 0 Empty Partition 1 does not end on cylinder boundary. ######################################################################## ========================================================================1.13 == == DISK /dev/sdg IS PRECLEARED with a starting sector of 64 == ============================================================================

pulled drive from drive cage and re-inserted. /boot# smartctl -a -A -Tpermissive /dev/sdg smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green (Adv. Format) family Device Model: WDC WD20EARS-00S8B1 Serial Number: WD-WCAVY4386698 Firmware Version: 80.00A80 User Capacity: 2,000,398,934,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Thu Apr 4 18:44:29 2013 CDT SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (40800) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3031) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 23 3 Spin_Up_Time 0x0027 157 143 021 Pre-fail Always - 9108 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 83 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 068 068 000 Old_age Always - 23586 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 71 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 32 193 Load_Cycle_Count 0x0032 189 189 000 Old_age Always - 35228 194 Temperature_Celsius 0x0022 118 110 000 Old_age Always - 34 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 1 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 1 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 2 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay ran short test, it passed. started preclear again for the disk. on step 2 89% done.

WD20EARS-00S8B1 -- remove drive from array (it had no data on it anyways), started preclear script with -A on it again. Once this is done I'll report back. woke up to find that pre-clear script ran and died in the middle... but at least it shows that sector was reallocated? ================================================================== 1.13 = unRAID server Pre-Clear disk /dev/sdg = cycle 1 of 1, partition start on sector 64 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it = **** This will take a while... you can follow progress below: = = = = = = = = Elapsed Time: 4:31:34 0+0 records in 0+0 records out 0 bytes (0 B) copied, 0.000232038 s, 0.0 kB/s ./preclear_disk.sh: line 642: let: percent_wrote=(0 / ): syntax error: operand expected (error token is ")") Wrote 0 bytes out of bytes (% Done) ./preclear_disk.sh: line 1849: / (1365100859 - 1365100832) / 1000000 : syntax error: operand expected (error token is "/ (1365100859 - 1365100832) / 1000000 ") ========================================================================1.13 == WDC WD20EARS-00S8B1 WD-WCAVY4386698 == Disk /dev/sdg has been successfully precleared == with a starting sector of 64 ============================================================================ ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ./preclear_disk.sh: line 817: [: : integer expression expected ** Changed attributes in files: /tmp/smart_start_sdg /tmp/smart_finish_sdg ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 200 ok Spin_Up_Time = 155 ok Start_Stop_Count = 100 ok Reallocated_Sector_Ct = 200 ok Seek_Error_Rate = 200 ok Power_On_Hours = 68 ok Spin_Retry_Count = 100 ok Calibration_Retry_Count = 100 ok Power_Cycle_Count = 100 ok Power-Off_Retract_Count = 200 ok Load_Cycle_Count = 189 ok Temperature_Celsius = 123 ok Reallocated_Event_Count = 200 ok Current_Pending_Sector = 200 ok Offline_Uncorrectable = 200 ok UDMA_CRC_Error_Count = 200 ok Multi_Zone_Error_Rate = 200 ok No SMART attributes are FAILING_NOW 1 sector was pending re-allocation before the start of the preclear. a change of -1 in the number of sectors pending re-allocation. 0 sectors had been re-allocated before the start of the preclear. a change of 0 in the number of sectors re-allocated. SMART overall-health status = looking at: