Cyong

Greetings, So, I think that my upgrade from 6.12.3 to 6.12.4 went sideways. Following clicking the reboot button via the unraid GUI. I find the system unable to boot, and gives the message "Loading /bzimage... Failed: No such file or Directory" when i attempt to use the safe mode, i get the same error. Any thoughts? Or should I grab my backup and restore? (that is 3 weeks old cause I forgot to do a backup right before upgrading, I have gotten to used to unraid 'just working', my mistake.) Kind Regards,

So as it stands today I have all my array data drives formatted as xfs - encrypted. Also I have 4 pools as follows Apps (xfs) for Docker/VM -Single NVME Cache (btrfs) for writing to Array - Single SATA SSD Aux (btrfs) for user shares of things I want served fast - 2xNVME Scratch (xfs) for SMB general purpose temporary - Single SATA SSD I am aware of the benefits of zfs with things like TrueNAS, and making performant zpools for an enterprise. I am already planning to format the Apps to zfs for checkpoints. But what about the array data disks, and the other pools ? What benefits would zfs bring, and when should it be considered over the other filesystems?

Diagnostics attached. unraid-diagnostics-20230426-1926.zip

Greetings, Earlier this month, I had a non-graceful shutdown. So I ran a parity check and found that there was 1 error. I ran it again and confirmed it was corrected. Then during the monthly parity check another error occured, I have run several manual parity checks with error correction since, and as you can see, the errors count is going up, first two, then three... I look at the error count of the drives, and there appears to be no un-recoverable errors. So I am confused where these parity errors are coming from, as well as why they are going up on subsequent runs when doing the parity check with writing corrections. Any advice or thoughts? Kind Regards,

+1 for built-in snapshotting