neilt0 Posted May 12, 2015 Author Share Posted May 12, 2015 Good luck putting an 800W PSU in a Microserver! :-) I do have an 850W PSU in one of my older servers, but I prefer using two Microservers with a small number of high capacity drives in each. Quote Link to comment
c3 Posted May 12, 2015 Share Posted May 12, 2015 Yes, the HP Microserver is one of those great platforms for storage. Did anyone every get the 16GB working? I know they got a single 8GB stick working. Quote Link to comment
neilt0 Posted May 12, 2015 Author Share Posted May 12, 2015 There are several DIMMs that get you to 16GB in the G7, but they weren't cheap last time I looked, so I stuck with 8GB. Quote Link to comment
JackBauer Posted May 16, 2015 Share Posted May 16, 2015 Can someone more knowledgeable than me comment on the results? I ran ONE cycle on each drive, in parallel. ========================================================================1.15 == invoked as: ./preclear_disk.sh /dev/sdh == ST8000AS0002 == Disk /dev/sdh has been successfully precleared == with a starting sector of 1 == Ran 1 cycle == == Using :Read block size = 8388608 Bytes == Last Cycle's Pre Read Time : 17:19:54 (128 MB/s) == Last Cycle's Zeroing time : 19:08:23 (116 MB/s) == Last Cycle's Post Read Time : 40:43:30 (54 MB/s) == Last Cycle's Total Time : 77:13:03 == == Total Elapsed Time 77:13:03 == == Disk Start Temperature: 35C == == Current Disk Temperature: 33C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdh /tmp/smart_finish_sdh ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 104 100 6 ok 6600680 Seek_Error_Rate = 73 100 30 ok 21788094 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 67 65 45 near_thresh 33 Temperature_Celsius = 33 35 0 ok 33 Hardware_ECC_Recovered = 104 100 0 ok 6600680 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. ============================================================================ ========================================================================1.15 == invoked as: ./preclear_disk.sh /dev/sdj == ST8000AS0002 == Disk /dev/sdj has been successfully precleared == with a starting sector of 1 == Ran 1 cycle == == Using :Read block size = 8388608 Bytes == Last Cycle's Pre Read Time : 17:01:00 (130 MB/s) == Last Cycle's Zeroing time : 18:41:33 (118 MB/s) == Last Cycle's Post Read Time : 40:09:07 (55 MB/s) == Last Cycle's Total Time : 75:52:45 == == Total Elapsed Time 75:52:45 == == Disk Start Temperature: 35C == == Current Disk Temperature: 34C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdj /tmp/smart_finish_sdj ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 120 100 6 ok 241910736 Seek_Error_Rate = 73 100 30 ok 21319826 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 66 65 45 near_thresh 34 Temperature_Celsius = 34 35 0 ok 34 Hardware_ECC_Recovered = 120 100 0 ok 241910736 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. ============================================================================ Quote Link to comment
danioj Posted May 16, 2015 Share Posted May 16, 2015 Can someone more knowledgeable than me comment on the results? I ran ONE cycle on each drive, in parallel. ========================================================================1.15 == invoked as: ./preclear_disk.sh /dev/sdh == ST8000AS0002 == Disk /dev/sdh has been successfully precleared == with a starting sector of 1 == Ran 1 cycle == == Using :Read block size = 8388608 Bytes == Last Cycle's Pre Read Time : 17:19:54 (128 MB/s) == Last Cycle's Zeroing time : 19:08:23 (116 MB/s) == Last Cycle's Post Read Time : 40:43:30 (54 MB/s) == Last Cycle's Total Time : 77:13:03 == == Total Elapsed Time 77:13:03 == == Disk Start Temperature: 35C == == Current Disk Temperature: 33C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdh /tmp/smart_finish_sdh ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 104 100 6 ok 6600680 Seek_Error_Rate = 73 100 30 ok 21788094 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 67 65 45 near_thresh 33 Temperature_Celsius = 33 35 0 ok 33 Hardware_ECC_Recovered = 104 100 0 ok 6600680 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. ============================================================================ ========================================================================1.15 == invoked as: ./preclear_disk.sh /dev/sdj == ST8000AS0002 == Disk /dev/sdj has been successfully precleared == with a starting sector of 1 == Ran 1 cycle == == Using :Read block size = 8388608 Bytes == Last Cycle's Pre Read Time : 17:01:00 (130 MB/s) == Last Cycle's Zeroing time : 18:41:33 (118 MB/s) == Last Cycle's Post Read Time : 40:09:07 (55 MB/s) == Last Cycle's Total Time : 75:52:45 == == Total Elapsed Time 75:52:45 == == Disk Start Temperature: 35C == == Current Disk Temperature: 34C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdj /tmp/smart_finish_sdj ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 120 100 6 ok 241910736 Seek_Error_Rate = 73 100 30 ok 21319826 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 66 65 45 near_thresh 34 Temperature_Celsius = 34 35 0 ok 34 Hardware_ECC_Recovered = 120 100 0 ok 241910736 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. ============================================================================ Seems fine to me. Although I would do more than 1 cycle. I'd suggest running them for 2 more (LT don't suggest 3 cycles for no reason). If you want quicker post write read times then use BJP's "faster" preclear script. Worked fine for me. Also - Weebo suggested something to me that I liked - a long S.M.A.R.T test post preclears which essentially gives you final confidence in the drive and puts a marker in the log for future reference. I liked that. What I'm suggesting is going to put you out a fair few more days BUT we are talking about drive confidence and it is your data that's going on them! I guess it's all a matter of perspective and cost vs gain. But for me for the sake of a few days KNOWING the drives have had a strenuous work before trusting them with your data is a nice peice of mind. Quote Link to comment
JackBauer Posted May 17, 2015 Share Posted May 17, 2015 Thanks - I may do one more preclear... Strange seeing two identical drives, that started preclears 4 sec apart, to have a 1 hour & 21 minute overall differential on the preclears... Preclear Successful ... Total time 77:13:03 ... Pre-Read time 17:19:54 (128 MB/s) ... Zeroing time 19:08:23 (116 MB/s) ... Post-Read time 40:43:30 (54 MB/s) Preclear Successful ... Total time 75:52:45 ... Pre-Read time 17:01:00 (130 MB/s) ... Zeroing time 18:41:33 (118 MB/s) ... Post-Read time 40:09:07 (55 MB/s) Quote Link to comment
pras1011 Posted May 17, 2015 Share Posted May 17, 2015 On the second time use the faster preclear script and use the -W option to bypass the the pre-read. Quote Link to comment
danioj Posted May 17, 2015 Share Posted May 17, 2015 Thanks - I may do one more preclear... Strange seeing two identical drives, that started preclears 4 sec apart, to have a 1 hour & 21 minute overall differential on the preclears... Preclear Successful ... Total time 77:13:03 ... Pre-Read time 17:19:54 (128 MB/s) ... Zeroing time 19:08:23 (116 MB/s) ... Post-Read time 40:43:30 (54 MB/s) Preclear Successful ... Total time 75:52:45 ... Pre-Read time 17:01:00 (130 MB/s) ... Zeroing time 18:41:33 (118 MB/s) ... Post-Read time 40:09:07 (55 MB/s) There are a number of factors that can affect this when trying to preclear multiple drives at the same time - are they utilising the same bus, different controllers etc etc BUT on average your speeds are within the norm that I have experienced (it happened to me too). Quote Link to comment
danioj Posted May 17, 2015 Share Posted May 17, 2015 On the second time use the faster preclear script and use the -W option to bypass the the pre-read. I wouldn't use this switch. Use the Faster preclear sure - BUT remember this is not just about clearing the drive it is also about giving them a workout and getting over the mortality period - its all a work out. I'd rather have my drives fail when going through this routine than when I have important data on them or when you want your array available. Just bite the bullet, run the cycles and wait! You'll be better off! Quote Link to comment
c3 Posted May 18, 2015 Share Posted May 18, 2015 On the second time use the faster preclear script and use the -W option to bypass the the pre-read. I wouldn't use this switch. Use the Faster preclear sure - BUT remember this is not just about clearing the drive it is also about giving them a workout and getting over the mortality period - its all a work out. I'd rather have my drives fail when going through this routine than when I have important data on them or when you want your array available. Just bite the bullet, run the cycles and wait! You'll be better off! If you run the script for more than one cycle it does not do the pre-read again, hence if you are manually running the script multiple times, you can use the -W to get the same workout. Quote Link to comment
JackBauer Posted May 21, 2015 Share Posted May 21, 2015 I just re-ran a FULL pre-clear on both. ========================================================================1.15 == ST8000AS0002 == Disk /dev/sdh has been successfully precleared == with a starting sector of 1 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdh /tmp/smart_finish_sdh ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 108 119 6 ok 19881872 Seek_Error_Rate = 76 73 30 ok 43858244 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 69 64 45 near_thresh 31 Temperature_Celsius = 31 36 0 ok 31 Hardware_ECC_Recovered = 108 119 0 ok 19881872 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. == ST8000AS0002 == Disk /dev/sdj has been successfully precleared == with a starting sector of 1 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdj /tmp/smart_finish_sdj ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 104 117 6 ok 6679376 Seek_Error_Rate = 76 73 30 ok 43018460 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 68 64 45 near_thresh 32 Temperature_Celsius = 32 36 0 ok 32 Hardware_ECC_Recovered = 104 117 0 ok 6679376 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. smartctl -a info: 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 119 099 006 Pre-fail Always - 231985856 3 Spin_Up_Time 0x0003 099 099 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 1 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 076 060 030 Pre-fail Always - 44125258 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 203 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 1 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 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 072 060 045 Old_age Always - 28 (Min/Max 28/40) 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 - 6 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 11 194 Temperature_Celsius 0x0022 028 040 000 Old_age Always - 28 (0 28 0 0 0) 195 Hardware_ECC_Recovered 0x001a 119 099 000 Old_age Always - 231985856 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 - 148451249619101 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 31256106448 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 95360491263 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 119 099 006 Pre-fail Always - 201831768 3 Spin_Up_Time 0x0003 099 099 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 1 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 076 060 030 Pre-fail Always - 43265003 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 203 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 1 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 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 071 059 045 Old_age Always - 29 (Min/Max 28/41) 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 - 6 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 11 194 Temperature_Celsius 0x0022 029 041 000 Old_age Always - 29 (0 28 0 0 0) 195 Hardware_ECC_Recovered 0x001a 119 099 000 Old_age Always - 201831768 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 - 130975027691674 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 31256106432 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 95360474552 Comments guys? Thanks Quote Link to comment
HellDiverUK Posted May 28, 2015 Share Posted May 28, 2015 I just re-ran a FULL pre-clear on both. Comments guys? Pretty normal it would seem, I get similar reading from my pair. Quote Link to comment
danioj Posted May 29, 2015 Share Posted May 29, 2015 I just re-ran a FULL pre-clear on both. Comments guys? Pretty normal it would seem, I get similar reading from my pair. Both are fine IMHO. Quote Link to comment
pras1011 Posted May 31, 2015 Share Posted May 31, 2015 Any notice how this these drives tick/click? Quote Link to comment
gtaylor Posted June 4, 2015 Share Posted June 4, 2015 Is there anything I need to upgrade/change before adding these 8TB drives? I'm currently running unRAID 5.0.6 (latest release) with the following hardware: CPU: Intel Core i3 2100T Mainboard: Supermicro X9SCM-F LGA1155 SAS Controller: LSI M1015 <- Running v7 firmware System Memory: Kingston KVR1333D3E9SK2/8G (2 x 4GB Kit) Case: Norco RPC-4224 Power Supply: Seasonic X-750 750W USB: Lexar Echo ZX 8GB Drives: A mix of WD REDs, Hitachi 5k3000 & Samsung drives. The firmware on my LSI M1015 is a little out of date but everything is working fine so I haven't seen the need to update. Is there anything else I need to consider before adding 8TB drives to my array? Quote Link to comment
opentoe Posted June 4, 2015 Share Posted June 4, 2015 Any notice how this these drives tick/click? To me, this is Seagate just being Seagate. I bought one drive to "play" around with it and it ticks away. Maybe Seagate forgot to add some oil and lubrication in there? Quote Link to comment
garycase Posted June 4, 2015 Share Posted June 4, 2015 The "tick" is likely just a seek ... there may be a few more seeks than in a typical drive, since many writes will use the persistent cache. Also, when you're not writing to the drive, the firmware (after some unspecified amount of idle time) will empty that cache and do any pending band rewrites ... this will also result in a bit of seek activity. No way of knowing for sure if that's what you're hearing, but it would certainly explain the extra "ticks". Quote Link to comment
enetec Posted June 5, 2015 Share Posted June 5, 2015 Any notice how this these drives tick/click? To me, this is Seagate just being Seagate. I bought one drive to "play" around with it and it ticks away. Maybe Seagate forgot to add some oil and lubrication in there? LOL Opentoe can you describe better your clicks? When they occours? Quote Link to comment
opentoe Posted June 5, 2015 Share Posted June 5, 2015 Any notice how this these drives tick/click? To me, this is Seagate just being Seagate. I bought one drive to "play" around with it and it ticks away. Maybe Seagate forgot to add some oil and lubrication in there? LOL Opentoe can you describe better your clicks? When they occours? During power on and mostly during reads and writes. I just assume it is the normal sound of this drive. Most drives I have are silent. So this one just stands out a little, PLUS I'm using it in an exposed SATA dock. So it may sound louder. I've used other drives in this dock, the 8TB is the loudest. I can break out the sound meter if really interested. Quote Link to comment
garycase Posted June 5, 2015 Share Posted June 5, 2015 ... I can break out the sound meter if really interested. Your comment implies these are pretty loud clicks ... I had assumed they were typical seeking noises (30-35db I'd guess). Are they louder than that? Quote Link to comment
opentoe Posted June 5, 2015 Share Posted June 5, 2015 ... I can break out the sound meter if really interested. Your comment implies these are pretty loud clicks ... I had assumed they were typical seeking noises (30-35db I'd guess). Are they louder than that? In a silent room with just the exposed drive in an external dock the decibels were 30-32dB. I would imagine the normal sound of the drive. If I had two to compare I can confirm that's a normal sound and not some kind of defect. Quote Link to comment
garycase Posted June 5, 2015 Share Posted June 5, 2015 Agree ... that sound level isn't unusual for actuator movements (i.e. seeks). I suspect this is exactly what I suggested earlier ... just movement associated with "housekeeping" of the shingled bands and persistent cache. I've installed a couple of these drives for some friends (not with UnRAID) ... next time I'm at one of their homes I'll listen very carefully to see if I can hear what you're referring to => they're mounted internally in a VERY well insulated case (Fractal) ... so we'll have to pop the side off the case, but that's not a problem. Daniel => Have you heard any indication of this? My guess is that the noise level is low enough that when the drives are mounted in a case, the normal noise level from the fans probably masks this sound ... or at least makes it very difficult to hear. Quote Link to comment
HellDiverUK Posted June 6, 2015 Share Posted June 6, 2015 Both mine are noisy, only drives I have that are noisier are my two Toshiba MC04 drives, which are an enterprise drive. Even my WD RE drives are quieter than the Seagates. Quote Link to comment
danioj Posted June 6, 2015 Share Posted June 6, 2015 Both mine are noisy, only drives I have that are noisier are my two Toshiba MC04 drives, which are an enterprise drive. Even my WD RE drives are quieter than the Seagates. Mine are absolutely fine. The 2 I have in the Main Server in a Fractal Design R5 (which does have EXCELLENT dampening) I can't hear a thing. Pure silence. The 3 I have in the Backup Server in a Silverstone DS380 I do hear them spin up (if I REALLY listen) and there is a very low sort of high pitched sound before the standard seek "tap" which (again if I REALLY listen) I can hear. And by REALLY I mean having nothing else running (tv etc) no one talking (everyone is out) and the windows closed. Plus because its a Backup Server it serves NO clients at all so in normal operation the 3 drives are spun down all day until 12am (when I am in bed anyway) when the daily incremental backup kicks in from the onboard W10 VM. All in all its all pretty much a silent setup to me. Quote Link to comment
johnsanc Posted June 6, 2015 Share Posted June 6, 2015 I haven't noticed any abnormal noises with mine. I will say these are definitely worth the money. I currently just have one as my parity drive right now and I beat the hell out of it. Lately I've had a few things that required operations on several hundred gigabytes of data. No issues with downloading massive (200gb+) torrents to a protected share. No issues with recompressing an entire harddrive's worth of files on a protected share. I don't think I have ever "hit the wall" so to speak. I wish there was a way to directly monitor the persistent cache, it would be really interesting to see it in action. 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.