bcbgboy13 Posted June 19, 2011 Share Posted June 19, 2011 I am running the 12 beta on a brand new 3TB Hitachi green HD. There was a 6 to 11 MB/s difference in the speed reported from the console (higher) than the myMain at one point. This difference has grown now to 40 MB/s during the post-read. myMain speed is given as 51 MB/s while the console is showing around 91 MB/s ( at the 58% done post-read -around 28h:30min mark) Will report later once it is done. After it is done, and before assigning the drive to the unRAID array, you can post the results of this command to assist me in knowing if it worked as expected on your 3 TB drive: dd if=/dev/sda count=1 2>/dev/null | od -x -A x (substituting your disk for /dev/sda ) The report: Jun 18 21:27:21 unraid preclear_disk-diff[16035]: ========================================================================1.12 Jun 18 21:27:21 unraid preclear_disk-diff[16035]: == invoked as: ./preclear_disk1.12beta.sh -A /dev/sdb Jun 18 21:27:21 unraid preclear_disk-diff[16035]: == Hitachi HDS5C3030ALA630 MJ1311YNG258NA Jun 18 21:27:21 unraid preclear_disk-diff[16035]: == Disk /dev/sdb has been successfully precleared Jun 18 21:27:21 unraid preclear_disk-diff[16035]: == with a starting sector of 1 Jun 18 21:27:21 unraid preclear_disk-diff[16035]: == Ran 1 cycle Jun 18 21:27:21 unraid preclear_disk-diff[16035]: == Jun 18 21:27:21 unraid preclear_disk-diff[16035]: == Using :Read block size = 8225280 Bytes Jun 18 21:27:21 unraid preclear_disk-diff[16035]: == Last Cycle's Pre Read Time : 9:42:34 (85 MB/s) Jun 18 21:27:21 unraid preclear_disk-diff[16035]: == Last Cycle's Zeroing time : 9:26:21 (88 MB/s) Jun 18 21:27:21 unraid preclear_disk-diff[16035]: == Last Cycle's Post Read Time : 18:50:50 (44 MB/s) Jun 18 21:27:21 unraid preclear_disk-diff[16035]: == Last Cycle's Total Time : 38:00:54 Jun 18 21:27:21 unraid preclear_disk-diff[16035]: == Jun 18 21:27:21 unraid preclear_disk-diff[16035]: == Total Elapsed Time 38:00:54 Jun 18 21:27:21 unraid preclear_disk-diff[16035]: == Jun 18 21:27:21 unraid preclear_disk-diff[16035]: == Disk Start Temperature: 29C Jun 18 21:27:21 unraid preclear_disk-diff[16035]: == Jun 18 21:27:21 unraid preclear_disk-diff[16035]: == Current Disk Temperature: 32C, Jun 18 21:27:21 unraid preclear_disk-diff[16035]: == Jun 18 21:27:21 unraid preclear_disk-diff[16035]: ============================================================================ Jun 18 21:27:21 unraid preclear_disk-diff[16035]: ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb Jun 18 21:27:21 unraid preclear_disk-diff[16035]: ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Jun 18 21:27:21 unraid preclear_disk-diff[16035]: Temperature_Celsius = 187 206 0 ok 32 Jun 18 21:27:21 unraid preclear_disk-diff[16035]: No SMART attributes are FAILING_NOW Jun 18 21:27:21 unraid preclear_disk-diff[16035]: Jun 18 21:27:21 unraid preclear_disk-diff[16035]: 0 sectors were pending re-allocation before the start of the preclear. Jun 18 21:27:21 unraid preclear_disk-diff[16035]: 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. Jun 18 21:27:21 unraid preclear_disk-diff[16035]: 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. Jun 18 21:27:21 unraid preclear_disk-diff[16035]: 0 sectors are pending re-allocation at the end of the preclear, Jun 18 21:27:21 unraid preclear_disk-diff[16035]: the number of sectors pending re-allocation did not change. Jun 18 21:27:21 unraid preclear_disk-diff[16035]: 0 sectors had been re-allocated before the start of the preclear. Jun 18 21:27:21 unraid preclear_disk-diff[16035]: 0 sectors are re-allocated at the end of the preclear, Jun 18 21:27:21 unraid preclear_disk-diff[16035]: the number of sectors re-allocated did not change. Jun 18 21:27:21 unraid preclear_disk-diff[16035]: ============================================================================ The output of the command: dd if=/dev/sdb count=1 2>/dev/null | od -x -A x 000000 0000 0000 0000 0000 0000 0000 0000 0000 * 0001c0 0002 ff00 ffff 0001 0000 ffff ffff 0000 0001d0 0000 0000 0000 0000 0000 0000 0000 0000 * 0001f0 0000 0000 0000 0000 0000 0000 0000 aa55 000200 Quote Link to comment
SSD Posted June 19, 2011 Share Posted June 19, 2011 ... MyMain is reporting a cummulative speed that takes into account not only the I/O command speed, but the other commands in the telnet script. The speed on the post read is considerably less due to the checking that the data is all zeros. Quote Link to comment
Joe L. Posted June 19, 2011 Share Posted June 19, 2011 The output of the command: dd if=/dev/sdb count=1 2>/dev/null | od -x -A x 000000 0000 0000 0000 0000 0000 0000 0000 0000 * 0001c0 0002 ff00 ffff 0001 0000 ffff ffff 0000 0001d0 0000 0000 0000 0000 0000 0000 0000 0000 * 0001f0 0000 0000 0000 0000 0000 0000 0000 aa55 000200 That is as Tom @ lime-tech described it needs to be in his communication to me about the GPT protective MBR pre-clear signature. Quote Link to comment
madburg Posted June 20, 2011 Share Posted June 20, 2011 Hitachi 3TB 5K drive running a "dd if=/dev/sdb count=1 2>/dev/null | od -x -A x" after short preclear test via 1.12 beta the results I sent Joe L. were: 000000 0001 0000 0000 0000 0000 0000 0000 0000 000010 0000 0000 0000 0000 0000 0000 0000 0000 * 0001c0 0002 ff00 ffff 0001 0000 ffff ffff 0000 0001d0 0000 0000 0000 0000 0000 0000 0000 0000 * 0001f0 0000 0000 0000 0000 0000 0000 0000 aa55 000200 After completing a successfuly 2 Cycle preclear via 1.12Beta (Total Elapsed Time: 66:18:08), results of "dd if=/dev/sdb count=1 2>/dev/null | od -x -A x" were: 000000 0000 0000 0000 0000 0000 0000 0000 0000 * 0001c0 0002 ff00 ffff 0001 0000 ffff ffff 0000 0001d0 0000 0000 0000 0000 0000 0000 0000 0000 * 0001f0 0000 0000 0000 0000 0000 0000 0000 aa55 000200 Not sure where this is at, from other responses, so I did not try to add this to the unRAID array yet. Holding for direction from Joe L. what I should do next. I am trying to understand who is actually generating the GPT GUID and stamping it? Is preclear doing this and unRAID is supposed to pick it up, or something completely different... Quote Link to comment
Joe L. Posted June 20, 2011 Share Posted June 20, 2011 Hitachi 3TB 5K drive running a "dd if=/dev/sdb count=1 2>/dev/null | od -x -A x" after short preclear test via 1.12 beta the results I sent Joe L. were: 000000 0001 0000 0000 0000 0000 0000 0000 0000 000010 0000 0000 0000 0000 0000 0000 0000 0000 * 0001c0 0002 ff00 ffff 0001 0000 ffff ffff 0000 0001d0 0000 0000 0000 0000 0000 0000 0000 0000 * 0001f0 0000 0000 0000 0000 0000 0000 0000 aa55 000200 After completing a successfuly 2 Cycle preclear via 1.12Beta (Total Elapsed Time: 66:18:08), results of "dd if=/dev/sdb count=1 2>/dev/null | od -x -A x" were: 000000 0000 0000 0000 0000 0000 0000 0000 0000 * 0001c0 0002 ff00 ffff 0001 0000 ffff ffff 0000 0001d0 0000 0000 0000 0000 0000 0000 0000 0000 * 0001f0 0000 0000 0000 0000 0000 0000 0000 aa55 000200 Not sure where this is at, from other responses, so I did not try to add this to the unRAID array yet. Holding for direction from Joe L. what I should do next. I am trying to understand who is actually generating the GPT GUID and stamping it? Is preclear doing this and unRAID is supposed to pick it up, or something completely different... Those are both exactly as expected. The first is not a valid pre-clear signature, but then you did not perform the full-pre-clear. It is exactly as expected with the short test. The second is a valid pre-clear signature as described by Tom @ lime-technologies. The GPT protective MBR (first 512 bytes you dumped) was written by the pre-clear script. The actual GPT will be written when you assign the drive to the array. I suspect you'll find the same as bjp999, that unRAID will not respect the preclear signature but proceed to clear the drive again. You array will be off-line for 7 or so hours while this is occurring, so do not add the drive when the family is expecting to watch a movie. Do it before retiring for bed. That way, if it does clear the drive, the array will be ready again the next morning. Joe L. Quote Link to comment
madburg Posted June 20, 2011 Share Posted June 20, 2011 The actual GPT will be written when you assign the drive to the array. Do you think or can you confirm with Tom, maybe as the code is right now when unRAID see's a drive >2TB (or 2.2) it expects to see not only the GPT (table) but a GUID in that GPT and if it does not see a GUID in that GPT, then it believes it needs to be cleared...? I am assuming this based on reading the wiki "GPT retains the MBR entry as the first sector on the disk followed by a primary partition table header, the actual beginning of a GPT." OR Maybe Also per wiki "GPT also provides redundancy, writing the GPT header and partition table both at the beginning and at the end of the disk.". Could Tom have forgotten to meantion the second GPT to you, maybe? Quote Link to comment
Joe L. Posted June 20, 2011 Share Posted June 20, 2011 The actual GPT will be written when you assign the drive to the array. Do you think or can you confirm with Tom, maybe as the code is right now when unRAID see's a drive >2TB (or 2.2) it expects to see not only the GPT (table) but a GUID in that GPT and if it does not see a GUID in that GPT, then it believes it needs to be cleared...? I am assuming this based on reading the wiki "GPT retains the MBR entry as the first sector on the disk followed by a primary partition table header, the actual beginning of a GPT." OR Maybe Also per wiki "GPT also provides redundancy, writing the GPT header and partition table both at the beginning and at the end of the disk.". Could Tom have forgotten to mention the second GPT to you, maybe? No, he did not forget the second GPT. Both copies of the GPT are created when the GPT partition is created. He specifically said only the MBR is to be populated when pre-cleared, exactly as I am,and the remainder of the disk all zeros. I have no way to contact Tom that you do not have. PM or email to [email protected]. The actual logic to when to use a GPT partition is when the disk size in blocks is greater than or equal to 0xFFFFFFFF You can still have an MBR based partition if the disk is < 2.2TB, or if the disk reports its size in 4k blocks you can have a 16TB disk with an MBR only partition. (problem is, no disk reports its blocks as 4k. They all revert to reporting their size in 512 byte blocks. Too much embedded logic around that 512 byte size in the bios and disk drivers I suppose.) all you can do at this point is send Tom an e-mail, point him to this thread and see if he responds, or try adding the 3TB precleared disk without waiting. If it does not get recognized, it will just mean you array will be offline for 7 hours or so while it writes zeros to it again.. Quote Link to comment
madburg Posted June 20, 2011 Share Posted June 20, 2011 I have no issue just adding this drive even if I have to wait 7 hours, I am in no great rush at the moment. The drive precleared successfuly so I know it does not have to be RMA'ed. Thats all that mattered at the moment, many thanks to your script. Its just I believe its a good idea to nip this in the bud while Tom gave us this first cut with 3TB support, and fixing a bunch of other stuff he meantioned in the latest beta thread. I am sure he supports your efforts as otherwise without it there would need to be a large disclosure of just how long ones array could be down while adding a large disk to an array. Not a great selling point. I figured your communication with him (more techy and same level plain) would be more key than mine just saying it don't work... I am offerring HW/SW testing as thats all I can offer for this subject. Do support your efforts in every way. Quote Link to comment
Joe L. Posted June 20, 2011 Share Posted June 20, 2011 I have no issue just adding this drive even if I have to wait 7 hours, I am in no great rush at the moment. The drive precleared successfuly so I know it does not have to be RMA'ed. Thats all that mattered at the moment, many thanks to your script. Its just I believe its a good idea to nip this in the bud while Tom gave us this first cut with 3TB support, and fixing a bunch of other stuff he meantioned in the latest beta thread. I am sure he supports your efforts as otherwise without it there would need to be a large disclosure of just how long ones array could be down while adding a large disk to an array. Not a great selling point. I figured your communication with him (more techy and same level plain) would be more key than mine just saying it don't work... I am offerring HW/SW testing as thats all I can offer for this subject. Do support your efforts in every way. Actually, even 7 hours is a short time compared to many other RAID implementations when you have to break the raid array and rebuild it. For an array of 3TB drives, it would be a LONG time. At one point, Tom sold pre-cleared/burned in drives. My original pair of Hitachi 500Gig drives were supplied by him when I purchased my server from him 5+years ago. The drives were $300+ each. We've come a long way now that a 2TB on sale is > $70. Add the drive, see what happens. Two reports of the software not recognizing the pre-clear signature will help to convince him. But need to point him to this thread, or, better yet, post in the announcement thread for 5.0beta7. Quote Link to comment
madburg Posted June 21, 2011 Share Posted June 21, 2011 Thanks Joe L. I just posted in the 5.0Beta7 announcement page, I assigned my 3TB precleared drive to the array it took! Log is attached there. Page 16 on the forum. Beautiful job Joe L.! Many thanks as always (getting old but u deserve it ), and for those that dont know Joe L. has added the ability to detect hd% or sd% drives with out having to worry about the -A option I got it all wrong Joe L. explaination of addition below (correct me if & were I am wrong Joe L.) as of 1.12beta of his script, its a beautiful thing. Quote Link to comment
Joe L. Posted June 21, 2011 Share Posted June 21, 2011 Thanks Joe L. I just posted in the 5.0Beta7 announcement page, I assigned my 3TB precleared drive to the array it took! Log is attached there. Page 16 on the forum. Beautiful job Joe L.! Many thanks as always (getting old but u deserve it ), and for those that dont know Joe L. has added the ability to detect hd% or sd% drives with out having to worry about the -A option (correct me if & were I am wrong Joe L.) as of 1.12beta of his script, its a beautiful thing. It never cared about hda vs. sda disks. It was always using the "-d ata" option to the smartctl command it uses. That was necessary on much of the hardware over the past 5 years. In other words, the drive behind the SATA or IDE controller was an ATA command set. Now, with a newer smartctl version it autodetects the disk better and the "-d ata" is no longer needed and in fact gets in the way with some chipsets. The 1.12beta version of the preclear script first tries the smartctl command without the "-d ata" and if it works without it, it does not use it. If it does not work, it tries with "-d ata". Joe L. Quote Link to comment
pickthenimp Posted June 21, 2011 Share Posted June 21, 2011 Hey guys, new to preclearing here. I have looked all over for any kind of cheat sheet or a "How to interpret your preclear results" guide. I got my email saying "Preclear PASS!" but after reading through a few posts in this thread there is clearly a lot of things to consider. Any help is greatly appreciated. Quote Link to comment
Superorb Posted June 21, 2011 Share Posted June 21, 2011 Hey guys, new to preclearing here. I have looked all over for any kind of cheat sheet or a "How to interpret your preclear results" guide. I got my email saying "Preclear PASS!" but after reading through a few posts in this thread there is clearly a lot of things to consider. Any help is greatly appreciated. The important thing to look for (besides PASS/FAIL) is the amount of reallocated sectors. If the numbers go up at the end compared to the beginning, your drive might be on its way out. If the number goes down, but doesn't disappear, you might want to run another few cycles to try to get them to zero out. Quote Link to comment
pickthenimp Posted June 21, 2011 Share Posted June 21, 2011 The important thing to look for (besides PASS/FAIL) is the amount of reallocated sectors. If the numbers go up at the end compared to the beginning, your drive might be on its way out. If the number goes down, but doesn't disappear, you might want to run another few cycles to try to get them to zero out. Easy Enough! Thanks Quote Link to comment
dgaschk Posted June 29, 2011 Share Posted June 29, 2011 I don't understand why preclear is reporting a smartctl problem. When I run smarctl manually it seems to work fine. root@192:/boot# preclear_disk.sh /dev/sdc Pre-Clear unRAID Disk /dev/sdc ################################################################## 1.11 smartctl may not be able to run on /dev/sdc with the -d ata option. however this should not affect the clearing of a disk. smartctl exit status = 4 smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Seagate DB35.3 Series Device Model: ST3160215SCE Serial Number: 5RX1MFTP Firmware Version: 3.ACF User Capacity: 160,041,885,696 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Wed Jun 29 13:55:16 2011 PDT SMART support is: Available - device has SMART capability. SMART support is: Enabled Error SMART Status command failed Please get assistance from http://smartmontools.sourceforge.net/ Register values returned from SMART Status command are: ST =0x40 ERR=0x00 NS =0x00 SC =0xa0 CL =0x9e CH =0xa1 SEL=0x40 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'): root@192:/boot# smartctl -d ata -a /dev/sdc smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Seagate DB35.3 Series Device Model: ST3160215SCE Serial Number: 5RX1MFTP Firmware Version: 3.ACF User Capacity: 160,041,885,696 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Wed Jun 29 13:55:48 2011 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 See vendor-specific Attribute list for marginal Attributes. General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. 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: (15556) 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: ( 54) minutes. SCT capabilities: (0x0031) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 115 072 006 Pre-fail Always - 92652310 3 Spin_Up_Time 0x0003 098 097 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 79 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 087 060 030 Pre-fail Always - 498343952 9 Power_On_Hours 0x0032 086 086 000 Old_age Always - 12374 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 79 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 064 044 045 Old_age Always In_the_past 36 (Lifetime Min/Max 35/36) 194 Temperature_Celsius 0x0022 036 056 000 Old_age Always - 36 (0 11 0 0) 195 Hardware_ECC_Recovered 0x001a 115 064 000 Old_age Always - 92652310 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0 202 Data_Address_Mark_Errs 0x0032 100 253 000 Old_age Always - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 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. root@192:/boot# Why am I seeing this problem? Quote Link to comment
prostuff1 Posted June 29, 2011 Share Posted June 29, 2011 Is the drive hanging off a SASLP card? or possibly another SATA card? Those cards don't like the arguments passed with smartctl and therefore the issue you are seeing. Quote Link to comment
Joe L. Posted June 29, 2011 Share Posted June 29, 2011 I don't understand why preclear is reporting a smartctl problem. When I run smarctl manually it seems to work fine. root@192:/boot# preclear_disk.sh /dev/sdc Pre-Clear unRAID Disk /dev/sdc ################################################################## 1.11 smartctl may not be able to run on /dev/sdc with the -d ata option. however this should not affect the clearing of a disk. smartctl exit status = 4 smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Seagate DB35.3 Series Device Model: ST3160215SCE Serial Number: 5RX1MFTP Firmware Version: 3.ACF User Capacity: 160,041,885,696 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Wed Jun 29 13:55:16 2011 PDT SMART support is: Available - device has SMART capability. SMART support is: Enabled Error SMART Status command failed Please get assistance from http://smartmontools.sourceforge.net/ Register values returned from SMART Status command are: ST =0x40 ERR=0x00 NS =0x00 SC =0xa0 CL =0x9e CH =0xa1 SEL=0x40 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'): root@192:/boot# smartctl -d ata -a /dev/sdc smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Seagate DB35.3 Series Device Model: ST3160215SCE Serial Number: 5RX1MFTP Firmware Version: 3.ACF User Capacity: 160,041,885,696 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Wed Jun 29 13:55:48 2011 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 See vendor-specific Attribute list for marginal Attributes. General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. 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: (15556) 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: ( 54) minutes. SCT capabilities: (0x0031) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 115 072 006 Pre-fail Always - 92652310 3 Spin_Up_Time 0x0003 098 097 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 79 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 087 060 030 Pre-fail Always - 498343952 9 Power_On_Hours 0x0032 086 086 000 Old_age Always - 12374 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 79 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 064 044 045 Old_age Always In_the_past 36 (Lifetime Min/Max 35/36) 194 Temperature_Celsius 0x0022 036 056 000 Old_age Always - 36 (0 11 0 0) 195 Hardware_ECC_Recovered 0x001a 115 064 000 Old_age Always - 92652310 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0 202 Data_Address_Mark_Errs 0x0032 100 253 000 Old_age Always - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 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. root@192:/boot# Why am I seeing this problem? When you run the command, are you checking its exit status? the preclear script is, and your smartctl is exiting with a non-zero exit status. Try the 1.12 version of the preclear_disk.sh script attached to this post: http://lime-technology.com/forum/index.php?topic=4068.msg128289#msg128289 It is version 1.12... I had originally posted it there to allow those with 3TB drives to give it a try, but it also should fix your issue too. (as long as your disk will report with just smartctl -a /dev/sdX ) Quote Link to comment
dgaschk Posted June 29, 2011 Share Posted June 29, 2011 The drive is on a SASLP card. The 1.12 version started without complaint. Quote Link to comment
slarco Posted June 30, 2011 Share Posted June 30, 2011 I just added a new disk, can anyone tell me if the Preclear results looks normal? Thx syslog-2011--06-29.txt Quote Link to comment
Joe L. Posted July 1, 2011 Share Posted July 1, 2011 I just added a new disk, can anyone tell me if the Preclear results looks normal? Thx perfectly normal, BUT your version of the preclear script is probably at least 10 versions old. Please always download and use the newest one. Quote Link to comment
slarco Posted July 1, 2011 Share Posted July 1, 2011 I just added a new disk, can anyone tell me if the Preclear results looks normal? Thx perfectly normal, BUT your version of the preclear script is probably at least 10 versions old. Please always download and use the newest one. Dang, I didn't know. I am going to look for the newest version right now. Thx Joe Quote Link to comment
Joe L. Posted July 1, 2011 Share Posted July 1, 2011 I just added a new disk, can anyone tell me if the Preclear results looks normal? Thx perfectly normal, BUT your version of the preclear script is probably at least 10 versions old. Please always download and use the newest one. Dang, I didn't know. I am going to look for the newest version right now. Thx Joe Actually, very newest is here: http://lime-technology.com/forum/index.php?topic=4068.msg128289#msg128289 It still is in need of a few wording changes when used with a 3TB drive, as it still refers to the resulting partition starting on sector 64 on a >2.2TB drive, but it is entirely functional even if it "fibs" when you use it with a 3TB drive. Quote Link to comment
MrLondon Posted July 5, 2011 Share Posted July 5, 2011 I just precleared an existing Samsung F4 drive and it says it failed, but I don't know why Disk: /dev/sdh smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: SAMSUNG HD204UI Serial Number: S2HGJ1AZ801624 Firmware Version: 1AQ10001 User Capacity: 2,000,398,934,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Not recognized. Minor revision code: 0x28 Local Time is: Tue Jul 5 21:56:32 2011 BST ==> WARNING: May need -F samsung or -F samsung2 enabled; see manual for details. 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: (21060) 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: ( 2) minutes. Extended self-test routine recommended polling time: ( 255) minutes. SCT capabilities: (0x003f) 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 100 051 Pre-fail Always - 0 2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0 3 Spin_Up_Time 0x0023 067 067 025 Pre-fail Always - 10020 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 189 5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0 8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 1572 10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 252 252 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 183 181 Unknown_Attribute 0x0022 098 098 000 Old_age Always - 45803486 191 G-Sense_Error_Rate 0x0022 100 100 000 Old_age Always - 2 192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0 194 Temperature_Celsius 0x0002 064 064 000 Old_age Always - 33 (Lifetime Min/Max 21/36) 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always - 0 196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 252 252 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0036 100 100 000 Old_age Always - 2 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 0 223 Load_Retry_Count 0x0032 252 252 000 Old_age Always - 0 225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 189 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 (0) should be 1 SMART Selective self-test log data structure revision number 0 Warning: ATA Specification requires selective self-test log data structure revision number = 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Completed [00% left] (0-65535) 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
Joe L. Posted July 6, 2011 Share Posted July 6, 2011 I just precleared an existing Samsung F4 drive and it says it failed, but I don't know why Disk: /dev/sdh smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: SAMSUNG HD204UI Serial Number: S2HGJ1AZ801624 Firmware Version: 1AQ10001 User Capacity: 2,000,398,934,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Not recognized. Minor revision code: 0x28 Local Time is: Tue Jul 5 21:56:32 2011 BST ==> WARNING: May need -F samsung or -F samsung2 enabled; see manual for details. 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: (21060) 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: ( 2) minutes. Extended self-test routine recommended polling time: ( 255) minutes. SCT capabilities: (0x003f) 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 100 051 Pre-fail Always - 0 2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0 3 Spin_Up_Time 0x0023 067 067 025 Pre-fail Always - 10020 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 189 5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0 8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 1572 10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 252 252 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 183 181 Unknown_Attribute 0x0022 098 098 000 Old_age Always - 45803486 191 G-Sense_Error_Rate 0x0022 100 100 000 Old_age Always - 2 192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0 194 Temperature_Celsius 0x0002 064 064 000 Old_age Always - 33 (Lifetime Min/Max 21/36) 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always - 0 196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 252 252 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0036 100 100 000 Old_age Always - 2 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 0 223 Load_Retry_Count 0x0032 252 252 000 Old_age Always - 0 225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 189 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 (0) should be 1 SMART Selective self-test log data structure revision number 0 Warning: ATA Specification requires selective self-test log data structure revision number = 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Completed [00% left] (0-65535) 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. where does it say it failed? I don't see it. Please attach the preclear report. Without it I'm unable to interpret what you are seeing. It should be in the preclear_reports directory on your flash drive. Quote Link to comment
MrLondon Posted July 6, 2011 Share Posted July 6, 2011 the unmenu shows not successful, here is the report and screenshot preclear_finish__S2HGJ1AZ801624_2011-07-05.zip 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.