itimpi

I am successfully using both the G2 and G3 models with Unraid. I believe that there is some question as to whether all G3 ones have unique GUIDs but hopefully you will find you are OK.

Your ‘system’ share is on disk1 so if you run any docker containers or VMs you will get the symptoms you describe. You really want this share to be only on the cache pool. You need the docker and VM services temporarily disabled to be able to move it as they keep files open in that share

It IS possible to use macvlan with the 6.12.4 release, but you have to make sure you have satisfied the other requirements mentioned in the release notes if you want to do so.

It might be worth seeing if the Tailscale plugin will work in your environment.

The logs in the diagnostics start over every time the system is booted. You would need to enable the syslog server to get a syslog that survives a reboot so we can see what lead up to the crash. The commonest cause of instability seems to be using macvlan with docker so it might be worth checking for that. The easiest solution is to switch to using ipvlan instead.

The key is valid for all versions of Unraid.

I think that this can happen if Linux has the information it needs cached in RAM so it does not need to access the physical drive.

Not sure why you think this. XFS is far more resilient to problems after crashes or dodgy hardware (particularly RAM) than BTRFS is and it tends to perform better. With XFS you can install the File Integrity plugin if you want checksums.

If you can boot with non-GUI mode then you can get the diagnostics via the command line. They will be put into the logs folder on the flash drive. Posting those might help with diagnosing your problem.

The only reason you normally get blacklisted is because the flash drive you are trying to use does not meet the requirement of having a unique GUID. The licence is tied to that GUID which is why it must be unique. If you contact support they can help get you sorted out.

Another point to note that if a file already exists on the array, then copying that file will always go the array (i.e. it overwrite) even though it may be the secondary storage, so make sure files do not already exist when doing your speed tests.

The 'Single' option you mention only applies to BTRFS pools as far as I know.

The command that was used moved the files to / which is the root of the file system and which is in RAM. That would fill up the RAM and eventually crash the server, and on reboot the files would be gone.

Yes

You should now run a correcting parity check to confirm that the parity really is valid, and if not update it to match the current drive set.

You need to contact support to get them to do this for you.

The syslog in the diagnostics restarts every boot so cannot show what lead up to the problem. If you want a syslog that can survive a reboot you should enable the syslog server. You should also look at this section of the online documentation that has information on troubleshooting unclean shutdowns.

That suggests that you have something generating spurious keyboard input.

No problem using the same Unraid Connect account - and if anything it is recommended so you have all your licences/backups in one place.

If you are writing to the Unraid parity protected array then this is the sort of speed you can expect as described here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI. In addition every forum page has a DOCS link at the top and a Documentation link at the bottom. You can get higher speeds if writing to a pool that is outside the parity protected array.

Yes.

it is perfectly normal to administer Unraid remotely across the network. In fact before Unraid v6 that was the only option. You would normally just load up a browser on the PC and point it to the network address of your server. This would be using a URL of the form http://servername where the default for servername is ‘tower’ if you did not specify something different when creating the flash drive. Alternatively you can use http://ip-address where you can get the ip-address from your router if you do not know it. The above assumes that Unraid booted correctly and initialised the network connection successfully. If that is not happening then you may temporarily need a keyboard+monitor attached to the server to help resolve why. Having said that if the server hardware supports IPMI which can simulate a locally attached keyboard+monitor then you may be able to do this remotely also - not sure if that applies in your case?

I am very confused why you think a plugin might be required? Unraid allows you to boot in GUI mode that allows you to access the Unraid web interface on a locally attached monitor. Alternatively you use a browser on another machine to access it across the network (which is the way all version before v6 worked).

You can do this via the appdata backup plugin.

This is incorrect. Unraid is quite happy with USB3 as long as the BIOS correctly handles it during the boot sequence. USB2 drives are simply recommended if possible as they have proved more reliable as they tend to run cooler which is better for long life and BIOS's tend to handle them more reliably when booting. If using a USB3 drive then if you can plugging it into a USB2 socket as they drive runs cooler when only run at USB2 speeds again it is more reliable.