yaksaredabomb

All 3 drives are fine, no issues seen. The white label drive looks like a WD, same SMART attributes. Thanks very much, RobJ! I appreciate your time and the good news didn't hurt either . Have a good one!

Hello, I'm hoping someone will help take a look at the preclear results for these three drives to see if there is anything I should be concerned about or keep an eye on. Only 4 attachments are allowed so I've attached the reports, starts, and finishes together in one zip file "preclearFiles.zip" The 4TB drives seem to have more SMART attributes in the report than the 6TB, even though the 6TB's "finish" file says its SMART support is available and enabled. Maybe there is something extra I need to do in the BIOS or preclear switches? The 4TB drives are both Seagate but the 6TB drive is a "white label" with just a one year warranty so I'm more concerned about it. Thank you for anyone's input! Without further ado, here are the contents of the reports: ST4000DM000-1F2168 W3002X5W ========================================================================1.15 == invoked as: /boot/preclear_disk.sh -c 3 /dev/sdc == ST4000DM000-1F2168 W3002X5W == Disk /dev/sdc has been successfully precleared == with a starting sector of 1 == Ran 3 cycles == == Using :Read block size = 8388608 Bytes == Last Cycle's Pre Read Time : 9:51:06 (112 MB/s) == Last Cycle's Zeroing time : 8:45:43 (126 MB/s) == Last Cycle's Post Read Time : 23:15:30 (47 MB/s) == Last Cycle's Total Time : 32:02:14 == == Total Elapsed Time 105:31:57 == == Disk Start Temperature: 29C == == 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 Raw_Read_Error_Rate = 111 119 6 ok 38120536 Seek_Error_Rate = 64 62 30 ok 2892140 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 90 95 0 ok 10 Airflow_Temperature_Cel = 70 71 45 near_thresh 30 Temperature_Celsius = 30 29 0 ok 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 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. ============================================================================ ST4000DM000-1F2168 Z3006399 ========================================================================1.15 == invoked as: /boot/preclear_disk.sh -c 3 /dev/sdb == ST4000DM000-1F2168 Z3006399 == Disk /dev/sdb has been successfully precleared == with a starting sector of 1 == Ran 3 cycles == == Using :Read block size = 8388608 Bytes == Last Cycle's Pre Read Time : 9:37:50 (115 MB/s) == Last Cycle's Zeroing time : 8:32:32 (130 MB/s) == Last Cycle's Post Read Time : 22:51:46 (48 MB/s) == Last Cycle's Total Time : 31:25:18 == == Total Elapsed Time 103:29:49 == == Disk Start Temperature: 29C == == Current Disk Temperature: 30C, == ============================================================================ ** 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 = 114 111 6 ok 74700168 Seek_Error_Rate = 63 61 30 ok 2620745 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 93 97 0 ok 7 Airflow_Temperature_Cel = 70 71 45 near_thresh 30 Temperature_Celsius = 30 29 0 ok 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 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. ============================================================================ WL6000GSA6454 WOL240346597 ========================================================================1.15 == invoked as: /boot/preclear_disk.sh -c 2 /dev/sda == WL6000GSA6454 WOL240346597 == Disk /dev/sda has been successfully precleared == with a starting sector of 1 == Ran 2 cycles == == Using :Read block size = 8388608 Bytes == Last Cycle's Pre Read Time : 15:43:39 (109 MB/s) == Last Cycle's Zeroing time : 13:00:39 (132 MB/s) == Last Cycle's Post Read Time : 36:20:24 (47 MB/s) == Last Cycle's Total Time : 49:22:02 == == Total Elapsed Time 114:41:28 == == Disk Start Temperature: 30C == == Current Disk Temperature: 29C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sda /tmp/smart_finish_sda ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Unknown_Attribute = 4 0 0 near_thresh 85883701621 Temperature_Celsius = 123 122 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 2. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 2. 0 sectors were pending re-allocation after post-read in cycle 1 of 2. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 2. 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. ============================================================================ preclearFiles.zip

Thank you so much for working on this, SlrG! I was burglarized a few months ago and afterwards got a wired IP camera (specifically this one here http://www.dahuasecurity.com/products/ipc-hdw2100-195.html). I set it up just assuming, for some reason, that I could set it up to record to my Unraid box (they both connect to the same switch). I then discovered oops, ftp is apparently not a simple thing to get working - at least not for a Linux noob like me haha. Hopefully one day in the next few months I'll be able to get my camera to record to Unraid somehow. I'm hoping not to be burglarized again of course, but if it does happen again I'd love to be able to have a clue about when it was, what was taken, how many people there were, and maybe even how they got in or who they were. I know some people have said they setup ftp on a computer and then copy the files from there to their Unraid box, but I'd really rather not have another device in the loop using power and being a possible source of failure. Right now I'm running 4.7, but I have a couple 4TB drives pre-clearing on 5.0-rc12a via the preclear_disk.sh script and virtual terminals on the console. I'm wary of migrating the array I care about to a beta but I'm considering it soon. After all, this is only the 36th iteration of version 5 so how many bugs can be left? Ok, maybe a lot - I don't know how these things work haha. Thanks again anyways for your work on this. Looking forward to seeing if I can use it to help set up an ftp destination for my ipcam!