Joe L. Posted April 22, 2013 Share Posted April 22, 2013 There is no significance to "60" it might be a value used by that model drive once it is in use. NORMALIZED values are not described by the manufactures other than if they are above the affiliated error-threshold, the disk is healthy. Manufacturers all set their own logic on how the RAW values are presented. Some are actual counts, others are not. As ab example, your power-on hours looks like an actual value 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 7 but head-flying hours is probably not an actual human-readable value. 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 11154030067719 Your disks look fine. Quote Link to comment
navi Posted April 22, 2013 Share Posted April 22, 2013 There is no significance to "60" it might be a value used by that model drive once it is in use. NORMALIZED values are not described by the manufactures other than if they are above the affiliated error-threshold, the disk is healthy. Manufacturers all set their own logic on how the RAW values are presented. Some are actual counts, others are not. As ab example, your power-on hours looks like an actual value 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 7 but head-flying hours is probably not an actual human-readable value. 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 11154030067719 Your disks look fine. Thanks for the quick response Joe and also for your excellent tools for Unraid. Quote Link to comment
dalben Posted April 24, 2013 Share Posted April 24, 2013 I'm in the midst of preclearing new 4TB drives which will replace my current 2tb drives. I think the first 3 cycle preclear went fine. Log attached. 90+ hours. I think I'll use this one for parity and run the other 4 drives on a single pre-clear as I'm hoping to have the system backup by Christmas. preclear.txt Quote Link to comment
hjgunraid Posted April 29, 2013 Share Posted April 29, 2013 Hi all, i just precleared a Seagate 4TB (ST4000DM000) on my test unRAID (VIA C7 - 800 MHz - 512MB Ram - SATA1 150MB/s). It take a long time for 3 Cycles, but I think the reason is the old test hardware. I'm a little bit confused about the value "near_tresh" in the result: Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Here are the complete results: Disk: /dev/sdc smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST4000DM000-1F2168 Serial Number: Z300CRLF Firmware Version: CC52 User Capacity: 4,000,787,030,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Tue Apr 16 21:25:04 2013 CEST 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: ( 117) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No 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: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x1085) SCT Status 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 117 100 006 Pre-fail Always - 134596344 3 Spin_Up_Time 0x0003 098 098 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 2 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 5662 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 3 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 2 183 Runtime_Bad_Block 0x0032 099 099 000 Old_age Always - 1 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 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 076 073 045 Old_age Always - 24 (Min/Max 24/25) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 2 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 10 194 Temperature_Celsius 0x0022 024 040 000 Old_age Always - 24 (0 20 0 0) 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 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 131108171677698 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 0 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 617923027 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. Disk: /dev/sdc smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST4000DM000-1F2168 Serial Number: Z300CRLF Firmware Version: CC52 User Capacity: 4,000,787,030,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Mon Apr 29 11:56:18 2013 CEST 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: ( 612) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No 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: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x1085) SCT Status 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 114 099 006 Pre-fail Always - 81687640 3 Spin_Up_Time 0x0003 098 098 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 2 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 889878 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 306 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 2 183 Runtime_Bad_Block 0x0032 099 099 000 Old_age Always - 1 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 099 099 000 Old_age Always - 1 190 Airflow_Temperature_Cel 0x0022 074 072 045 Old_age Always - 26 (Min/Max 24/28) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 2 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 10 194 Temperature_Celsius 0x0022 026 040 000 Old_age Always - 26 (0 20 0 0) 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 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 144349555851569 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 23442111648 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 56125268688 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. ========================================================================1.13 == invoked as: ./preclear_disk.sh -A -c 3 /dev/sdc == ST4000DM000-1F2168 Z300CRLF == Disk /dev/sdc has been successfully precleared == with a starting sector of 1 == Ran 3 cycles == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 19:08:41 (58 MB/s) == Last Cycle's Zeroing time : 24:51:06 (44 MB/s) == Last Cycle's Post Read Time : 69:57:01 (15 MB/s) == Last Cycle's Total Time : 94:49:13 == == Total Elapsed Time 302:31:14 == == Disk Start Temperature: 24C == == Current Disk Temperature: 26C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdc /tmp/smart_finish_sdc ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 114 117 6 ok 81687640 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 99 100 0 ok 1 Airflow_Temperature_Cel = 74 76 45 ok 26 Temperature_Celsius = 26 24 0 ok 26 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. ============================================================================ Please give me feedback if I can replace my old 2TB parity disk with this 4TB disk. Quote Link to comment
Joe L. Posted April 29, 2013 Share Posted April 29, 2013 Hi all, i just precleared a Seagate 4TB (ST4000DM000) on my test unRAID (VIA C7 - 800 MHz - 512MB Ram - SATA1 150MB/s). It take a long time for 3 Cycles, but I think the reason is the old test hardware. I'm a little bit confused about the value "near_tresh" in the result: Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Your manufacturer of your disk has set the failure threshold for those two parameters to value very close to the initial starting normalized values. Basically, there has never been an error, but if your disk ever has an issue in spinning up (possibly thee failures?) the disk will be considered as failing. The "end-to-end" failure is (I think) the ability to write and subsequently read the disk. If that cannot occur, the disk will be considered failed. The manufacturer could have put the failure threshold at 50 and incremented the normalized value by 50 for each failure, and had the same result but they each impliment SMART in their own way, and they aren't telling anybody of the details. Enjoy your disk. It looks great. Joe L. Quote Link to comment
NiklasK Posted April 30, 2013 Share Posted April 30, 2013 I´m a bit of a noob when it comes to unRAID and thought I would ask what my pre-clear means. So far I´m only done with my planned cache disk and got 2x 4tb drives in the process as well. preclear_start: Last login: Mon Apr 29 18:18:52 on ttys003 Mac-mini:~ Niklas$ /Volumes/flash/preclear_reports/preclear_start_\ WD-WXQ1EB1JSLAM_2013-04-30 ; exit; /Volumes/flash/preclear_reports/preclear_start_ WD-WXQ1EB1JSLAM_2013-04-30: line 1: Disk:: command not found /Volumes/flash/preclear_reports/preclear_start_ WD-WXQ1EB1JSLAM_2013-04-30: line 2: syntax error near unexpected token `(' /Volumes/flash/preclear_reports/preclear_start_ WD-WXQ1EB1JSLAM_2013-04-30: line 2: `smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build)' logout [Processen slutförd] preclear_finish: Last login: Tue Apr 30 12:13:56 on ttys003 Mac-mini:~ Niklas$ /Volumes/flash/preclear_reports/preclear_finish_\ WD-WXQ1EB1JSLAM_2013-04-30 ; exit; /Volumes/flash/preclear_reports/preclear_finish_ WD-WXQ1EB1JSLAM_2013-04-30: line 1: Disk:: command not found /Volumes/flash/preclear_reports/preclear_finish_ WD-WXQ1EB1JSLAM_2013-04-30: line 2: syntax error near unexpected token `(' /Volumes/flash/preclear_reports/preclear_finish_ WD-WXQ1EB1JSLAM_2013-04-30: line 2: `smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build)' logout [Processen slutförd] preclear_rpt: Last login: Tue Apr 30 12:17:25 on ttys003 Mac-mini:~ Niklas$ /Volumes/flash/preclear_reports/preclear_rpt_\ WD-WXQ1EB1JSLAM_2013-04-30 ; exit; /Volumes/flash/preclear_reports/preclear_rpt_ WD-WXQ1EB1JSLAM_2013-04-30: line 1: ========================================================================1.13: command not found /Volumes/flash/preclear_reports/preclear_rpt_ WD-WXQ1EB1JSLAM_2013-04-30: line 2: ==: command not found /Volumes/flash/preclear_reports/preclear_rpt_ WD-WXQ1EB1JSLAM_2013-04-30: line 3: ==: command not found /Volumes/flash/preclear_reports/preclear_rpt_ WD-WXQ1EB1JSLAM_2013-04-30: line 4: ==: command not found /Volumes/flash/preclear_reports/preclear_rpt_ WD-WXQ1EB1JSLAM_2013-04-30: line 5: ==: command not found /Volumes/flash/preclear_reports/preclear_rpt_ WD-WXQ1EB1JSLAM_2013-04-30: line 6: ==: command not found /Volumes/flash/preclear_reports/preclear_rpt_ WD-WXQ1EB1JSLAM_2013-04-30: line 7: ==: command not found /Volumes/flash/preclear_reports/preclear_rpt_ WD-WXQ1EB1JSLAM_2013-04-30: line 8: ==: command not found /Volumes/flash/preclear_reports/preclear_rpt_ WD-WXQ1EB1JSLAM_2013-04-30: line 10: syntax error near unexpected token `(' /Volumes/flash/preclear_reports/preclear_rpt_ WD-WXQ1EB1JSLAM_2013-04-30: line 10: `== Last Cycle's Zeroing time : 2:49:12 (73 MB/s)' logout [Processen slutförd] When I look at the terminal after the preclear is done I get the following: ========================================================================1.13 == WDC WD7500BPVT-55HXZT3 WD-WXQ1EB1JSLAM == Disk /dev/sdc has been successfully precleared == with a starting sector of 64 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdc /tmp/smart_finish_sdc ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Seek_Error_Rate = 100 200 0 ok 0 Temperature_Celsius = 115 119 0 ok 7200 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. root@Tower:/boot# Is it correct with all these different error messages in the reports since the terminal doesnt mention anything regarding allocation...? Quote Link to comment
Joe L. Posted April 30, 2013 Share Posted April 30, 2013 Is it correct with all these different error messages in the reports since the terminal doesnt mention anything regarding allocation...? It indicates that either the preclear_disk.sh is corrupted, OR, you have programs missing on your server it is expecting to use. You should have none of the "command not found" or "syntax error" messages. did you open the preclear_disk.sh script in an editor? (possibly accidentally add carriage returns to the ends of the lines?) Quote Link to comment
NiklasK Posted April 30, 2013 Share Posted April 30, 2013 From what I know I only downloaded the script from the forum post and put it on my unRAID flash. So I should cancel the other 2 preclears and try with a new script then maybe... Is it correct with all these different error messages in the reports since the terminal doesnt mention anything regarding allocation...? It indicates that either the preclear_disk.sh is corrupted, OR, you have programs missing on your server it is expecting to use. You should have none of the "command not found" or "syntax error" messages. did you open the preclear_disk.sh script in an editor? (possibly accidentally add carriage returns to the ends of the lines?) Quote Link to comment
Joe L. Posted April 30, 2013 Share Posted April 30, 2013 From what I know I only downloaded the script from the forum post and put it on my unRAID flash. So I should cancel the other 2 preclears and try with a new script then maybe... Is it correct with all these different error messages in the reports since the terminal doesnt mention anything regarding allocation...? It indicates that either the preclear_disk.sh is corrupted, OR, you have programs missing on your server it is expecting to use. You should have none of the "command not found" or "syntax error" messages. did you open the preclear_disk.sh script in an editor? (possibly accidentally add carriage returns to the ends of the lines?) Another possibility is you ran out of memory for all you were running. Look in your syslog for out-of-memory (oom) errors. Unless you used the -r -w and -b options of the preclear script, three simultaneous preclears of large drives will likely run out of memory. Quote Link to comment
NiklasK Posted April 30, 2013 Share Posted April 30, 2013 Cant see any error messages referring to the memory. I did however include the syslog if I dont look at it right. From what I know I only downloaded the script from the forum post and put it on my unRAID flash. So I should cancel the other 2 preclears and try with a new script then maybe... Is it correct with all these different error messages in the reports since the terminal doesnt mention anything regarding allocation...? It indicates that either the preclear_disk.sh is corrupted, OR, you have programs missing on your server it is expecting to use. You should have none of the "command not found" or "syntax error" messages. did you open the preclear_disk.sh script in an editor? (possibly accidentally add carriage returns to the ends of the lines?) Another possibility is you ran out of memory for all you were running. Look in your syslog for out-of-memory (oom) errors. Unless you used the -r -w and -b options of the preclear script, three simultaneous preclears of large drives will likely run out of memory. syslog.txt Quote Link to comment
Joe L. Posted April 30, 2013 Share Posted April 30, 2013 Cant see any error messages referring to the memory. I did however include the syslog if I dont look at it right. From what I know I only downloaded the script from the forum post and put it on my unRAID flash. So I should cancel the other 2 preclears and try with a new script then maybe... Is it correct with all these different error messages in the reports since the terminal doesnt mention anything regarding allocation...? It indicates that either the preclear_disk.sh is corrupted, OR, you have programs missing on your server it is expecting to use. You should have none of the "command not found" or "syntax error" messages. did you open the preclear_disk.sh script in an editor? (possibly accidentally add carriage returns to the ends of the lines?) Another possibility is you ran out of memory for all you were running. Look in your syslog for out-of-memory (oom) errors. Unless you used the -r -w and -b options of the preclear script, three simultaneous preclears of large drives will likely run out of memory. I do not see anything unusual either, other than your disk's way of reporting its temperature. (and that does not harm anything) Joe L. Quote Link to comment
axeman Posted May 1, 2013 Share Posted May 1, 2013 grrr. whenever i use the -m [email protected] or -M 4 options, the help/usage text shows on screen if i take those options out, it seems to start the pre-clear process. i've done this in the past, so i can't imagine what i'm doing wrong now.. set email info using SimpleFeatures [1.0.11]; i'm on UnRaid 5.0-rc12a; and pre-clear version 1.13. I am receiving email from SimpleFeatures, periodically; and the command below works fine: echo -e "Subject: a test\n\nThis is the email body." | ssmtp -d root Command line i'm trying to execute: ./preclear_disk.sh -M 4 -c 1 -a /dev/sdd also tried simple: ./preclear_disk.sh -M 4 /dev/sdd anything obvious that i'm missing? Quote Link to comment
Joe L. Posted May 2, 2013 Share Posted May 2, 2013 grrr. whenever i use the -m [email protected] or -M 4 options, the help/usage text shows on screen anything obvious that i'm missing? Yes, reading the first line of the error message...(at the very top of the usage output) error: "mail" program does not exist. SimpleFeatures does not install a "mail" program. Sorry... but "ssmtp" is not a replacement for "mail" "ssmtp" is used in combination with "mail". For "mail" to work properly with "cron" it must be an executable, not a shell script. It is why I installl and use mailx, so I can get the errors from cron. Joe L. Quote Link to comment
axeman Posted May 2, 2013 Share Posted May 2, 2013 thanks Joe When I run it in screen via putty, I don't see that error; strange thing is, I got it to work, about 2 months ago. either something changed in Unraid or simple features. searched around for mailx... not sure I can get that going easily. going to fire off the first set... these were precleared back a month ago. I wiped everything out and starting fresh. figure i'll just run 1 pass. Quote Link to comment
Joe L. Posted May 2, 2013 Share Posted May 2, 2013 searched around for mailx... not sure I can get that going easily. mailx can be installed through unMENU's package manager. It also installs ssmtp, so that might clobber your SimpleFeatures install. You might need a different solution. Sorry, SimpleFeatures might look better, but in some cases,not as complete as the unMENU equivalents. Perhaps somebody has created a mailx plugin. Quote Link to comment
axeman Posted May 2, 2013 Share Posted May 2, 2013 ah - i thought unmenu was for 4.x only... meh i guess i'll have to forgo email notifications. Quote Link to comment
Joe L. Posted May 2, 2013 Share Posted May 2, 2013 ah - i thought unmenu was for 4.x only... meh i guess i'll have to forgo email notifications. No, not at all, unMENU works with any version of unRAID (Although I'm not sure if it was ever tested in the 3.X series, but it was created in 2008, so it might have been) in fact, unMENU recently underwent a major appearance upgrade..it now supports .css skinning, with the ability to have selectable horizontal or vertical menus. See here: http://lime-technology.com/forum/index.php?topic=27051.0 Quote Link to comment
axeman Posted May 4, 2013 Share Posted May 4, 2013 interesting. I might do that when I switch to 5.0 Prod. I am undecided about which one I like - both seem to really jazz up UnRaid. Can someone peruse through these and see if there's anything of concern? the Samsung log is super long. incidentally - my other very similar Samsung just croaked. soooo i'm concerned. the replacement for the one that died just got here today - about to fire off the script on that. preclear_finish__S2AEJ1BZ600843_2013-05-02.txt preclear_finish__WD-WCAZAJ087969_2013-05-03.txt preclear_finish__WD-WCAZAJ142017_2013-05-03.txt Quote Link to comment
axeman Posted May 5, 2013 Share Posted May 5, 2013 One more drive finished . this is my latest - replacing the dead Samsung with.. preclear_finish__13E0B47VS_2013-05-05.txt Quote Link to comment
axeman Posted May 6, 2013 Share Posted May 6, 2013 one more question.. the original posting of the script mentions NOT using anything OTHER than the UnRaid management UI to format the pre-cleared drives. Since I've already installed Simple Features, can I use that? Or do I need to go back to stock to be safe? Quote Link to comment
Joe L. Posted May 6, 2013 Share Posted May 6, 2013 one more question.. the original posting of the script mentions NOT using anything OTHER than the UnRaid management UI to format the pre-cleared drives. Since I've already installed Simple Features, can I use that? Or do I need to go back to stock to be safe? SimpleFeatures is just a "skin" for the stock unRAID management pages. You can use the "Format" button on it. Quote Link to comment
axeman Posted May 8, 2013 Share Posted May 8, 2013 is it OK that the pre-clear marked my 2TB (advanced format) drive with the 512/63 ? see attached. Quote Link to comment
Joe L. Posted May 8, 2013 Share Posted May 8, 2013 is it OK that the pre-clear marked my 2TB (advanced format) drive with the 512/63 ? see attached. All modern disks lie about their geometry. You can ignore what it says. There is absolutely no way the disk has that many heads, nor a fixed number of cylinders per track. The actual geometry has a variable number of sectors per track, and only a few disk heads. Joe L. Quote Link to comment
axeman Posted May 8, 2013 Share Posted May 8, 2013 is it OK that the pre-clear marked my 2TB (advanced format) drive with the 512/63 ? see attached. All modern disks lie about their geometry. You can ignore what it says. There is absolutely no way the disk has that many heads, nor a fixed number of cylinders per track. The actual geometry has a variable number of sectors per track, and only a few disk heads. Joe L. Thanks! got nervous - wasn't sure what it was saying... finally got my situation sorted out. i'm starting to move data over to my new array. Quote Link to comment
hjgunraid Posted May 12, 2013 Share Posted May 12, 2013 Hi all, I just finished clearing my 4TB Seagate. I'm little confused about the value in the report: ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Seek_Error_Rate = 60 100 30 ok 1119619 In my first 4TB Seagate, this value was not changed and stays on "100": 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 889878 Do I have a problem with this disk? preclear_start.txt preclear_finish.txt preclear_rpt.txt 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.