GreggP Posted October 4, 2010 Share Posted October 4, 2010 Joe, thanks again for your help. I've run pre-clear on the "sdg" drive again. This is the one that had 4 reallocated sectors (0 pending). I've copied the contents of the screen to my clipboard: =========================================================================== = unRAID server Pre-Clear disk /dev/sdg = cycle 1 of 1 = 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 - Testing if the clear has been successful. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 29C, Elapsed Time: 24:37:24 ============================================================================ == == Disk /dev/sdg has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 19,20c19,20 < Offline data collection status: (0x80) Offline data collection activity < was never started. --- > Offline data collection status: (0x84) Offline data collection activity > was suspended by an interrupting command from host. ============================================================================ root@Media:/boot# Not sure what it means by "error count difference detected after pre-clear" and the offline data collection activity - "was never started" and "was suspended by an interrupting command." Is the script trying to do something it can't execute? With my other new drive (the one with no reallocated sectors), I don't think there were any text strings following the line that showed the drive was successfully pre-cleared. Anyhow, I ran another smart report and it shows nothing has changed. The reallocated sector count is the same. So hopefully this drive (sdg) is good to go. SMART_report_for_sdg_drive_after_2nd_pre-clear.txt Quote Link to comment
Joe L. Posted October 4, 2010 Share Posted October 4, 2010 Offline data collection activity is another name for self tests done by the drive when it thinks it is idle. Apparently it tried to run one but it was interrupted by the pre-clearing accesses. Your drive looks fine. Quote Link to comment
madpoet Posted October 7, 2010 Share Posted October 7, 2010 Reran preclear on my 5 drives. 3 finished in 34 hours with no errors. 2 took 40+ hours and had the following: Oct 7 00:28:53 Tower preclear_disk-diff[26133]: ============================================================================ Oct 7 00:28:53 Tower preclear_disk-diff[26133]: S.M.A.R.T. error count differences detected after pre-clear Oct 7 00:28:53 Tower preclear_disk-diff[26133]: note, some 'raw' values may change, but not be an indication of a problem Oct 7 00:28:53 Tower preclear_disk-diff[26133]: 55c55 Oct 7 00:28:53 Tower preclear_disk-diff[26133]: < 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 5 Oct 7 00:28:53 Tower preclear_disk-diff[26133]: --- Oct 7 00:28:53 Tower preclear_disk-diff[26133]: > 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 9 Oct 7 00:28:53 Tower preclear_disk-diff[26133]: ============================================================================ Oct 7 00:28:53 Tower preclear_disk-diff[26133]: Oct 7 00:26:35 Tower preclear_disk-diff[26001]: ============================================================================ Oct 7 00:26:35 Tower preclear_disk-diff[26001]: S.M.A.R.T. error count differences detected after pre-clear Oct 7 00:26:35 Tower preclear_disk-diff[26001]: note, some 'raw' values may change, but not be an indication of a problem Oct 7 00:26:35 Tower preclear_disk-diff[26001]: 55c55 Oct 7 00:26:35 Tower preclear_disk-diff[26001]: < 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 3 Oct 7 00:26:35 Tower preclear_disk-diff[26001]: --- Oct 7 00:26:35 Tower preclear_disk-diff[26001]: > 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 7 Oct 7 00:26:35 Tower preclear_disk-diff[26001]: ============================================================================ Do I need to be worried about those 2? Quote Link to comment
Joe L. Posted October 7, 2010 Share Posted October 7, 2010 Reran preclear on my 5 drives. 3 finished in 34 hours with no errors. 2 took 40+ hours and had the following: Oct 7 00:28:53 Tower preclear_disk-diff[26133]: ============================================================================ Oct 7 00:28:53 Tower preclear_disk-diff[26133]: S.M.A.R.T. error count differences detected after pre-clear Oct 7 00:28:53 Tower preclear_disk-diff[26133]: note, some 'raw' values may change, but not be an indication of a problem Oct 7 00:28:53 Tower preclear_disk-diff[26133]: 55c55 Oct 7 00:28:53 Tower preclear_disk-diff[26133]: < 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 5 Oct 7 00:28:53 Tower preclear_disk-diff[26133]: --- Oct 7 00:28:53 Tower preclear_disk-diff[26133]: > 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 9 Oct 7 00:28:53 Tower preclear_disk-diff[26133]: ============================================================================ Oct 7 00:28:53 Tower preclear_disk-diff[26133]: Oct 7 00:26:35 Tower preclear_disk-diff[26001]: ============================================================================ Oct 7 00:26:35 Tower preclear_disk-diff[26001]: S.M.A.R.T. error count differences detected after pre-clear Oct 7 00:26:35 Tower preclear_disk-diff[26001]: note, some 'raw' values may change, but not be an indication of a problem Oct 7 00:26:35 Tower preclear_disk-diff[26001]: 55c55 Oct 7 00:26:35 Tower preclear_disk-diff[26001]: < 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 3 Oct 7 00:26:35 Tower preclear_disk-diff[26001]: --- Oct 7 00:26:35 Tower preclear_disk-diff[26001]: > 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 7 Oct 7 00:26:35 Tower preclear_disk-diff[26001]: ============================================================================ Do I need to be worried about those 2? No worry. The "normalized" current value is 100, and did not change, and is still the initial value given by the manufacturer, and is nowhere near the failure threshold of 51. All drives have internal raw read errors, some report them, some do not, and only the manufacturer knows how to interpret the "raw" values. Enjoy your new drives. Quote Link to comment
Joe L. Posted October 9, 2010 Share Posted October 9, 2010 Figured I'd post one of my own preclear results... This is a 1.5TB Seagate ST31500341AS. = unRAID server Pre-Clear disk /dev/sda = cycle 1 of 1 = 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 - Testing if the clear has been successful. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 30C, Elapsed Time: 22:56:52 -Average speed was 84 MB/s. ============================================================================ == == Disk /dev/sda has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 54c54 < 1 Raw_Read_Error_Rate 0x000f 100 100 006 Pre-fail Always - 6694 --- > 1 Raw_Read_Error_Rate 0x000f 118 100 006 Pre-fail Always - 195233335 <-- normalized value improved during preclear 58c58 < 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 471 --- > 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 91031 <- just raw value changes... ignore these 63,66c63,66 < 188 Unknown_Attribute 0x0032 100 253 000 Old_age Always - 0 < 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 < 190 Airflow_Temperature_Cel 0x0022 073 070 045 Old_age Always - 27 (Lifetime Min/Max 25/27) < 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always --- > 188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 > 189 High_Fly_Writes 0x003a 086 086 000 Old_age Always - 14 <- there were some high-fly-writes detected, but normalized value nowhere near threshold. > 190 Airflow_Temperature_Cel 0x0022 070 064 045 Old_age Always - 30 (Lifetime Min/Max 25/36) <-- temp got up to 36 during writes, ended at 30C. > 195 Hardware_ECC_Recovered 0x001a 059 048 000 Old_age Always 69,72c69,72 < 199 UDMA_CRC_Error_Count 0x003e 200 253 000 Old_age Always - 0 < 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 151629525417984 < 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 0 < 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 5746 --- > 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 <- factory 253 value changes to starting 200 value. > 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 231743550390295 <-- yes, head was flying... no idea of how to interpret raw value... sure is not seconds, or even microseconds. > 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 2931361246 > 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 455163613 ============================================================================ root@Tower2:/boot# Since I have no need to add this immediately to the array, I'll do one or two more preclear cycles on it while it is un-assigned. Joe L. Quote Link to comment
mifronte Posted October 10, 2010 Share Posted October 10, 2010 Attached is my first two ever PreClear outputs of a Seagate ST31000520AS Barracuda LP 1TB (Preclear sdj.txt) and WD 10EADS Caviar Green 1TB (PreClear sdk.txt). I think everything looks OK, please review to see if I am interpreting the files correctly. There is one SMART Unknown_Attribute (Vendor ID # 184) with a Failing_Now in PreClear sdj.txt! Should I be concerned? The PreClear sdk.txt has a message of "Not in smartctl database". Should I be concern? The /tmp/read_speedsdj file says 57.8 MB/s and /tmp/read_speedsdk says 41.0 MB/s. Is this the average read throughput? How can I get it to be higher? The second reading is really low and this is on the Syba SD-PCXSA2-2E2R Sil3124 base PCI-X 64-bit 133MHz SATA controller. PreClear_sdj.txt PreClear_sdk.txt Quote Link to comment
Joe L. Posted October 11, 2010 Share Posted October 11, 2010 Attached is my first two ever PreClear outputs of a Seagate ST31000520AS Barracuda LP 1TB (Preclear sdj.txt) and WD 10EADS Caviar Green 1TB (PreClear sdk.txt). I think everything looks OK, please review to see if I am interpreting the files correctly. There is one SMART Unknown_Attribute (Vendor ID # 184) with a Failing_Now in PreClear sdj.txt! Should I be concerned? Yes you should be concerned. We have no idea what that parameter is, but if it is failing you do not want that drive in your server. RMA it. The PreClear sdk.txt has a message of "Not in smartctl database". Should I be concern?That is not an issue, most newer drives are not in its database. The /tmp/read_speedsdj file says 57.8 MB/s and /tmp/read_speedsdk says 41.0 MB/s. Is this the average read throughput? How can I get it to be higher? The second reading is really low and this is on the Syba SD-PCXSA2-2E2R Sil3124 base PCI-X 64-bit 133MHz SATA controller. Those are the speeds reported by the last of the "dd" commands. That speed is affected by anything else going on at the same time on the server. Joe L. Quote Link to comment
Rajahal Posted October 14, 2010 Share Posted October 14, 2010 Definitely looks like this one failed. I'm preclearing a brand new 2 TB WD EARS (w/ jumper) for a client. The preclear appeared to have gotten through all 10 steps, but it finished in just 10.5 hours, which I know is far too short. The message reported is 'SORRY: Disk /dev/sda MBR could NOT be precleared'. Screenshot of the output screen: Syslog attached. Bad drive? Or something else? Syslog_10-13-10_failed_preclear_2_TB_WD_EARS_w_jumper.txt Quote Link to comment
Joe L. Posted October 14, 2010 Share Posted October 14, 2010 Can't really tell. First I'd try a power cycle. Then you can zero the "MBR" and the sector following it by typing dd if=/dev/zero of=/dev/sda bs=512 count=2 (Just in case the data that was in the second sector is confusing the fdisk program since you added the jumper) Next, try a preclear again. See if it responds at all. Joe L. Quote Link to comment
Rajahal Posted October 15, 2010 Share Posted October 15, 2010 Alright, did all of that. Starting a new preclear now. I'm also preclearing a second identical drive (2 TB WD EARS w/ jumper) in the same machine, side by side. I started both within one minute of each other. After about 4.5 hours, the original troublesome drive (sda) is only 25% complete with the pre-read, whereas the second drive (sdb) is already at 63% in the pre-read. I'm definitely starting to think that sda has some problems. However, I'll let both preclears finish and see what SMART says about them. Maybe it just has some bad sectors that need to be reallocated, and once that is taken care of it will be fine. Edit: Also, sda is running a bit hotter than sdb. sda is at 31C and sdb is at 28C. Both temperatures are perfectly acceptable, of course, but I would expect them to be closer together since they are identical drives in identical drive cages (each with identical dedicated cooling). Quote Link to comment
Rajahal Posted October 15, 2010 Share Posted October 15, 2010 Well damn. sda failed preclear again, with the exact same error as pictured above. Time was 10:46 this time. I'll try it in some other drive slots, just to make sure there isn't something wrong with my hardware. Past that, it looks like I'll be RMAing it, unless you have any other things for me to try. Quote Link to comment
Joe L. Posted October 15, 2010 Share Posted October 15, 2010 Well damn. sda failed preclear again, with the exact same error as pictured above. Time was 10:46 this time. I'll try it in some other drive slots, just to make sure there isn't something wrong with my hardware. Past that, it looks like I'll be RMAing it, unless you have any other things for me to try. One more thing to try. It will not fix it, but it will let us see what did happen. The two values printed should be the MS-DOS expected signature at bytes 510 and 511 of the MBR. They should not be zero as you are seeing in the output. Please post the output of dd if=/dev/sda bs=512 count=2 | od -x -A d It should look a lot like this (the actual numbers in the lines will vary based on the size of the disk, but the "aa55" should be there on that line starting with address 0000496): root@Tower:/boot# dd if=/dev/sda bs=512 count=2 | od -x -A d 0000000 0000 0000 0000 0000 0000 0000 0000 0000 * 0000448 0000 0000 0000 003f 0000 6341 1d38 0000 0000464 0000 0000 0000 0000 0000 0000 0000 0000 * 0000496 0000 0000 0000 0000 0000 0000 0000 aa55 0000512 0000 0000 0000 0000 0000 0000 0000 0000 * 0001024 2+0 records in 2+0 records out 1024 bytes (1.0 kB) copied, 0.0174509 s, 58.7 kB/s Edited to ask for a count=2 instead of count=1 Joe L. Quote Link to comment
Joe L. Posted October 15, 2010 Share Posted October 15, 2010 I'd also be interested in seeing what fdisk -l /dev/sda and blockdev --getsz /dev/sda and sfdisk -g /dev/sda show for the disk. Joe L. Quote Link to comment
Rajahal Posted October 15, 2010 Share Posted October 15, 2010 Thanks Joe. I'll try all these when I get home tonight. Quote Link to comment
Rajahal Posted October 16, 2010 Share Posted October 16, 2010 The two values printed should be the MS-DOS expected signature at bytes 510 and 511 of the MBR. They should not be zero as you are seeing in the output. Output is: 0+0 records in 0+0 records out 0 bytes (0 B) copied, 1.6837e-05 s, 0.0 kB/s 0000000 fdisk -l /dev/sda No output blockdev --getsz /dev/sda Outputs: 0 sfdisk -g /dev/sda No output Attempting to access or save the syslog seems to be locking up the server now. Edit: I was able to get the syslog off the flash drive (I had entered the command to save it to the flash drive from the system console before it started locking up). The syslog is huge, 384 mb! It is currently stalling notepad as it tries to open it. I'm going to let it go and see what happens. Obviously it will be far to large to post here... Quote Link to comment
Flomaster Posted October 16, 2010 Share Posted October 16, 2010 im guessing everything looks to be in order here, == Disk /dev/sdb has been successfully precleared Oct 15 23:59:41 Tower preclear_disk-diff[12185]: == Oct 15 23:59:41 Tower preclear_disk-diff[12185]: == Ran 1 preclear-disk cycle Oct 15 23:59:41 Tower preclear_disk-diff[12185]: == Oct 15 23:59:41 Tower preclear_disk-diff[12185]: == Using :Read block size = 8225280 Bytes Oct 15 23:59:41 Tower preclear_disk-diff[12185]: == Last Cycle's Pre Read Time : 3:35:05 (77 MB/s) Oct 15 23:59:41 Tower preclear_disk-diff[12185]: == Last Cycle's Zeroing time : 3:22:39 (82 MB/s) Oct 15 23:59:41 Tower preclear_disk-diff[12185]: == Last Cycle's Post Read Time : 6:55:51 (40 MB/s) Oct 15 23:59:41 Tower preclear_disk-diff[12185]: == Last Cycle's Total Time : 13:54:43 Oct 15 23:59:41 Tower preclear_disk-diff[12185]: == Oct 15 23:59:41 Tower preclear_disk-diff[12185]: == Total Elapsed Time 13:54:43 Oct 15 23:59:41 Tower preclear_disk-diff[12185]: == Oct 15 23:59:41 Tower preclear_disk-diff[12185]: == Disk Start Temperature: 26C Oct 15 23:59:41 Tower preclear_disk-diff[12185]: == Oct 15 23:59:41 Tower preclear_disk-diff[12185]: == Current Disk Temperature: 25C, Oct 15 23:59:41 Tower preclear_disk-diff[12185]: == Oct 15 23:59:41 Tower preclear_disk-diff[12185]: ============================================================================ Oct 15 23:59:41 Tower preclear_disk-diff[12185]: S.M.A.R.T. error count differences detected after pre-clear Oct 15 23:59:41 Tower preclear_disk-diff[12185]: note, some 'raw' values may change, but not be an indication of a problem Oct 15 23:59:41 Tower preclear_disk-diff[12185]: 63c63 Oct 15 23:59:41 Tower preclear_disk-diff[12185]: < 193 Load_Cycle_Count 0x0032 192 192 000 Old_age Always - 26144 Oct 15 23:59:41 Tower preclear_disk-diff[12185]: --- Oct 15 23:59:41 Tower preclear_disk-diff[12185]: > 193 Load_Cycle_Count 0x0032 192 192 000 Old_age Always - 26145 Oct 15 23:59:41 Tower preclear_disk-diff[12185]: ============================================================================ Oct 15 23:59:41 Tower preclear_disk-diff[12185]: im just going to go ahead and assing this as disk2 and build my parity now Quote Link to comment
CupCak3 Posted October 16, 2010 Share Posted October 16, 2010 I've ran 4 preclears on my new Samsung 2TB F3 HD203WI. No problems except for the following errors: Oct 8 12:28:03 Tower preclear_disk-start[4799]: 1 Raw_Read_Error_Rate 0x002f 252 252 051 Pre-fail Always - 0 Oct 10 07:21:47 Tower preclear_disk-start[5998]: 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 38 Oct 12 00:20:50 Tower preclear_disk-start[30688]: 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 64 Oct 13 08:42:33 Tower preclear_disk-finish[4552]: 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 94 Oct 15 05:30:19 Tower preclear_disk-finish[14054]: 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 121 Oct 8 12:28:03 Tower preclear_disk-start[4799]: 200 Multi_Zone_Error_Rate 0x002a 252 252 000 Old_age Always - 0 Oct 10 07:21:47 Tower preclear_disk-start[5998]: 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 3 Oct 12 00:20:50 Tower preclear_disk-start[30688]: 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 4 Oct 13 08:42:33 Tower preclear_disk-finish[4552]: 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 4 Oct 15 05:30:19 Tower preclear_disk-finish[14054]: 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 5 Is it OK for me to use this drive? I'm very much concerned with the always rising Raw_Read_Error_Rate numbers. Thanks! Quote Link to comment
Juano11 Posted October 16, 2010 Share Posted October 16, 2010 Adding a new drive, preclear completed. Anything to worry about below? Is there more that I should have copied? Thanks. ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 58c58 < 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 --- > 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 63c63 < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 20 --- > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 21 ============================================================================ Quote Link to comment
mkny13 Posted October 16, 2010 Share Posted October 16, 2010 I got identical results to the last poster (Seek_error_rate) on 1 of 2 new WD20EARS I just precleared. Anything to worry about? Quote Link to comment
Joe L. Posted October 16, 2010 Share Posted October 16, 2010 I got identical results to the last poster (Seek_error_rate) on 1 of 2 new WD20EARS I just precleared. Anything to worry about? No... and you should read the first post in this thread to learn how to interpert the results of a smart report. The issue is this. The pre-clear script ONLY shows the differences between the beginning SMART report and the post clear SMART report. If the beginning one was failing and the end one is failing too, then no output pertaining to it would print. The lines you showed are just factory initialized values (253) being set to a median starting value (100) once the drive starts getting some use. Load cycle incrementing is a good thing. If it did not increment at least once, your disk heads would not have loaded onto the platters and your disk would be non-functional. Quote Link to comment
mkny13 Posted October 16, 2010 Share Posted October 16, 2010 Thanks, and I apologize for not reading the first post. I should have started there before I searched. Quote Link to comment
mcdonagg Posted October 16, 2010 Share Posted October 16, 2010 I am in the process of preclearing 5 disks, 3 2tb WD Greens, 1 2tb WD Black, and one 1tb old WD. 4 of them have fished but one of the Greens is still running the first read. Here are the results from the clears. == Disk /dev/sdb has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 63c63 < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 2767 --- > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 2768 ============================================================================ ============================================================================ == == Disk /dev/sdd has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 54c54 < 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 1 --- > 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 2 63c63 < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 989 --- > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 990 ============================================================================ ============================================================================ == == Disk /dev/sde has been successfully precleared == ============================================================================ ============================================================================ == == Disk /dev/hdb has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 63c63 < 193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 5703 --- > 193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 5705 ============================================================================ and the one that is still running, =========================================================================== = unRAID server Pre-Clear disk /dev/sdc = cycle 1 of 1 = Disk Pre-Read in progress: 75% complete = ( 1,513,606,348,800 bytes of 2,000,398,934,016 read ) 11.2 MB/s = = = = = = = = = = Disk Temperature: 33C, Elapsed Time: 39:22:36 should I be worried about that? Quote Link to comment
hunter69 Posted October 16, 2010 Share Posted October 16, 2010 Sorry about the double post, I just bumped into this post. I just got done with 3 brand new wdears 2tb disks. Here are the results Here is one disk sdc ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 63c63 < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 25 --- > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 26 ============================================================================ another sda ============================================================================ == == Disk /dev/sda has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 54c54 < 1 Raw_Read_Error_Rate 0x002f 100 253 051 Pre-fail Always - 0 --- > 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 63c63 < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 24 --- > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 25 ============================================================================ another sdd == Disk /dev/sdd has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 54c54 < 1 Raw_Read_Error_Rate 0x002f 100 253 051 Pre-fail Always - 0 --- > 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 63c63 < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 16 --- > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 17 67c67 < 199 UDMA_CRC_Error_Count 0x0032 200 253 000 Old_age Always - 0 --- > 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 ============================================================================ Thanks Quote Link to comment
wsume99 Posted October 17, 2010 Share Posted October 17, 2010 and the one that is still running, =========================================================================== = unRAID server Pre-Clear disk /dev/sdc = cycle 1 of 1 = Disk Pre-Read in progress: 75% complete = ( 1,513,606,348,800 bytes of 2,000,398,934,016 read ) 11.2 MB/s = = = = = = = = = = Disk Temperature: 33C, Elapsed Time: 39:22:36 should I be worried about that? I've never had a WD Green drive with that slow of a read rate. I don't think that running 4 drives at a time would cause this. Is this a WD EARS drive? If so, did you put the jumper on pins 7 & 8? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.