itimpi

Yes. You only want the driver if you intend to use the GPU in docker containers. If passing it through to a VM you do not want the driver.

The templates that have the settings you use are stored on the flash drive and you can re-install docker binaries using previous settings via Apps->Previous Apps->Docker. You want to install the Appdata Backup plugin that can automate making a backup of the working set files for each container (normally held in the appdata share). That plugin can also make a backup of the flash drive if you want.

Just realised you have set docker to use a directory rather than an image file. I would suggest /mnt/user/system/docker. If you use a file instead then the default name of the file is docker.img. It is normally under the ‘system’ share - not sure why it is in the ‘domains’ share for you!

The value you have is default. I think that path gets created automatically when you first successfully start docker.

I would suggest leaving it at default then as it will make future support easier.

It has to be a filename. The normal default is /mnt/user/system/docket.img. Any reason for changing it?

Points I noted: you have not set the MinimumFree Space setting for the ‘cache’ pool. This means if it fills up you will start getting ‘out of space errors’. This should be set to something like twice the size of the largest file you expect to write. Not sure if you encountered this at any point. in a similar vein you should set the Minium Free Space setting for each User Share to set the condition for switching to another array drive. Probably not going to impact you until the drives start getting close to full. there were lots of panic’s in the syslog that appear to be samba related. No idea of the cause. you have quite a few .cfg files in the config/shares folder on the flash drive that relate to shares you no longer have. A good idea to remove superfluous ones to tidy up the diagnostics. None of these, however, seem to explain all your symptoms so not sure what to suggest.

Put the extra disk in a pool; Creat a Downloads share which has the pool set as primary storage and no secondary storage; Set the media share to have the pool as primary storage; the array as secondary storage and mover direction to be pool->array.

Don’t see how you can do that using Unraid standard facilities. Sounds as if you need to split out the downloads (although they could go to a pool rather than the Unassigned Device).

If you use the “Mirror to Flash” option then there is no direct dependency on the network working so more chance of catching something.

Yes (as this count never resets).

You should post your system's diagnostics zip file in your next post in this thread to get more informed feedback. It is always a good idea to post this if your question might involve us seeing how you have things set up or to look at recent logs.

You seem to be getting continual resets on disk3 which probably explains the slow speed. You might want to check the power and/or sata cabling to the drive is well seated. I assume the PSU is up to handling the extra drive? BTW: You probably need to disable spindown to get the Extended SMART test to complete. If the drive cannot pass that it will need replacing.

No - the options just need to be space separated.

Have you tried using just http:// instead of https:// ?

So we are told. Not sure what the ETA is going to be.

Yes, unfortunately as Unraid does not realise you are doing this to get around the current requirement to have at least 1 drive in the Unraid type array.

You seem to have a network problem limiting your speeds. It is as if you are only connecting at about 100 Mbps. Have you tried alternative LAN cables and/or ports on the router? If not all ports on a LAN connection are connecting the speed will silently degrade to 100Mbps as that connection needs less active connections in the cable than is required for 1000 Mbps.

Did you get the Unraid boot menu which gives you several boot options? The default is to boot to console mode which your screen shot shows seems to show has happened, but if you got the boot menu you can instead select to boot to GUI mode. Regardless have you tried connecting to the Unraid server from another machine with a web browser (on the displayed address which seems to be 192.168.0.105 at this point). This should bring up the web GUI. It is the traditional way that Unraid has been administered from before the days that there was even a GUI boot mode. If for any reason that does not work then you can type the word 'diagnostics' on the console shown in your screen shot and that will create a file in the 'logs' folder on the flash drive that you can post here (in your next post) so we can see what might be going wrong.

As mentioned in the Release Notes if you want to continue using macvlan you need to disable bridging on eth0.

I would suggest getting the version from memtest86.com which supports UEFI booting as well as generally being more up-to-date.

The disk assignments have always been held in the super.dat file in the backup. This is a binary file and thus not human readable. Not sure when/how the disk_assignments .txt file gets created.

This is probably excessive. More frequent is running them monthly, or even quarterly.

Nearly right - you need to omit the commas as the options are space separated. Normally easiest to do it via Main->Boot Device->Syslinux Configuration

They are already being stored on the flash drive.