itimpi

Just google for it. OpenVPN is used on millions of systems so there should be plenty of information available.

You are going to need to provide the diagnostics zip file (obtained via Tools->Diagnostics) while the problem is occurring to get any feedback other than wild guesses.

If you delete the image and then restart docker it will create a new empty image. You can then go into the Previous Applications section of Community Applications and from there templates that Community Applications will have earlier saved on the USB drive to reinstall the containers with the previous settings. As long as the containers were properly configured to have their configuration information installed externally to the container you are back up and running exactly as you were before.

Yes, you can do this but during the install you need to give at least one it a new name (as well as different config options). I do it with two MyMediaForAlexa containers because I want one to handle Music and the other AudioBooks.

What version of UnRAID are you running? There was a cron related problem with some of the 6.6.x releases that is now corrected in the 6.6.5 release.

When building parity Unraid makes no assumption about the existing contents of the parity and simply overwrites it without looking at the sector contents. Since parity has no concept of file systems it cannot make assumptions about the meaning of any sectors contents. Unless your drives had just been pre-cleared then UnRAID would not have been copying empty sectors. A formatted drive has the file system control information written to the relevant sectors. That is actually a non-trivial amount of information as it can run around 1GB per TB of useable space.

Actually 6.6.3 is the latest.

UnRAID never moves files between array disks automatically, this always has to be done manually if you want it to happen.

That sounds like a reasonable approach. At least that way the users will know what the problem is rather than continually getting this raised as a support question.

I see that is the version that it currently has available. However if you raise a request in the NerdPack plugin thread it is likely it will be updated. are you actually intending to make use of features that require 3.6.6?

Python is not included as standard on UnRAID, but It can be installed via the NerdPack plugin.

Why do you not have the Minimum Free Space setting for the Cache drive set to a suitable value so that if space gets low new files start by-passing the cache and going directly to the array? This means that at least things keep working all the time. Writes that by-pass the cache will tend to be slower, but is your work pattern one where this will get noticed in practice? If you are regularly filling up your cache then maybe you should be investing in larger cache?

Not necessarily. It is not that a new Unraid release can break Nerdpack, but the opposite where Nerdpack breaks UnRAID. The point is that Nerdpack can install many packages and it is possible that some of these can cause problems with core Unraid capability if they are incompatible versions and overwrite the versions supplied with core UnRAID. As such incompatibilities (if any) are found then Nerdpack tends to get upgraded to use compatible versions. Therefore whether Nerdpack will cause problems if you upgrade depends if one of the packages you want fall into this category of needing a different version when used with the current UnRAID release. This has been a much bigger issue when using DevPack as that has tended to install far more wide-ranging array of components.

If the app is crashing and you cannot identify the cause then you need to contact MyMediaForAlexa support for help as they are the authors of the software and producers of the container. They are closed source binaries so it is unlikely anyone else can help unless the problem is obvious. The app will be writing log file(s) to it’s appdata Folder (by default this at /mnt/user/appdata/MyMediaForAlexa) so you might want to look at a log file there after a crash to see if anything stands out. You can also download the latest logs via the Admin option. If nothing stands out you could try attaching them here to see if anyone can spot anything. The only time I have seen crashes is when there was problems with specific albums in my library (I assume they were corrupt). This became obvious as the crash would always happen at the same point during the scanning process. By perusing the log file I was able to identify the problem albums and correct the issues. Since then the container has been completely stable. If you cannot see any cause then raise a support request on the MyMediaForAlexa web site attaching the log files. Let us know when/if the issue is resolved

You do not need to get NordVPN involved at all if your requirement is to securely connect to your home server from a client that is external to your home network. I do this quite happily by having the openvpn-as server docker on UnRAID and then running an OpenVPN client on the remote client. This allows me to act as if the client machine is plugged into my home LAN even though I am physically remorse. The time you want NordVPN (or an equivalent) involved is when you want to make an outbound connection (possibly from your home LAN) from the client machine and hide your IP address (or perhaps make it appear you are located in another country to run an application that does geo-location checking). I use NordVPN client on my iOS and Windows machines for exactly these capabilities. In this case the outbound connection is going via the NordVPN servers and being routed on from there.

IF you install the docket using the Community Applications plugin then you are presented with a template where the only entry you need to alter is the one pointing to the location of your medis

The checksum does not provide any capability to correct errors. The idea is that it identifies files that appear to be corrupt so that they can be restored from backups.

There is no automatic transfer without a rebuild. since you mention a rebuild then I assume you have (valid) parity? I assume the parity is at least 6TB since you want to use a 6TB data drive. In which case the procedure is: - stop the array - Unassigned the drive and start the array without the drive assigned. This is to simulate the drive failing. - stop the array and assign the new drive - start the array to initiate a rebuild onto the new drive. When the rebuild completes the data will be on the drive.

No hard drives can reach even SATA2 speeds so the limiting factor is what speed the drives themselves can do. The copy speed will be determined by which is the slower of the source and destination drives.

That was exactly the reason I wrote it in the first place as I ended up in the same situation

If it is on;y 1GB then you definitely cannot update via the GUI! In such a case you can only update via the manual method of downloading the ZIP file of the release and copying all the bz* type files to the root of the USB drive overwriting any existing files of that type. it is a shame that the upgrade process does not check the RAM before attempting to upgrade and issue a warning in such a case.

How much RAM do you have? If it is only 2GB then I do not think that upgrading via the GUI works as the new release is downloaded and unpacked to RAM before updating the USB stick. Another possibility is that the USB stick is going read-only for some reason. Posting the system diagnostics ZIP file (obtained via Tools->Diagnostics) would allow for more informed feedback.

The storage location value is wrong. It needs to include the name of the actual file, not just the folder that contains it.

Your USB key has been set to read-only. This could be because there is file system corruption or because the USB stick is starting to fail. The USB stick can be checked by plugging it into a Windows PC and then letting Windows scan it and repair any errors. if you decide it is failing and want to purchase a replacement USB stick then it is recommended that you get a USB2 version as they tend to me more reliable than USB3 and since Unraid runs from RAM after initial boot there is no measurable performance hit.

That suggests you have not got the appropriate network drivers installed in the VM.