BRiT

No easy way to get audio working on unRaid Host as audio support in Linux is a cluster and requires entirely too much space in the bz* files to be worth it.

This isn't entirely what you're looking for but here's tidbits that I'm just throwing stuff out there... If you can't work out the ping and network connectivity testing you could schedule a script to start docker 10 minutes after bootup. echo /etc/rc.d/rc.docker start | at now + 10 min To control docker from a whole you can use /etc/rc.d/rc.docker. That script has the following parameters: start stop restart status

I would switch over to the dynamix cache dirs. plugin and remove the line from your go file.

From the Docker FAQ

My Parity checks with 6 4TB HGST drives was easily under 9 hours. Hell, even my mixed 6*4TB+3*8TB Parity Check is half your parity check time. 2017-04-01, 11:43:17 -- 8 hr, 43 min, 16 sec -- 127.4 MB/s = 6 * 4TB HGST 2017-07-01, 21:17:13 -- 18 hr, 17 min, 12 sec -- 121.5 MB/s = 6 * 4TB HGST + 3 * 8TB Seagate Archival 2017-10-24, 10:47:46 -- 15 hr, 37 min, 32 sec -- 142.2 MB/s = 4 * 8TB Seagate Archival

Close your old browser windows. There is a FAQ for wrong csrf_tokens.

I do parity checks on the following schedule: 1. Before Hardware Upgrades 2. After Hardware Upgrades 3. Before Moving the Server Equipment 4. After Moving the Server Equipment 5. After Graceful powerdowns due to Power Outages 6. Monthly

On Thursday I picked up another 8TB External Seagate Drive, this time from Newegg. The model found inside is ST8000DM004-2CX188. It seems like they definitely switched over to this model. I'm not sure if they're using the Shingled Archive drives in externals anymore. For the parity drive, I'll have to run a few drive speed tests to determine which model would be better. I'm thinking the DM004 would be slightly better than the AS0002.

Yes it is possible. You'd have to look at the params of the script to find out. Although with dynamix plugin there might also be a /etc/rc.d script for it as well. Thatwill allow you to stop it easily too. I'm away from the system right now so I cant look.

@Pauven I hope is going well with you. Any thoughts on releasing the last version you had under private release to the public so the rest of us can benefit from it?

Maybe the file was still locked by the applications for a bit of time after the close_rewrite event and thus was unable to be check-summed? Sounds like a timing issue of playing roulette, making it very hard to reproduce reliably.

You do NOT need the container_id at all. you can use the Container Name.

Multiple unRAID pools will require substantial rework of the unRAID MD Driver and the emHttpd management control. It's not a simple change.

Which version of unRaid? Is it the 6.3.x stable or the 6.4 beta series?

Dont reformat anything, yet. What device did you run xfs repair on, was it on /dev/sdk2 ?

LT is inlining UD on future releases.

Didn't they [Linux Kernel Developers] officially kill off AUFS entirely in the kernel? I know one of the systems was totally gutted from being overly complex and causing too many issues in the kernel.

There is never a need to involve logic when assigning blame.

I'd tell them the exact same thing everyone here would tell them, Restore from backups.

Install and use CA (Community Applications) then use advanced mode.

Or everyone is already hacked...

That's because there is no difference between Core and HyperThread. Core and Hyperthread is 2 sides to the same coin. It depends which side is face up. Both 0 and 12 are part of the same CORE and the HT. Which one is operating at the time determines which one is considered the "core" and the one not currently operating can be considered the "hyperthread".

@squid I'm sure you're already working on adding checks for the following already, missing the new bz images on the /boot/ device for 6.4+ ....

@Squid any thoughts on allowing for plugable extension scripts to CA Fix Common Problems that can be installed from other Plugins or even Dockers? That way you dont need to maintain them but it could provide another layer of sanity checks for the other devs if their items are FCP aware. Yeah, still a possible can of worms but it wouldnt be your can.