JorgeB

Yes, if it's same size or larger than the current boot pool, I see the GUI reporting 32.2GB for the current boot partition, so 32Gb may not be enough

Type mv /boot/config/pools/cache_ssd.cfg /boot/config/pools/cache_ssd.bak Reboot and you shoudl be all set

Click on the data partition and then "Erase Pool" (it won't erase the boot partition) Then set the filesystem to "auto"

Please post the diagnostics to check the pool names.

PS C:\WINDOWS\system32> Get-SmbServerConfiguration AnnounceComment : AnnounceServer : False AsynchronousCredits : 64 AuditSmb1Access : False AutoDisconnectTimeout : 15 AutoShareServer : True AutoShareWorkstation : True CachedOpenLimit : 10 DurableHandleV2TimeoutInSeconds : 180 EnableAuthenticateUserSharing : False EnableDownlevelTimewarp : False EnableForcedLogoff : True EnableLeasing : True EnableMultiChannel : True EnableOplocks : True EnableSecuritySignature : False EnableSMB1Protocol : False EnableSMB2Protocol : True EnableStrictNameChecking : True EncryptData : False IrpStackSize : 15 KeepAliveTime : 2 MaxChannelPerSession : 32 MaxMpxCount : 50 MaxSessionPerConnection : 16384 MaxThreadsPerQueue : 20 MaxWorkItems : 1 NullSessionPipes : NullSessionShares : OplockBreakWait : 35 PendingClientTimeoutInSeconds : 120 RejectUnencryptedAccess : True RequireSecuritySignature : False ServerHidden : True Smb2CreditsMax : 2048 Smb2CreditsMin : 128 SmbServerNameHardeningLevel : 0 TreatHostAsStableStorage : False ValidateAliasNotCircular : True ValidateShareScope : True ValidateShareScopeNotAliased : True ValidateTargetName : True

Not with a data partition; you can if you erase that first and the boot partition is the same size or smaller than the new device (any data there would be lost)

The test was made from Windows 10 Pro

Syslog is being spammed with USB Manager messages; see if you can fix that. It's difficult to look for other issues. I see that disk1 is NTFS. NTFS has limited support with Linux, recomend backing up and reformatting with a native Linux filesystem. The default for the array is XFS.

If you created a new Docker folder, I recommend using overlay2 as the storage driver; it tends to be more reliable than btrfs with Docker.

Nope, you must copy the key file to the flash drive, see the link above. No, because the data partition is also mirrored when you add a second device. so it would need to be 1TB. You can add a device just large enough to cover the boot partition if you erase the data partition first (all data there woudl be lost).

You don't need to transfer the key, you can boot from a flash drive and still use the TPM key.

New device must be the same size or larger than the old one.

You can replace a device from a mirrored pool (same size or larger). You can also add a new device to a single boot pool, then remove the other one (again, same size or larger), to replace it with a smaller device, you can boot from a flash drive, then run the wizard to create the boot pool on the new device https://forums.unraid.net/topic/198440-73xx-version-moving-boot-drive-nvmessd-to-another-drive-nvmessd/#findComment-1619744

Please post the diagnostics.

You can upgrade, 7.1.x users with updates expired for 7.2.0 can now update to 7.2.7 and any newer 7.2 release.

Possibly, you can post or send me one with the special characters in a different order, or better yet, keep the special characters in the same order and change only the other ones.

Reboot and try again, if it still fails, post new diags right after trying to start it.

If the pool is really a mirror you can follow the steps above, if you are not sure, post the diagnostics. This step is not needed; a mirror is automatically created once you add a 2nd device.

The device is read-only, so Unraid will not be able to remove it from the pool. Try shutting down the server, physically removing that device, and then starting the array with the remaining one, if it still fails to mount, post new diags.

If the USB is not in sync, copy the config first to it: https://forums.unraid.net/topic/198440-73xx-version-moving-boot-drive-nvmessd-to-another-drive-nvmessd/#findComment-1619744

I see that you are using the SAS spin down plugin, could be related to that based on the syslog. I recommend retesting without it.

Yes, as mentioned, you will need to use the Limine bootloader if you are booting from a flash drive, can use the stock one if booting from an internal boot pool, since that will use the Grub bootloader instead.

That suggests an issue with Plex. Recommend looking for its support thread; there can be some config or known issue.

According to the diags a new config was done. What error do you see when trying to start the array?

Please post the diagnostics