JohnnyDrama

Has anyone successfully configured a docker-compose for a wireguard VPN? (Mullvad). I'm stuck on how to put in the sysctls.

Because then I'd have to fiddle around with fixing up shares/split levels etc, which I don't have time to do. It's much easier for me to swap a drive or kick off a parity check then go to work or go to sleep, and do the next step later when I'm back at home. The point is that it *should* work. I know that IT doesn't always work the way it should (I work with geographically distributed FC/SSD enterprise storage in the multi-petabyte range) but it's a risk that I take. I have backups of the important stuff if it totally dies. In any case, I'm running MD5 checks on all the files on all volumes, from MD5 hashes stored when the files were moved to the array, and so far they have all passed clean. Odd.

Thanks, I seem to have missed that thread in my quick search. I have one more upgrade yet to complete (sde: WD15EARS to WD20EARS), if you would like me to do anything before I start it later tonight, please let me know. After the upgrade I plan to add both old WD15EARS drives as new drives to the array (zeroing out the MBR and then re-adding them).

Hey guys, I did a small upgrade (1.5tb to 2.0tb drive) on my unraid box, specs as follows: SuperMicro X7SPA-HF 2x 2gig Kingston sodimms. sda - WD20EARS sdb - WD20EARS sdc - WD15EARS originally, now upgraded to WD20EARS sde - WD15EARS Memtest was run overnight before the upgrade and passed fine. To be extra careful, I ran a reiserfsck on each data drive (not the parity) one drive at a time, and this passed with no errors. A partiy check was then run, and passed fine with no sync errors. I followed the procedure in the Wiki to upgrade a drive - power down, remove old drive, insert new drive, power up, start array and let it rebuild & expand. This occured with no errors. Once this was done, I ran another parity check as I'd like to replace sdd with another ES20EARS. The check completed with 4 errors. I have attached a syslog with the full output, however the lines involved are: Jun 21 01:19:04 R2D2 kernel: md: recovery thread checking parity... Jun 21 01:19:04 R2D2 kernel: md: using 1152k window, over a total of 1953514552 blocks. Jun 21 01:19:11 R2D2 kernel: md: parity incorrect: 16240 Jun 21 01:19:11 R2D2 kernel: md: parity incorrect: 19552 Jun 21 01:19:11 R2D2 kernel: md: parity incorrect: 19560 Jun 21 01:19:11 R2D2 kernel: md: parity incorrect: 19568 Jun 21 09:08:45 R2D2 kernel: md: sync done. time=28181sec rate=69320K/sec I'm a little concerned, however I understand that the updates occured to correct parity information. What worries me is that there was bad parity to start with, and my data drive I upgraded may not have rebuilt cleanly in the first place. I have the old drive and have considered doing an initconfig with it, and starting the process from scratch, but wanted to get some feedback from the gurus here first Any ideas? Am I being overly paranoid? edit - added smartctl outputs for each drive unraid.txt smart.txt

Hey guys, Just completed my first ever unRAID build, specs are in my sig. Quite pleased at the ease of use, and speed at getting this up and running. I ran the preclear script on my 3 WD10EARS (jumpered) drives by opening 3 shells and running the script for each drive on a different shell, before adding them to the array and building parity for the first time. I noticed my third drive (sdc) logged some errors and I shrugged them off at the time as a couple of simple read errors, but now I'm wondering if I should have paid more attention before adding it to the array and letting it rebuild parity (sda). Just wondering if anyone can put my mind at ease? I've attached my full syslog as a ZIP in case it's needed or if anyone is just curious. == Disk /dev/sdc has been successfully precleared == == Ran 1 preclear-disk cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 7:01:54 (59 MB/s) == Last Cycle's Zeroing time : 7:27:25 (55 MB/s) == Last Cycle's Post Read Time : 16:58:26 (24 MB/s) == Last Cycle's Total Time : 31:28:54 == == Total Elapsed Time 31:28:54 == == Disk Start Temperature: 30C == == Current Disk Temperature: 35C, == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 19,20c19,20 < Offline data collection status: (0x80)^IOffline data collection activity < ^I^I^I^I^Iwas never started. --- > Offline data collection status: (0x84)^IOffline data collection activity > ^I^I^I^I^Iwas suspended by an interrupting command from host. 54c54 < 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 --- > 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 2 58c58 < 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 --- > 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 63c63 < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 29 --- > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 31 ============================================================================ syslog.zip