itimpi

The GUID that is being referred to is that of the current USB you are using. I suspect your problem is the second point listed. What brand/model of USB drive are you using? It may be one where the manufacturer is not giving each drive they make a unique GUID. if you think it is something else then you may need to contact LimeTech support to get it resolved.

I use the Openvpn-as server as a docker container (rather than the openvpn plugin) and have not had any problem with my configuration surviving updates.

I think in this case you ARE seeing live values. If you take that action it is probably assumed that you are happy to take any performance hit the action might cause.

It sounds as if the unraid USB stick has not been passed through correctly to the VM! If it is then you will see the contents listed under /boot. If it is not being passed through and recognised by unRAID then that would explain your symptoms as the USB stick is required to correctly complete the later stages of the boot process and this would include launching the web GUI.

Difficult to say! Most likely cause is a misconfigured docker that is writing files to RAM. The thing to remember is that all files that are not under /mnt or /boot are in RAM.

How many drives do you have assigned to the cache? If it is more than 1 then the only option will be BTRFS as XFS Is only an option if the cache is limited to 1 drive.

You did not mention that before removing any disks you first need to copy any data you want to keep to another location as removing a disk from the array also removes any content it might have. Once you have done that you can remove as many disks as you like in one operation as removing any disk invalidates parity so it will need rebuilding anyway whether you remove one disk or several disks at the same time. After doing the New Config you are free to change what slots disks are assigned to, and to remove drives you no longer want in the array When you start the array unRAID will recognise disks previously used by unRAID and their data will be left intact.

To reformat a drive you need to stop the array: click on the disk to be formatted and change the format to the one you want; restart the array and the disk will now show as unmountable. You can now use the option to format unmountable disks. NOTE: this will erase any existing data on the drive so make sure you first copy anything you want to keep to another location.

There can be a delay before the GUI is updated. What do you have under Settings->Disk Settings->Tunable (poll_attributes) ? The default value of 1800 means that the disks are only polled every 30 minutes. You may want a much smaller value - something like 300 (5 minutes) is what I use.

Upgrade from rc1 appears to have gone through without issue. Well timed as I was just about to report the issue with dockers not updating!

Just a check - the number of attached devices limits for the Basic/Plus licenses includes all devices - not just those allocated to unRAID. Probably not an issue for you, but some people think having other devices plugged in that are not assigned for use with unRAID do not count.

Install the CA Backup Plugin. It backs up all such information.

Just thought it was worth mentioning that a similar issue (and I assume a similar solution) exists fro Dev Pack.

I would have thought you should be able to set these scripts up under the User Scripts plugin? Then you can run it from the unRAID GUI without the need for ssh.

Also empty on my system! Plugin probably needs an upgrade to be compatible with 6.6.0-rc1.

No. You can add a script to do this at regular intervals via User Scripts.

Mover can move files in either direction! What you see is expected behaviour if you have set a user share to Use Cache=Prefer. You want Use Cache=Yes for mover to move files from cache to array. Turn on the Help in the GUI to get more details on how the setting affects mover.

Have you raised a formal request to get the groups file included in the Config folder on the flash drive? If there are no other ramifications I expect LimeTech would implement this as being a trivial change. This is obviously a much smaller change than getting full baked-in support for groups but still worth asking for as a small step on the way.

I thought you might have simply gotten away with copying the /etc/group file onto the flash drive and back into position rather than recreating the users? This would be simpler than recreating the groups on each boot. However it may well be more complicated than that and recreating the users each time may be easier to maintain?

Good to hear! Have you copied the files that get altered (e.g /etc/groups) to the flash drive, and then added entries into the ‘go’ file to copy them back into position during the boot process? This is needed as unRAID is running from RAM so you need to take positive action to make such changes survive a reboot. Perhaps at the end you could create a brief ‘How To’ post in case anyone else has similar needs in the future?

I find the VNC connections are rock-solid so this is definitely unusual behaviour. It suggests there is some sort of problem at the networking level. I would suggest that you post the diagnostics zip file (obtained via Tools->Diagnostics) after the problem has occurred to see if anyone can see any information there that might suggest the cause.

Thanks for the feedback. I may decide to mention it anyway next time I have a reason to drop an email to them. i see they have now updated the Change Log on their web site(I complained that they had not been doing so) so as long as they continue to do this it will be easy to see when/if this gets implemented.

Have you raised this with MyMediaForAlexa support? If not mention that here and I will do so to get a definitive answer. Since any transcoding happens locally it feels more like a bug than an intentional limitation and I certainly could not find any mention of such a limitation on their web site.

Well that proves there is a working connection at the network level and the router is working fine, so there must be something blocking things at the software level. Since it is only this PC exhibiting problems it has to be something on the PC rather than at the unRAID end. No idea what it could be though?