whipdancer

Isn't that just based on your settings?

In the US, being shucked is not automatically grounds for rejecting a repair. It's certainly more of a hassle, but the right-to-repair laws are normally on your side. After having my internal drive repair rejected because of "evidence of tampering", I quit worrying about it. I'll save the approx. $120 per drive (x15 so far) and take my chances in small claims court if it fails within the warranty period.

I do. Pre-cleared, ready to go.

Like @Vr2Io said - could be helium or air CMR drives. I don't think they were regularly priced at $159. https://shucks.top/

NVidia Shield, Roku+, Apple TV. Using Plex, I rarely encounter any issues playing back UHD source anymore because my device is what does the decoding - not my server. My server is able to just stream the file directly in most cases. The only thing that seems to give me a headache are the HD sound tracks (because the server has to transcode those) and subtitles (again, forces transcoding).

I had both N300 and X300 drives in various sizes. No issues.

I found the answer - I found the clipboard and was able to paste it there, then copy it and paste it into the registration text. Hopefully someone has run into this previously, but I can't enter my registration code successfully. I can't paste it directly, so I do have to type it in (it's a 68 character string). I'm pretty sure I enter it correctly (made sure I'm using a font that display Ii10Oo distinctly). I see an error pop up every time - "Registration code is incorrect". Is there any way to populate the registration code via the settings? Or any idea what else I can try? Thanks for any assistance!

Have you tried brickseek?

If the budget isn't a barrier, why bother with consumer grade? Move up to a dual CPU server MB with a pair Xeon's and ECC memory. Greater expansion, more power, more room to handle unanticipated needs.

Hi! I have this running on my server now, but I'm not sure how to actually do what I'm after. In your wiki documentation, you mention your plugin stack: Is that available somewhere? It is very close to what I'm trying to do.

Does anyone in that community have experience running Synapse in a Docker? How do they deal with the settings you need in a Docker? If not, does anyone in that community have experience running it in a VM?

*** IANANA/E (i am not a network architect/engineer) *** Have you planned out your network? Literally drawn up a map for it? I'm not good enough at network architecture to do anything beyond basic configuration without drawing up a diagram/map/<something> to make sure I'm not missing something. How do you plan on connecting VLAN 80 to pfSense?

I cleared my last 4 drives with preclear and I'm on 6.4.0. Like @wreave mentioned, I'm concerned about the stress test - is there another tool that will facilitate a stress test?

Based on what I've read in this thread (and these boards), I think theses drives should be ok. Any feedback? I did run badblocks prior to running preclear 3 cycles (both drives): ========================================================================1.13 == invoked as: ./preclear_disk.sh -M 3 -c 3 /dev/sdd == Hitachi HDT721010SLA360 STF604MR20HZ0P == Disk /dev/sdd has been successfully precleared == with a starting sector of 64 == Ran 3 cycles == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 3:24:52 (81 MB/s) == Last Cycle's Zeroing time : 3:06:57 (89 MB/s) == Last Cycle's Post Read Time : 8:11:33 (33 MB/s) == Last Cycle's Total Time : 11:19:38 == == Total Elapsed Time 37:32:40 == == Disk Start Temperature: 37C == == Current Disk Temperature: 38C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdd /tmp/smart_finish_sdd ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 157 162 0 ok 38 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. 5 sectors had been re-allocated before the start of the preclear. 5 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================ ========================================================================1.13 == invoked as: ./preclear_disk.sh -M 3 -c 3 /dev/sdk == Hitachi HDT721010SLA360 STF607MH32SY3K == Disk /dev/sdk has been successfully precleared == with a starting sector of 64 == Ran 3 cycles == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 3:28:25 (79 MB/s) == Last Cycle's Zeroing time : 3:10:20 (87 MB/s) == Last Cycle's Post Read Time : 8:15:26 (33 MB/s) == Last Cycle's Total Time : 11:26:53 == == Total Elapsed Time 38:07:19 == == Disk Start Temperature: 34C == == Current Disk Temperature: 35C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdk /tmp/smart_finish_sdk ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 171 176 0 ok 35 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. 1 sector had been re-allocated before the start of the preclear. 1 sector is re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================ Thanks, ~Whip