itimpi

Yes, although the share using exclusive access should be automatic once all files/folders are on the pool and the Secondary storage option is then removed from that share’s settings

Just to check the obvious - I assume that you rebooted after changing the syslinux.cfg file to make the change take effect? In terms of compatibility if there is an issue it is likely to be at the Linux kernel level rather than specifically Unraid (i.e. other Linux systems also affected), so worth checking that with Asus.

Probably worth posting diagnostics zip file created after a failure trying to run the self-test so we can see why it failed.

Are you sure that the disks have failed and not simply been disabled due a write error caused by an external factor (such as the power failure)? Running the extended SMART test on a drive is a good indication of a drives health.

The syslog is full of the repeating error: May 8 22:24:08 unRAID2 kernel: pcieport 0000:00:06.0: device [8086:464d] error status/mask=00000001/00002000 May 8 22:24:08 unRAID2 kernel: pcieport 0000:00:06.0: [ 0] RxErr (First) May 8 22:24:08 unRAID2 kernel: pcieport 0000:00:06.0: AER: Correctable error message received from 0000:00:06.0 Not sure of the best way to handle this - @JorgeB may have an idea.

The diagnostics should be a single zip file containing all the files you posted. Sounds as if your system "helped" you by automatically opening the zip file and showing its contents (Macs seem particularly prone to this). Please post just that single zip file as it is much easier to work with.

Turning on XMP means you are overclocking.

Yes - when you use the New Config tool then any drives previously used by Unraid keep their content intact.

You cannot both swap parity for a larger drive and also add a new drive in the same step and remain protected against data loss. If data loss is a criteria it needs to be done in two steps. Having said that if you do not mind running unprotected for a time then you could use Tools->New config (starting with the retain all option) and then assign a 28TB drive to parity and then assign the old parity drive to a new slot. When you start the array Unraid will start to build new parity on the 28TB drive and the old parity drive will show up as unformatted and will need formatting before it can be used to store data. You can even do this format while parity is rebuilding as although it will slightly slow down the rebuild while it is running it does not take very long. The downside of this approach is that if an existing data drive fails before parity completes rebuilding its contents will be lost but that may not be critical to you?

That is not the 'go' file. It is the contents of the syslinux.cfg file. If you include your system's diagnostics zip file we will be able to see what you actually have in the 'go' file

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.

You have to disable (temporarily) the Docker and VM services under Settings as they hold files open on the System share that will prevent them being moved. You cannot do it in Maintenance mode as then the files are not available to be moved. That will be because not all the files are on the ‘Pool-apps’ pool. It will be enabled automatically for all shares which meet the conditions if you have the global option enabled, so if shows up as No when you look at the share settings it typically means that not all files/folders for the share are in the right location although it could be one of the other required conditions Providing the requested diagnostics would allow us to check for other possible issues.

You can configure the plugin to give you notifications when the plug-in does a pause/resume, and the reason why.

It did not restart (from the beginning). At about 3:00 it was paused by the parity check tuning plugin because an appdata backup started running (and you have the tuning plugin configured to pause checks while backup is running) and then resumed from where it was when the backup finished at 3’;48.

Typically the Appdata Backup and VM Backup plugins are used for this purpose. If you have special requirements these do not meet then a custom script run via User Scripts plugin would be the way to go.

You can always remove the parity drive(s) without affecting the data on the array disks. It is not clear if you already have HDD in the array? If so probably easiest to keep them there. Shares can be configured to use specific disks (or pools). Not sure where you go the idea that data cannot be moved between pools? However unless you have HDD pools then probably no need to have one pool operating as 'cache' for another which seems the only obvious Use Case.

If you click on the orange thumbs down icon and select the Acknowledge menu option then Unraid will stop alerting unless the value changes.

Click on the thumbs down icon to get more information about the error. Depending on what it is it may be of concern or not. 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 and configuration information (including SMART information for all your drives).

A fix normally only takes a few minutes.

a) Depends on how worried you are about bit-rot (it is not that common in the real world although many people are paranoid about it). XFS is probably the most stable option but does not include detecting bit-rot, whereas BTRFS (the other sensible option) does. however with XFS you can use the File Integrity plugin to automatically create checksums which can be used to file corruption. If you DO get file corruption you need to have backups to recover or be able to get the file(s) involved again. b) The downside to any encryption is that if you have file system problems it makes it much harder to recover all data intact. You have not stated why you want to use it? It really only protects against those who have physical access to the drives while Unraid is not running but that might be the reason you want it.

Have you tried booting in Safe Mode as you have a deprecated [plugin that may be causing problems. You also have a number of issues from Fix Common Problems that should be taken care of: May 2 23:44:14 ur root: Fix Common Problems: Warning: Share appdata.2 is an implied array-only share, but files / folders exist on the cache May 2 23:44:14 ur root: Fix Common Problems: Warning: Share etc is an implied array-only share, but files / folders exist on the cache May 2 23:44:14 ur root: Fix Common Problems: Warning: Share mnt is an implied array-only share, but files / folders exist on the cache May 2 23:44:14 ur root: Fix Common Problems: Warning: Share SyncThing set to cache-only, but files / folders exist on the array May 2 23:44:14 ur root: Fix Common Problems: Warning: Share backups set to not use the cache, but files / folders exist on the cache drive May 2 23:44:15 ur root: Fix Common Problems: Warning: Deprecated plugin folder.view2.plg

See if you can get diagnostics first and if so post them. Highly likely, though, that it will not be possible. After trying that I would suggest power-cycling the server (if necessary long pressing the power button to get it to shutdown) and see if that brings things back. Posting diagnostics taken after doing that is also a good idea.

@GeorgeJetson20 Do you pass any hardware through to your VMs? Could not get the diagnostics to download to have a look. If so adding the new NIC may have changed the IDs. I would suggest deleting config/vfio.cfg fom the flash drive, rebooting, and then redoing the hardware passthroughs.

You can use the steps described here to get your drives assigned again so they are accessible. If you are not sure about the process ask questions. As was mentioned VM configurations are not stored on the flash drive and for docker containers only the templates that were used to configure them. We can work on getting those operational again once you have correct access to all your drives restored. We would want you to post diagnostics at that point so we can see the current state of things.

According to those diagnostics the 'media' share is now configured with Primary=cache and nothing for secondary which will force all new files to only go to the 'cache' pool. The existing files for that share currently reside on the array. You probably want Primary=cache, Secondary=Array and Mover direction to be cache->array for files to initially be written to the cache pool for best performance and then later moved to the main array. If you never want the files to be cached then set the Primary=Array and nothing for the Secondary.