3doubled Posted February 7, 2011 Share Posted February 7, 2011 I am running 4.7. The preclear using the -A option is now running, I will let you know whether it is successful or whether it ends in an error like the last attempt using the old (ancient?) preclear script. My fingers are crossed. Quote Link to comment
jeff.lebowski Posted February 8, 2011 Share Posted February 8, 2011 I accessed the unRAID Main page, stopped the array, then went to the Devices page, and unassigned the disk to be pre-cleared. I then saw an X under status, and Unknown 0K under type. Is that what is supposed to be there? The pre-clear appears to be running normally. The unRAID main page has DISK_DSBL_NP in the Array Disk Status section. The other four disks are listed as OK. Quote Link to comment
Joe L. Posted February 8, 2011 Share Posted February 8, 2011 I accessed the unRAID Main page, stopped the array, then went to the Devices page, and unassigned the disk to be pre-cleared. I then saw an X under status, and Unknown 0K under type. Is that what is supposed to be there? The pre-clear appears to be running normally. The unRAID main page has DISK_DSBL_NP in the Array Disk Status section. The other four disks are listed as OK. NP = not present = currently un-assigned. It is expected. It will go back to OK once you re-assign and re-construct the disk. Oh yes, I did find the issue that caused the smartctl error you encountered. Your errors capture provided me the clue I needed. Thanks. I'll be putting out version 1.5 of the preclear script shortly. It was a typo on my part. It it errors out again, invoke it like this: preclear_disk.sh -d ata -A /dev/sdX It will work around the fact I did not initialize the device type correctly in version 1.4. Joe L. Quote Link to comment
jeff.lebowski Posted February 8, 2011 Share Posted February 8, 2011 Thanks yet again, Joe. Quote Link to comment
3doubled Posted February 8, 2011 Share Posted February 8, 2011 I'll be putting out version 1.5 of the preclear script shortly. Cool! I'm glad a few hours of me banging my head against the desk amounted to something useful for a change Thanks for all your hard work on this script, it is a great program! Quote Link to comment
3doubled Posted February 8, 2011 Share Posted February 8, 2011 So the preclear on that 2TB EARS drive failed again. This time I used "preclear_disk.sh -A /dev/sdX" as I mentioned in my previous post. I've attached the preclear output, please let me know what you think. I'm thinking this drive is unreliable and I'll have to RMA it. It is especially annoying that when it freezes up, I have to reboot the server to gain access to it again. I've also attached the SMART report from the beginning of the preclear. I don't think there is much of interest there other than the "not in smartctl database" error... but I'll leave the final judgment to the experts. I also might add that this drive is connected to a Supermicro AOC-SAT2-MV8. Thanks! **Edit** I just took a look at my syslog and I've got a ton of red lines. I'd attach my full syslog, but it is 624MB (and growing). It just keeps repeating the same set of errors many times a second. I can't even open the .txt file its so large. I can tell from the log that it is coming from /dev/sdb... which is that 2TB EARS drive. Could these errors just be the result of the drive being non-responsive? Feb 8 10:53:27 Tower kernel: ata1: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 (Drive related) Feb 8 10:53:27 Tower kernel: ata1: status=0x41 { DriveReady Error } (Errors) Feb 8 10:53:27 Tower kernel: ata1: error=0x04 { DriveStatusError } (Errors) Feb 8 10:53:27 Tower kernel: ata1: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 (Drive related) Feb 8 10:53:27 Tower kernel: ata1: status=0x41 { DriveReady Error } (Errors) Feb 8 10:53:27 Tower kernel: ata1: error=0x04 { DriveStatusError } (Errors) Feb 8 10:53:27 Tower kernel: ata1: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 (Drive related) Feb 8 10:53:27 Tower kernel: ata1: status=0x41 { DriveReady Error } (Errors) Feb 8 10:53:27 Tower kernel: ata1: error=0x04 { DriveStatusError } (Errors) Feb 8 10:53:27 Tower kernel: ata1: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 (Drive related) Feb 8 10:53:27 Tower kernel: ata1: status=0x41 { DriveReady Error } (Errors) Feb 8 10:53:27 Tower kernel: ata1: error=0x04 { DriveStatusError } (Errors) Feb 8 10:53:27 Tower kernel: ata1: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 (Drive related) Feb 8 10:53:27 Tower kernel: ata1: status=0x41 { DriveReady Error } (Errors) Feb 8 10:53:27 Tower kernel: ata1: error=0x04 { DriveStatusError } (Errors) Feb 8 10:53:27 Tower kernel: ata1: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 (Drive related) Feb 8 10:53:27 Tower kernel: ata1: status=0x41 { DriveReady Error } (Errors) Feb 8 10:53:27 Tower kernel: ata1: error=0x04 { DriveStatusError } (Errors) Feb 8 10:53:27 Tower kernel: ata1: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 (Drive related) Feb 8 10:53:27 Tower kernel: ata1: status=0x41 { DriveReady Error } (Errors) Feb 8 10:53:27 Tower kernel: ata1: error=0x04 { DriveStatusError } (Errors) Feb 8 10:53:27 Tower kernel: ata1: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00 (Drive related) Feb 8 10:53:27 Tower kernel: ata1: status=0x41 { DriveReady Error } (Errors) Feb 8 10:53:27 Tower kernel: ata1: error=0x04 { DriveStatusError } (Errors) Feb 8 10:53:27 Tower kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 (Drive related) Feb 8 10:53:27 Tower kernel: ata1: status=0x51 { DriveReady SeekComplete Error } (Errors) Feb 8 10:53:27 Tower kernel: ata1: error=0x04 { DriveStatusError } (Errors) Feb 8 10:53:27 Tower kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 (Drive related) Feb 8 10:53:27 Tower kernel: ata1: status=0x51 { DriveReady SeekComplete Error } (Errors) Feb 8 10:53:27 Tower kernel: ata1: error=0x04 { DriveStatusError } (Errors) Feb 8 10:53:27 Tower kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 (Drive related) Feb 8 10:53:27 Tower kernel: ata1: status=0x51 { DriveReady SeekComplete Error } (Errors) Feb 8 10:53:27 Tower kernel: ata1: error=0x04 { DriveStatusError } (Errors) Feb 8 10:53:27 Tower kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 (Drive related) Feb 8 10:53:27 Tower kernel: ata1: status=0x51 { DriveReady SeekComplete Error } (Errors) Feb 8 10:53:27 Tower kernel: ata1: error=0x04 { DriveStatusError } (Errors) Feb 8 10:53:27 Tower kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 (Drive related) Feb 8 10:53:27 Tower kernel: ata1: status=0x51 { DriveReady SeekComplete Error } (Errors) Feb 8 10:53:27 Tower kernel: ata1: error=0x04 { DriveStatusError } (Errors) Feb 8 10:53:27 Tower kernel: ata1: translated ATA stat/err 0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00 (Drive related) Feb 8 10:53:27 Tower kernel: ata1: status=0x51 { DriveReady SeekComplete Error } (Errors) Feb 8 10:53:27 Tower kernel: ata1: error=0x04 { DriveStatusError } (Errors) 2TB-EARS-FAIL.txt smart_start_sdb.txt Quote Link to comment
Joe L. Posted February 8, 2011 Share Posted February 8, 2011 I'll be putting out version 1.5 of the preclear script shortly. Cool! I'm glad a few hours of me banging my head against the desk amounted to something useful for a change Thanks for all your hard work on this script, it is a great program! Version 1.5 of the preclear script is in place attached to the original post. - I fixed the bug you discovered, - I added the model/serial number of the disk to the output report stored in the preclear_reports subdirectory. (The device name might change over time, but the model/serial number will allow you to know which drive was reported on if looking at the files at some future time) - A added intermediate reports of sectors pending re-allocation. We should now be able to tell if they are being discovered in the post-read phase. Joe L. Quote Link to comment
Joe L. Posted February 8, 2011 Share Posted February 8, 2011 So the preclear on that 2TB EARS drive failed again. This time I used "preclear_disk.sh -A /dev/sdX" as I mentioned in my previous post. I've attached the preclear output, please let me know what you think. I'm thinking this drive is unreliable and I'll have to RMA it. It is especially annoying that when it freezes up, I have to reboot the server to gain access to it again. I'm thinking you are right. The errors in the syslog are a result of the attempts to communicate with the disk failing. Quote Link to comment
jeff.lebowski Posted February 8, 2011 Share Posted February 8, 2011 The old report: ========================================================================1.4 == invoked as: ./preclear_disk.sh -A /dev/sdc == == Disk /dev/sdc has been successfully precleared == with a starting sector of 64 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 7:23:44 (75 MB/s) == Last Cycle's Zeroing time : 6:47:41 (81 MB/s) == Last Cycle's Post Read Time : 15:00:12 (37 MB/s) == Last Cycle's Total Time : 29:12:44 == == Total Elapsed Time 29:12:44 == == Disk Start Temperature: 34C == == Current Disk Temperature: 29C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdc /tmp/smart_finish_sdc ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 123 118 0 ok 29 No SMART attributes are FAILING_NOW 13 sectors were pending re-allocation before the start of the preclear. 2 sectors are pending re-allocation at the end of the preclear, a change of -11 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. ============================================================================ It looks like those two sectors cannot be repaired. The report after a second preclear: ========================================================================1.4 == invoked as: ./preclear_disk.sh -A /dev/sdc == == Disk /dev/sdc has been successfully precleared == with a starting sector of 64 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 8:15:49 (67 MB/s) == Last Cycle's Zeroing time : 6:46:55 (81 MB/s) == Last Cycle's Post Read Time : 14:10:29 (39 MB/s) == Last Cycle's Total Time : 29:14:20 == == Total Elapsed Time 29:14:20 == == Disk Start Temperature: 24C == == Current Disk Temperature: 28C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdc /tmp/smart_finish_sdc ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 124 128 0 ok 28 No SMART attributes are FAILING_NOW 3 sectors were pending re-allocation before the start of the preclear. 2 sectors are pending re-allocation at the end of the preclear, a change of -1 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. ============================================================================ The drive was bought May of 2010. If I RMA this, WD is gonna send a refurb, won't they? Quote Link to comment
Joe L. Posted February 9, 2011 Share Posted February 9, 2011 Version 1.6 of preclear_disk.sh has now been released. It is attached to the first post in the original preclear_disk.sh thread. The newest unRAID 5.0beta made changes to the format of the config/disk.cfg file that broke the "-l" option of preclear_disk.sh. The new version 1.6 of preclear_disk.sh may be used with both older and newer versions of unRAID. Have fun. Joe L. Quote Link to comment
Heretic Posted February 13, 2011 Share Posted February 13, 2011 If i understand correctly these disks are fine and need no further investigation? the -C 64 command is already used to fix alignment thanks in advance ========================================================================1.6 == invoked as: ./preclear_disk.sh /dev/sda == WDC WD20EARS-00MVWB0 WD-WCAZA1761835== Disk /dev/sda has been successfully precleared == with a starting sector of 63 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 6:20:25 (87 MB/s) == Last Cycle's Zeroing time : 6:22:19 (87 MB/s) == Last Cycle's Post Read Time : 12:36:52 (44 MB/s) == Last Cycle's Total Time : 25:20:43 == == Total Elapsed Time 25:20:43 == == Disk Start Temperature: 27C == == Current Disk Temperature: 28C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sda /tmp/smart_finish_sda ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 122 123 0 ok 28 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. ============================================================================ ========================================================================1.6 == invoked as: ./preclear_disk.sh /dev/sdb == WDC WD20EARS-00MVWB0 WD-WMAZA2781596== Disk /dev/sdb has been successfully precleared == with a starting sector of 63 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 6:32:48 (84 MB/s) == Last Cycle's Zeroing time : 6:34:49 (84 MB/s) == Last Cycle's Post Read Time : 12:59:57 (42 MB/s) == Last Cycle's Total Time : 26:08:40 == == Total Elapsed Time 26:08:40 == == Disk Start Temperature: 26C == == Current Disk Temperature: 27C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 123 124 0 ok 27 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. ============================================================================ Quote Link to comment
Joe L. Posted February 13, 2011 Share Posted February 13, 2011 If i understand correctly these disks are fine and need no further investigation? the -C 64 command is already used to fix alignment thanks in advance ========================================================================1.6 == invoked as: ./preclear_disk.sh /dev/sda == WDC WD20EARS-00MVWB0 WD-WCAZA1761835== Disk /dev/sda has been successfully precleared == with a starting sector of 63 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 6:20:25 (87 MB/s) == Last Cycle's Zeroing time : 6:22:19 (87 MB/s) == Last Cycle's Post Read Time : 12:36:52 (44 MB/s) == Last Cycle's Total Time : 25:20:43 == == Total Elapsed Time 25:20:43 == == Disk Start Temperature: 27C == == Current Disk Temperature: 28C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sda /tmp/smart_finish_sda ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 122 123 0 ok 28 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. ============================================================================ ========================================================================1.6 == invoked as: ./preclear_disk.sh /dev/sdb == WDC WD20EARS-00MVWB0 WD-WMAZA2781596== Disk /dev/sdb has been successfully precleared == with a starting sector of 63 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 6:32:48 (84 MB/s) == Last Cycle's Zeroing time : 6:34:49 (84 MB/s) == Last Cycle's Post Read Time : 12:59:57 (42 MB/s) == Last Cycle's Total Time : 26:08:40 == == Total Elapsed Time 26:08:40 == == Disk Start Temperature: 26C == == Current Disk Temperature: 27C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 123 124 0 ok 27 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. ============================================================================ You understood correctly. Quote Link to comment
Heretic Posted February 13, 2011 Share Posted February 13, 2011 thanks for clearing that up! Quote Link to comment
Al09 Posted February 14, 2011 Share Posted February 14, 2011 Hi all, noobie here. Just finished a 2 cycle preclear on my first build. both drives are 2 TB WD EARS. I precleared the drives with 4k alignment (-A). No drive errors, but I thought I'd post my syslog since I have no idea what anything else means. If anyone sees anything funny (preclear results or something else in the syslog), please let me know as I have no clue how to read it. Thanks! Al syslog-2011-02-11.txt Quote Link to comment
Joe L. Posted February 14, 2011 Share Posted February 14, 2011 Hi all, noobie here. Just finished a 2 cycle preclear on my first build. both drives are 2 TB WD EARS. I precleared the drives with 4k alignment (-A). No drive errors, but I thought I'd post my syslog since I have no idea what anything else means. If anyone sees anything funny (preclear results or something else in the syslog), please let me know as I have no clue how to read it. Thanks! Al You used an older version of preclear_disk.sh. Current is version 1.6, and when lime-tech releases 5.0beta5 there will be a new version 1.7. The newer versions of preclear_disk.sh have some new added features and have improved their final report to make it slightly easier for noobies. (The actual clearing is the same) # Version 1.3 - Added logic to read desired "default" Partition Type from /boot/config. # - Added logic to save dated copies of the final preclear and SMART reports to a # "preclear_reports" subdirectory on the flash drive. # - Added "-R" option to suppress the copy of final reports to a "preclear_reports" # directory on the flash drive. (they are always in /tmp until you reboot) # Version 1.4 - Added "-D" option to suppress use of "-d ata" on smartctl commands # Added "-d device_type" to allow use of alternate device_types as arguments to smartctl. # Added "-z" option to zero the MBR and do nothing else. (remainder of the drive will not # be cleared) # Version 1.5 - Added Model/Serial number of disk to output report. # Fixed default argument to smartctl when "-d" and "-D" options not given. # Added intermediate report of sectors pending re-allocation. # Version 1.6 - Fixed logic to prevent use on disk assigned to array in 5.0beta4 version of unRAID Your disks look perfectly fine. Joe L. Quote Link to comment
Al09 Posted February 14, 2011 Share Posted February 14, 2011 Hi all, noobie here. Just finished a 2 cycle preclear on my first build. both drives are 2 TB WD EARS. I precleared the drives with 4k alignment (-A). No drive errors, but I thought I'd post my syslog since I have no idea what anything else means. If anyone sees anything funny (preclear results or something else in the syslog), please let me know as I have no clue how to read it. Thanks! Al You used an older version of preclear_disk.sh. Current is version 1.6, and when lime-tech releases 5.0beta5 there will be a new version 1.7. The newer versions of preclear_disk.sh have some new added features and have improved their final report to make it slightly easier for noobies. (The actual clearing is the same) # Version 1.3 - Added logic to read desired "default" Partition Type from /boot/config. # - Added logic to save dated copies of the final preclear and SMART reports to a # "preclear_reports" subdirectory on the flash drive. # - Added "-R" option to suppress the copy of final reports to a "preclear_reports" # directory on the flash drive. (they are always in /tmp until you reboot) # Version 1.4 - Added "-D" option to suppress use of "-d ata" on smartctl commands # Added "-d device_type" to allow use of alternate device_types as arguments to smartctl. # Added "-z" option to zero the MBR and do nothing else. (remainder of the drive will not # be cleared) # Version 1.5 - Added Model/Serial number of disk to output report. # Fixed default argument to smartctl when "-d" and "-D" options not given. # Added intermediate report of sectors pending re-allocation. # Version 1.6 - Fixed logic to prevent use on disk assigned to array in 5.0beta4 version of unRAID Your disks look perfectly fine. Joe L. Thanks Joe! I will update preclear to latest version when I get home. I think I might have to go buy another drive already. Started dumping my files and i'm up to 1.4 TB used already. I've got stacks of DVD's that I still want to bring into the server, so I'll be filling up soon. Quote Link to comment
mrmachine Posted February 17, 2011 Share Posted February 17, 2011 I'm trying to run the preclear script on an SSD (Corsair F60) with unraid 5.0 beta 4, running directly on the hardware with a virgin install. I get the following output: root@unraid:/boot# ./preclear_disk.sh /dev/sda Pre-Clear unRAID Disk /dev/sda ################################################################## 1.6 Error: preclear_disk unable to continue. smartctl is unable to run on /dev/sda with the -d ata option. smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: Corsair CSSD-F60GB2 Serial Number: 11036506340009990035 Firmware Version: 2.0 User Capacity: 60,022,480,896 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 6 Local Time is: Thu Feb 17 22:09:44 2011 EST 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: ( 0) seconds. Offline data collection capabilities: (0x7f) SMART execute Offline immediate. Auto Offline data collection on/off support. Abort 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 48) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x003d) 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 120 120 050 Pre-fail Always - 0 5 Reallocated_Sector_Ct 0x0033 100 100 003 Pre-fail Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 3178275799066 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 8 171 Unknown_Attribute 0x0032 000 000 000 Old_age Always - 0 172 Unknown_Attribute 0x0032 000 000 000 Old_age Always - 0 174 Unknown_Attribute 0x0030 000 000 000 Old_age Offline - 2 177 Wear_Leveling_Count 0x0000 000 000 000 Old_age Offline - 0 181 Program_Fail_Cnt_Total 0x0032 000 000 000 Old_age Always - 0 182 Erase_Fail_Count_Total 0x0032 000 000 000 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 194 Temperature_Celsius 0x0022 032 046 000 Old_age Always - 32 (Lifetime Min/Max 27/46) 195 Hardware_ECC_Recovered 0x001c 120 120 000 Old_age Offline - 0 196 Reallocated_Event_Count 0x0033 100 100 000 Pre-fail Always - 0 231 Temperature_Celsius 0x0013 100 100 010 Pre-fail Always - 0 233 Media_Wearout_Indicator 0x0000 000 000 000 Old_age Offline - 0 234 Unknown_Attribute 0x0032 000 000 000 Old_age Always - 0 241 Total_LBAs_Written 0x0032 000 000 000 Old_age Always - 0 242 Total_LBAs_Read 0x0032 000 000 000 Old_age Always - 0 Error SMART Error Log Read failed: Input/output error Smartctl: SMART Error Log Read Failed Error SMART Error Self-Test Log Read failed: Input/output error Smartctl: SMART Self Test Log Read Failed 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@unraid:/boot# What does it mean? How do I preclear this drive? I want to use it as a cache drive. Do I even need to preclear it? Quote Link to comment
Joe L. Posted February 17, 2011 Share Posted February 17, 2011 Try using the "-D" option. The SSD is apparently not responding to the '"ata" command set as expected by smartctl. preclear_disk.sh -D /dev/sda Joe L. Quote Link to comment
mrmachine Posted February 17, 2011 Share Posted February 17, 2011 Try using the "-D" option. The SSD is apparently not responding to the '"ata" command set as expected by smartctl. preclear_disk.sh -D /dev/sda Joe L. Same (or similar, at least) problem, I'm afraid root@unraid:/boot# ./preclear_disk.sh -D /dev/sda Pre-Clear unRAID Disk /dev/sda ################################################################## 1.6 Error: preclear_disk unable to continue. smartctl is unable to run on /dev/sda with the option. smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: Corsair CSSD-F60GB2 Serial Number: 11036506340009990035 Firmware Version: 2.0 User Capacity: 60,022,480,896 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 6 Local Time is: Thu Feb 17 23:25:02 2011 EST 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: ( 0) seconds. Offline data collection capabilities: (0x7f) SMART execute Offline immediate. Auto Offline data collection on/off support. Abort 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 48) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x003d) 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 120 120 050 Pre-fail Always - 0 5 Reallocated_Sector_Ct 0x0033 100 100 003 Pre-fail Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 3204045602843 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 8 171 Unknown_Attribute 0x0032 000 000 000 Old_age Always - 0 172 Unknown_Attribute 0x0032 000 000 000 Old_age Always - 0 174 Unknown_Attribute 0x0030 000 000 000 Old_age Offline - 2 177 Wear_Leveling_Count 0x0000 000 000 000 Old_age Offline - 0 181 Program_Fail_Cnt_Total 0x0032 000 000 000 Old_age Always - 0 182 Erase_Fail_Count_Total 0x0032 000 000 000 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 194 Temperature_Celsius 0x0022 031 046 000 Old_age Always - 31 (Lifetime Min/Max 27/46) 195 Hardware_ECC_Recovered 0x001c 120 120 000 Old_age Offline - 0 196 Reallocated_Event_Count 0x0033 100 100 000 Pre-fail Always - 0 231 Temperature_Celsius 0x0013 100 100 010 Pre-fail Always - 0 233 Media_Wearout_Indicator 0x0000 000 000 000 Old_age Offline - 0 234 Unknown_Attribute 0x0032 000 000 000 Old_age Always - 0 241 Total_LBAs_Written 0x0032 000 000 000 Old_age Always - 0 242 Total_LBAs_Read 0x0032 000 000 000 Old_age Always - 0 Error SMART Error Log Read failed: Input/output error Smartctl: SMART Error Log Read Failed Error SMART Error Self-Test Log Read failed: Input/output error Smartctl: SMART Self Test Log Read Failed 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@unraid:/boot# Quote Link to comment
Joe L. Posted February 17, 2011 Share Posted February 17, 2011 I'm not sure I'd believe the SMART results anyway... It shows 3204045602843 hours operation. That might indicate you have one of the time-warp SSD devices. (indicating a manufacture date roughly 356 million years ago) Quote Link to comment
mrmachine Posted February 17, 2011 Share Posted February 17, 2011 I'm not sure I'd believe the SMART results anyway... It shows 3204045602843 hours operation. That might indicate you have one of the time-warp SSD devices. (indicating a manufacture date roughly 356 million years ago) I did notice that. Strange. I couldn't find any other forum posts about using the preclear script with SSD. Does nobody do this? Is it not necessary (for a cache drive)? Is my only alternative to use "-n" to skip the pre and post read that would allow smart firmware to identify bad blocks? Edit: Just tried it, and that didn't work either. Quote Link to comment
Joe L. Posted February 17, 2011 Share Posted February 17, 2011 I'm not sure I'd believe the SMART results anyway... It shows 3204045602843 hours operation. That might indicate you have one of the time-warp SSD devices. (indicating a manufacture date roughly 356 million years ago) I did notice that. Strange. I couldn't find any other forum posts about using the preclear script with SSD. Does nobody do this? Is it not necessary (for a cache drive)? Is my only alternative to use "-n" to skip the pre and post read that would allow smart firmware to identify bad blocks? Edit: Just tried it, and that didn't work either. I think it is that most people do not have SSD devices, and they certainly do not have the same issues as physical media. You might be able to run the "long" test through smartctl. See if it is supported. Joe L. Quote Link to comment
aiden Posted February 17, 2011 Share Posted February 17, 2011 Wouldn't something like a Memtest approach be more appropriate for SSDs? Quote Link to comment
mrmachine Posted February 17, 2011 Share Posted February 17, 2011 I think it is that most people do not have SSD devices, and they certainly do not have the same issues as physical media. You might be able to run the "long" test through smartctl. See if it is supported. Joe L. I'm running the long text now. I found smartctl a little confusing, as running `smartctl --test=long /dev/sda` returned almost immediately and told me to check the results in 48 minutes. I think I just do `smartctl -a /dev/sda` to check the results? I found a web page that seemed to indicate I could call `smartctl` with the `-a` option to check the results and/or the status of a currently running test. But when I try (while the test is running), I see "Error SMART Error Log Read failed: Input/output error". Should I just give up and start using the drive? I intend to use it as a cache drive. Is the preclear script and long smartctl tests even required or useful in this case, since it will only be storing data short term until it is moved onto the array? Cheers. root@unraid:/boot# smartctl --test=long -C /dev/sda smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION === Sending command: "Execute SMART Extended self-test routine immediately in captive mode". Drive command "Execute SMART Extended self-test routine immediately in captive mode" successful. Testing has begun. Please wait 48 minutes for test to complete. Test will complete after Fri Feb 18 10:23:29 2011 root@unraid:/boot# smartctl -a /dev/sda smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: Corsair CSSD-F60GB2 Serial Number: 11036506340009990035 Firmware Version: 2.0 User Capacity: 60,022,480,896 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 6 Local Time is: Fri Feb 18 09:35:39 2011 EST 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: (0x05) Offline data collection activity was aborted by an interrupting command from host. Auto Offline Data Collection: Disabled. Self-test execution status: ( 64) The previous self-test completed having a test element that failed and the test element that failed is not known. Total time to complete Offline data collection: ( 0) seconds. Offline data collection capabilities: (0x7f) SMART execute Offline immediate. Auto Offline data collection on/off support. Abort 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 48) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x003d) 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 106 104 050 Pre-fail Always - 14546713 5 Reallocated_Sector_Ct 0x0033 100 100 003 Pre-fail Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 213296665853989 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 8 171 Unknown_Attribute 0x0032 000 000 000 Old_age Always - 0 172 Unknown_Attribute 0x0032 000 000 000 Old_age Always - 0 174 Unknown_Attribute 0x0030 000 000 000 Old_age Offline - 2 177 Wear_Leveling_Count 0x0000 000 000 000 Old_age Offline - 0 181 Program_Fail_Cnt_Total 0x0032 000 000 000 Old_age Always - 0 182 Erase_Fail_Count_Total 0x0032 000 000 000 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 194 Temperature_Celsius 0x0022 033 046 000 Old_age Always - 33 (Lifetime Min/Max 27/46) 195 Hardware_ECC_Recovered 0x001c 106 104 000 Old_age Offline - 14546713 196 Reallocated_Event_Count 0x0033 100 100 000 Pre-fail Always - 0 231 Temperature_Celsius 0x0013 100 100 010 Pre-fail Always - 0 233 Media_Wearout_Indicator 0x0000 000 000 000 Old_age Offline - 0 234 Unknown_Attribute 0x0032 000 000 000 Old_age Always - 0 241 Total_LBAs_Written 0x0032 000 000 000 Old_age Always - 0 242 Total_LBAs_Read 0x0032 000 000 000 Old_age Always - 0 Error SMART Error Log Read failed: Input/output error Smartctl: SMART Error Log Read Failed Error SMART Error Self-Test Log Read failed: Input/output error Smartctl: SMART Self Test Log Read Failed 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@unraid:/boot# Quote Link to comment
Joe L. Posted February 17, 2011 Share Posted February 17, 2011 I think I just do `smartctl -a /dev/sda` to check the results? Correct. After waiting for it to complete. Joe L. 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.