itimpi

You should post your system's diagnostics zip file so we can see what is happening.

If you went via the automated licence transfer process you should get it within seconds. Carefully check that it has not ended up in Spam.

It still Unsupported partition layout If you change the format to explicitly be xfs and then reboot, when you click on the drive you should have the check filesystem option. This is the way to clear the unmountable status.

Not sure why you posted in this thread as your issue seems to have nothing to do with the thread title. If you have put the new disk into a new slot on the array, then after starting the array it will need formatting. If your problem is anything else you should start a new thread about it.

I would suggest that you click on the drive and explicitly set the format to be xfs. This should then allow you to a file system repair via the GUI.

I normally estimate something like ~2 hours per TB of the parity disk so the time does not seem excessive.

The message should mean exactly what it says, but if you want me to look any further I would need a log taken with the testing mode active in the plugin settings. in terms of the parity history not showing are you up-to-date with the plugin? There was a issue with this happening on some Unraid releases but it was corrected a few plugin releases ago and should now work fine as far as I know. What Unraid and plugin releases are you running? If you post (or PM me) a copy of the config/parity-checks.log file from your flash drive I can try and reproduce your symptoms. EDIT: Just done some checking - and I may have broken some of the CLI commands. I will do some testing to today and fix any issues I find. I will also enhance the error messages to give more detailed information about any operation in progress.

If by this you mean no longer have at least 1 drive in the main array, then the answer is no. It was never intended that this requirement would be removed in the 6.12 series releases.

Have you actually tried to format it after adding it to Unraid as a pool? If you have then please post a diagnostics zip file taken after an attempt to format. in terms of the file system type you can set it explicitly by clicking on the drive on the Main tab.

The syslog in those diagnostics show problems with the flash drive. I would suggest you put it in a PC/Mac to check it can be read correctly. It may be failing, so do you have a. backup taken since you last made any configuration changes?

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 version of Unraid are you using? In Unraid 6.12 (currently at rc5 status and expected to soon become a stable release) this is built into the GUI, earlier releases involved manual editing of the SMB-extras file.

If you install the parity check tuning plugin then it has an option in its settings to pause a parity check while the backup is running and resume it afterwards. This is independent of the other features the plugin provides.

Those sort of errors in the logs typically mean connection issues such as power or SATA cabling to the drive

You need to run a correcting check (when you run such a check it will report the same number of errors as it corrects them) - were you doing this earlier? Your diagnostics only showed the one (correcting) check so it is not possible to check from them whether earlier ones were correcting or not. . Any subsequent checks after a correcting one should then report 0 errors.

Did you set the option in the plugin settings to attempt to restart array operations after a reboot? If you did then the plugin should have attempted to restart the operation from the point reached after the reboot as long as the shutdown was a clean shutdown. if you have that option set then please post your system’s diagnostics zip file so I can have a look to see if I can spot why the restart did not happen.

Is the drive showing in the BIOS? If not I would not expect Unraid to ever see it. If it is you should post your system’s diagnostics zip file so we can see what is happening on your system.

The files/folders in lost+found are ones where the repair process could not locate the directory information to give them their correct name and position in the file structure.

I have no real experience based on evidence to give a view either way It would be nice to have some feedback on where measurements have been made to give a good answer to this question

I never said do not use it - I just said many people do not. The documentation could be made more prominent by promoting the icon that opens it to be at the top of the GUI rather than at the bottom where it tends to get missed. Another option to make it even more prominent would be to have a top level tab that opens up into the manual - it would then be very hard to miss. Creating 'wizards' for tasks is quite resource intensive and although they would be nice to have but I do not see Limetech having the resources to develop these in addition to core Unraid functionality that they are already stretched to deliver in the sort of timescales that many users would like.

It is not clear that ZFS in the array offers significant benefits over using BTRFS in the array as performance is still capped by the way the array maintains parity, and there have been reports that ZFS is slower. The big benefit of ZFS is going to be when it is used in a pool as there it can give significant performance benefits. Long term the current Unraid array is going to become just another pool type that you can use when appropriate for a particular use case.

Most of those topics are already covered in the online documentation and if there are ones where that information is deficient it tends to get improved when people point out they did not understand what was written or have suggestions for changes! I do not see much advantage to adding that detail directly into the GUI as that makes maintaining/updating the information difficult. Perhaps a page in the GUI that simply contained a set of links to the documentation would be useful but even that is problematical because the links might change as the documentation is updated. It is surprising how many people ignore the fact that the online documentation exists

The check is normally very fast for xfs format drives so minutes sounds correct. You should now look to see if you have a lost+found folder on the drive which is where the repair process would put any files for which it could not find the name.

I doubt if that is a problem as the zeroing process is going to almost immediately destroy the file system on the drive so it would not be possible to write file to the drive. I have not checked but I would expect the script to also have unmounted the drive before it started zeroing it.

If a data drive fails while building parity2 this is not something I have personally experienced, but what I believe happens is that Unraid starts emulating the failed drive using parity1 plus the other data drives so the build of parity2 continues unaffected. someone may be able to chime in who has actual experience of this scenario.