archedraft Posted December 11, 2013 Share Posted December 11, 2013 Alright that gives me a starting point. Thanks! Quote Link to comment
archedraft Posted December 11, 2013 Share Posted December 11, 2013 So I removed one of the graphics cards and used a new power cable, sata cable, and new hard drive. This time the Pre-Clear gets stuck on step 2 of 10 on 48% and the syslog is ugly... The errors are above my head. Does anyone know what they mean? Preclear root@eSilo:~# screen -r ================================================================== 1.13 = unRAID server Pre-Clear disk /dev/sda = cycle 1 of 3, partition start on sector 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 = **** This will take a while... you can follow progress below: = = = = = = = = Elapsed Time: 22:57:07 695425+26 records in 695425+26 records out 1458439135232 bytes (1.5 TB) copied, 20644.3 s, 70.6 MB/s Wrote 1,458,439,135,232 bytes out of 3,000,592,982,016 bytes (48% Done) Smart Test SMART status Info for /dev/sdf 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 === Device Model: WDC WD30EFRX-68EUZN0 Serial Number: WD-WCC4N0291956 Firmware Version: 80.00A80 User Capacity: 3,000,592,982,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 9 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Wed Dec 11 11:00:32 2013 CST 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: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. 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: (39900) 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: (0x703d) SCT Status supported. SCT Error Recovery Control 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 - 0 3 Spin_Up_Time 0x0027 100 253 021 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 2 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 100 100 000 Old_age Always - 23 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 - 2 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 1 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 291 194 Temperature_Celsius 0x0022 126 117 000 Old_age Always - 24 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 23 - 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. syslog-2013-12-11.zip Quote Link to comment
Drider Posted December 11, 2013 Share Posted December 11, 2013 Greetings! My first post, but I've been around the forums about two months now, gathering information, and learning. (Thank God for search buttons!) I've built my first unRAID box, thanks to my father, and I'm looking to add the HDD's I was previously using to store media files, (.iso's). The drives were never in a system, but always used in a Thermaltake BlacX Duet. Anyway, I'd like to use these drives, as I don't have much else at the moment, and I will plan to upgrade them eventually, just not sure exactly when. I'm not sure what all I need to attach but for now, here's the 4 preclear.sh reports: 4BXV1: ========================================================================1.14 == invoked as: ./preclear_disk.sh -A /dev/sdg == ST31500341AS 9VS4BXV1 == Disk /dev/sdg has been successfully precleared == with a starting sector of 64 == Ran 1 cycle == == Using :Read block size = 8388608 Bytes == Last Cycle's Pre Read Time : 5:05:15 (81 MB/s) == Last Cycle's Zeroing time : 4:21:02 (95 MB/s) == Last Cycle's Post Read Time : 10:24:25 (40 MB/s) == Last Cycle's Total Time : 19:51:44 == == Total Elapsed Time 19:51:44 == == Disk Start Temperature: 30C == == Current Disk Temperature: 31C, == ============================================================================ ** 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 = 116 117 6 ok 103695522 Seek_Error_Rate = 62 61 30 ok 1576598 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 84 91 0 ok 16 Airflow_Temperature_Cel = 69 70 45 near_thresh 31 Temperature_Celsius = 31 30 0 ok 31 Hardware_ECC_Recovered = 60 48 0 ok 103695522 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. ============================================================================ BCJ7: ========================================================================1.14 == invoked as: ./preclear_disk.sh -A /dev/sdf == ST31500341AS 9VS4BCJ7 == Disk /dev/sdf has been successfully precleared == with a starting sector of 64 == Ran 1 cycle == == Using :Read block size = 8388608 Bytes == Last Cycle's Pre Read Time : 4:41:25 (88 MB/s) == Last Cycle's Zeroing time : 4:23:44 (94 MB/s) == Last Cycle's Post Read Time : 10:34:57 (39 MB/s) == Last Cycle's Total Time : 19:41:07 == == Total Elapsed Time 19:41:07 == == Disk Start Temperature: 33C == == Current Disk Temperature: 34C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdf /tmp/smart_finish_sdf ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Seek_Error_Rate = 70 69 30 ok 10659712 Spin_Retry_Count = 100 100 97 near_thresh 22 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 1 1 0 near_thresh 477 Airflow_Temperature_Cel = 66 67 45 In_the_past 34 Temperature_Celsius = 34 33 0 ok 34 Hardware_ECC_Recovered = 55 35 0 ok 30022470 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. 43 sectors had been re-allocated before the start of the preclear. 43 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================ 07CY: ========================================================================1.14 == invoked as: ./preclear_disk.sh -A /dev/sdi == ST31000340AS 5QJ107CY == Disk /dev/sdi has been successfully precleared == with a starting sector of 64 == Ran 1 cycle == == Using :Read block size = 8388608 Bytes == Last Cycle's Pre Read Time : 3:19:23 (83 MB/s) == Last Cycle's Zeroing time : 3:16:38 (84 MB/s) == Last Cycle's Post Read Time : 7:36:59 (36 MB/s) == Last Cycle's Total Time : 14:14:01 == == Total Elapsed Time 14:14:01 == == Disk Start Temperature: 30C == == Current Disk Temperature: 31C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdi /tmp/smart_finish_sdi ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 118 115 6 ok 192958221 Seek_Error_Rate = 51 51 30 near_thresh 253411065852 Spin_Retry_Count = 100 100 97 near_thresh 6 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 69 70 45 In_the_past 31 Temperature_Celsius = 31 30 0 ok 31 Hardware_ECC_Recovered = 57 40 0 ok 192958221 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. 2 sectors had been re-allocated before the start of the preclear. 2 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================ 0843: ========================================================================1.14 == invoked as: ./preclear_disk.sh -A /dev/sdh == WDCWD1001FALS-00J7B1 WD-WMATV3090843 == Disk /dev/sdh has been successfully precleared == with a starting sector of 64 == Ran 1 cycle == == Using :Read block size = 8388608 Bytes == Last Cycle's Pre Read Time : 3:35:01 (77 MB/s) == Last Cycle's Zeroing time : 3:14:57 (85 MB/s) == Last Cycle's Post Read Time : 7:34:28 (36 MB/s) == Last Cycle's Total Time : 14:25:27 == == Total Elapsed Time 14:25:27 == == Disk Start Temperature: 34C == == Current Disk Temperature: 35C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdh /tmp/smart_finish_sdh ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 115 116 0 ok 35 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. 1 sector had been re-allocated before the start of the preclear. 1 sector is re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================ Thanks so much for all your help! -D Quote Link to comment
RobJ Posted December 11, 2013 Share Posted December 11, 2013 So I removed one of the graphics cards and used a new power cable, sata cable, and new hard drive. This time the Pre-Clear gets stuck on step 2 of 10 on 48% and the syslog is ugly... The errors are above my head. Does anyone know what they mean? Of Joe's 3 possibilities (bad power, bad cable, bad drive), I would have leaned strongly toward bad drive, except that you switched to a different drive! I see no evidence of a bad SATA cable, so I rule that out. Power issues seem very possible, except for some complications I will discuss later. Heat would be another possibility but SMART reports for both drives show only very cool temps. Bad disk controller or SATA port is a remote possibility, but it's one you can eliminate easily by switching to a different SATA port, and possibly a different SATA controller. The failures are all essentially the same, the drive times out (stops responding to a write request), so the Error Handler kicks in and resets the drive. The drive almost always responds very poorly or not at all to the first reset, then seems to respond acceptably on a second reset. It was only when the drive failed the second reset that the drive was disabled and dropped (at Dec 11 01:42:50). Errors after that can be ignored. The response to the first reset was usually no identity info at all, but if it did return identity info, then the data was found to include corruption. There are no CRC errors, so the drive itself must have created and sent these corrupted identity data packets! What is fascinating about these errors is that they aren't random, but appear to occur very close to a 30 second timetable. If you were to graph the occurrences, you would see a flat graph first then a sharp rise around 25 seconds, peaking around 30 seconds and returning to flat around 35 seconds. It would stay flat until another peak between about 55 to 65 seconds, then again around 85 to 95 seconds, and again around 115 to 125 seconds! It's hard to imagine a 30 second clock in the drive that could crash the drive. But it's also hard to imagine a power issue that occurs at roughly 30 second intervals. Is it possible that there is something creating a heavy power draw roughly twice a minute? Probably unrelated, but you might turn off Plex and any other drive related process, that includes any timer initiated processes. Sorry we can't help any more than that, but hope your testing can discover a cause. Quote Link to comment
archedraft Posted December 11, 2013 Share Posted December 11, 2013 Of Joe's 3 possibilities (bad power, bad cable, bad drive), I would have leaned strongly toward bad drive, except that you switched to a different drive! I see no evidence of a bad SATA cable, so I rule that out. Power issues seem very possible, except for some complications I will discuss later. Heat would be another possibility but SMART reports for both drives show only very cool temps. Bad disk controller or SATA port is a remote possibility, but it's one you can eliminate easily by switching to a different SATA port, and possibly a different SATA controller. The failures are all essentially the same, the drive times out (stops responding to a write request), so the Error Handler kicks in and resets the drive. The drive almost always responds very poorly or not at all to the first reset, then seems to respond acceptably on a second reset. It was only when the drive failed the second reset that the drive was disabled and dropped (at Dec 11 01:42:50). Errors after that can be ignored. The response to the first reset was usually no identity info at all, but if it did return identity info, then the data was found to include corruption. There are no CRC errors, so the drive itself must have created and sent these corrupted identity data packets! What is fascinating about these errors is that they aren't random, but appear to occur very close to a 30 second timetable. If you were to graph the occurrences, you would see a flat graph first then a sharp rise around 25 seconds, peaking around 30 seconds and returning to flat around 35 seconds. It would stay flat until another peak between about 55 to 65 seconds, then again around 85 to 95 seconds, and again around 115 to 125 seconds! It's hard to imagine a 30 second clock in the drive that could crash the drive. But it's also hard to imagine a power issue that occurs at roughly 30 second intervals. Is it possible that there is something creating a heavy power draw roughly twice a minute? Probably unrelated, but you might turn off Plex and any other drive related process, that includes any timer initiated processes. Sorry we can't help any more than that, but hope your testing can discover a cause. Well we can rule out bad SATA port because I also switched that as well. Am an leaning towards the PSU being the issue. Is there anyway an older motherboard would be the cause of this because the hard drive is 3 TB? I was of the understanding that it shouldn't matter with unRAID but thought I would check anyways. My friends server is running Plex, Sickbeard, and Transmission. Plex updates itself every hour, Sickbeard every 10 minuets, and I am sure Transmission updates it self as well... I guess I will turn off all the plugins and try again before I tell my friend to buy new stuff but the question is, will adding this drive to the array cause problems later on if I turn the plugins back on? Quote Link to comment
RobJ Posted December 11, 2013 Share Posted December 11, 2013 Am leaning towards the PSU being the issue. Is there anyway an older motherboard would be the cause of this because the hard drive is 3 TB? I was of the understanding that it shouldn't matter with unRAID but thought I would check anyways. If the disk controller was not compatible with 3TB drives, then it would not work at all, that is, you would not see 3TB available. Yours does appear to work fine. I can't see any connection with the motherboard, because we need a suspect that is able to cause corruption and trouble WITHIN the drive, and that is a very short list. The only possibilities I can think of are power issues, heat issues, or a defective drive (bad firmware). My friends server is running Plex, Sickbeard, and Transmission. Plex updates itself every hour, Sickbeard every 10 minuets, and I am sure Transmission updates it self as well... I guess I will turn off all the plugins and try again before I tell my friend to buy new stuff but the question is, will adding this drive to the array cause problems later on if I turn the plugins back on? Remember that if you discover a relation between a software running and the drive crashing, then that could only point to heavy power draw (perhaps pulling the voltage down too low), and that implicates the power supply (not the software or other hardware), as either too inadequate or too poorly designed. Aerocool makes interesting products (I like some of their cases), but I don't believe they are a good name in power supplies (I could be wrong, I haven't kept up with PSU's recently). I can't help being very suspicious of your PSU. Quote Link to comment
RobJ Posted December 12, 2013 Share Posted December 12, 2013 My first post, but I've been around the forums about two months now, gathering information, and learning. (Thank God for search buttons!) I've built my first unRAID box, thanks to my father, and I'm looking to add the HDD's I was previously using to store media files, (.iso's). The drives were never in a system, but always used in a Thermaltake BlacX Duet. Anyway, I'd like to use these drives, as I don't have much else at the moment, and I will plan to upgrade them eventually, just not sure exactly when. Greetings and welcome! While the better funded users around here would probably respond that they prefer late model drives with pristine SMART reports, your 4 drives fit the other philosophy, of using UnRAID as a great place, a second life, for drives to retire to. Your drives do show some age and wear, but are still in very good shape, and the Preclears found no new problems. I would use them without hesitation. All but the first show a few remapped sectors, and one shows a higher than normal High_Fly_Writes count of 477, and one shows a lower than normal Seek_Error_Rate of 51, so I would monitor the SMART reports for these drives now and then, perhaps every few months? Quote Link to comment
Drider Posted December 12, 2013 Share Posted December 12, 2013 Greetings and welcome! While the better funded users around here would probably respond that they prefer late model drives with pristine SMART reports, your 4 drives fit the other philosophy, of using UnRAID as a great place, a second life, for drives to retire to. Your drives do show some age and wear, but are still in very good shape, and the Preclears found no new problems. I would use them without hesitation. All but the first show a few remapped sectors, and one shows a higher than normal High_Fly_Writes count of 477, and one shows a lower than normal Seek_Error_Rate of 51, so I would monitor the SMART reports for these drives now and then, perhaps every few months? Ah, wonderful news! Thanks so much, I will follow your advise and check every couple months. -D Sent from my SCH-I545 using Tapatalk Quote Link to comment
squirrellydw Posted December 13, 2013 Share Posted December 13, 2013 any idea how long it takes to pre clear a 3TB WD Red drive? I just started pre clearing one, doing it 3 times Quote Link to comment
archedraft Posted December 13, 2013 Share Posted December 13, 2013 any idea how long it takes to pre clear a 3TB WD Red drive? I just started pre clearing one, doing it 3 times My 3TB Red took 82 hours and 10 minutes with 3 cycles. Quote Link to comment
squirrellydw Posted December 13, 2013 Share Posted December 13, 2013 Thanks, another question. I just realized I'm still using 1.13 and not 1.14, I forgot to update it, is this going to be a problem? How Can I stop the pre clear, I have it doing 3 cycles. Quote Link to comment
BobPhoenix Posted December 13, 2013 Share Posted December 13, 2013 Thanks, another question. I just realized I'm still using 1.13 and not 1.14, I forgot to update it, is this going to be a problem? How Can I stop the pre clear, I have it doing 3 cycles. I'm still on 1.13 and it preclears 3TB Reds just fine. I've done about 20 of them many times. I do plan on updating to 1.14 just forgot it was available Quote Link to comment
DrMexSS Posted December 14, 2013 Share Posted December 14, 2013 Hi! I have one question regarding the 4k alignment. I am preclearing 2 drives in parallel (new drives) in a new computer. I have downloaded unraid and preclear. Boot from usb and entered to the console. The drives: Western Digital Green 4tb : wd40ezrx Western Digital Red 4tb : wd40efrx I have writen the following line in the console (one console per disk) preclear_disk.sh -A -c 3 /dev/sdc preclear_disk.sh -A -c 3 /dev/sdb In both cases the preclearing is starting at sector 1 (not at sector 64) Is there any problem? Last year I precleared a 3tb western digital green drive in my current unraid ring and the preclear started at sector 64. Quote Link to comment
Joe L. Posted December 14, 2013 Share Posted December 14, 2013 Hi! I have one question regarding the 4k alignment. I am preclearing 2 drives in parallel (new drives) in a new computer. I have downloaded unraid and preclear. Boot from usb and entered to the console. The drives: Western Digital Green 4tb : wd40ezrx Western Digital Red 4tb : wd40efrx I have writen the following line in the console (one console per disk) preclear_disk.sh -A -c 3 /dev/sdc preclear_disk.sh -A -c 3 /dev/sdb In both cases the preclearing is starting at sector 1 (not at sector 64) Is there any problem? Last year I precleared a 3tb western digital green drive in my current unraid ring and the preclear started at sector 64. You must be using an older version of the preclear script. The newer version of the preclear script explains that disks over 2.2TB will ALWAYS have a "protective" MBR entry made so it looks like the partition starts on sector 1 to keep legacy utilities thinking the disk is fully utilized. The "-a" or "-A" is ALWAYS silently ignored on disks > 2.2TB. They are meaningless with disks over 2.2TB. The actual GPT partition used on disks over 2.2TB IS always aligned on a 4k boundary. Oh yes, you should always get the newest version of the preclear script... No need to re-start, the newer version allows it to properly detect assigned disks if you've not yet started the array (to prevent you from accidentally clearing the wrong disk) It has the improved wording describing the partition it will create. Neither affects the actual preclear. Joe L. Quote Link to comment
DrMexSS Posted December 14, 2013 Share Posted December 14, 2013 Thank you Joe, I am using the last version of the preclear script. However, I am using a tv as the monitor, and I don't see everything that is printed in the screen. There was a message saying something with the "> 2.2TB", but I wasn't able to read it. Therefore, I understand that everything is OK. Thank you very much. Quote Link to comment
brisimmons105 Posted December 16, 2013 Share Posted December 16, 2013 I am in the middle of formatting my 4th disk (to use as a cache) and when I started the preclear, I think I got a different response form the other three. Here is what it said: Do I need to do something different? Its a 1TB Lacie... Pre-Clear unRAID Disk /dev/sda ################################################################## 1.14 smartctl may not be able to run on /dev/sda with the -d ata option. however this should not affect the clearing of a disk. smartctl exit status = 2 smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright © 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org Read Device Identity failed: Invalid argument A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.$ Do you wish to continue? (Answer Yes to continue. Capital 'Y', lower case 'es'): Yes WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /dev/sda: 1000.2 GB, 1000204886016 bytes 255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 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/sda1 1 1953525167 976762583+ ee GPT ######################################################################## invoked as ./preclear_disk.sh /dev/sda ######################################################################## (partition starting on sector 63) (it will not be 4k-aligned) Are you absolutely sure you want to clear this drive? (Answer Yes to continue. Capital 'Y', lower case 'es'): Yes Quote Link to comment
squirrellydw Posted December 16, 2013 Share Posted December 16, 2013 Just want someone to confirm what I see, everything look good to me. 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 3. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 3. 0 sectors were pending re-allocation after post-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 3. 0 sectors were pending re-allocation after post-read in cycle 2 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 3. 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. [code/] [code]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 - 0 3 Spin_Up_Time 0x0027 100 253 021 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 2 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 81 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 - 2 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 1 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 9 194 Temperature_Celsius 0x0022 126 118 000 Old_age Always - 24 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 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. [code/] Quote Link to comment
Thermo Posted December 18, 2013 Share Posted December 18, 2013 Quick question I am about to preclear 9 hard disks (ranging from 3tb to 1.5tb) on a AMD A4-5300 Dual Core 3.4Gh with 4gb of ram. Based on reading the configuration tutorial, I intend to use the following command to run the prelcears all at the same time (in separate screen sessions): preclear_disk.sh -r 65536 -w 65536 -b 2000 -A -m [email protected] /dev/sdX Do I still need to have the -r, -w and -b variables and will these effect performance? Note: I am using the v1.14 of the script and I have selected MBR-4k-aligned in the unraid settings. Thanks for your help! Quote Link to comment
Joe L. Posted December 18, 2013 Share Posted December 18, 2013 Quick question I am about to preclear 9 hard disks (ranging from 3tb to 1.5tb) on a AMD A4-5300 Dual Core 3.4Gh with 4gb of ram. Based on reading the configuration tutorial, I intend to use the following command to run the prelcears all at the same time (in separate screen sessions): preclear_disk.sh -r 65536 -w 65536 -b 2000 -A -m [email protected] /dev/sdX Do I still need to have the -r, -w and -b variables and will these effect performance? Note: I am using the v1.14 of the script and I have selected MBR-4k-aligned in the unraid settings. Thanks for your help! yes, yes. -A (and 4k-aligned setting) only apply to disks < 2.2TB. They are both silently ignored on disks > 2.2TB. Quote Link to comment
Thermo Posted December 18, 2013 Share Posted December 18, 2013 Great, will keep them on! Thanks Joe Quote Link to comment
squirrellydw Posted December 18, 2013 Share Posted December 18, 2013 Just want someone to confirm what I see, everything look good to me. 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 3. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 3. 0 sectors were pending re-allocation after post-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 3. 0 sectors were pending re-allocation after post-read in cycle 2 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 3. 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. [code/] [code]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 - 0 3 Spin_Up_Time 0x0027 100 253 021 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 2 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 81 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 - 2 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 1 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 9 194 Temperature_Celsius 0x0022 126 118 000 Old_age Always - 24 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 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. [code/] anyone Quote Link to comment
BobPhoenix Posted December 18, 2013 Share Posted December 18, 2013 Just want someone to confirm what I see, everything look good to me. 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 3. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 3. 0 sectors were pending re-allocation after post-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 3. 0 sectors were pending re-allocation after post-read in cycle 2 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 3. 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. [code/] [code]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 - 0 3 Spin_Up_Time 0x0027 100 253 021 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 2 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 81 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 - 2 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 1 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 9 194 Temperature_Celsius 0x0022 126 118 000 Old_age Always - 24 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 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. [code/] anyone Looks fine. Quote Link to comment
nanoman06 Posted December 20, 2013 Share Posted December 20, 2013 Can anyone give me an opinion on these resultes? Are the drives bad? They are two days out of the original packaging.. Drive 1: ========================================================================1.14 == GB1000EAFJL == Disk /dev/sdb has been successfully precleared == with a starting sector of 64 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VA LUE Raw_Read_Error_Rate = 78 82 44 ok 774410 85 Spin_Retry_Count = 100 100 97 near_thresh 0 Airflow_Temperature_Cel = 63 65 45 near_thresh 37 Temperature_Celsius = 37 34 0 ok 37 Hardware_ECC_Recovered = 59 38 0 ok 774410 85 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 5. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 5. 0 sectors were pending re-allocation after post-read in cycle 1 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 5. 0 sectors were pending re-allocation after post-read in cycle 2 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 5. 0 sectors were pending re-allocation after post-read in cycle 3 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 4 of 5. 0 sectors were pending re-allocation after post-read in cycle 4 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 5 of 5. 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. Drive 2: ========================================================================1.14 == GB1000EAFJL == Disk /dev/sdc has been successfully precleared == with a starting sector of 64 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdc /tmp/smart_finish_sdc ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_V LUE Raw_Read_Error_Rate = 81 82 44 ok 15229 693 Spin_Retry_Count = 100 100 97 near_thresh 0 Airflow_Temperature_Cel = 64 66 45 near_thresh 36 Temperature_Celsius = 36 34 0 ok 36 Hardware_ECC_Recovered = 66 48 0 ok 15229 693 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 5. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 5. 0 sectors were pending re-allocation after post-read in cycle 1 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 5. 0 sectors were pending re-allocation after post-read in cycle 2 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 5. 0 sectors were pending re-allocation after post-read in cycle 3 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 4 of 5. 0 sectors were pending re-allocation after post-read in cycle 4 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 5 of 5. 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. Are these drives reliable? Quote Link to comment
Joe L. Posted December 20, 2013 Share Posted December 20, 2013 Can anyone give me an opinion on these resultes? Are the drives bad?no, they look great. are they reliable? Probably... only time will tell. Quote Link to comment
Thermo Posted December 20, 2013 Share Posted December 20, 2013 Hi All, Done a big batch of preclearing - can anyone please look at the 3 reports below? The first two are from brand new Seagate NAS drives - have I got lemons? Drive 1 (new Seagate NAS) ========================================================================1.14 == invoked as: ./preclear_disk.sh -r 65536 -w 65536 -b 2000 -A /dev/sdi == ST3000VN000-1H4167 Z3100E4N == Disk /dev/sdi has been successfully precleared == with a starting sector of 1 == Ran 1 cycle == == Using :Read block size = 65536 Bytes == Last Cycle's Pre Read Time : 9:43:20 (85 MB/s) == Last Cycle's Zeroing time : 7:43:57 (107 MB/s) == Last Cycle's Post Read Time : 20:47:55 (40 MB/s) == Last Cycle's Total Time : 38:16:17 == == Total Elapsed Time 38:16:17 == == Disk Start Temperature: 25C == == Current Disk Temperature: -->41<--C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdi /tmp/smart_finish_sdi ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 119 100 6 ok 206149480 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 48 100 0 ok 52 Airflow_Temperature_Cel = 59 75 45 near_thresh 41 Temperature_Celsius = 41 25 0 ok 41 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. ============================================================================ Drive 2 (new Seagate NAS) ========================================================================1.14 == invoked as: ./preclear_disk.sh -r 65536 -w 65536 -b 2000 -A /dev/sdh == ST3000VN000-1H4167 Z300QL08 == Disk /dev/sdh has been successfully precleared == with a starting sector of 1 == Ran 1 cycle == == Using :Read block size = 65536 Bytes == Last Cycle's Pre Read Time : 9:32:39 (87 MB/s) == Last Cycle's Zeroing time : 7:33:53 (110 MB/s) == Last Cycle's Post Read Time : 20:39:40 (40 MB/s) == Last Cycle's Total Time : 37:47:17 == == Total Elapsed Time 37:47:17 == == Disk Start Temperature: 25C == == Current Disk Temperature: -->41<--C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdh /tmp/smart_finish_sdh ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 119 100 6 ok 203909368 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 94 100 0 ok 6 Airflow_Temperature_Cel = 59 75 45 near_thresh 41 Temperature_Celsius = 41 25 0 ok 41 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. ============================================================================ Drive 3 (old Seagate) ========================================================================1.14 == invoked as: ./preclear_disk.sh -r 65536 -w 65536 -b 2000 -A /dev/sdj == ST2000DL003-9VT166 5YD3BJ1V == Disk /dev/sdj has been successfully precleared == with a starting sector of 64 == Ran 1 cycle == == Using :Read block size = 65536 Bytes == Last Cycle's Pre Read Time : 7:03:18 (78 MB/s) == Last Cycle's Zeroing time : 5:42:31 (97 MB/s) == Last Cycle's Post Read Time : 16:07:50 (34 MB/s) == Last Cycle's Total Time : 28:54:44 == == Total Elapsed Time 28:54:44 == == Disk Start Temperature: 25C == == Current Disk Temperature: 30C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdj /tmp/smart_finish_sdj ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Seek_Error_Rate = 67 66 30 ok 5294102 Power_On_Hours = 21 21 0 near_thresh 69431 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 70 75 45 near_thresh 30 Temperature_Celsius = 30 25 0 ok 30 Hardware_ECC_Recovered = 37 30 0 ok 85804520 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. ============================================================================ In addition, I still have 2 WDC_WD30EZRX preclearing after 46 hours (one 89% of copying zeros and the other at 3% of the post-read) (sdd and sdf). I have previously had issues trying to preclear these a few days ago where they got stuck late in the post-read process. A third drive I have of exactly the same type successfully precleared after 37 hours with no issues. Attached is a link to the errors and minor issues in the syslog. These drives look like they are in a world of pain. Should I write them off? https://www.dropbox.com/s/wg36u841ijo9of3/SysLogExtract.txt Sorry for the long post... Any help is very much appreciated 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.