JorgeB

Please post the diagnostics.

Unfortunately, there's nothing relevant logged, this can also be a hardware issue, one thing you can try is to boot the server in safe mode with all docker containers/VMs disabled, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one, including the individual docker containers.

Reboot to clear the logs, and post new diags after it fails again.

That looks like a filesystem problem, also btrfs is detecting data corruption on both devices. There's a known issue with Ryzen and overclocked RAM like you have, where it will cause data corruption; first thing would be to correct that https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-819173 Then you can also run a few memtest passes to make sure there are no obvious RAM issues, and after that, back up and recreate the pool.

If you don't have a flash drive with the same release you are running, then yes, first create it with the USB tool, then continue the other steps.

You can do this: https://forums.unraid.net/topic/198440-73xx-version-moving-boot-drive-nvmessd-to-another-drive-nvmessd/#findComment-1619744

Syslog is being spammed with HBA issues: May 26 05:07:21 Unraid kernel: mpt3sas_cm0 fault info from func: mpt3sas_base_make_ioc_ready May 26 05:07:21 Unraid kernel: mpt3sas_cm0: fault_state(0x6004)! May 26 05:07:21 Unraid kernel: mpt3sas_cm0: sending diag reset !! May 26 05:07:22 Unraid kernel: mpt3sas_cm0: diag reset: SUCCESS May 26 05:07:22 Unraid kernel: mpt3sas_cm0: CurrentHostPageSize is 0: Setting default host page size to 4k May 26 05:07:22 Unraid kernel: mpt3sas_cm0: basedisplay_fwpkg_version: complete May 26 05:07:22 Unraid kernel: mpt3sas_cm0: LSISAS3224: FWVersion(09.00.100.00), ChipRevision(0x01) May 26 05:07:22 Unraid kernel: mpt3sas_cm0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ) May 26 05:07:22 Unraid kernel: mpt3sas_cm0: sending port enable !! May 26 05:08:13 Unraid kernel: mpt3sas_cm0: port enable: SUCCESS May 26 05:08:13 Unraid kernel: mpt3sas_cm0: search for end-devices: start Make sure it's well seated and properly cooled; you can also try a different PCIe slot.

This can only be NIC, cable or switch/router.

Enable the syslog server then post that together with fresh diagnostics after a crash.

Storage is mounting correctly. I then see containers starting, if that covers a crash, disable the Docker service and see if it still crashes, and post a new syslog if it does.

Restart the array, and they should go way, it's a bug.

You would need to erase this. 8GB is enough for a dedicated boot pool (but you still cannot add a smaller device to an existing one, e.g., if you had a 16GB dedicated boot pool, you could not add an 8GB device; you could the other way around)

Recommend removing all the extra SMB parameters and retesting. If nothing else, they are spamming the log.

That's possible.

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.