itimpi

In theory reallocated sectors are not a problem as long as the number remains stable, but they are never a good sign, and if they continue to increase the drive will need replacing. Definitely want to keep an eye on it. Might want to consider running the extended SMART test on the drive as that is a good way to test it’s health. if you click on the orange icon for the drive on the Dashboard and select the Acknowledge option Unraid will only notify you again if it increases.

I notice that there to be I/O errors on disk5 do you might need to check the SATA and power cabling to that drive. The diagnostics do not show any attempt to format the drives so it might be a good idea to try again and post new diagnostics so we can see what happens when you try.

It is on the flash drive as '/config/network.cfg' so you can plug the flash drive into another machine and delete it from there.

The diagnostics show that there is definitely something wrong with the flash drive and it is being forced to be read-only. You should try plugging it into a PC/Mac to check that it can be read (and written) correctly.

Where have you configured your VM's vdisks to be located? If you have explicitly said on the cache drive this would explain your VMs not starting (at least until you put the files back there). it might be worth posting your system's diagnostics zip file in your next post in this thread to see if they allow us to give more informed feedback.

The forum can only help with technical issues - not with key/licence ones. When you attempted to contact support did you get an automated acknowledgement? If not then the request may not have got through and you should try again via the contact support form.

It is definitely possible to move the data. However are you sure the drive has failed? More often then not a drive is disabled (because a write failed) due to an external factor such as cabling or power. You should post your system's diagnostics zip file in your next post in this thread to get more informed feedback. You can also try running an extended SMART test on the drive as if it passes that the drive is probably OK.

Looking through the diagnostics it seems the parity1 drive has gone offline and as a result there is no SMART information for it. You might want to check the power/cabling to the drive.

If the drive was previously showing as mountable then have you followed the procedure documented here for handling unmountable disks 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 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.

Looks like most of your shares have the share security set as “public” which means anyone can access them. If you do not want this you need to set them to one of the more secure modes - whichever is appropriate for your use.

If you are having problems doing it on the server you can always instead plug the flash drive into a PC/Mac to make a backup as it is in standard FAT32 format. All you need is the contents of the ‘config’ folder as that contains all your settings and the licence key.

You should post the settings for a share exhibiting this behaviour so we can see how you have its security set up. Alternatively you are likely to get better informed feedback if you attach your system’s diagnostics 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,

According to your diagnostics disk3 (where the domains share) is spitting out read errors.

from an earlier request I have been working on an option to pause (rather than stop) user specified docker containers during parity operations and resume them when an increment ends. Sounds like that might satisfy this need without the need for a script?

It is not clear to me why you think there would be any files on a drive you have just added? Have I missed something? Normally when you add a new drive to the array Unraid Clears it (I.e. sets it to be all zeroes) to avoid invalidating parity. When that completes you then format the drive to create an empty file system and make it ready for use. This is the process documented here for adding drives in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page.

You are likely to get better informed feedback if you attach your system’s diagnostics 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.

Looking at you diagnostics you may have managed to get 2 shares which differ in capitalisation (not certain because of anonymization) appdata shareUseCache="prefer" # Share exists on cache domains shareUseCache="prefer" # Share exists on cache E-------------------) shareUseCache="yes" # Share exists on disk1, disk2 isos shareUseCache="yes" # Share exists on disk1, disk2, disk4 j------------------s shareUseCache="yes" # Share does not exist N-----------p shareUseCache="yes" # Share exists on disk2 O----------e shareUseCache="yes" # Share exists on disk1, disk2 P-------------s shareUseCache="yes" # Share exists on disk1, disk2 P--X shareUseCache="yes" # Share exists on disk1, disk2, disk4 S--------m shareUseCache="no" # Share exists on disk2, disk3 system shareUseCache="yes" # Share exists on disk1 J------------------s shareUseCache="no" # Share exists on cache, disk1, disk2, disk4 as you can see the one that has files on the cache starts with a capital J and is set to “no” for using cache so gets ignored by mover.

If by any chance you have a LAN cable where not all 4 twisted pairs are connecting end-to-end then a 1000Mbps LAN typically silently degrades to 100Mbps. This can be confusing as no error is indicated and the LAN is operational - just not at the expected speed. It may be just that the original cable was defective in this way?

The easiest thing would be to download the current 6.12.10 zip file and then copy over all the bz* type files from the zip. As a side-benefit you will be upgraded to the latest release. At the moment this seems the most stable release.

You are likely to get better informed feedback if you attach your system’s diagnostics 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.

No. if you want just the drive assignments it is the super.dat file. Having said that why not copy everything over? Avoids you setting everything up from scratch (unless of course you explicitly want to do so).

What is it you actually want to do if the check is paused? There may be a better way to achieve this.? Also what is the Use Case you have for even running a script at start/end? Just asking as if it is a good one I could consider adding support for this as a standard feature in the Parity Check Tuning plugin.

Fair enough - but you did not say what you had tried. The procedure I pointed you to worked for me, so not sure why it is not working for you.

If you are passing through hardware to a VM then any drivers needed are loaded into the VM - not into Unraid. You need to remove any driver you tried to install at the Unraid level and then reboot the system.

You are likely to get better informed feedback if you attach your system’s diagnostics 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. your description makes it sound like you may only be getting a 100Mbps connection to your Unraid server despite you thinking it should be 1000Mbps.