itimpi

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.

The ‘config’ folder on the flash drive contains all your settings (including your licence). If you copy across the contents of the config folder (except for the licence file) to the flash drive to be used for the new server then all settings are transferred. To give you a chance to check thing out I would recommend, however, that you disable the Docker and VM services on the current server before copying the config folder so that they are not auto started on the new server. You may also want to disable array autostart. Note that Unraid will never automatically format any drive. This always requires manual action from the user.

Thanks for that feedback. Given that extra information I was able to recreate the issue and will put a fix into the next release of the plugin. I need to initialise a variable that the CustomMerge script expects to already have been loaded before it is called. The error will occur anytime you make a change under Settings->Disk Settings away from the defaults.

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.

The New Config tool is covered here in the 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.

It depends on whether you are prepared to take any risks with the current data. The simplest and probably quickest way would be to use the New Config tool and via that assign the disks that you want to finish up with removing the surplus drives; start the array; format the new disks; and then build parity based on those. You could then mount each of the drives removed in turn via Unassigned Devices and copy their data back to the array. This has the risk, though, of one of the removed drives failing before you can copy their data back to the array (thus losing the contents). Any other approach is going to be more laborious but it should be possible to keep parity protection in place so you are protected against a single drive failure, but it will take longer and put more overall stress on the drives.

If you did not get an automated acknowledgement then my guess is it did not get through. I would suggest trying again via the contact support form.

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 a crash. 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.

You can install the plugin with the check already running. Not much point in stopping the current check as you would just need to start again from the beginning. The plugin is not responsible for initiating the operation (which is Unraid’s responsibility), it just adds better management of what happens after it is started. Yes, but it will run much slower than when the check is not running (and also slow down the Check while they are both running) due to contention on the drives. You should therefore avoid doing large amounts of writes to the data drives while a check/sync is running as doing them separately would end up being faster, but small amounts would be fine. When you add a drive, parity is not regenerated. Instead the drive is Cleared (if not pre-cleared) to avoid it affecting parity. You can find a discussion of Clear v Preclear here 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.

Have you read this section of 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 that covers using WireGuard? The Unraid OS->Manual section in particular covers most features of the current Unraid 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. 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. Do you by any chance have the S3Sleep plugin installed? That has been known to spuriously shutdown servers.

If you read that link carefully you will see that despite its name it is NOT for replacing an existing parity drive with a larger one. For that you simply follow the procedure for Upgrading parity disks.

Parity sync time is not determined by how much data you think is there but by the size of the parity drive as it works at the raw sector level and works through every sector on the parity drive. My experience I’d something like 1-2 hours per TB of the largest parity drive size s not atypical. You might want to read this section of 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 to get a better idea of how parity works. The Unraid OS->Manual section in particular covers most features of the current Unraid release. While a parity sync/check is active performance of the array is significantly reduced and since parity checks/syncs take so long with large modern drives you might want to consider using the Parity Check Tuning plugin to offload the check to running in increments outside prime time.

You could use the User Scripts plugin to periodically set the permissions to Unraid default. Under the covers the New Permissions tool invokes the ‘newperms’ binary that can be used in a script.

Then you would need to get the author of the container to provide a way to set permissions correctly. Typically this is done by exposing the unmask setting in the container

Under the Peer Allowed IPs field you need to put entries for each subnet you want to be able to access via WireGuard.

It is not clear if you intend to have a pool called Main or not or if you intend these files to be on the Unraid array? You should start by setting up User Shares for “Data”, “Download” and “Data”, specify where you want them stored as the Primary Storage setting, and then make sure that for these shares you have the SMB Export setting to something other than the default of “No” so they are accessible as shares across the network. It is not clear to me if you also need “Main” as share? If you are and you are using the main Unraid array then you could install the Unassigned Devices plugin and use its feature for a ‘root’ share and call it Main to expose the whole of the array as the “Main” share. if you are using a pool rather than the main array then you could call that pool “Main” and export that instead.