itimpi

Have you tried deleting (or renaming) the config/network.ctg file on the flash drive and rebooting to get a new one generated with default settings? If you want more informed feedback you should post your system’s diagnostics zip file (obtained via Tools -> Diagnostics) attached to your next post in this thread.

If you post your system’s diagnostics zip file attached to your next post in this thread (so we can see what is going on) we might be able to give some informed feedback. You can penetrate this zip file either via Tools->Diagnostics in the GUI or via the ‘diagnostics’ command at the CLI. If using the CLI it is written to the ‘logs’ folder on the flash.

Prior to 6.9 you could only have one pool and it was always called ‘Cache’. Starting with 6.9.0 you can have multiple pools and call them what ever you like. You can now configure at the individual share which pool (if any) it should be associated with.

No data drive can be larger than the smallest parity drive You can, however, achieve what you want using the Parity Swap procedure that is documented in the online documentation that can be accessed using the 'Manual' link at the bottom of the Unraid GUI.

FYI: This is covered here in the online documentation that can be accessed via the ‘Manual’ link at the bottom of the Unraid GUI.

It could be worth running the appropriate make_bootable command for your OS from the USB stick (running as administrator) . I have see cases where the USB Creator tool seems to fail writing to the boot sector to make the flash drive bootable for some reason.

Where does the CLI get involved? The backup option gives you a ZIP file containing the contents of the flash drive and gives you a browser ‘save as’ dialog so you can put it where you want.

This information is in the zip file produced by the backup option offered after you click on the Boot Device on the Main tab. You also have a lot of the needed information if you use the Tools -> Diagnostics option although that does not include everything on the flash drive.

You can achieve this using rsync to do the copy with the --sparse parameter. I think the cp command has an equivalent option.

You currently have disk1 excluded under Settings -> Global Share Settings

If that is what is being reported in the log, then yes you do need to convert them to 512 byte sectors before Unraid can use them.

Once a card is bound to VFIO it is not available to be used either by Unraid or by any Docker container.

You can do this by specifying the IP range allowed when defining a tunnel at the Unraid end. a point to note is that if you want to access the IPs on your local LAN form a remote point across a WireGuard link then the client must be on a different subnet to that used on your home LAN. This may well mean that you want to avoid using commonly used subsets like 192.168.0.x and 192.168.1.x on your home LAN as you will find there is a high chance of the client being on one of these subnets.

I believe tHe frequency is determined by Settings -> Disk settings -> Tunable (poll_attributes): which has a default of 1800 seconds (30 minutes). I normally change it something shorter like 300 seconds.

It is a requirement of Unraid that each disk is passed through with a unique serial number - is this the case with your hardware? If you posted your system’s diagnostics zip file(obtained via Tools -> Diagnostics) it would give us enough to determine if this is your problem or whether something else is going on.