jbuszkie

Aww crud.. I start a parity check because I just upgraded to V6.1 and I was testing speeds and I had a couple drives with a current sector pending. one went away.. but another disk got a bunch of read errors! Will this disk now be red balled? The parity check didn't get any errors. but I got 113 read errors. Sep 24 03:05:01 Tower kernel: sd 7:0:0:0: [sdf] tag#3 CDB: opcode=0x28 28 00 a5 a6 78 5f 00 05 40 00 (Drive related) Sep 24 03:05:01 Tower kernel: blk_update_request: I/O error, dev sdf, sector 2779150872 (Errors) Sep 24 03:05:01 Tower kernel: ata7: EH complete (Drive related) Sep 24 03:05:01 Tower kernel: md: disk6 read error, sector=2779150808 (Errors) Sep 24 03:05:01 Tower kernel: md: disk6 read error, sector=2779150816 (Errors) Sep 24 03:05:01 Tower kernel: md: disk6 read error, sector=2779150824 (Errors) Sep 24 03:05:01 Tower kernel: md: disk6 read error, sector=2779150832 (Errors) Sep 24 03:05:01 Tower kernel: md: disk6 read error, sector=2779150840 (Errors) Sep 24 03:05:01 Tower kernel: md: disk6 read error, sector=2779150848 (Errors) Sep 24 03:05:01 Tower kernel: md: disk6 read error, sector=2779150856 (Errors) Sep 24 03:05:01 Tower kernel: md: disk6 read error, sector=2779150864 (Errors) Sep 24 03:05:01 Tower kernel: md: disk6 read error, sector=2779150872 (Errors) Sep 24 03:05:01 Tower kernel: md: disk6 read error, sector=2779150880 (Errors) Sep 24 03:05:01 Tower kernel: md: disk6 read error, sector=2779150888 (Errors) Sep 24 03:05:01 Tower kernel: md: disk6 read error, sector=2779150896 (Errors) . . . What should I do? Since the parity check didn't give any errors?? The disk is 5 years old.. but I have a couple that are 6 that are next in line to be replaced.. Jim

Thanks! That explains it!

Updates the drives database for smartctl ok.. When would one need to press this button?

What does "Update Smartmontools Database" do? Also.. very cool plugin! Thanks! Jim

That's what I figured... I assume there's enough ammunition to merit a RMA? Sigh! looks like my other drive will have to be a parity drive for a couple weeks! grr... Thanks for the input. Jim

There were more errors like that.. Here are the results of the preclear.. ========================================================================1.15 == ST4000VN000-1H4168 Z3013V86 == Disk /dev/sda has been successfully precleared == with a starting sector of 1 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sda /tmp/smart_finish_sda ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 117 112 6 ok 161315704 Spin_Retry_Count = 100 100 97 near_thresh 0 Unknown_Attribute = 100 100 99 near_thresh 0 Reported_Uncorrect = 18 69 0 near_thresh 82 High_Fly_Writes = 1 1 0 near_thresh 129 Airflow_Temperature_Cel = 74 78 45 ok 26 Temperature_Celsius = 26 22 0 ok 26 No SMART attributes are FAILING_NOW 64 sectors were pending re-allocation before the start of the preclear. 56 sectors were pending re-allocation after pre-read in cycle 1 of 1. 48 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 32 sectors are pending re-allocation at the end of the preclear, a change of -32 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. 1/2 cleared themselves out. Attached is the full preclear report with the smart results. I wish it was cut and dry.. none of the pending got reallocated. Should I try to RMA the drive anyway? should I run another preclear? Preclear_SDA_results.txt

I'm getting errors on the old parity drive... Apr 30 09:06:12 Tower kernel: ata1.00: error: { UNC } (Errors) Apr 30 09:06:12 Tower kernel: ata1.00: configured for UDMA/133 (Drive related) Apr 30 09:06:12 Tower kernel: sd 1:0:0:0: [sda] Unhandled sense code (Drive related) Apr 30 09:06:12 Tower kernel: sd 1:0:0:0: [sda] (Drive related) Apr 30 09:06:12 Tower kernel: sd 1:0:0:0: [sda] (Drive related) Apr 30 09:06:12 Tower kernel: sd 1:0:0:0: [sda] (Drive related) Apr 30 09:06:12 Tower kernel: sd 1:0:0:0: [sda] CDB: (Drive related) Apr 30 09:06:12 Tower kernel: end_request: I/O error, dev sda, sector 2551149104 (Errors) Apr 30 09:06:12 Tower kernel: Buffer I/O error on device sda, logical block 318893638 (Errors) Apr 30 09:06:12 Tower kernel: ata1: EH complete (Drive related) Apr 30 09:23:08 Tower kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors) Apr 30 09:23:08 Tower kernel: ata1.00: irq_stat 0x40000001 (Drive related) Apr 30 09:23:08 Tower kernel: ata1.00: failed command: READ DMA EXT (Minor Issues) Apr 30 09:23:08 Tower kernel: ata1.00: cmd 25/00:00:00:b8:1d/00:01:9f:00:00/e0 tag 0 dma 131072 in (Drive related) Apr 30 09:23:08 Tower kernel: ata1.00: status: { DRDY ERR } (Drive related) Apr 30 09:23:08 Tower kernel: ata1.00: error: { UNC } (Errors) Apr 30 09:23:08 Tower kernel: ata1.00: configured for UDMA/133 (Drive related) Apr 30 09:23:08 Tower kernel: sd 1:0:0:0: [sda] Unhandled sense code (Drive related) Apr 30 09:23:08 Tower kernel: sd 1:0:0:0: [sda] (Drive related) Apr 30 09:23:08 Tower kernel: sd 1:0:0:0: [sda] (Drive related) Apr 30 09:23:08 Tower kernel: sd 1:0:0:0: [sda] (Drive related) Apr 30 09:23:08 Tower kernel: sd 1:0:0:0: [sda] CDB: (Drive related) Apr 30 09:23:08 Tower kernel: end_request: I/O error, dev sda, sector 2669525192 (Errors) Apr 30 09:23:08 Tower kernel: Buffer I/O error on device sda, logical block 333690649 (Errors) Apr 30 09:23:08 Tower kernel: Buffer I/O error on device sda, logical block 333690650 (Errors) Apr 30 09:23:08 Tower kernel: Buffer I/O error on device sda, logical block 333690651 (Errors) Apr 30 09:23:08 Tower kernel: Buffer I/O error on device sda, logical block 333690652 (Errors) Apr 30 09:23:08 Tower kernel: Buffer I/O error on device sda, logical block 333690653 (Errors) Apr 30 09:23:08 Tower kernel: Buffer I/O error on device sda, logical block 333690654 (Errors) Apr 30 09:23:08 Tower kernel: Buffer I/O error on device sda, logical block 333690655 (Errors) Apr 30 09:23:08 Tower kernel: ata1: EH complete (Drive related) It's in the post read part of the preclear.. Maybe by this evening it will be done. but probably tomorrow morning.

I killed the parity check before it finished. I'm about to preclear the drive and will report back it's status.. Jim

Yeah.. makes sense.. But I'll probably wait till the rebuild finished before I start the preclear on the old parity drive.

Yeah.. That's what I figured. Doing a parity check now. That will be done tomorrow. Then another 26ish hours for the rebuild. Then another 36ish hours for the pre-clear... Yeah.. It's gonna be a while! Thanks for the opinion! Jim

So how many of you would risk running without parity for a couple days while I re-preclear the parity drive to check for more errors? I have 3 options.. 1. Do nothing and see if it clears itself out. 2. Take the parity out and run preclear on it. and run unprotected for like 36h (plus rebuild time if the disk checks out) 3. Take my new (green) 4T disk and let it rebuild parity on that. when that's done then run preclear on the old parity. If all good swap parity out again with the old disk or replace with the returned drive when it eventually arrives. This means my new drive (slated for something else) will have to not go into its new home for a week or so.. What would you guys do?

I thought about doing this. Coincidentally, I'm almost done preclearing another drive for a different use. maybe I'll just temporarily switch it out with the new drive and run another preclear.. hmm.. Will Seagate replace a drive with 64 bad sectors?

For giggles.. I decided to take a look at my smart report from unraid. This is what I got » reported_uncorrect=31 » high_fly_writes=112 » current_pending_sector=64 » offline_uncorrectable=64 » ata_error_count=31 This is on my parity drive. I have no idea when these occurred. My last parity check was 25 days ago with no sync errors. What should I do? It just under a year old. Thanks, Jim

Don't get me wrong.. The time it takes sucks! But I will never put a new disk in a system WITHOUT pre-clearing it first! That goes for windows disks too!! Again, Thanks Joe! Jim

That's what I figured. It was more of a "it won't save me any time" type of question. Like if I had a known good drive already that I had already used.. it doesn't save me anytime to pre-clear it! 9 hours to do the pre read on my 4TB disk! (122MB/s calculated) This is gonna take a while! :-) Jim

Dumb question.... Do I need to pre-clear a new drive if it's going into the parity slot? I think the answer is no... but... I will pre-clear anyway to test the drive... but is it necessary? isn't the drive completely written anyway when it generates the new parity? Jim

HPA??

The last 4TB drive I ran it on took 36:41:32 41:34:51 !! :-) But no errors, at least!

How long have some of your 4T drives taken? It's trending that mine will be well over 24hrs.. Possibly closer to 48! Almost 10 hours for the pre-read! :-)

not that I'll ever need to... but can that run kemit or x-modem???

No.. Never did.. Gave up.. I don't even remember why I wanted it.. Maybe someone else can help with a terminal emulation package?

SeaSonic X Series X650 Gold ((SS-650KM Active PFC F3)) 650W ATX12V V2.3/EPS 12V V2.91 SLI Ready CrossFire Ready 80 PLUS GOLD Certified Full Modular Active PFC Power Supply $89.99 With Promo Code: EMCYTZT2318 Damn! Damn! Damn! Damn! I just bought the X750 last week for ~$125 Oh well.. I'm not ripping it out to save ~$35!

Any updates to this list?? I need to get one today and I'm looking if there are any new ones or removed ones... Thanks, Jim

Joe, I put it back in the xbox and it seems to still have issues. If a disk has an issue writing a '1' will preclear find it? I'm wondering if this is my issue. should I change the script to have it write '1's instead? Maybe to make a more bullet proof test, you write '1's first and post read and then write '0's then post read again? Sure it will make the test longer.. but if it will catch more errors.... What do you think? Jim

Joe, This is in an XBOX! :-) I wish I could get a syslog!