itimpi

Yes. Not directly, but if you do this in maintenance mode and keep the old parity drive intact until the rebuild finishes then in the event of a data drive failing there is a procedure that would allow you to temporarily reinstate the old parity drive to handle recovering the failed data drive. Another possibility is to add the new parity drive as parity2 and only remove parity1 after successfully building parity2. That leaves you at the end with a parity2 and no parity1 (which is valid) but some people do not like ending up in this position.

This not Unraid specific so you can try googling for results. For instance trying "zfs where is parity held" shows that it is striped across drives, and that there is no direct equivalent to the Unraid Parity Check functionalit as that is handled automatiall as a background activity..

Make sure that the timeout for VMs (under Settings->VM Manager (advanced view) is sufficient to allow your VMs to shutdown, and that the Shutdown timer for the disks (under Settings->Disk Settings) is larger than the VM value.

Unexpected restarts are nearly always hardware related. Commonest causes are probably either bad RAM or power related although other possibilities are not infrequent either. 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 the problem. 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 and log to a share instead. Having said that if the crashes are due to hardware then typically nothing get recorded in the syslog.

That looks like an incomplete list. The "total 12" line suggest there should be more shown.

Are you sure that none of the disks were used to replace a disk that had failed (and been originally formatted in an earlier Unraid release). A rebuild always restores the original file system exactly.

It is gone I am afraid. You should not have formatted the drive. You would have got a warning when you tried that you will lose the contents of that drive. The correct process for handling a drive that suddenly become unmountable is covered here in the online documentation.

You would need to put that in as a feature request if you want Limetech to see it.

Follow the process for reformatting a drive as documented here. Do it twice, the first time selecting something other than what you want to finish up with, and then a second time setting it to XFS (which will automatically now be v5).

Just to update this in case someone else has a similar problem it seems to work if you use a <div> element instead of a <span> one.

If I remember correctly the licence is only checked when you start the array. Assuming I am correct (and I am sure someone will mention it if I am not) then you should be able to complete the requested checks before requesting the licence extension.

I would go with tmux instead. It provides similar functionality and is normally already present on most Unraid systems. There is also a plugin for it that provides a GUI interface for managing sessions so you do not have to use the command line.

You need to make sure the case of the .cfg files in the ‘shares’ folder on the flash drive is the same as the folders on your drives that make up the share. A mismatch can cause your symptoms.

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

It is meant to be fixed in 7.2.1-rc1 which is now available if you want to confirm it is fixed for you.

That should not be necessary.

It could be worth downloading the zip file for the release and then extract all the bz* type files overwriting those in the root of the flash drive. For some reason it can help if the system is having trouble reading these reliably from the flash drive. Having said that there have bern reports of the 7.2 release having problems on Macs (a suspected kernel compatibility) so if that does not work then reverting to the backed up release might be best.

If Unraid finds a disk already in a format supported by Unraid then it will leave them unchanged when you start again. This is doe to make it easier to get data into Unraid if disks already have data on them. You therefore need to take some action to remove the existing format which is what step 2 does. However you could also do this from the Unraid GUI using the option to erase the disk before attempting to reformat it.

I would suggest opening up the server and looking for a flash drive plugged directly into the motherboard.

I was wondering if there is a supported way to dynamically show/hide the prompt, input and help fields for a setting in a .page file under Javascript control? I have tried adding <span>...</span> type constructs around the setting but that does not work as the standard processing of a .page file ends up putting the <span> and </span> tags into different html elements thus rendering them ineffective. The reason I want to do this is to hide settings that are not relevant if previous setting are set to a particular value as I feel that provides a friendlier and more intuitive user experience. At the moment all I have managed to do is disable the input field for such settings. If there is a better way to handle this I am open to ideas?

Yes. You could create a new array (via New Config) with the undamaged drives and their data will remain intact.

Sounds as if you have another flash drive plugged in somewhere? You have not got one by any chance internally plugged directly into the motherboard.

If you do not mind having parity2 and no parity1, then when the build of parity2 completes you can simply stop the array; unassign parity1 and assign it in place of the failed drive (disk2?) and then start the array to rebuild the failed drive.

You are likely to get more informed feedback if you attach your system's diagnostics zip file to your next post in this thread. It is always a good idea to do this to allow us to see the current state of your system and so we can see logs.

Here