nanoman06

I don't know unfortunately, never looked until now. I can google and possibly call tomorrow I suppose. For now my array is turned off.

I have 5x 3TB drives. 2 are parity, 3 are data. My toshiba 3tb (parity 2) showed up with a red X some time after I transferred a bit of data to the unraid arroy. The server sits undisturbed by me in my rack (which probably vibrates like crazy). I ran the extended SMART test and the drive passed. Should I toss this drive or keep using it? Here's the download: smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.9.30-unRAID] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Toshiba 3.5" DT01ACA... Desktop HDD Device Model: TOSHIBA DT01ACA300 Serial Number: -------------------- LU WWN Device Id: 5 000039 ff4dcc23c Firmware Version: MX6OABB0 User Capacity: 3,000,592,982,016 bytes [3.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 7200 rpm Form Factor: 3.5 inches Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Thu Jul 26 18:33:11 2018 EDT 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: (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: (22222) 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: ( 371) minutes. SCT capabilities: (0x003d) 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 0x000b 100 100 016 Pre-fail Always - 0 2 Throughput_Performance 0x0005 139 139 054 Pre-fail Offline - 71 3 Spin_Up_Time 0x0007 140 140 024 Pre-fail Always - 392 (Average 425) 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 207 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 124 124 020 Pre-fail Offline - 33 9 Power_On_Hours 0x0012 098 098 000 Old_age Always - 19982 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 104 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 469 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 469 194 Temperature_Celsius 0x0002 162 162 000 Old_age Always - 37 (Min/Max 15/48) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 332 SMART Error Log Version: 1 ATA Error Count: 332 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 332 occurred at disk power-on lifetime: 19957 hours (831 days + 13 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 80 d0 c2 2b 09 Error: ICRC, ABRT at LBA = 0x092bc2d0 = 153862864 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 61 00 00 50 c2 2b 40 00 4d+20:30:26.894 WRITE FPDMA QUEUED ef 10 02 00 00 00 00 00 4d+20:30:26.697 SET FEATURES [Enable SATA feature] ef 02 00 00 00 00 00 00 4d+20:30:26.697 SET FEATURES [Enable write cache] ef aa 00 00 00 00 00 00 4d+20:30:26.697 SET FEATURES [Enable read look-ahead] ef 03 46 00 00 00 00 00 4d+20:30:26.697 SET FEATURES [Set transfer mode] Error 331 occurred at disk power-on lifetime: 19957 hours (831 days + 13 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 90 c0 c4 2b 09 Error: ICRC, ABRT at LBA = 0x092bc4c0 = 153863360 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 61 00 00 50 c2 2b 40 00 4d+20:30:26.645 WRITE FPDMA QUEUED ef 10 02 00 00 00 00 00 4d+20:30:26.448 SET FEATURES [Enable SATA feature] ef 02 00 00 00 00 00 00 4d+20:30:26.448 SET FEATURES [Enable write cache] ef aa 00 00 00 00 00 00 4d+20:30:26.448 SET FEATURES [Enable read look-ahead] ef 03 46 00 00 00 00 00 4d+20:30:26.448 SET FEATURES [Set transfer mode] Error 330 occurred at disk power-on lifetime: 19957 hours (831 days + 13 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 90 c0 c4 2b 09 Error: ICRC, ABRT at LBA = 0x092bc4c0 = 153863360 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 61 00 00 50 c2 2b 40 00 4d+20:30:26.395 WRITE FPDMA QUEUED ef 10 02 00 00 00 00 00 4d+20:30:26.141 SET FEATURES [Enable SATA feature] ef 02 00 00 00 00 00 00 4d+20:30:26.141 SET FEATURES [Enable write cache] ef aa 00 00 00 00 00 00 4d+20:30:26.141 SET FEATURES [Enable read look-ahead] ef 03 46 00 00 00 00 00 4d+20:30:26.141 SET FEATURES [Set transfer mode] Error 329 occurred at disk power-on lifetime: 19957 hours (831 days + 13 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 90 c0 c4 2b 09 Error: ICRC, ABRT at LBA = 0x092bc4c0 = 153863360 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 61 00 00 50 c2 2b 40 00 4d+20:30:25.648 WRITE FPDMA QUEUED ef 10 02 00 00 00 00 00 4d+20:30:25.452 SET FEATURES [Enable SATA feature] ef 02 00 00 00 00 00 00 4d+20:30:25.452 SET FEATURES [Enable write cache] ef aa 00 00 00 00 00 00 4d+20:30:25.452 SET FEATURES [Enable read look-ahead] ef 03 46 00 00 00 00 00 4d+20:30:25.452 SET FEATURES [Set transfer mode] Error 328 occurred at disk power-on lifetime: 19957 hours (831 days + 13 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 90 c0 c4 2b 09 Error: ICRC, ABRT at LBA = 0x092bc4c0 = 153863360 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 61 00 00 50 c2 2b 40 00 4d+20:30:25.399 WRITE FPDMA QUEUED ef 10 02 00 00 00 00 00 4d+20:30:25.262 SET FEATURES [Enable SATA feature] ef 02 00 00 00 00 00 00 4d+20:30:25.262 SET FEATURES [Enable write cache] ef aa 00 00 00 00 00 00 4d+20:30:25.262 SET FEATURES [Enable read look-ahead] ef 03 46 00 00 00 00 00 4d+20:30:25.261 SET FEATURES [Set transfer mode] SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 19966 - # 2 Short offline Completed without error 00% 19959 - 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.

The vm (now that I can see it) appears to be stuck at starting windows (installation) before I get to the driver prompts. Anyone encounter that before? I left it all day and it had not progressed beyond the multi color flash screen (w7)

I do remember reading that but after midnight I wasn't able to understand it . Thanks for the help. I plan on setting up steam and using in-home steam streaming to another pc or eventually some kind if thin client.

Yes, it was turned on and it appears as green. I just created another VM this time not passing a GPU and there is a VNC port listed - 5900. I am able to see the option you were referring to and successfully connect to it. The GUI seems pretty easy to use for GPU passthrough (which I believe my hardware completely supports) but it seems like I missed something - maybe the VM is not really turned on.

Hmm, I suppose I forgot to mention I'm passing a GPU to this VM. Not sure if that changes how I remote into it.

I am using Google Chrome 43.0.2357.130 m. I tried in IE 8 (yeah...I know) and got the same options. I tried connecting to ports: 5700, 5701, 5900, 5901 and could not connect. There is no port shown under "VNC Port". EDIT: I just tried the most recent version of Firefox and saw the same options as I did in Chrome and IE8.

Thanks for the quick reply. I do not have that option. I have: Desktop - when I click nothing happens Stop Pause Restart Force Stop View XML I also noticed if I click the text name of my VM, under VNC port, there is no port listed. Did I miss a step somewhere?

Hello all, I just installed my trial key for unraid 6.0.1. Looks like there have been quite a few upgrades since I used unraid last...ha. I created a VM for windows 7 which is currently running. I'm not sure how to connect to it so I can being installing windows though. I found old posts that explain I should use a vnc client and connect to the ip with various port numbers..5700, 5701, 5900, 5901 but I haven't had luck with any of those. How should I be connecting to the VMs I create initially?

OH, cool. I incorrectly assumed that was a bad direction..lol. Some day I should really learn to read these reports..

Thank you all who have helped in the past! I have two more drives I'd like to ask about ========================================================================1.14 == ST3000DM001- XXXXXXWA == Disk /dev/sdb has been successfully precleared == with a starting sector of 1 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 112 100 6 ok 48827176 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 71 70 45 ok 29 Temperature_Celsius = 29 30 0 ok 29 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 5. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 5. 0 sectors were pending re-allocation after post-read in cycle 1 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 5. 0 sectors were pending re-allocation after post-read in cycle 2 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 5. 0 sectors were pending re-allocation after post-read in cycle 3 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 4 of 5. 0 sectors were pending re-allocation after post-read in cycle 4 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 5 of 5. 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.14 == ST3000DM001-1CH166 XXXXXX44 == Disk /dev/sdc has been successfully precleared == with a starting sector of 1 ============================================================================ ** 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 100 6 ok 74792176 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 70 70 45 near_thresh 30 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 5. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 5. 0 sectors were pending re-allocation after post-read in cycle 1 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 5. 0 sectors were pending re-allocation after post-read in cycle 2 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 5. 0 sectors were pending re-allocation after post-read in cycle 3 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 4 of 5. 0 sectors were pending re-allocation after post-read in cycle 4 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 5 of 5. 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. These came out of the box and were ran through 5 cycles as I normally do. Are these drives worthy of joining my array or do they need to go back into the box? Do these issues mean something when they are presented at the same time? (dropped during shipping?)

Disk Temperature: 37C, Elapsed Time: 30:05:55 ========================================================================1.14 == TOSHIBADT01ACA300 XXXXXXX == Disk /dev/sdc has been successfully precleared == with a starting sector of 1 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdc /tmp/smart_finish_sdc ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 162 166 0 ok 37 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. What's up with the bolded line?

I rebooted and it seems like there isn't an issue anymore. I made 5 other directories in \Movies and I was able to copy into all of them. Thanks gentleman

@ Gary - I looked around a little more but still don't see anything that indicates what you're asking for. @ Itimpi - I put 20000000 in but that did not help. I renamed the file and was able to copy it into \Movies. Seems like I can't copy it into \Movies\Test. Derp for not figuring that out earlier.. EDIT: I can however copyfiles under 8.5GB into \Movies\Test. odd..

Unfortunately I do not understand what you're asking me for. I don't see this in any of the settings windows I can see. Does it matter though? Does one method cap out at 8.5GB? The guest OS is windows 7. I presume you mean the ROUTER is a Cisco/Linksys E1000. That's not a NIC No, I mean the E1000 nic.

I am using vmware - 5.5. Vm is windows 7. I haven't changed anything beyond whatever default settings are for the vm. The nic is the E1000. I made a new folder called test (inside of the media share) so, I'm not copying it back to the same directory. I did not change the name of the file.

Added. Everything is on the same network if that is what you mean? I copy and swap files regularly. My iso's live on the unraid box as well. I copied the file from the unraid box to this vm. I just wanted to test the speed of copying the file back to the unraid box.

This is the share. Im copying from the console of a win 7 VM to the unraid box.

I am having an issue copying a large (slightly over 10GB) file to my unraid box. It says there needs to be 1.5GB free'd up but there is just over 2TB free on the drive that I am currently using. Any ideas?

========================================================================1.14 == ST3320311CS == Disk /dev/sdb has been successfully precleared == with a starting sector of 64 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 113 117 6 ok 57888365 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 64 71 45 near_thresh 36 Temperature_Celsius = 36 29 0 ok 36 Hardware_ECC_Recovered = 59 57 0 ok 57888365 No SMART attributes are FAILING_NOW ========================================================================1.14 == ST3320311CS == 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 Raw_Read_Error_Rate = 119 114 6 ok 225771406 Start_Stop_Count = 37 37 20 near_thresh 65535 Power_On_Hours = 82 83 0 ok 15778 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 1 1 0 near_thresh 794 Airflow_Temperature_Cel = 64 71 45 In_the_past 36 Temperature_Celsius = 36 29 0 ok 36 No SMART attributes are FAILING_NOW Are these drives okay to use?

Can I run unRAID on one of the embedded AMD APUs? I'm thinking this model in particular: http://www.newegg.com/Product/Product.aspx?Item=N82E16813157228 It comes with 4 sata ports and has a pcie x16 slot that I can put a SATA card into later for more drives. My main concern is compatibility. I've read the power draw is very low on this APU which is what drew my attention. Also, do we know what can't unRAID run on?

no, they look great. Probably... only time will tell. So I should not be worried about the raw read error rate or spin retry count? Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 I could not improve on Joe's response, as he was absolutely correct. Just a tip, if you are going to question the experts, it would be good to understand the subject matter first? As you can see above, the VALUE's for Spin_Retry_Count and End-to-End_Error are 100, could not be more perfect. The VALUE's for Raw_Read_Error_Rate for 2 of the drives at THIS moment are a little below 100, but are not a problem, they are still a long way from 44. I believe you misinterpreted the text.. I am unfamiliar with most of the test results. I know that I have had some drives that return with no additional notes above the 0 SMART failures list before. I wasn't sure if he perhaps had missed the notes above the smart tests. These drives were different, they listed a few seemingly not great things. Thank you both for shedding some light on the result from the preclear script. I feel comfortable with filling these drives now

no, they look great. Probably... only time will tell. So I should not be worried about the raw read error rate or spin retry count? I have another 3tb that came out with this: == ST3000DM001-1CH166 W1F2YATC == Disk /dev/sdc has been successfully precleared == with a starting sector of 1 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdc /tmp/smart_finish_sdc ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_V LUE Raw_Read_Error_Rate = 118 102 6 ok 17262 704 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 74 77 45 ok 26 Temperature_Celsius = 26 23 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 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@Storage:/boot#

Can anyone give me an opinion on these resultes? Are the drives bad? They are two days out of the original packaging.. Drive 1: ========================================================================1.14 == GB1000EAFJL == Disk /dev/sdb has been successfully precleared == with a starting sector of 64 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VA LUE Raw_Read_Error_Rate = 78 82 44 ok 774410 85 Spin_Retry_Count = 100 100 97 near_thresh 0 Airflow_Temperature_Cel = 63 65 45 near_thresh 37 Temperature_Celsius = 37 34 0 ok 37 Hardware_ECC_Recovered = 59 38 0 ok 774410 85 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 5. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 5. 0 sectors were pending re-allocation after post-read in cycle 1 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 5. 0 sectors were pending re-allocation after post-read in cycle 2 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 5. 0 sectors were pending re-allocation after post-read in cycle 3 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 4 of 5. 0 sectors were pending re-allocation after post-read in cycle 4 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 5 of 5. 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. Drive 2: ========================================================================1.14 == GB1000EAFJL == 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_V LUE Raw_Read_Error_Rate = 81 82 44 ok 15229 693 Spin_Retry_Count = 100 100 97 near_thresh 0 Airflow_Temperature_Cel = 64 66 45 near_thresh 36 Temperature_Celsius = 36 34 0 ok 36 Hardware_ECC_Recovered = 66 48 0 ok 15229 693 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 5. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 5. 0 sectors were pending re-allocation after post-read in cycle 1 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 5. 0 sectors were pending re-allocation after post-read in cycle 2 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 5. 0 sectors were pending re-allocation after post-read in cycle 3 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 4 of 5. 0 sectors were pending re-allocation after post-read in cycle 4 of 5. 0 sectors were pending re-allocation after zero of disk in cycle 5 of 5. 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. Are these drives reliable?

Nope, it actually began reading slower than 3MBps, ~450KBps as I kept switching and re-testing.