garycase Posted August 13, 2014 Share Posted August 13, 2014 Whoops ... my error. The number of cycles requires a -c parameter before the number. As Jonathan noted, the argument after -M is how often you want e-mails. It's not in time ... it's simply a parameter between 1 & 4, which defines this as follows (copied from JoeL's documentation): -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
garycase Posted August 13, 2014 Share Posted August 13, 2014 Wrong. -c is the cycle count. Yes, I noticed that right after I posted ... you posted twice while I was correcting myself Quote Link to comment
JonathanM Posted August 13, 2014 Share Posted August 13, 2014 Whoops ... my error. The number of cycles requires a -C parameter before the number. -c is number of cycles, -C is used to change the start sector from 63 to 64 or vice-versa on an already precleared drive. Case is important. Quote Link to comment
squirrellydw Posted August 13, 2014 Share Posted August 13, 2014 One more question, if I want to do this preclear_disk.sh -c 3 -m email@address -M4 /dev/sdX with screen from another computer incase I lose power what would I type? My server is on a backup so I'm not to worry about it losing power but my laptop could. Thanks If it makes a difference I'm using a Mac Quote Link to comment
JonathanM Posted August 13, 2014 Share Posted August 13, 2014 One more question, if I want to do this preclear_disk.sh -c 3 -m email@address -M4 /dev/sdX with screen from another computer incase I lose power what would I type? My server is on a backup so I'm not to worry about it losing power but my laptop could. Thanks If it makes a difference I'm using a Mac If you have screen installed, you simply type screen in your telnet session, and it gives you the overview information, and you hit return or space to get back to a prompt. You then execute the preclear as mentioned, and you can hit ctrl-a then d to return to the normal prompt. If you need to get back to that screen session, just login and type screen -r and it will drop you right back where you were. Another option is to simply start the preclear at the local console if you have a monitor and keyboard attached to your server. One cool thing to note is that screen sessions are attachable from local or telnet sessions, so if you use screen at the local console, you can attach to it later using a telnet session. Quote Link to comment
squirrellydw Posted August 14, 2014 Share Posted August 14, 2014 So what should I do if my server froze over night? I didn't lose power so I don't know whats going on but I can't access it? Here is the link to the syslog, I can access the flash drive. https://www.dropbox.com/s/zn9gllhhmv4ubbu/syslog-20140813-155539.txt Quote Link to comment
trurl Posted August 14, 2014 Share Posted August 14, 2014 So what should I do if my server froze over night? I didn't lose power so I don't know whats going on but I can't access it? Do you mean you can't access the webGUI or you can't even telnet? If you mean the webGUI, since you are on v5 and were trying to preclear 4TB, it is likely ran out of memory and emhttp (webGUI) was killed. See here. If you have unMenu you may still be able to access that or at least restart it. Quote Link to comment
BobPhoenix Posted August 14, 2014 Share Posted August 14, 2014 Another option is to simply start the preclear at the local console if you have a monitor and keyboard attached to your server. One cool thing to note is that screen sessions are attachable from local or telnet sessions, so if you use screen at the local console, you can attach to it later using a telnet session. Also if you have IPMI you can get to the console remotely without having to connect a monitor and keyboard. Quote Link to comment
squirrellydw Posted August 14, 2014 Share Posted August 14, 2014 I have precleared 3TB drives before without a problem but this is the first 4TB drive I'm trying to clear. I have PMS, CP, SB, SAB and NZBDrone running. Should I have stopped those first? How should I power down my server? edit, yes I can't access the webgui, TELNET works fine it looks like. So how can I shutdown my server from telnet? I can than start it back up turn off all the plugins and try again. Quote Link to comment
trurl Posted August 14, 2014 Share Posted August 14, 2014 I have precleared 3TB drives before without a problem but this is the first 4TB drive I'm trying to clear. I have PMS, CP, SB, SAB and NZBDrone running. Should I have stopped those first? How should I power down my server? edit, yes I can't access the webgui, TELNET works fine it looks like. So how can I shutdown my server from telnet? I can than start it back up turn off all the plugins and try again. If you were running the preclear in screen you may still be able to reconnect to it and let it complete before rebooting. Do you have unMenu installed? If not then you can probably still install it from telnet. It has a powerdown script you can run and it will also let you follow the progress of preclears. You can also try /sbin/shutdown. Quote Link to comment
trurl Posted August 14, 2014 Share Posted August 14, 2014 There is this post further down in that thread I linked to that tells how to run preclear so it doesn't use as much memory. And the next few posts after that might also have useful info. Quote Link to comment
squirrellydw Posted August 14, 2014 Share Posted August 14, 2014 I got it shutdown and started clearing the drive again. I shut down everything I had running this time so we shall see what happens. Never had this problem before, but I never had PMS running on my server when I did this last time. Quote Link to comment
mnever33 Posted August 16, 2014 Share Posted August 16, 2014 Hello. I replaced my old parity drive (Seagate Barracuda XT ST32000641AS) with a new WD Red 4TB. Everything ok. Then I precleared that 2TB Seagate drive, in order to use it as Data drive. Disk /dev/sdb has been successfully precleared, but results show the following SMART errors: Aug 15 23:13:46 Tower preclear_disk-diff[27597]: ATA Error Count: 37 (device log contains only the most recent five errors) Aug 15 23:13:46 Tower preclear_disk-diff[27597]: ^ICR = Command Register [HEX] Aug 15 23:13:46 Tower preclear_disk-diff[27597]: ^IFR = Features Register [HEX] Aug 15 23:13:46 Tower preclear_disk-diff[27597]: ^ISC = Sector Count Register [HEX] Aug 15 23:13:46 Tower preclear_disk-diff[27597]: ^ISN = Sector Number Register [HEX] Aug 15 23:13:46 Tower preclear_disk-diff[27597]: ^ICL = Cylinder Low Register [HEX] Aug 15 23:13:46 Tower preclear_disk-diff[27597]: ^ICH = Cylinder High Register [HEX] Aug 15 23:13:46 Tower preclear_disk-diff[27597]: ^IDH = Device/Head Register [HEX] Aug 15 23:13:46 Tower preclear_disk-diff[27597]: ^IDC = Device Command Register [HEX] Aug 15 23:13:46 Tower preclear_disk-diff[27597]: ^IER = Error register [HEX] Aug 15 23:13:46 Tower preclear_disk-diff[27597]: ^IST = Status register [HEX] Aug 15 23:13:46 Tower preclear_disk-diff[27597]: Powered_Up_Time is measured from power on, and printed as Aug 15 23:13:46 Tower preclear_disk-diff[27597]: DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, Aug 15 23:13:46 Tower preclear_disk-diff[27597]: SS=sec, and sss=millisec. It "wraps" after 49.710 days. Aug 15 23:13:46 Tower preclear_disk-diff[27597]: Aug 15 23:13:46 Tower preclear_disk-diff[27597]: Error 37 occurred at disk power-on lifetime: 3536 hours (147 days + 8 hours) Aug 15 23:13:46 Tower preclear_disk-diff[27597]: When the command that caused the error occurred, the device was active or idle. Aug 15 23:13:46 Tower preclear_disk-diff[27597]: Aug 15 23:13:46 Tower preclear_disk-diff[27597]: After command completion occurred, registers were: Aug 15 23:13:46 Tower preclear_disk-diff[27597]: ER ST SC SN CL CH DH Aug 15 23:13:46 Tower preclear_disk-diff[27597]: -- -- -- -- -- -- -- Aug 15 23:13:46 Tower preclear_disk-diff[27597]: 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Aug 15 23:13:46 Tower preclear_disk-diff[27597]: Aug 15 23:13:46 Tower preclear_disk-diff[27597]: Commands leading to the command that caused the error were: Aug 15 23:13:46 Tower preclear_disk-diff[27597]: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name Aug 15 23:13:46 Tower preclear_disk-diff[27597]: -- -- -- -- -- -- -- -- ---------------- -------------------- Aug 15 23:13:46 Tower preclear_disk-diff[27597]: 25 00 18 ff ff ff ef 00 4d+08:17:50.204 READ DMA EXT Aug 15 23:13:46 Tower preclear_disk-diff[27597]: 25 00 60 ff ff ff ef 00 4d+08:17:50.196 READ DMA EXT Aug 15 23:13:46 Tower preclear_disk-diff[27597]: e5 00 00 00 00 00 00 00 4d+08:17:50.195 CHECK POWER MODE Aug 15 23:13:46 Tower preclear_disk-diff[27597]: 25 00 70 ff ff ff ef 00 4d+08:17:47.956 READ DMA EXT Aug 15 23:13:46 Tower preclear_disk-diff[27597]: 25 00 90 ff ff ff ef 00 4d+08:17:47.943 READ DMA EXT Aug 15 23:13:46 Tower preclear_disk-diff[27597]: Aug 15 23:13:46 Tower preclear_disk-diff[27597]: Error 36 occurred at disk power-on lifetime: 3536 hours (147 days + 8 hours) Aug 15 23:13:46 Tower preclear_disk-diff[27597]: When the command that caused the error occurred, the device was active or idle. Aug 15 23:13:46 Tower preclear_disk-diff[27597]: Aug 15 23:13:46 Tower preclear_disk-diff[27597]: After command completion occurred, registers were: Aug 15 23:13:46 Tower preclear_disk-diff[27597]: ER ST SC SN CL CH DH Aug 15 23:13:46 Tower preclear_disk-diff[27597]: -- -- -- -- -- -- -- Aug 15 23:13:46 Tower preclear_disk-diff[27597]: 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Aug 15 23:13:46 Tower preclear_disk-diff[27597]: Aug 15 23:13:46 Tower preclear_disk-diff[27597]: Commands leading to the command that caused the error were: Aug 15 23:13:46 Tower preclear_disk-diff[27597]: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name Aug 15 23:13:46 Tower preclear_disk-diff[27597]: -- -- -- -- -- -- -- -- ---------------- -------------------- Aug 15 23:13:46 Tower preclear_disk-diff[27597]: 25 00 00 ff ff ff ef 00 4d+07:22:23.100 READ DMA EXT Aug 15 23:13:46 Tower preclear_disk-diff[27597]: 27 00 00 00 00 00 e0 00 4d+07:22:23.099 READ NATIVE MAX ADDRESS EXT Aug 15 23:13:46 Tower preclear_disk-diff[27597]: ec 00 00 00 00 00 a0 00 4d+07:22:23.098 IDENTIFY DEVICE Aug 15 23:13:46 Tower preclear_disk-diff[27597]: ef 03 46 00 00 00 a0 00 4d+07:22:23.097 SET FEATURES [set transfer mode] Aug 15 23:13:46 Tower preclear_disk-diff[27597]: 27 00 00 00 00 00 e0 00 4d+07:22:23.097 READ NATIVE MAX ADDRESS EXT Aug 15 23:13:46 Tower preclear_disk-diff[27597]: Aug 15 23:13:46 Tower preclear_disk-diff[27597]: Error 35 occurred at disk power-on lifetime: 3536 hours (147 days + 8 hours) Aug 15 23:13:46 Tower preclear_disk-diff[27597]: When the command that caused the error occurred, the device was active or idle. Aug 15 23:13:46 Tower preclear_disk-diff[27597]: Aug 15 23:13:46 Tower preclear_disk-diff[27597]: After command completion occurred, registers were: Aug 15 23:13:46 Tower preclear_disk-diff[27597]: ER ST SC SN CL CH DH Aug 15 23:13:46 Tower preclear_disk-diff[27597]: -- -- -- -- -- -- -- Aug 15 23:13:46 Tower preclear_disk-diff[27597]: 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Aug 15 23:13:46 Tower preclear_disk-diff[27597]: Aug 15 23:13:46 Tower preclear_disk-diff[27597]: Commands leading to the command that caused the error were: Aug 15 23:13:46 Tower preclear_disk-diff[27597]: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name Aug 15 23:13:46 Tower preclear_disk-diff[27597]: -- -- -- -- -- -- -- -- ---------------- -------------------- Aug 15 23:13:46 Tower preclear_disk-diff[27597]: 25 00 00 ff ff ff ef 00 4d+07:22:20.125 READ DMA EXT Aug 15 23:13:46 Tower preclear_disk-diff[27597]: 27 00 00 00 00 00 e0 00 4d+07:22:20.124 READ NATIVE MAX ADDRESS EXT Aug 15 23:13:46 Tower preclear_disk-diff[27597]: ec 00 00 00 00 00 a0 00 4d+07:22:20.123 IDENTIFY DEVICE Aug 15 23:13:46 Tower preclear_disk-diff[27597]: ef 03 46 00 00 00 a0 00 4d+07:22:20.123 SET FEATURES [set transfer mode] Aug 15 23:13:46 Tower preclear_disk-diff[27597]: 27 00 00 00 00 00 e0 00 4d+07:22:20.123 READ NATIVE MAX ADDRESS EXT Aug 15 23:13:46 Tower preclear_disk-diff[27597]: Aug 15 23:13:46 Tower preclear_disk-diff[27597]: Error 34 occurred at disk power-on lifetime: 3535 hours (147 days + 7 hours) Aug 15 23:13:46 Tower preclear_disk-diff[27597]: When the command that caused the error occurred, the device was active or idle. Aug 15 23:13:46 Tower preclear_disk-diff[27597]: Aug 15 23:13:46 Tower preclear_disk-diff[27597]: After command completion occurred, registers were: Aug 15 23:13:46 Tower preclear_disk-diff[27597]: ER ST SC SN CL CH DH Aug 15 23:13:46 Tower preclear_disk-diff[27597]: -- -- -- -- -- -- -- Aug 15 23:13:46 Tower preclear_disk-diff[27597]: 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Aug 15 23:13:46 Tower preclear_disk-diff[27597]: Aug 15 23:13:46 Tower preclear_disk-diff[27597]: Commands leading to the command that caused the error were: Aug 15 23:13:46 Tower preclear_disk-diff[27597]: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name Aug 15 23:13:46 Tower preclear_disk-diff[27597]: -- -- -- -- -- -- -- -- ---------------- -------------------- Aug 15 23:13:46 Tower preclear_disk-diff[27597]: 25 00 00 ff ff ff ef 00 4d+07:22:17.129 READ DMA EXT Aug 15 23:13:46 Tower preclear_disk-diff[27597]: 27 00 00 00 00 00 e0 00 4d+07:22:17.128 READ NATIVE MAX ADDRESS EXT Aug 15 23:13:46 Tower preclear_disk-diff[27597]: ec 00 00 00 00 00 a0 00 4d+07:22:17.127 IDENTIFY DEVICE Aug 15 23:13:46 Tower preclear_disk-diff[27597]: ef 03 46 00 00 00 a0 00 4d+07:22:17.126 SET FEATURES [set transfer mode] Aug 15 23:13:46 Tower preclear_disk-diff[27597]: 27 00 00 00 00 00 e0 00 4d+07:22:17.126 READ NATIVE MAX ADDRESS EXT Aug 15 23:13:46 Tower preclear_disk-diff[27597]: Aug 15 23:13:46 Tower preclear_disk-diff[27597]: Error 33 occurred at disk power-on lifetime: 3535 hours (147 days + 7 hours) Aug 15 23:13:46 Tower preclear_disk-diff[27597]: When the command that caused the error occurred, the device was active or idle. Aug 15 23:13:46 Tower preclear_disk-diff[27597]: Aug 15 23:13:46 Tower preclear_disk-diff[27597]: After command completion occurred, registers were: Aug 15 23:13:46 Tower preclear_disk-diff[27597]: ER ST SC SN CL CH DH Aug 15 23:13:46 Tower preclear_disk-diff[27597]: -- -- -- -- -- -- -- Aug 15 23:13:46 Tower preclear_disk-diff[27597]: 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Aug 15 23:13:46 Tower preclear_disk-diff[27597]: Aug 15 23:13:46 Tower preclear_disk-diff[27597]: Commands leading to the command that caused the error were: Aug 15 23:13:46 Tower preclear_disk-diff[27597]: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name Aug 15 23:13:46 Tower preclear_disk-diff[27597]: -- -- -- -- -- -- -- -- ---------------- -------------------- Aug 15 23:13:46 Tower preclear_disk-diff[27597]: 25 00 00 ff ff ff ef 00 4d+07:22:14.055 READ DMA EXT Aug 15 23:13:46 Tower preclear_disk-diff[27597]: 27 00 00 00 00 00 e0 00 4d+07:22:14.054 READ NATIVE MAX ADDRESS EXT Aug 15 23:13:46 Tower preclear_disk-diff[27597]: ec 00 00 00 00 00 a0 00 4d+07:22:14.053 IDENTIFY DEVICE Aug 15 23:13:46 Tower preclear_disk-diff[27597]: ef 03 46 00 00 00 a0 00 4d+07:22:14.052 SET FEATURES [set transfer mode] Aug 15 23:13:46 Tower preclear_disk-diff[27597]: 27 00 00 00 00 00 e0 00 4d+07:22:14.052 READ NATIVE MAX ADDRESS EXT Should I worry about these errors? Can I safely assign this drive as a Data drive? Quote Link to comment
RobJ Posted August 16, 2014 Share Posted August 16, 2014 Hello. I replaced my old parity drive (Seagate Barracuda XT ST32000641AS) with a new WD Red 4TB. Everything ok. Then I precleared that 2TB Seagate drive, in order to use it as Data drive. Disk /dev/sdb has been successfully precleared, but results show the following SMART errors: Aug 15 23:13:46 Tower preclear_disk-diff[27597]: ATA Error Count: 37 (device log contains only the most recent five errors) ... Aug 15 23:13:46 Tower preclear_disk-diff[27597]: Aug 15 23:13:46 Tower preclear_disk-diff[27597]: Error 37 occurred at disk power-on lifetime: 3536 hours (147 days + 8 hours) ... Aug 15 23:13:46 Tower preclear_disk-diff[27597]: 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 ... ... ... Aug 15 23:13:46 Tower preclear_disk-diff[27597]: Error 33 occurred at disk power-on lifetime: 3535 hours (147 days + 7 hours) ... Aug 15 23:13:46 Tower preclear_disk-diff[27597]: 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 ... Should I worry about these errors? Can I safely assign this drive as a Data drive? We need to see the entire SMART report. This excerpt just shows the ATA error section, displaying the last 5 ATA errors, no matter how long ago they occurred. In this case, the drive reported at least 5 UNC errors, bad sectors that probably affected the reallocated sector counts (Reallocated_Sector_Ct) and/or the current pending sector (Current_Pending_Sector) counts. However these errors occurred at the 3536 and 3535 operational hour points, and you need to check the current Hours (Power_On_Hours) number, in order to know if that is recent or a very long time ago. If a long time ago, ignore it. If recent, then they should have been reported by Preclear and/or the SMART report as changes in Reallocated_Sector_Ct and/or Current_Pending_Sector. Note: this may have been a spurious error, as all 5 displayed are at the same 'apparent' sector number, with mask of 0x0fffffff, "UNC at LBA = 0x0fffffff = 268435455". Quote Link to comment
mnever33 Posted August 16, 2014 Share Posted August 16, 2014 We need to see the entire SMART report. This excerpt just shows the ATA error section, displaying the last 5 ATA errors, no matter how long ago they occurred. In this case, the drive reported at least 5 UNC errors, bad sectors that probably affected the reallocated sector counts (Reallocated_Sector_Ct) and/or the current pending sector (Current_Pending_Sector) counts. However these errors occurred at the 3536 and 3535 operational hour points, and you need to check the current Hours (Power_On_Hours) number, in order to know if that is recent or a very long time ago. If a long time ago, ignore it. If recent, then they should have been reported by Preclear and/or the SMART report as changes in Reallocated_Sector_Ct and/or Current_Pending_Sector. Note: this may have been a spurious error, as all 5 displayed are at the same 'apparent' sector number, with mask of 0x0fffffff, "UNC at LBA = 0x0fffffff = 268435455". RobJ thank you for your help! I attach the entire preclear report. preclear_results_ST32000641AS_Aug2014.txt Quote Link to comment
RobJ Posted August 17, 2014 Share Posted August 17, 2014 We need to see the entire SMART report. This excerpt just shows the ATA error section, displaying the last 5 ATA errors, no matter how long ago they occurred. In this case, the drive reported at least 5 UNC errors, bad sectors that probably affected the reallocated sector counts (Reallocated_Sector_Ct) and/or the current pending sector (Current_Pending_Sector) counts. However these errors occurred at the 3536 and 3535 operational hour points, and you need to check the current Hours (Power_On_Hours) number, in order to know if that is recent or a very long time ago. If a long time ago, ignore it. If recent, then they should have been reported by Preclear and/or the SMART report as changes in Reallocated_Sector_Ct and/or Current_Pending_Sector. Note: this may have been a spurious error, as all 5 displayed are at the same 'apparent' sector number, with mask of 0x0fffffff, "UNC at LBA = 0x0fffffff = 268435455". RobJ thank you for your help! I attach the entire preclear report. As you've probably already determined for yourself, the drive is currently showing 22,702 hours of operation. So while there was a problem at 3535 hours, a long time ago, it apparently wasn't serious and was completely resolved by the drive, without having to remap a single sector. Enjoy your drive, assign it anyway you like, as its SMART report looks fine, and the Preclear report was clean. Quote Link to comment
squirrellydw Posted August 18, 2014 Share Posted August 18, 2014 So I think this drive has no problems from what I can tell correct. Going to replace my parity drive. HGSTHDN724040ALE640 PK1334PBHWBJDX == Disk /dev/sdf has been successfully precleared == with a starting sector of 1 == Ran 3 cycles == == Using :Read block size = 8388608 Bytes == Last Cycle's Pre Read Time : 9:49:40 (113 MB/s) == Last Cycle's Zeroing time : 8:38:59 (128 MB/s) == Last Cycle's Post Read Time : 18:37:02 (59 MB/s) == Last Cycle's Total Time : 27:17:06 == == Total Elapsed Time 91:40:57 == == Disk Start Temperature: 35C == == Current Disk Temperature: 36C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdf /tmp/smart_finish_sdf ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 166 171 0 ok 36 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/sdf == Disk: /dev/sdf smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: HGST HDN724040ALE640 Serial Number: PK1334PBHWBJDX LU WWN Device Id: 5 000cca 23dda88cd Firmware Version: MJAOA5E0 User Capacity: 4,000,787,030,016 bytes [4.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Device is: Not in smartctl database [for details use: -P showall] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Thu Aug 14 10:54:42 2014 EDT 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: (0x80) Offline data collection activity was never started. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 24) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 557) minutes. SCT capabilities: (0x003d) 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 0x000b 100 100 016 Pre-fail Always - 0 2 Throughput_Performance 0x0005 136 136 054 Pre-fail Offline - 82 3 Spin_Up_Time 0x0007 100 100 024 Pre-fail Always - 0 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 4 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 121 121 020 Pre-fail Offline - 34 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 18 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 4 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 5 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 5 194 Temperature_Celsius 0x0002 171 171 000 Old_age Always - 35 (Min/Max 25/40) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 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/sdf == Disk: /dev/sdf smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: HGST HDN724040ALE640 Serial Number: PK1334PBHWBJDX LU WWN Device Id: 5 000cca 23dda88cd Firmware Version: MJAOA5E0 User Capacity: 4,000,787,030,016 bytes [4.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Device is: Not in smartctl database [for details use: -P showall] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Mon Aug 18 06:35:38 2014 EDT SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 24) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 557) minutes. SCT capabilities: (0x003d) 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 0x000b 100 100 016 Pre-fail Always - 0 2 Throughput_Performance 0x0005 136 136 054 Pre-fail Offline - 82 3 Spin_Up_Time 0x0007 100 100 024 Pre-fail Always - 0 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 4 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 121 121 020 Pre-fail Offline - 34 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 110 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 4 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 5 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 5 194 Temperature_Celsius 0x0002 166 166 000 Old_age Always - 36 (Min/Max 25/40) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 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. == preclear_rpt_PK1334PBHWBJDX_2014-08-18.txt Quote Link to comment
RobJ Posted August 18, 2014 Share Posted August 18, 2014 So I think this drive has no problems from what I can tell correct. Going to replace my parity drive. Correct. Just a question ... Those of us with SMART and Preclear experience could easily see that the Preclear was successful and the drive is excellent, but many users like yourself don't have that same experience and often post here with their results requesting confirmation of success. That would seem to indicate we could do a better job of communicating. In your opinion, are the Preclear reports too confusing, or just too much information? What if they started with something like - *** In summary *** Preclear was successful, drive is excellent. - or - Preclear was successful, but see Details for very minor issues - or - Preclear was not successful, see Details for issues *** Details *** [and full Preclear and SMART reports continue here] Quote Link to comment
squirrellydw Posted August 18, 2014 Share Posted August 18, 2014 I figured it was good from the little experience I have with it but anything to make it easier is always better. Quote Link to comment
mnever33 Posted August 18, 2014 Share Posted August 18, 2014 I have zero knowledge in interpreting preclear results but what I did was this: I compared the first preclear report of the drive (when I bought it) with the current one. They were both successful and identical except for the SMART errors I posted earlier. I guess that if these errors were important the report wouldn't be successful... But I needed your confirmation before I assign the drive, thanks again! Quote Link to comment
viperdiver Posted August 19, 2014 Share Posted August 19, 2014 I think first preclear reports are very hard to interpret. But there is a lot of good info. A basic wiki, even at the start of this thread that goes line by line through a report and shows what it means/should say would help out a lot. You can even use one that is all good, since that is likely the majority of results, which would just result in actual problems being posted here. Obviously changing the preclear report to say 'this is a good drive, don't post to the forums' would work too, but I think most people doing this would like an explanation of what they see so they can get smarter. Quote Link to comment
trurl Posted August 19, 2014 Share Posted August 19, 2014 There is this chart on wikipedia Quote Link to comment
squirrellydw Posted August 19, 2014 Share Posted August 19, 2014 I think first preclear reports are very hard to interpret. But there is a lot of good info. A basic wiki, even at the start of this thread that goes line by line through a report and shows what it means/should say would help out a lot. You can even use one that is all good, since that is likely the majority of results, which would just result in actual problems being posted here. Obviously changing the preclear report to say 'this is a good drive, don't post to the forums' would work too, but I think most people doing this would like an explanation of what they see so they can get smarter. I like this idea as long as it only reports what important and it's at the beginning of the thread. Quote Link to comment
RobJ Posted August 19, 2014 Share Posted August 19, 2014 There is this chart on wikipedia That's probably the best explanation of the various SMART attributes. Just remember that it is general info concerning many drives from many vendors, both older and newer. Each drive has its own differing subset of the attributes, and they may not be used consistently. THERE IS NO STANDARD USAGE! I think first preclear reports are very hard to interpret. But there is a lot of good info. A basic wiki, even at the start of this thread that goes line by line through a report and shows what it means/should say would help out a lot. You can even use one that is all good, since that is likely the majority of results, which would just result in actual problems being posted here. Obviously changing the preclear report to say 'this is a good drive, don't post to the forums' would work too, but I think most people doing this would like an explanation of what they see so they can get smarter. I started such a wiki tool, found at Understanding SMART Reports. Unfortunately, like almost all of my projects (I'm severe ADHD and either Aspergers or brain damaged), it was not finished, is incomplete especially in the attribute section, but it will give you (I think!) a good background on SMART and SMART reports. At the bottom of the wiki page are more reference links about SMART. At the moment, the wiki is locked, read-only, but once editable again, I'll try to complete the page. I would like to ask Joe L to consider adding the changes I suggested, that included among other things, removing the spurious 'near_thresh' warnings from the Preclear reports. We've understood the problem since almost when they first began appearing, and I *think* we all agree they are a source of confusion. Quote Link to comment
SSD Posted August 20, 2014 Share Posted August 20, 2014 ...I started such a wiki tool, found at Understanding SMART Reports. ... RobJ - great job! Great info so far, and once complete this will be an outstanding resource!!! I will be adding a link from myMain. 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.