newbie_dude Posted July 17, 2014 Share Posted July 17, 2014 I had some error that I don't remember seeing from my previous preclear run on other disks. Here is what I saw: All you posted is the output of a smartctl report. It looks fine. What error are you seeing? Joe L. Oh. I thought the disk had errors. It was just listed on the final output. Things like Attribute NEW VAL OLD VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 118 101 6 OK 186259920 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-end_error = 100 100 99 near_thresh 0 Airflow_Temper_Cel = 66 69 45 near_thresh 34 Temper_Cel = 34 31 0 ok 34 I was worried about the near_threshold issues. Does it sort of mean the disk is not new if there are old smart attribtes? Sorry, this is really confusing! Quote Link to comment
Joe L. Posted July 17, 2014 Share Posted July 17, 2014 I had some error that I don't remember seeing from my previous preclear run on other disks. Here is what I saw: All you posted is the output of a smartctl report. It looks fine. What error are you seeing? Joe L. Oh. I thought the disk had errors. It was just listed on the final output. Things like Attribute NEW VAL OLD VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 118 101 6 OK 186259920 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-end_error = 100 100 99 near_thresh 0 Airflow_Temper_Cel = 66 69 45 near_thresh 34 Temper_Cel = 34 31 0 ok 34 I was worried about the near_threshold issues. Does it sort of mean the disk is not new if there are old smart attribtes? Sorry, this is really confusing! It indicates the current normalized value is close to the affiliated failure threshold set by that disks manufacturer. Nobody knows how the "raw" counts on those attributes equate to the normalized values, at they typically do not tell, but if we assume the normalized value will decrement by 1 every time the disk fails to spin up, then it would take three failures to spin up to get to the affiliated failure threshold of 97. To me, even one failure to spin up is an issue, so if you ever see that value increasing, keep an eye on it. HOWEVER, the starting value for spin-retry is 100, and there have been NO failures in the raw column, so the disk has never failed to spin-up. (a good thing) The "near_thresh" is just there to help you decide if you need to investigate further. If you are that interested, you really should learn hoe to interpret the full smartctl reports, and not the summary the preclear script gives to you in its attempt to show you the parameters that have changed in the before and after reports. basically, according to what I can see from that difference report, the disk is fine. Joe L. Quote Link to comment
newbie_dude Posted July 18, 2014 Share Posted July 18, 2014 I had some error that I don't remember seeing from my previous preclear run on other disks. Here is what I saw: All you posted is the output of a smartctl report. It looks fine. What error are you seeing? Joe L. Oh. I thought the disk had errors. It was just listed on the final output. Things like Attribute NEW VAL OLD VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 118 101 6 OK 186259920 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-end_error = 100 100 99 near_thresh 0 Airflow_Temper_Cel = 66 69 45 near_thresh 34 Temper_Cel = 34 31 0 ok 34 I was worried about the near_threshold issues. Does it sort of mean the disk is not new if there are old smart attribtes? Sorry, this is really confusing! It indicates the current normalized value is close to the affiliated failure threshold set by that disks manufacturer. Nobody knows how the "raw" counts on those attributes equate to the normalized values, at they typically do not tell, but if we assume the normalized value will decrement by 1 every time the disk fails to spin up, then it would take three failures to spin up to get to the affiliated failure threshold of 97. To me, even one failure to spin up is an issue, so if you ever see that value increasing, keep an eye on it. HOWEVER, the starting value for spin-retry is 100, and there have been NO failures in the raw column, so the disk has never failed to spin-up. (a good thing) The "near_thresh" is just there to help you decide if you need to investigate further. If you are that interested, you really should learn hoe to interpret the full smartctl reports, and not the summary the preclear script gives to you in its attempt to show you the parameters that have changed in the before and after reports. basically, according to what I can see from that difference report, the disk is fine. Joe L. Thanks so much! I'm going to start looking up to read the reports now. I have a feeling my cache drive is acting up from the reports in the unmenu section and I'd really like to know what it's saying. Once again, thanks! Quote Link to comment
Lt-Chewie Posted July 20, 2014 Share Posted July 20, 2014 Just precleared one of my Samsungs that I had laying about, I think from the numbers in the start and finish files it looks okay but the "pending re-allocation" parts in the report is what concerns me. I've also attached the start and finish files from the preclears if that is needed. Any insight as to what I should do with this drive, and perhaps a little understanding of what the last paragraph means for future preclears would be appreciated, thanks. First 2 cylcle preclear: ========================================================================1.15 == invoked as: ./preclear_disk.sh -A -c 2 /dev/sdb == SAMSUNGHD204UI S2HGJ1BZ828875 == Disk /dev/sdb has been successfully precleared == with a starting sector of 64 == Ran 2 cycles == == Using :Read block size = 8388608 Bytes == Last Cycle's Pre Read Time : 6:34:59 (84 MB/s) == Last Cycle's Zeroing time : 5:33:53 (99 MB/s) == Last Cycle's Post Read Time : 12:17:30 (45 MB/s) == Last Cycle's Total Time : 17:52:27 == == Total Elapsed Time 42:21:33 == == Disk Start Temperature: 29C == == Current Disk Temperature: 32C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Current_Pending_Sector = 99 100 0 ok 149 No SMART attributes are FAILING_NOW 11 sectors were pending re-allocation before the start of the preclear. 160 sectors were pending re-allocation after pre-read in cycle 1 of 2. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 2. 151 sectors were pending re-allocation after post-read in cycle 1 of 2. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 2. 149 sectors are pending re-allocation at the end of the preclear, a change of 138 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. ============================================================================ Second 2 cycle preclear: ========================================================================1.15 == invoked as: ./preclear_disk.sh -A -c 2 /dev/sdb == SAMSUNGHD204UI S2HGJ1BZ828875 == Disk /dev/sdb has been successfully precleared == with a starting sector of 64 == Ran 2 cycles == == Using :Read block size = 8388608 Bytes == Last Cycle's Pre Read Time : 6:29:41 (85 MB/s) == Last Cycle's Zeroing time : 5:34:01 (99 MB/s) == Last Cycle's Post Read Time : 12:07:12 (45 MB/s) == Last Cycle's Total Time : 17:42:18 == == Total Elapsed Time 42:05:16 == == Disk Start Temperature: 27C == == Current Disk Temperature: 32C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Current_Pending_Sector = 100 99 0 ok 100 No SMART attributes are FAILING_NOW 149 sectors were pending re-allocation before the start of the preclear. 150 sectors were pending re-allocation after pre-read in cycle 1 of 2. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 2. 149 sectors were pending re-allocation after post-read in cycle 1 of 2. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 2. 100 sectors are pending re-allocation at the end of the preclear, a change of -49 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. ============================================================================ preclear_start_S2HGJ1BZ828875_2014-07-17.txt preclear_finish_S2HGJ1BZ828875_2014-07-17.txt preclear_start_S2HGJ1BZ828875_2014-07-19.txt preclear_finish_S2HGJ1BZ828875_2014-07-19.txt Quote Link to comment
itimpi Posted July 20, 2014 Share Posted July 20, 2014 You do not want to use a disk in unRAID that is showing any Pending sectors. The good sign is that the number went down during the pre-clear without forcing any re-allocation. More worrying is why were they not all cleared! I would suggest you put it through another pre_clear cycle to see what happens. If you cannot clear the Pending Sectors then you need to consider a RMA. Quote Link to comment
Joe L. Posted July 20, 2014 Share Posted July 20, 2014 You do not want to use a disk in unRAID that is showing any Pending sectors. The good sign is that the number went down during the pre-clear without forcing any re-allocation. More worrying is why were they not all cleared! I would suggest you put it through another pre_clear cycle to see what happens. If you cannot clear the Pending Sectors then you need to consider a RMA. agreed... at this point, I would never trust that drive. The pending sectors needs to be cleared, and stay cleared. (writing the zeros to the drive should re-allocate all the sectors, and it seems it is, as the count goes to zero after the write phase, but the subsequent "read" detects more un-readable sectors. ) Note: it could be a power supply issue... If the poor quality power induces errors on reading where the sector contents do not match the checksum at the end of the sector... or perhaps what is being written does not match that expected, so the checksum when read back is wrong and the sector marked as un-readable. Basically, unless you can get through several additional read/write cycles with NO sectors pending re-allocation, and since that drive seems to constantly detect additional un-readable sectors, it is a strong candidate for an RMA. Be thankful you found it before you used it for your data. As it is currently working, it would cause hair-loss. Joe L. Quote Link to comment
Lt-Chewie Posted July 20, 2014 Share Posted July 20, 2014 Thank you itimpi and Joe, RMA won't happen since it's past warranty - purchased about 3 or so years ago. I don't think it's the power-supply as I have precleared other drives with no issues. I'll just stick this into something unimportant like the NAS for the CCTV at work. Thanks again for taking the time to look at it Quote Link to comment
FreeMan Posted July 23, 2014 Share Posted July 23, 2014 I just upgraded my parity from a 3TB drive to a 4TB. The 4 precleared & parity has been rebuilt & checked just fine. I went to preclear the 3TB, and I get this output from preclear_disk.sh before starting the clear: root@NAS:/boot/scripts# preclear_disk.sh -n /dev/sdm Pre-Clear unRAID Disk /dev/sdm ################################################################## 1.15 Model Family: Western Digital Caviar Green (AF, SATA 6Gb/s) Device Model: WDC WD30EZRX-00D8PB0 Serial Number: WD-WMC4N0533589 LU WWN Device Id: 5 0014ee 603d7fd9c Firmware Version: 80.00A80 User Capacity: 3,000,592,982,016 bytes [3.00 TB] WARNING: GPT (GUID Partition Table) detected on '/dev/sdm'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /dev/sdm: 3000.6 GB, 3000592982016 bytes 256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdm1 1 4294967295 2147483647+ ee GPT Partition 1 does not start on physical sector boundary. ######################################################################## invoked as ./preclear_disk.sh -n /dev/sdm ######################################################################## (MBR 4k-aligned set. Partition will start on sector 64 for disks <= 2.2TB and sector 1 for disks > 2.2TB) Though I've upgraded my parity before (from 2 to 3TB), I don't recall seeing a message like this, though it may have been there. What concerns me is Partition 1 does not start on physical sector boundary. Is that an issue to worry about? I'm running unRaid v5.0.4. TIA FreeMan Quote Link to comment
Joe L. Posted July 23, 2014 Share Posted July 23, 2014 I just upgraded my parity from a 3TB drive to a 4TB. The 4 precleared & parity has been rebuilt & checked just fine. I went to preclear the 3TB, and I get this output from preclear_disk.sh before starting the clear: root@NAS:/boot/scripts# preclear_disk.sh -n /dev/sdm Pre-Clear unRAID Disk /dev/sdm ################################################################## 1.15 Model Family: Western Digital Caviar Green (AF, SATA 6Gb/s) Device Model: WDC WD30EZRX-00D8PB0 Serial Number: WD-WMC4N0533589 LU WWN Device Id: 5 0014ee 603d7fd9c Firmware Version: 80.00A80 User Capacity: 3,000,592,982,016 bytes [3.00 TB] WARNING: GPT (GUID Partition Table) detected on '/dev/sdm'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /dev/sdm: 3000.6 GB, 3000592982016 bytes 256 heads, 63 sectors/track, 363376 cylinders, total 5860533168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdm1 1 4294967295 2147483647+ ee GPT Partition 1 does not start on physical sector boundary. ######################################################################## invoked as ./preclear_disk.sh -n /dev/sdm ######################################################################## (MBR 4k-aligned set. Partition will start on sector 64 for disks <= 2.2TB and sector 1 for disks > 2.2TB) Though I've upgraded my parity before (from 2 to 3TB), I don't recall seeing a message like this, though it may have been there. What concerns me is Partition 1 does not start on physical sector boundary. Is that an issue to worry about? I'm running unRaid v5.0.4. TIA FreeMan nothing to worry about. "fdisk" is reporting about the fake "protective" partition that was defined to fool older utilities (such as "fdisk") into thinking the entire disk is allocated. The actual GPT partition does not start at sector 1. Quote Link to comment
nanoman06 Posted July 27, 2014 Share Posted July 27, 2014 Disk Temperature: 37C, Elapsed Time: 30:05:55 ========================================================================1.14 == TOSHIBADT01ACA300 XXXXXXX == Disk /dev/sdc has been successfully precleared == with a starting sector of 1 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdc /tmp/smart_finish_sdc ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 162 166 0 ok 37 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. What's up with the bolded line? Quote Link to comment
Joe L. Posted July 27, 2014 Share Posted July 27, 2014 ** Changed attributes in files: /tmp/smart_start_sdc /tmp/smart_finish_sdc ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 162 166 0 ok 37 What's up with the bolded line? Exactly as the line above described. Changed attributes in files: /tmp/smart_start_sdc /tmp/smart_finish_sdc That attribute in your two smart reports (the one at the start of the preclear vs. the one at the finish) changed. The normalized value changed from 166 to 162. Probably as a result of the disk heating up while it was being used. The end-value of 37C is perfectly fine, so I doubt you have anything to do except to learn more about how to interpret smartctl reports. The see the actual lines, you would need to look in the to files listed: /tmp/smart_start_sdc /tmp/smart_finish_sdc Joe L. Quote Link to comment
SSD Posted July 29, 2014 Share Posted July 29, 2014 Thank you itimpi and Joe, RMA won't happen since it's past warranty - purchased about 3 or so years ago. I don't think it's the power-supply as I have precleared other drives with no issues. I'll just stick this into something unimportant like the NAS for the CCTV at work. Thanks again for taking the time to look at it If you bought with Amex you get an extra year of warranty, and that's from the purchase date, not the borne date. I refer to the problem you see with that disk as the pothole effect. Every time the drive reads that area and reallocates some sectors, the pothole gets bigger and more need to be remapped. Quote Link to comment
steve.c7677 Posted August 8, 2014 Share Posted August 8, 2014 HI all, Looking for some advice. I have installed the latest stable unraid 5 version with unmenu and screen, logged in via putty and began preclearing 4x4tb hdd's as per the config turorial last night. Today made the mistake of rebooting my router. The pre-clear process was almost finished steps 10 of 10 done, and it was about 25% through the post clear read. Once my network went down the putty session gave me a message 'session disconnected' Now the networks back up i have tried reconnecting with the command screen -r ____________________________________________________________ root@CRUX:~# screen -r Sorry: /dev/sdG does not exist as a block device Clearing will NOT be performed root@CRUX:/boot# preclear_disk.sh -l ====================================1.15 Disks not assigned to the unRAID array (potential candidates for clearing) ======================================== /dev/sdd = ata-ST2000DM001-9YN164_Z1E0TY6Y /dev/sdg = ata-ST4000VN000-1H4168_S3007M1T /dev/sdc = ata-ST4000VN000-1H4168_Z3012VMD /dev/sdb = ata-Samsung_SSD_840_PRO_Series_S1ATNSAF511971N /dev/sdf = ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E69K7X7C /dev/sde = ata-WDC_WD40EFRX-68WT0N0_WD-WCC4E74FXX52 root@CRUX:/boot# _____________________________________________________________ Just curious where to go from here. I have had a look at the syslog_match file in my unraid (flash drive) trying to determine if the pre-clear has finished, cant see anything. I suppose if the network interrupt has not affected the pre-clear it will still be running the post clear and the syslog wont be available yet? Or have i messed this up proper? Quote Link to comment
Joe L. Posted August 8, 2014 Share Posted August 8, 2014 You apparently typed /dev/sdG (with a capital "G") instead of /dev/sdg (all lower case) Basically, the preclear script said the device did not exist and exited. (Linux is case-sensitive.) Joe L. Quote Link to comment
steve.c7677 Posted August 9, 2014 Share Posted August 9, 2014 Thanks Joe, I missed that. I initially typed the wrong command (capital G) and then went on to type the correct commands after. The reports have shown up 10hrs later than expected, but they are finished cycle 1 now. I have 2x WD reds and 2x Seagate NAS. The WD's are showing no errors in the summary reports both the Seagate's are showing lots of near thresh' Status markers. Does anyone know if this is normal, Smart support is enables for all HDD's. ------------------------------------------------------------------------------------------------------------------- Changed attributes in files: /tmp/smart_start_sdc /tmp/smart_finish_sdc ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 111 100 6 ok 39777448 Seek_Error_Rate = 60 100 30 ok 1233430 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 87 100 0 ok 13 Airflow_Temperature_Cel = 67 70 45 near_thresh 33 Temperature_Celsius = 33 30 0 ok 33 No SMART attributes are FAILING_NOW ------------------------------------------------------------------------------------------------- Quote Link to comment
Joe L. Posted August 9, 2014 Share Posted August 9, 2014 Thanks Joe, I missed that. I initially typed the wrong command (capital G) and then went on to type the correct commands after. The reports have shown up 10hrs later than expected, but they are finished cycle 1 now. I have 2x WD reds and 2x Seagate NAS. The WD's are showing no errors in the summary reports both the Seagate's are showing lots of near thresh' Status markers. Does anyone know if this is normal, Smart support is enables for all HDD's. ------------------------------------------------------------------------------------------------------------------- Changed attributes in files: /tmp/smart_start_sdc /tmp/smart_finish_sdc ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 111 100 6 ok 39777448 Seek_Error_Rate = 60 100 30 ok 1233430 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 87 100 0 ok 13 Airflow_Temperature_Cel = 67 70 45 near_thresh 33 Temperature_Celsius = 33 30 0 ok 33 No SMART attributes are FAILING_NOW ------------------------------------------------------------------------------------------------- I guess you did not take the time to read back a few posts: http://lime-technology.com/forum/index.php?topic=4068.msg317738#msg317738 Quote Link to comment
viperdiver Posted August 10, 2014 Share Posted August 10, 2014 So completed first preclear. Any comments on my results? Also, this is a post from the e-mail I got, if there is a better way to share the results please let me know and I will do that. Looks good to me, but I am honestly not entirely sure what I am looking at. ========================================================================1.15 == invoked as: ./preclear_disk.sh -A -m -c 3 /dev/sdb --(NOTE: I deleted my e-mail from this post which was after -m and before -c) == WDCWD20EURX-63T0FY0 WD-WCC4M1851765 == Disk /dev/sdb has been successfully precleared == with a starting sector of 64 == Ran 3 cycles == == Using :Read block size = 8388608 Bytes == Last Cycle's Pre Read Time : 5:48:50 (95 MB/s) == Last Cycle's Zeroing time : 4:47:28 (115 MB/s) == Last Cycle's Post Read Time : 9:52:21 (56 MB/s) == Last Cycle's Total Time : 14:40:49 == == Total Elapsed Time 49:51:38 == == Disk Start Temperature: 28C == == Current Disk Temperature: 29C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 118 119 0 ok 29 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. ============================================================================ ============================================================================ == == S.M.A.R.T Initial Report for /dev/sdb == Disk: /dev/sdb 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 === START OF INFORMATION SECTION === Device Model: WDC WD20EURX-63T0FY0 Serial Number: WD-WCC4M1851765 LU WWN Device Id: 5 0014ee 25f23e70c Firmware Version: 80.00A80 User Capacity: 2,000,398,934,016 bytes [2.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5400 rpm Device is: Not in smartctl database [for details use: -P showall] ATA Version is: ACS-2 (minor revision not indicated) SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Thu Aug 7 21:00:42 2014 PDT 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: (26400) 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: ( 266) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x7035) 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 100 253 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 - 5 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 - 2 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 - 5 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 1 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 3 194 Temperature_Celsius 0x0022 119 118 000 Old_age Always - 28 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. == ============================================================================ ============================================================================ == == S.M.A.R.T Final Report for /dev/sdb == Disk: /dev/sdb 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 === START OF INFORMATION SECTION === Device Model: WDC WD20EURX-63T0FY0 Serial Number: WD-WCC4M1851765 LU WWN Device Id: 5 0014ee 25f23e70c Firmware Version: 80.00A80 User Capacity: 2,000,398,934,016 bytes [2.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5400 rpm Device is: Not in smartctl database [for details use: -P showall] ATA Version is: ACS-2 (minor revision not indicated) SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Sat Aug 9 22:52:20 2014 PDT 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: (26400) 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: ( 266) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x7035) 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 - 0 3 Spin_Up_Time 0x0027 100 253 021 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 5 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 - 52 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 - 5 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 1 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 3 194 Temperature_Celsius 0x0022 118 116 000 Old_age Always - 29 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. == ============================================================================ Quote Link to comment
steve.c7677 Posted August 12, 2014 Share Posted August 12, 2014 I guess you did not take the time to read back a few posts: At 155 pages i didnt, thanks for taking the time pointing me in the right direction Cheers edit: actually I could have done a topic search too, so shame on me twice. I think i was rushing Quote Link to comment
squirrellydw Posted August 13, 2014 Share Posted August 13, 2014 Getting ready to pre clear a drive 3 times and just want to make sure this is correct. Drive is a HGST Deskstar NAS H3IKNAS40003272SN(0S03664) 4TB 7200 RPM 64MB Cache SATA 6.0Gb/s 3.5" High-Performance Hard Drive preclear_disk.sh -c 3 /dev/sdX X being whatever the drive letter is I need to clear Also where do the reports show up again, its been awhile since I have done this. Thanks Quote Link to comment
itimpi Posted August 13, 2014 Share Posted August 13, 2014 Sounds correct! Assuming that you are running the pre_clear script from /boot, that is where the reports will be placed on completion. A suggestion is to run preclear_disk.sh -l before doing the actual preclear to get the list of devices that are available. Helps avoid any accidents Quote Link to comment
JonathanM Posted August 13, 2014 Share Posted August 13, 2014 Getting ready to pre clear a drive 3 times and just want to make sure this is correct. Drive is a HGST Deskstar NAS H3IKNAS40003272SN(0S03664) 4TB 7200 RPM 64MB Cache SATA 6.0Gb/s 3.5" High-Performance Hard Drive preclear_disk.sh -c 3 /dev/sdX X being whatever the drive letter is I need to clear If you have email notifications set up on the machine, you can add -m [email protected] -M 4 to get real time status updates emailed to you while it's happening. Also, unmenu myMain tab will allow you to watch the progress. Quote Link to comment
squirrellydw Posted August 13, 2014 Share Posted August 13, 2014 what is the 4 in -M 4, hours?? SO it would be preclear_disk.sh -c 3 /dev/sdX -m [email protected] -M 4 Quote Link to comment
garycase Posted August 13, 2014 Share Posted August 13, 2014 what is the 4 in -M 4, hours?? No, it's the number of pre-clear cycles you want to run. If not specified, one cycle is run. Otherwise, it can be anywhere from 1 to 20 (Note that a pre-clear cycle takes a LONG time ... especially with very large disks). Quote Link to comment
JonathanM Posted August 13, 2014 Share Posted August 13, 2014 what is the 4 in -M 4, hours?? SO it would be preclear_disk.sh -c 3 /dev/sdX -m [email protected] -M 4 I use preclear_disk.sh -c 3 -m email@address -M4 /dev/sdX I'm not sure if the switches all need to be before the device to be acted on or not. The M argument tells it how often you want emails. -M 1 = Will send an e-mail message at the end of the final results (default if -m is used, but no other -M option given) -M 2 = Will send an e-mail same as 1 plus at the end of a cycle (if multiple cycles are specified) -M 3 = Will send an e-mail same as 2 plus at the start and end of the pre-read, zeroing, post-read -M 4 = Will send an e-mail same as 3 plus also at intervals of 25% during the long tests Quote Link to comment
JonathanM Posted August 13, 2014 Share Posted August 13, 2014 what is the 4 in -M 4, hours?? No, it's the number of pre-clear cycles you want to run. If not specified, one cycle is run. Otherwise, it can be anywhere from 1 to 20 (Note that a pre-clear cycle takes a LONG time ... especially with very large disks). Wrong. -c is the cycle count. 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.