itimpi

You are likely to get better informed feedback if you post your system’s diagnostics zip file.

I would expect any 6.11 release to have significant new functionality. If it was only a kernel upgrade I would expect it to be a point release within the 6.10 series.

You left out the key step - Apply. The Done button is equivalent to a Cancel.

This is built into modern disk drives at the sector level and in the case of a mismatch a read error is returned. Note at this point there is no correcting of the error - just detection so that you can then take appropriate recovery action.

Unfortunately not (at least as far as I know).

Sounds like you have are encountering the issues described in the 6.10.2 release notes which can result in the NIC being (temporarily) blacklisted due to potential data corruption issue. If you need VMs and your system is not one that is affected by the data corruption issue you can take the steps laid out there to enable virtualisation support.

No - I would expect times to be unchanged. Unraid does not exploit techniques such as ‘striping’ on the main array to improve performance. Instead each drive in the main array is a self-contained file system that can (if necessary) be read when removed from the array. Using a cache drive speeds up the ‘perceived’ speeds for the file as cache pools do not have the same type of real time parity protection as the main array, The ‘slow’ write to the main array is displaced to the ‘mover’ job that typically runs overnight to transfer files from a cache pool to the main array when the user is not using the system.

The boot dtive does not count towards the licence limit. However any other drive (e.g. a removable one you use for backups) that is plugged into the server at the point the array is started DOES count even if it is not being used by Unraid.

You probably got confused by a statement that if you have a parity2 drive you cannot move drives between the slots on the GUI Main tab without invalidating parity since the slot number is part of the calculation of parity2 contents. Those slots are independent of the physical connection because as was stated Unraid identifies drives for a slot by the serial rather than where they are connected.

one begins to see a pattern after a while to certain types of error If no hardware is being passed through then there is no reason not to start the VM.

That is not a ‘parity’ process. It is a process (probably ‘mover’) that moves files from your cache (that I assume is not redundant so files on it are not protected) to the main array that is parity protected. Since all writes to the Main array always use real-time parity that would be the point at which those files become protected by the array parity.. if any files are written during the day to a share that is configured to write directly to the array then they are immediately protected by parity because Unraid parity on the main array is realtime.

I think I understand what you mean, but I would argue that what you said is not technically correct and could be misunderstood as there is no concept of an overnight parity calculation. Instead there is real-time parity calculation the moment a file is written to the main parity protected array. What I think you are referring to is the ‘mover’ job that is typically run overnight to transfer files that are written to a cache outside the array during the day for performance reasons onto the main array for their long term storage.

Have you got any unusual characters in any of the folder/file names? In my experience using characters like colon, asterisk and question mark for instance can cause problems as they are reserved characters at the SMB level.

OK, You CAN set the port explicitly if you edit in XML mode, but the problem with that is that if you switch back to form mode for any reason the setting gets lost and reset to default of ‘next port available’.

You cannot restart a check manually except from the start. What SHOULD work is that in the plugin's settings you set the option to automatically restart a parity check the next time the array starts. The plugin will then detect a parity check was in progress during the array shutdown process and save the information needed for restarting the parity check. As long as on restart the plugin thinks it was not an untidy shutdown the plugin will automatically resume the parity check from the point it had reached when the shutdown was initiated. If you cannot get that working then please turn on the Testing mode logging in the plugin's settings with the option to send the logging information to the flash drive set. You might also want to have the syslog server set up so that you have full syslog information covering the shutdown/reboot sequence. Then let me have that log file and I should be able to work out why it is not working for you on your system. Whether you have the "Scheduled parity check:" option set should be irrelevant as the plugin can resume both scheduled and manually initiated checks.

I have not looked at the diagnostics, but your symptoms suggest you are doing a hardware pass-through to the VM and the device now being selected is the disk controller. If you have recently upgraded Unraid you need to be aware that hardware ID’s can change after the upgrade and need to be checked before starting any VM using hardware pass-through.

At one level that is correct, but if you have backups it would normally be MUCH quicker to simply restore the files identified by the scrub as being corrupt.

Those are effectively the same location. Should be looking for a mapping that is either one of those that should have at least one more folder level. For instance a docker container that has a config folder directly mapped to /mnt/user instead of /mnt/user/appdata/appname which would be the normal location for such a folder.

That is definitely not enough to be able to upgrade vis the GUI. You can follow the procedure here to do the upgrade manually.

How much RAM do you have?

Don’t see how a snapshot would have helped. if you take a backup of the flash drive before updating it would only take about a minute to roll back by copying files from the backup back to the flash drive and then rebooting the server.

I agree - noMachine gives far better performance (and more capabilities) than using VNC. I only use the initial VNC support to allow me to install noMachine server within the VM (works for both Linux and Windows VMs).

Your syslog shows continual resets on the 8TB drives - in particular disk6 and disk7. You should carefully check SATA and Power cabling to those drives. Since you have just added some extra drives are you sure the power supply can handle them?

Maybe this section of the online documentations accessible via the ‘Manual’ link at the bottom of the GUI will answer your question?

As far as I know the #noParity option is a special feature of the User Scripts plugin.