MeowMeow

I just did enabled it thanks to @JorgeB

Thanks for the help, I know that. I was just trying to find what caused the system restart during that time. My only guess is something caused system crash around when mover started.

I know about the uptime and I'm sure it restarted 14 hours ago, when it starts moving items from cache to array.

I'm still not sure what happened, that could be start to track. Thanks.

I'm not 100% sure if my Unraid server got restarted last night, but this morning I saw it it was on the state that array wasn't started. Is there any place or ... I can check if that's restarted or not?

I still come back with my default configuration with XFS and Parity. I'll check things later again.

To answer my own question, I don't have much of data and so it's easy for me to switch between to check. Copy from NVME to SSD array, it was like 80 MB average with unblance But from NVME to ZFS pool, it's above 800MB, at least 10x faster! Compression it's also enabled

Are there any benchmarks showing the perf difference?

Thanks to everyone, I converted all my drives to ZFS (Cache and other drives) and tried the ZFS Pool with raidz, but revert the settings to unraid array because the mover doesn't support other pools at the moment. Somewhere in the forum I read in the 6.13 might this thing get released an normal unraid array becomes another pool

Ah great, thanks.

Sorry I didn't get this part. an old flash drive?

Hi friends, I'm noob when it comes to Raid and Unraid. At the moment my array configuration is like this: 1 SSD Parity 2 SSD Disks 1 NVME Cache I'm reading everywhere that I shouldn't use parity with SSD due to problems with trimming, also reading since version 6.12 things should be normal? My SSDs are all Samsung EVO and QVO. Should I ditch the parity and use that device as normal disk? Should I convert my configuration to ZFS? By the way, in the scheduler the trim is disabled. Please guide me