itimpi

Your first correcting check will report the same number of errors as it lists the number of corrections it made. Any subsequent checks (preferably non-correcting) should report zero.

There is nothing built into the Unraid GUI. As was mentioned what type of search are you wanting to do as this is likely to affect any recommendation of the best way to do it.

It is covered 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.

No. The drive that is added is cleared (written as all zeroes) if not pre-cleared before adding it. A drive that is all zeroes can then be added without affecting parity so no parity update is required.

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 checking that the remainder of the parity drives contain only zeroes. This is to make sure that it is now possible to add larger data drives (up to the size of the smallest parity drive) with parity remaining valid.

Thanks for the feedback. Always glad to have confirmation that the issue seems to have been resolved and something new has not immediately popped up

You could also try the original USB but with a stock config folder rather than your personalised one. That could give you an indication as to whether it is the physical flash drive or something in your configuration information. Not much point in doing a licence transfer to a new flash drive if it is not going to help.

You may be able to fix it by using Tools->New Config and then specifying the new Id for them that is being generated as part of the pass-through mechanism. I am not a ProxMox user so cannot be sure that would work, but that does work for other emulators.

It is unlikely that the plugin is what is stopping it from booting. You might want to try backing up the flash drive and then downloading the zip file for the release from the Unraid site and extracting all the bz* type files overwriting those in the root of the flash drive in case the system is having problems reading one of them. Having said that you can always remove (or disable) a specific plugin by by deleting its .plg file under config/plugins on the flash drive or by renaming it to have a different file extension and then rebooting. You can also always disable all plugins by booting in Safe Mode.

I believe the message originates from the Mover Tuning plugin so if it bothers you too much you can stop it by removing that plugin.

You should post your system’s diagnostics zip file. If the ‘emulated’ drive is mounting then you would lose NO data by rebuilding the data drive. Since both possible solutions put a similar stress on drives then not sure why you want to forgo the data drive rebuild option. In fact if the data drive is smaller than your parity drives it would put less stress on the drives than rebuilding parity.

The drive got disabled because a write to it failed for some reason and it is no longer in step with parity. Any attempt to reactivate the drive without rebuilding would at best lose any data that had been written to the drive since it was disabled, whereas the rebuild process would preserve that data. This is technically possible but it would then involve a parity drive rebuild instead of the data drive rebuild so just as much stress on the drives.

@Ruato @dopeytree Just thought I would check whether the lack of new reports is good sign and means your issues are now resolved since the last release of the plugin, or is that you have simply not been in a position where a check is running so you would notice if there is still a problem.

Dynamix File Manager always uses a copy/delete strategy regardless of whether the files are located as this is safest. Doing a move can sometimes result in unexpected results.

It is normally better to run it from the GUI if at all possible and it is easy to make a mistake with the command when running it via the command line.

No - that is a common misconception. Highwater is normally the best option for most users.

The file is in the ‘logs’ folder on the flash drive.

That is correct behaviour. The split points are based on the size of the largest drive - not on percentage used. It is as described in more detail 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.

It will if you enable the Mirror to flash option in the syslog server.

If you want a log that survives a reboot then you need to enable the syslog server.

You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread.

just for interest why not write directly to the array? You array write speeds seem much higher than I normally expect to see (unless running without parity) so the advantage of going via a cache pool may be marginal.

Nothing wrong with the steps you posted. It has the big advantage that in the first 2 steps you have the ‘removed’ drive intact in case something goes wrong. The array remains usable (albeit with reduced performance) during each step.

Can’t see it so it looks like it may somehow have really disappeared 😒. Not sure what could cause that.