archedraft

whoa... That's intense!

If the disk controller was not compatible with 3TB drives, then it would not work at all, that is, you would not see 3TB available. Yours does appear to work fine. I can't see any connection with the motherboard, because we need a suspect that is able to cause corruption and trouble WITHIN the drive, and that is a very short list. The only possibilities I can think of are power issues, heat issues, or a defective drive (bad firmware). Remember that if you discover a relation between a software running and the drive crashing, then that could only point to heavy power draw (perhaps pulling the voltage down too low), and that implicates the power supply (not the software or other hardware), as either too inadequate or too poorly designed. Aerocool makes interesting products (I like some of their cases), but I don't believe they are a good name in power supplies (I could be wrong, I haven't kept up with PSU's recently). I can't help being very suspicious of your PSU. Well my friend replaced his power supply but the preclear still give the same error (here is a link to my earlier post :http://lime-technology.com/forum/index.php?topic=4068.msg275829#msg275829). Thermo posted this a few weeks ago (http://lime-technology.com/forum/index.php?topic=30789.msg278242#msg278242) and had the same issue and indicated that buying a new PSU, motherboard, RAM, and CPU fixed the same error. I was able to successful run preclears on a 1 TB and 500 GB hard drive on his computer before. I am highly suspicious that his old motherboard does not like the fact that the 2 new hard drives are 3 TB... Any more thoughts before I tell him to nuke the computer and upgrade?

My 3TB Red took 82 hours and 10 minutes with 3 cycles.

Well we can rule out bad SATA port because I also switched that as well. Am an leaning towards the PSU being the issue. Is there anyway an older motherboard would be the cause of this because the hard drive is 3 TB? I was of the understanding that it shouldn't matter with unRAID but thought I would check anyways. My friends server is running Plex, Sickbeard, and Transmission. Plex updates itself every hour, Sickbeard every 10 minuets, and I am sure Transmission updates it self as well... I guess I will turn off all the plugins and try again before I tell my friend to buy new stuff but the question is, will adding this drive to the array cause problems later on if I turn the plugins back on?

So I removed one of the graphics cards and used a new power cable, sata cable, and new hard drive. This time the Pre-Clear gets stuck on step 2 of 10 on 48% and the syslog is ugly... The errors are above my head. Does anyone know what they mean? Preclear root@eSilo:~# screen -r ================================================================== 1.13 = unRAID server Pre-Clear disk /dev/sda = cycle 1 of 3, partition start on sector 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it = **** This will take a while... you can follow progress below: = = = = = = = = Elapsed Time: 22:57:07 695425+26 records in 695425+26 records out 1458439135232 bytes (1.5 TB) copied, 20644.3 s, 70.6 MB/s Wrote 1,458,439,135,232 bytes out of 3,000,592,982,016 bytes (48% Done) Smart Test SMART status Info for /dev/sdf 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 WD30EFRX-68EUZN0 Serial Number: WD-WCC4N0291956 Firmware Version: 80.00A80 User Capacity: 3,000,592,982,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 9 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Wed Dec 11 11:00:32 2013 CST 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: (39900) 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: (0x703d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 100 253 021 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 2 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 - 23 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 - 2 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 1 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 291 194 Temperature_Celsius 0x0022 126 117 000 Old_age Always - 24 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 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 23 - 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. syslog-2013-12-11.zip

Alright that gives me a starting point. Thanks!

Any thoughts on why that happened?

Does anyone know why this happens "SORRY: Disk /dev/sdb MBR could NOT be precleared" This disk is no longer shown in unMenu, Syslog now shows 0 lines in unMenu whereas before the preclear there was 2000? After a reboot I can see the hard drive again. I have attached a smart report but it looks OK to me. This is the second time it has happened. Also the motherboard is an ASUS P5N-e if that is relevant. eSilo login: root Password: Linux 3.9.6p-unRAID. root@eSilo:~# screen -r = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Elapsed Time: 10:15:41 ========================================================================1.13 == == SORRY: Disk /dev/sdb MBR could NOT be precleared == == out4= 00000 == out5= 00000 ============================================================================ 0000000 0+0 records in 0+0 records out 0 bytes (0 B) copied, 3.2404e-05 s, 0.0 kB/s root@eSilo:/boot# EDIT: The PSU is an "areocool s620" which has 2 - 12V rails (also currently there are 2 - 8800gt graphics cards installed). Could this be a power issue? smart_sdb_131210_WD3TB.txt

To those of you currently using SF, does the lock out happen often? I am considering trying it out and wanted to know how much of a pain it would be. To fix it all I would have to do is log into unmenu and reboot the server or is there a command?

+1