Leaderboard

Prior behavior on the Update Assistant was that it checked for a version of dynamix.plg with a file time before Jan 1, 2016 and told you to delete them (since latter versions checked on the OS version prior to installing). Since there's some bug or something in the version check on some of dynamix.plg, Update Assistant now will always tell you to delete dynamix.plg no matter the time stamp.

And by the looks of that screenshot looks like you're either using a port multiplier or have SATA ports in IDE mode, neither is good but the latter is easy to fix.

The disk controller has lost communication with the disk. Diagnostics will reveal more.

If you have an adblocker running, whitelist the GUI. If you have antivirus running, exclude the GUI.

Tools - Diagnostics, post complete zip

Yes, replacing the bz* files still works. It is possible a new release might have additional bz* type files but if so make sure that you copy all of them over. It is always recommended you make a backup of the existing contents before doing so to give you the (hopefully not needed) ability to revert to the previous release. No idea about the proxy - that is not something I personally have any experience of. Hopefully one of the networking experts will chime in on that.

Good to hear, you got it working. These Asus cards work well and I reach near 10Gbps speeds between my two servers.

Yes! Reached out to tech support, they stated to download the latest release, it will have the drivers. Updated now all is working! Love 10GbE! Hitting 300-900MB transfer rates on all workstations on network is scary. Thanks all!

If you're running a non-correcting monthly parity check (as you really ought to be doing) then after finding an error you need to investigate and then run a second, correcting check because parity with errors is not much use. If you happen to be running correcting monthly parity checks then the correction will already have been made. The reason why I say that you ought to schedule your monthly check to be non-correcting is because a hardware fault could overwrite good parity with bad.

If you have a docker of your own on dockerhub, then just use the Add Container page in unRAID to specify all the docker run parameters such as volume mappings, etc. Then when you have the Add Container page filled out just like you want it add the container, it will create the XML file you are talking about and store it in the location I mentioned before: You can use that XML as a starting point to develop the template for your docker that others can use. Not sure what is involved in actually getting your app added to Community Applications, Squid is in charge of that.

You can always do a manual upgrade by downloading the zip file of the release and then copy all the bz* files from the zip to the root of the USB stick.

Hear, hear... I like the new look. Please keep the bottom part of the GUI white. Also make forum match, black header, white body. ok, I confess, my old eyes don’t like reading white text on black background. I’m sure I’ll get used to it.

This not a dating website

You can set a password to access the UI: https://github.com/jlesage/docker-handbrake/#vnc-password