tdallen

Love the new theme, thank you!

Interesting card, but since it's made for QNAP enclosures you may have trouble with unRAID having the appropriate drivers. I don't have any direct experience, though.

If you just want to start by burning in the new hardware, you could use an unRAID 30-day Trial License for the purpose.

I started off my unRAID server with High Watermark and all disks included in all shares. It's a good setting for a new user to start with, and remains a good setting for users who just like to use their server rather than tinker with it. That said, I came to three conclusions. One, I actively manage my server - disks aren't going to fill up without my knowing. Two, I didn't like having files in a share scattered unnecessarily across multiple disks. Three, while having equal amounts of data smoothly spread across all disks seems appealing, it's actually a pain to manage. So, at the recommendation of some folks here like @SSD I switched over to having shares "include" only the disks I want the data on, and all shares are set to "Fill" each disk (with a nice big minimum free space). I also use the diskmv/consld8 utilities to move data from one set of disks to another when infrequently needed. Warning, this is a more advanced approach that requires you to actively manage your server - one disk could fill up while you have space available on others. But I prefer it so far.

No. There are a couple of ways you can arrange to move them. But, simply adding/rearranging the disks in the share settings doesn't automatically cause files to be moved.

If you create a "Media" share (well, any share), and you don't use a solution like cachedirs, then when you access the Media share the only way unRAID will have to determine the contents is to spin up all the drives associated with that share. Unused drives will spin back down after the standard delay. My personal preference is setup more granular shares - TV Shows, Movies, etc. And I target certain drives to be associated with each share. That minimizes the number of drives that need to spin up when a share is accessed.

Personal Preference - I feel like a Media folder is too general and prefer Movies, TV Shows, etc. Why would I want to spin up all the disks where TV Shows are located when I want to watch a movie? Downloads will generally be on your cache drive, not the array.

Torrenting can do bad things to your router, depending on what you are running. It may be necessary to restrict the number of active torrents, connections, bandwidth, etc. OpenVPN consumes a decent amount of CPU on my older system - 40% at times.

Something like: https://www.newegg.com/Product/Product.aspx?Item=N82E16833156258 You have a wired Ethernet connection from your computer to this device, and then it connects via wireless into your home network. Since all unRAID sees is the connection out via the wired Ethernet connection, it's happy. Read all the bad reviews, I don't recommend this approach - but it exists.

Well you could go the gaming adapter route, but Wifi is spotty, inconsistent, subject to interference and obstruction, etc. - basically not suitable for attaching a server to a network. My recommendation is to move your server to a place where it can be hard wired. I'd go Ethernet over powerline or MoCA before attempting Wifi for a server. Actually I'd drill holes for Ethernet before any of those, but you get what I mean.

Not directly. You could potentially use a gaming type adaptor - Ethernet from your server to the wifi device. Why wouldn't you want your VMs to share the Ethernet connection, though?

Thanks, this is a great review and detailed set of mods! Aside from room for an mATX motherboard, is there anything else you preferred about the CS380 over the DS380? The drive cage mod to allow a fan to be mounted on the bottom seems annoying, but important.

I'm quite interested in your opinion of and mods on the CS380!

Haswell and newer Intel CPUs contain support for the AVX2 instruction set. The unRAID dual parity calculations leverage this for faster performance, but your 2010 i7 should be able to handle dual parity without issue. The AVX2 instruction set probably benefits low end processors the most since they have less raw horsepower to work with.

With a 28 drive array, I would guess that there is a high likelihood that you would wind up having multiple disks from the same manufacturer, of the same size, purchased around the same time, from the same manufacturing lots. It's undesirable but seems inevitable in an array that large - and the corresponding slightly higher risk of multiple simultaneous failure is all I'd need to rationalize dual parity. It's probably been mentioned but is worth repeating - neither parity nor dual parity is going to save your bacon when a drive fails. Parity (single or dual) plus the fact that the rest of your array is healthy and capable of contributing to a rebuild is what saves your bacon. Dual parity buys you a little extra safety buffer, but you still need to stay vigilant about drive health.

Do you have htop? You can sort it by CPU usage.

Anyone seeing issues with the latest pull? I updated from a package than included 2.0.0 to 2.0.1 and am getting: 06/02/2017 11:09 [02/Jun/2017:11:09:56] ENGINE Error in HTTPServer.tick Traceback (most recent call last): File "/opt/sabnzbd/cherrypy/wsgiserver/__init__.py", line 2024, in start self.tick() File "/opt/sabnzbd/cherrypy/wsgiserver/__init__.py", line 2091, in tick s, ssl_env = self.ssl_adapter.wrap(s) File "/opt/sabnzbd/cherrypy/wsgiserver/ssl_builtin.py", line 67, in wrap server_side=True) File "/usr/lib/python2.7/ssl.py", line 363, in wrap_socket _context=self) File "/usr/lib/python2.7/ssl.py", line 611, in __init__ self.do_handshake() File "/usr/lib/python2.7/ssl.py", line 840, in do_handshake self._sslobj.do_handshake() error: [Errno 0] Error

Ok, thanks. I'm a little less confused now ;).

Ok, thanks. Is there a solution for that, can you point me in the right direction?

Hi, I've got some really dumb basic questions. They may be more general in nature, but I'm not sure if they might be implementation specific to Linuxserver.io OpenVPN-AS so posting them here - but please tell me if I should ask elsewhere. FYI, I'm familiar with router and Windows VPN implementations but not OpenVPN as a Docker. I'm struggling a bit with what I can do with OpenVPN as a Docker, and whether I need other components. So, I'll go ahead and install the Docker. But, how do I "tell" other Dockers to use the VPN connection for outbound traffic? Do I also need a proxy? Or does this implementation "know" about other containers and allow me to configure which containers will use the VPN connection? Or does it simply co-opt the entire docker0 network interface and route all containers configured for bridge mode? I assume it doesn't co-opt the entire host network interface... Similarly, if I want to have other devices on my network use the VPN connection, do I need a proxy? Or does OpenVPN-AS expose an interface that allows me to "point" traffic to it? With the help, perhaps, of a VPN client on the device? Feel free to send me to an appropriate resource to read, I've been googling without much success. I'm obviously a bit confused, so thanks for any help!

Thanks, I know it's not an issue with the backup. I'll run the new perms and that should at least let me pull down the files on an ad-hoc basis. I'm sure the permissions will come back with the next backup, though. I'd like to fully automate pulling down the backed-up files to the windows box, but I'm not sure if there's a good approach given that CA Backup is doing what it's supposed to - faithfully backing up Crashplan's permissions along with the files.

Question for you. I use CA Backup to backup to a user share. I then need to be able to backup the user share to an external hard drive. This is probably more of a Crashplan issue, but when CA Backup copies the Crashplan files it picks up their permissions as well, listed below. These prevent me from pulling the files down to my windows box. Any ideas on how to approach this? Thanks. [code] drwx------ 1 root root 4096 Dec 21 18:39 adb/ -rw-r--r-- 1 nobody users 3365 Feb 7 2016 custom_sample.properties -rw-r--r-- 1 nobody users 1119 Feb 7 2016 default.service.xml -rw-rw-rw- 1 nobody users 24077 Jan 21 10:42 my.service.xml -rw-rw-rw- 1 root root 4826 Mar 25 2016 service.log.xml -rw-rw-rw- 1 root root 76 Feb 7 2016 service.login -rw------- 1 nobody users 9024 Jan 21 18:43 service.model -rw-r--r-- 1 nobody users 1384 Feb 7 2016 ui.log.xml -rw-r--r-- 1 nobody users 278 Feb 7 2016 ui.properties -rw-rw-rw- 1 nobody root 97 Dec 3 18:07 ui_nobody.properties -rw-rw-rw- 1 root root 50 Dec 21 18:39 ui_root.properties -rw-rw-rw- 1 root root 0 Feb 9 2016 upgradeui.log.properties -rw-r--r-- 1 nobody users 1335 Feb 7 2016 upgradeui.log.xml -rw-r--r-- 1 nobody users 44 Feb 7 2016 upgradeui.properties

Hmm, is Help on by default for a new install?

CA Auto Update didn't have an update available, but CA did. That removed updateApplications.sh from cron.daily. Thanks, Squid!

crontab -l # If you don't want the output of a cron job mailed to you, you have to direct # any output to /dev/null. We'll do this here since these jobs should run # properly on a newly installed system. If a script fails, run-parts will # mail a notice to root. # # Run the hourly, daily, weekly, and monthly cron jobs. # Jobs that need different timing may be entered into the crontab as before, # but most really don't need greater granularity than this. If the exact # times of the hourly, daily, weekly, and monthly cron jobs do not suit your # needs, feel free to adjust them. # # Run hourly cron jobs at 47 minutes after the hour: 47 * * * * /usr/bin/run-parts /etc/cron.hourly 1> /dev/null # # Run daily cron jobs at 4:40 every day: 40 4 * * * /usr/bin/run-parts /etc/cron.daily 1> /dev/null # # Run weekly cron jobs at 4:30 on the first day of the week: 30 4 * * 0 /usr/bin/run-parts /etc/cron.weekly 1> /dev/null # # Run monthly cron jobs at 4:20 on the first day of the month: 20 4 1 * * /usr/bin/run-parts /etc/cron.monthly 1> /dev/null ls /etc/cron.daily logrotate* updateApplications.sh*