itimpi

I would check that the date and time on the server is correct. Somehow it seems you managed to get some history entries written with an old date.

Parity drives have no data do are not mountable. After doing the xfs_repair look to see if there is a lost+found folder on the drive. That is where the repair process puts files/folders (with numeric names) for which it could not find the directory entry to give the correct name. Not having that folder is a good sign that the repair completed successfully without data loss.

That should work. With current releases of Unraid it is important that the capitalisation of the share .cfg files is identical to the actual folders on the drives.

Not seen that error before! You are likely to get more informed feedback if you attach your system's diagnostics zip file to your next post in this thread. It is always a good idea to do this to allow us to see the current state of your system and so we can see logs.

Mover will ignore shares that do not have secondary storage set. To get shares moved from cache to array you need Primary Storage=Cache, Secondary Storage=Array, Mover Direction Cache->array. If that doe not solve you problems then post your system's diagnostics zip file giving the names of some shares that you expect to be moved.

This is expected as described in the Caution section in the online documentation here if you use Move from Krusader. You would need to use a Copy/Delete strategy to avoid this. If you use the Dynamix Gile Manager built into Unraid 7 you would get the behaviour expected as it knows how to do this correctly in Unraid avoiding the issue.

You are likely to get better informed feedback if you attach your system’s diagnostics (with everything in the one zip file) to your next post in this thread so we can see what Unraid is seeing. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.

It will be something to do with the configuration of the docker container that is creating the files. You should ask in the support thread for that container how to get the permissions correct as it can vary for different containers but is typically something around setting UMASK.

You are likely to get better informed feedback if you attach your system’s diagnostics (with everything in the one zip file) to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.

I have never had to reinstall Windows for this reason as long as the credentials are correctly set in windows Credentials Manager.

How much RAM are you trying to give to the VM?

How are you creating the files on the Unraid server. You probably want to fix the permissions issue at that level when the file is first created rather than doing it afterwards.

Server rebooting unexpectedly is almost always hardware related. The syslog in the diagnostics is the RAM copy and only shows what happened since the reboot. It could be worth enabling the syslog server to get a log that survives a reboot so we can see what happened prior to the reboot. The mirror to flash option is the easiest to set up, but if you are worried about excessive wear on the flash drive you can put your server’s address into the Remote Server field.

It sounds as if you forgot to click the Apply button to actually do the New Config?

Yes - but every correction is included in the error count (which you may find confusing?). You need to later run another check that reports 0 errors if you want to confirm parity is valid.

I suspect that the work to support multiple arrays has proven to be more than was perhaps originally envisaged. There is also the fact that work around getting ZFS support more solid has been significant. Limetech still seem to be upbeat about multiple array support arriving so I think it is just a case of completing all the steps they have identified for getting there with (hopefully) avoiding a breaking change to existing functionality

the order of the drives will not matter if you only have parity1 as long as you did not restrict shares to particular drives under your share settings. If that is the case you can use Tools->New Config and select the option to keep current assignments and click Apply. On returning to the Main tab add the additional drives. Click the Parity is Valid checkbox (ignore the warning about parity being overwritten as it does not take into account the checkbox) and then start the array. You should find all drives mount fine with their data intact. If you have parity2 you should not click the checkbox as its calculation uses disk number as one of its parameters so you need to rebuild parity from scratch. I would recommend you now run a parity check to confirm parity really was valid.

I suspect the extensions apply to the date from when you originally started the trial and do not take into account the fact you were not using Unraid for a period. Regardless, you should contact support as registration issues need to be dealt with by them and not via the forum.

You are likely to get more informed feedback if you attach your system's diagnostics zip file to your next post in this thread. It is always a good idea to do this to allow us to see the current state of your system and so we can see logs.

You can check off the ones you want re-installed and then get all the selected ones done at the same time.

As long as you copied the container templates then containers can be reinstalled via Apps->Previous Apps

It could also be worth trying booting in Safe Mode to see if it is a plugin that is causing the problem as that mode disables loading plugins.

The syslog in the diagnostics is the RAM version that starts afresh every time the system is booted. You should enable the syslog server (probably with the option to Mirror to Flash set) to get a syslog that survives a reboot so we can see what leads up to the problem. The mirror to flash option is the easiest to set up (and if used the file is then automatically included in any diagnostics), but if you are worried about excessive wear on the flash drive you can put your server's address into the remote server field and log to a share instead.

Maybe you did not realise that the "Unlimited" referred to connected drives rather than drives in the main array? Having said that more than 28 drives in one array with only two parity drives seems to be getting a bit risk? Multiple Unraid arrays are still a road map item that Limetech have stated they are working towards for some time now . I expect they will be relabelled as 'pools' at that point as in many ways the Unraid type array will no longer be special as far as many capabilities are concerned. Note that you can already easily go way over the 30 drive limit if you are prepared to use Pools in either BTRFS or ZFS formats - I think the current limit that way is something like 60 pools of 30 drives although it is not something that I have really checked out as it is way beyond my needs.

The same way you must have enabled it as it is not enabled by default 😊. Under Settings->Scheduler.