• Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

greyday's Achievements


Newbie (1/14)



  1. The stuff I download tends to be the like 1-3 seeders type (since I have streaming services for all the mainstream stuff). I'll grab a linux torrent later tonight and see what speeds I'm getting...
  2. My VPN (Windscribe) is also doing the phase out thing and I had the same issues, so here's what I did: Downloaded the updated ca.crt and ta.key files and replaced the ones in appdata/binhex-delugevpn/openvpn folder Opened the .ovpn file (name will vary based on your vpn), deleted the line "compress lzo" as per Windscribe's instrux, then manually copied the certificate from the ca.crt file and replaced the old one, closed Started delugevpn, it worked like normal. That was all it took. Hopefully this helps some of you!
  3. I know this is close to a year old, but still--my two cents? Spend the little extra (or use parts you have) to build a separate dedicated PF/OPNsense box. The first time you have to take your server down for more than 20 minutes you'll be glad you did.
  4. Just to hopefully save some other folks some time, because it's not posted here and this is what comes up most often when I search for this problem or how to resize the log (and the next like 10 answers also never state it), the file named "go" that you need to modify is located at: boot/config/
  5. After recovering from a bum drive, I need to pull data from old drives from my encrypted array. I may end up having to try UD, but considering my workflow and the server location, it would save me MANY hours to be able to copy the files through an Ubuntu workstation. Trouble is, while Ubuntu sees the drive, whenever I enter the encryption passphrase I get an "incorrect passphrase" error. My passphrase is long, but I know I entered it correctly (and just to be sure, I tried typing it out into a libre doc and copy/pasting it). Specific error reads: Unable to mount 3.0 TB Encrypted Error unlocking /dev/sdb1: Failed to activate device: Incorrect passphrase I've tried on two of the replaced drives from the array and neither worked. Any thoughts? Am I stuck having to use UD or is there a way to access them? I am comfortable using a different distro if Ubuntu is the problem... EDIT: Nevermind. I don't know how or why but I just tried again and it worked. It is possible I had typos in every previous attempt and that Ubuntu doesn't allow pasting for passwords, but either way it's working now...
  6. Rebuild went smoothly! Now just cataloging what files I need to pull from the old drives and then on to blanking and copying over. Parity seems to be just fine, zero read errors across the board leads me to believe that this worked. I'll update if there are any other problems, but otherwise marking as solved, thanks for all your help!
  7. Or use the 1gbe to set up pfsense and control your firewall.
  8. There may be a way from windows, but if you download the UnRAID trial on a separate thumbdrive you should be able to mount each drive individually as an unassigned device and copy the files that way. If you have a backup of your original, though, you should be able to restore it, though you have to contact Lime I think to change the UUID of the thumbdrive over.
  9. This is probably a "duh" question, but I'm noticing that your unassigned drives aren't mounted. Have you tried mounting them and then adding them back into the array? This may also be why their (and a couple others) SMART reports are blank; I count at least 6 reports that just read Short INQUIRY response, skip product id A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. If you're back to 6.8.3 check their SMART reports, and maybe do a fresh diagnostics dump for us to check?
  10. This is what I was thinking too--and it involves 4TB of writes to the parity drives instead of 14, though I'm sure the difference on the lives of them will be nominal. Since it's just one drive, and there's only one other data drive larger than it, I think this plus a parity check when done may be all I need. Plus since I don't want to mount this drive in the array again and it's likely pretty buggy/crashy on its own, a rebuild may be the only way I can get a list of files that need replacing... And, the more I think about it, the worst case scenario is an extra few hours, as I'd basically be right back at the "blank it and rebuild" stage if it doesn't work. I'm gonna give it a try, will report back when it's "done"! EDIT: just for shits and giggles, here's the same SMART stats after running the deeper SMART test: 5 Reallocated Sector Count (SMART): 445 196 Reallocated Event Count (SMART): 416 197 Current Pending Sectors (SMART): 3451
  11. I have 128gb of RAM and memtest takes about 12 hours per pass.
  12. SMART reports cover the history of the drive; the UnRAID gui errors are reset when the array is rebooted. (also UnRAID read errors aren't often on the drive level, so any read errors on the drive are usually lower)
  13. The SMART reports in your zip file show a small number of read errors. Not enough to worry about IMO unless you keep getting them on those drives.
  14. Which drive(s) is/are the read errors on? I only see a few that are drive level (on disk 2 and 4), which makes me think you may have a bad cable and/or card if they're occurring continually. Try reseating your card and if you have spare cables for drives 2 and 4, replacing those and running parity again. Also you may want to run it without corrections first; opinions vary on that, and realistically since you've run it a few time with it checked it makes little sense to bother now, but in future, so if it is just a bad cable or something similar, you aren't altering parity. Personally I run my monthly checks without, that way if there are errors I can determine the cause and run again before writing corrections.
  15. That makes sense, and thank you for your responses; I will most likely remove it from the array and rebuild parity, try to salvage the files from the originally removed drives. But to continue the thought (just to understand better), I 100% get what you are saying insofar as the time during the rebuild goes, that dual parity is most certainly hosed, but wouldn't a successful rebuild mean parity is restored? My understanding is that parity is based on adding up each 1 or 0 from the same sector of each drive and determining whether that sum is odd (1) or even (0), so that if a drive falls out adding the same numbers back up with the parity values will result in the missing value (I'm a little fuzzier on dual parity, to be honest, I'm guessing it is a line by line opposite to the first parity drive?). So then wouldn't reading all the healthy drives result in parity being vaild and any damage to it being written to the rebuilt drive? What I'm wondering here is if that drive can be rebuilt, then any corrupt files removed/replaced and the file system repaired without forcing a complete parity rebuild (again, academic at this point, I'm not planning to take this approach anymore, but I'm trying to understand how parity, and dual parity, work overall)...