itimpi

A drive being disabled simply means that a write to it has failed so it is no longer in sync with parity, More often than not this is not the drive itself but an external factor such as cabling and/or power. The instructions for re-enabling the drive are covered here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI. In addition every forum page has a DOCS link at the top and a Documentation link at the bottom. The Unraid OS->Manual section covers most aspects of the current Unraid release.

I have thought about it but not sure how easy that will be to do in a way that will not have issues. Has anyone looked at whether the docker containers can simply be paused rather than stop and restart? That would be much easier to implement. Using this type of solution it might be easy enough to be selective about which ones to pause as you would normally only be interested in ones that do array access. Having said that I think most people do not want docker containers to be unavailable for the length of time parity checks take.

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.

Not sure what is going on if you can see the SSD in the BIOS as there is no sign of it showing up even at the hardware level as Unraid is loading. Any existing content/format should be irrelevant.

I think at some point in the future it might be possible to have pools in both the secondary and primary storage. However that is just a guess, and even then I do not see UD being supported in that way.

If you have the Parity Check Tuning plugin installed then it has options to automatically pause array operations while mover or appdata backup are running (as they severely degrade performance if run in parallel with an array operation).

No, only the array can be secondary storage.

Have you tried stopping all docker containers and/or VMs? the File Activity plugin might give a clue by allowing you to see what files are being accessed.

The moment you get even a single error in memtest you have a RAM problem ☹️ Unfortunately the opposite is not always true - sometimes memtest shows no error but you can still get RAM errors when the system is under heavy load. That is one of the reasons we often suggest to try with less Ram sticks installed

There seem to be a lot of reads and writes to several drives in the array that are not due to the parity operation. These will severely degrade the parity operation so the way to speed it up is to stop whatever (person or application) is doing that array activity.

Do you really mean it reboots rathe than just freezing so that you have to manually reboot? if you really mean it is rebooting then it is almost certainly hardware with the most likely culprits being the PSU struggling or thermal issues such as CPU overheating.

You could always backup the flash drive to your PC and then put a fresh install of Unraid to prove that or boots up OK. If it does you can then copy the ‘config’ folder from the backup you have just made (which contains all your settings and your licence key) overwriting the config folder contents on the flash drive.

It should just ignore it.

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.

Were these SATA->SATA or Molex->SATA and how many ways were you splitting them? Nothing wrong with splitters per se but you do need to make sure that you are not trying to split a SATA connection in particular more than 2 ways. In my experience Molex->SATA splitters are more reliable as the Molex connector end is more robust and can take a heavier current without voltage sag happening.

Make sure that the EFI folder on the flash drive does not have a trailing character (if so remove it to enable UEFI boot). I think the latest Unraid release has UEFI boot enabled by default whereas earlier releases did not.

Do not understand why since the licence is tied to the flash drive. Do you intend to run 2 servers rather than 1 in the future (which WOULD require 2 licences). I am not quite sure exactly what is the current split of drives between the 2 servers and how you want things to end up? It is a bit confusing to be talking about 8TB drive and data drives that are larger as parity can never be smaller than the largest data drive.

The syslog in the diagnostics shows you are getting continual read errors on disk5 so not much point in continuing. Not quite sure why although the way it started suggests you might have an issue with the power/SATA cabling or insufficient power reaching the drive. Are your sure your PSU is OK and capable of handling the load of all the drives simultaneously?

Not an answer to the current issue, but once you have this resolved make sure that you set a Minimum Free Space value for the cache pool to stop the problem re-occurring.

Yes - assuming you want to keep using the Unraid server and have some protection against drive failure. Do you have the .key file? If so it should be just a case of putting it into the ‘config’ folder on the flash drive.

I personally use different shares with different Split Levels.

Not. Split level is at the User Share level so you have to have different shares to have different Split Levels.

I would say that it is definitely your flash drive as the messages mention [sda] which is standard for the flash drive. I do not think it will help in this case, but the key point of Safe Mode is that it stops plugins from being loaded (plugins can change system components) and that applies regardless of whether you are in GUI mode or not.

There is one included on the Unraid boot menu. That version only works if you boot in Legacy mode, but you can get a newer one that will boot in UEFI mode from memtest86.com

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