itimpi

I hope you did NOT try to format the emulated unmountable drive as that would wipe its contents and update parity to reflect this has been done.

The Prefer setting for Use Cache means you want files moved TO cache by mover. If you want mover to move files from cache to the array you need the Yes setting. There is good help built into the GUI for describing how the setting works and how it affects mover.

Normally the whole zip file is wanted.

There should be a progress.save file in the plugins folder on the flash drive. If you PM me that I might be able to work out why you do not get the correcting/non-correcting indicator. The fact that it is being flagged as a Manual check shows the plugin HAS updated the history as that is not done as standard. There is also a config/parity-checks.log file on the flash drive that is of interest so I can see if the correcting status WAS recorded there but not displayed when you invoked the history so you could PM me a copy of that as well. If you do not activate any of the extra functionality then the plugin will not be doing anything in those areas so any side-effects should be minimal/unlikely. The plugin does not install any new binaries which are the commonest reasons for plugins causing instabilities. You can see if Limetech will enhance the history without the plugin but not sure if they have any plans in that area so good luck with that. That is because of changes at the forum level and many previous links have recently been broken by the changes. The link in the plugin has been updated for the next plugin update (as part of getting ready for the 6.12 Unraid release).

In such a situation I am not sure you want to ‘move’ the data to other drives as a ‘move’ implies write operations on the drive. I would prefer to simply ‘copy’ the data elsewhere to avoid any writing to the suspect drive.

You need to put the address of your Unraid server into the ‘Remote syslog server’ field to get the server to log to itself. Without that it is just ‘listening’ for log requests. An alternative is to use the Mirror to Flash option.

Elapsed time should be the same (you cannot do both at once). The only difference might be around safety - having a second parity to protect against 2 simultaneous disks having issues vs rebuilding a possible problem data drive.

It would be normal for mover not to move files in the 'system' share if you have either the VM or Docker services enabled as they keep files open and mover cannot move open files. Those services should be disabled while trying to move files in the system share. As was mentioned you also seem to have the docker image file configured to be 100GB which is far more than you should need. The default of 20GB is fine for most people. If you find that you are filling it then that means you almost certainly have a docker container misconfigured so that it is writing files internal to the image when they should be mapped to an external location on the host.

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

The diagnostics show write errors on disk2, but for some reason do not show what lead up to that. You should carefully check all cabling (power and SATA) to the drive as that is the commonest cause of such issues.

You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread. What do you have set for the Minimum Free Space for the cache pool? This is an important setting as it sets the criteria for when Unraid should stop using the cache pool for new files.

Have you made sure that the current pool is in a redundant mode? It might be a good idea to post your system's diagnostics zip file so we can check to see if we spot any potential problems !

Was this drive showing as Unmountable before the rebuild or did the emulated drive mount OK? Just asking as the answer might affect the recommended way forward. If it WAS showing as unmountable the it showing as unmountable after the rebuild would be expected as all the rebuild does is make the physical drive match the emulated one. Are you sure the drive had really failed rather than simply been disabled due to a write failing? The correct handling of unmountable drives is covered here in the online manual accessible via the Manual link at the bottom of the Unraid GUI.

This almost certainly means that it was just the container folder name that was lost so if you recognise the contents you can rename that folder back to what it should be and then put it into its correct place in the disks folder structure. The hardest things to sort out would be any files that now only have the numeric cryptic name. As was mentioned the Linux file command can give you the file type (and thus it’s likely file extension) if you want to examine these further.

It is not critical to do it immediately but it has been announced that support for reiserfs is planned to be removed from the Linux kernel in 2025. possibly a good reason to consider doing it sooner is that reiserfs cannot handle drives larger than 16TB and hard drives exceeding this limit are now available.

Perhaps you should post a screenshot of what you can see when you click on the drive.

Just a FYI this is posted in the Unraid v5 part of the forum - I assume you are talking about v6?

It should just be Settings->Management Access

It USED to be 2GB RAM as the minimum requirement for Unraid v6 but as the functionality has increased so has the RAM requirement. Unraid runs from RAM so every bit of functionality added incurs a RAM cost.

It is easy enough normally to turn of the XMP setting in the BIOS to see if it helps.

It could as XMP is by definition an overclock. Many motherboard manufacturers now make it the default on the basis it normally does not cause problems.

Not sure you can easily. Limetech normally handles beta releases internally. The equivalent to ‘public beta’ releases from other vendors tend to be labelled as rc (release candidate) releases by Limetech.

I wonder if the rapid pace of recent beta builds means that Limetech are ‘polishing’ items getting ready for the public 6.12rc releases (being hopeful).

The diagnostics show that you are could be running into issues dues to not having enough RAM installed. Do you have the ability to add more? Current releases of Unraid really require about 4GB installed for all functionality to work correctly.

The syslog is not going to be much use as it is just after booting. you should post your system’s diagnostics zip file attached to your next post in this thread which contains much more than the syslog and in particular details of your hardware and how you have things configured.