January 9, 201313 yr Hi, I have a brand new build, and tried preclearing 3 brand new 2tb Green EARX drives. I opened 3 separate putty telnet sessions from my workstation (that is never down) and ran two cycles. After a couple days I noticed all three telnet sessions were gone. The following logs are present: root@Tower:/boot/preclear_logs# ls -ltr total 480 -rwxrwxrwx 1 root root 4401 2010-12-31 21:15 smart_start_sda* -rwxrwxrwx 1 root root 4401 2010-12-31 21:15 smart_start_sdb* -rwxrwxrwx 1 root root 4401 2010-12-31 21:16 smart_start_sdc* -rwxrwxrwx 1 root root 4401 2011-01-01 03:45 smart_mid_preread1_sdc* -rwxrwxrwx 1 root root 4401 2011-01-01 03:48 smart_mid_preread1_sda* -rwxrwxrwx 1 root root 4401 2011-01-01 03:49 smart_mid_preread1_sdb* -rwxrwxrwx 1 root root 4402 2011-01-01 09:39 smart_mid_after_zero1_sdc* -rwxrwxrwx 1 root root 4402 2011-01-01 11:04 smart_mid_after_zero1_sda* -rwxrwxrwx 1 root root 4402 2011-01-01 11:07 smart_mid_after_zero1_sdb* -rwxrwxrwx 1 root root 4402 2011-01-02 01:41 smart_mid_post_read1_sdc* -rwxrwxrwx 1 root root 4402 2011-01-02 04:46 smart_mid_post_read1_sda* -rwxrwxrwx 1 root root 4402 2011-01-02 05:00 smart_mid_post_read1_sdb* -rwxrwxrwx 1 root root 4402 2011-01-02 07:31 smart_mid_after_zero2_sdc* -rwxrwxrwx 1 root root 4402 2011-01-02 11:38 smart_mid_after_zero2_sda* -rwxrwxrwx 1 root root 4402 2011-01-02 12:02 smart_mid_after_zero2_sdb* (I've since fixed the system time) Reading through the extensive preclear thread, it seems like I'm missing some logs? All of the logs show pretty much the same information, ie: root@Tower:/boot/preclear_logs# cat smart_mid_after_zero2_sdc 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: WDC WD20EARX-00MMMB0 Serial Number: WD-WCAWZ2593893 Firmware Version: 80.00A80 User Capacity: 2,000,398,934,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Sun Jan 2 12:31:56 2011 Local time zone must be set--see zic m SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x80) Offline data collection activity was never started. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (37500) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3035) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 160 160 021 Pre-fail Always - 9000 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 9 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 33 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 9 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 7 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 13 194 Temperature_Celsius 0x0022 109 108 000 Old_age Always - 43 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. root@Tower:/boot/preclear_logs# I guess what I'm asking is, what exactly should I see to reassure me everything is ok with these disks? I'm anxious to jump in and start populating the array, but want to make sure I have an ideal hardware environment before I do. Thanks for any insight.
January 9, 201313 yr Author Also, a couple random questions I have: The drives hit a max temp of about 43C during portions of the preclear. Is this within tolerance? I have one drive that oddly enough seems slightly faster than the other two during the preclear (note the relative log times, above - sdc is noticeably faster). All three were ordered together, have near-sequential serials, etc. Any reason for this? Maybe SATA port location, or something? And, where would you place a faster drive - parity? Does it matter? Thank you!
January 9, 201313 yr Author Ack, sorry - I just checked in /tmp again and realized that I only copied out the logs that started with "smart" ... turns out there are other logs: root@Tower:/tmp# ls -al total 696 drwxrwxrwt 5 root root 0 2011-01-02 12:02 ./ drwxr-xr-x 16 root root 0 2011-01-01 08:46 ../ drwxrwxrwt 2 root root 0 2010-12-31 21:02 .ICE-unix/ drwxrwxrwt 2 root root 0 2010-12-31 21:02 .X11-unix/ -rw-r--r-- 1 root root 0 2011-01-03 07:23 preclear_assigned_disks1 -rw-r--r-- 1 root root 36 2010-12-31 21:15 preclear_candidates -rw-r--r-- 1 root root 59 2013-01-09 13:16 preclear_stat_sda -rw-r--r-- 1 root root 66 2011-01-02 23:03 preclear_stat_sdb -rw-r--r-- 1 root root 66 2011-01-02 23:03 preclear_stat_sdc -rw-r--r-- 1 root root 10 2013-01-09 13:16 read_speedsda -rw-r--r-- 1 root root 10 2011-01-02 23:04 read_speedsdb -rw-r--r-- 1 root root 10 2011-01-02 23:04 read_speedsdc -rw-r--r-- 1 root root 4402 2011-01-01 11:04 smart_mid_after_zero1_sda -rw-r--r-- 1 root root 4402 2011-01-01 11:07 smart_mid_after_zero1_sdb -rw-r--r-- 1 root root 4402 2011-01-01 09:39 smart_mid_after_zero1_sdc -rw-r--r-- 1 root root 4402 2011-01-02 11:38 smart_mid_after_zero2_sda -rw-r--r-- 1 root root 4402 2011-01-02 12:02 smart_mid_after_zero2_sdb -rw-r--r-- 1 root root 4402 2011-01-02 07:31 smart_mid_after_zero2_sdc -rw-r--r-- 1 root root 0 2011-01-03 07:23 smart_mid_pending_reallocate_sda -rw-r--r-- 1 root root 289 2011-01-02 12:02 smart_mid_pending_reallocate_sdb -rw-r--r-- 1 root root 289 2011-01-02 07:31 smart_mid_pending_reallocate_sdc -rw-r--r-- 1 root root 4402 2011-01-02 04:46 smart_mid_post_read1_sda -rw-r--r-- 1 root root 4402 2011-01-02 05:00 smart_mid_post_read1_sdb -rw-r--r-- 1 root root 4402 2011-01-02 01:41 smart_mid_post_read1_sdc -rw-r--r-- 1 root root 4401 2011-01-01 03:48 smart_mid_preread1_sda -rw-r--r-- 1 root root 4401 2011-01-01 03:49 smart_mid_preread1_sdb -rw-r--r-- 1 root root 4401 2011-01-01 03:45 smart_mid_preread1_sdc -rw-r--r-- 1 root root 4402 2011-01-03 07:23 smart_start_sda -rw-r--r-- 1 root root 4401 2010-12-31 21:15 smart_start_sdb -rw-r--r-- 1 root root 4401 2010-12-31 21:16 smart_start_sdc -rw-r--r-- 1 root root 363 2011-01-01 08:46 unmenu_manual_install.out -rw-r--r-- 1 root root 18 2011-01-01 08:28 unmenu_new_files -rw-r--r-- 1 root root 19044 2012-05-06 20:28 unmenu_release_list drwxr-xr-x 3 root root 0 2010-12-31 21:04 unmenu_tmp/ -rw-r--r-- 1 root root 179095 2011-01-02 11:38 zerosda -rw-r--r-- 1 root root 181113 2011-01-02 12:01 zerosdb -rw-r--r-- 1 root root 148746 2011-01-02 07:31 zerosdc Sorted by date: root@Tower:/tmp# ls -ltr total 696 drwxr-xr-x 3 root root 0 2010-12-31 21:04 unmenu_tmp/ -rw-r--r-- 1 root root 4401 2010-12-31 21:15 smart_start_sdb -rw-r--r-- 1 root root 36 2010-12-31 21:15 preclear_candidates -rw-r--r-- 1 root root 4401 2010-12-31 21:16 smart_start_sdc -rw-r--r-- 1 root root 4401 2011-01-01 03:45 smart_mid_preread1_sdc -rw-r--r-- 1 root root 4401 2011-01-01 03:48 smart_mid_preread1_sda -rw-r--r-- 1 root root 4401 2011-01-01 03:49 smart_mid_preread1_sdb -rw-r--r-- 1 root root 18 2011-01-01 08:28 unmenu_new_files -rw-r--r-- 1 root root 363 2011-01-01 08:46 unmenu_manual_install.out -rw-r--r-- 1 root root 4402 2011-01-01 09:39 smart_mid_after_zero1_sdc -rw-r--r-- 1 root root 4402 2011-01-01 11:04 smart_mid_after_zero1_sda -rw-r--r-- 1 root root 4402 2011-01-01 11:07 smart_mid_after_zero1_sdb -rw-r--r-- 1 root root 4402 2011-01-02 01:41 smart_mid_post_read1_sdc -rw-r--r-- 1 root root 4402 2011-01-02 04:46 smart_mid_post_read1_sda -rw-r--r-- 1 root root 4402 2011-01-02 05:00 smart_mid_post_read1_sdb -rw-r--r-- 1 root root 148746 2011-01-02 07:31 zerosdc -rw-r--r-- 1 root root 4402 2011-01-02 07:31 smart_mid_after_zero2_sdc -rw-r--r-- 1 root root 289 2011-01-02 07:31 smart_mid_pending_reallocate_sdc -rw-r--r-- 1 root root 179095 2011-01-02 11:38 zerosda -rw-r--r-- 1 root root 4402 2011-01-02 11:38 smart_mid_after_zero2_sda -rw-r--r-- 1 root root 181113 2011-01-02 12:01 zerosdb -rw-r--r-- 1 root root 4402 2011-01-02 12:02 smart_mid_after_zero2_sdb -rw-r--r-- 1 root root 289 2011-01-02 12:02 smart_mid_pending_reallocate_sdb -rw-r--r-- 1 root root 66 2011-01-02 23:03 preclear_stat_sdc -rw-r--r-- 1 root root 66 2011-01-02 23:03 preclear_stat_sdb -rw-r--r-- 1 root root 10 2011-01-02 23:04 read_speedsdc -rw-r--r-- 1 root root 10 2011-01-02 23:04 read_speedsdb -rw-r--r-- 1 root root 0 2011-01-03 07:23 preclear_assigned_disks1 -rw-r--r-- 1 root root 4402 2011-01-03 07:23 smart_start_sda -rw-r--r-- 1 root root 0 2011-01-03 07:23 smart_mid_pending_reallocate_sda -rw-r--r-- 1 root root 19044 2012-05-06 20:28 unmenu_release_list -rw-r--r-- 1 root root 10 2013-01-09 13:19 read_speedsda -rw-r--r-- 1 root root 59 2013-01-09 13:20 preclear_stat_sda Do I have everything I need? If not, where should I look for a problem?
January 9, 201313 yr Also, a couple random questions I have: The drives hit a max temp of about 43C during portions of the preclear. Is this within tolerance? WDC quotes 0C - 60C as the operating temperature range for these drives, so 43C is safe. I have one drive that oddly enough seems slightly faster than the other two during the preclear (note the relative log times, above - sdc is noticeably faster). All three were ordered together, have near-sequential serials, etc. Any reason for this? Maybe SATA port location, or something? And, where would you place a faster drive - parity? Does it matter? Thank you! It might be an issue with ports etc. as you are running all preclears at the same time, so you might not have the bandwidth to keep all three drives maxed out. That said, the fastest is about 15% faster than the others which probably is not too alarming. I had one drive (same model as you) which took over twice as long to preclear as they normally do. The SMART reports for it were clean but I took it back to the dealer and got another which worked at the normal speed. I think there are some other people here who have reported the odd very slow drive. Regards, Stephen
January 10, 201313 yr Author I feel like I'm losing my mind - I replied to this post earlier and now that post is gone. Also, there was another individual (dgaschk I believe) that replied with the location of expected reports, and that post seems to have disappeared as well. Further, this forum seems to go down ... a lot. Is the admin of this forum the same as the creator of the unRaid product? I hope this doesn't come across as overly snarky but it doesn't exactly inspire a tremendous amount of confidence as I evaluate if this will be a solid storage solution... So anyhow, thank you Stephen and the other person that replied regarding the "preclear_reports" subdirectory. Since said subdir was not created, can I assume something went wrong? Is there any way to determine what it could have been? I have 2GB of RAM and was attempting to preclear three drives at once; could this be the root cause, and how can I verify? Thanks again, hopefully this post will stick..
January 10, 201313 yr If there are no reports then the process did not complete. Normally this forum is very reliable. There was just a maintenance issue that has been resolved.
January 10, 201313 yr Author Thanks, is there someplace I can look for additional details, besides the syslog? I was looking for documentation on the wiki, when that also crashed: http://lime-technology.com/wiki/ Warning: Parameter 1 to AutoAuthenticateSMF() expected to be a reference, value given in /home/limetech/public_html/wiki/includes/Hooks.php on line 117 Internal error Set $wgShowExceptionDetails = true; at the bottom of LocalSettings.php to show detailed debugging information. Very discouraging. Not sure I can trust my data to a company that can't keep its own house in order.
January 10, 201313 yr There is a note in the rc9 announcement thread that Lime was surprised by their service provider. I guess things are not totally resolved yet. The syslog is the only record. 3rd party software like preclear may create their own logs or use the system log. preclear writes its reports in /boot/preclear reports.
Archived
This topic is now archived and is closed to further replies.