JorgeB

Try running bare-metal, with only one stick of RAM, if the same try the other one.

Possibly this issue:
https://forums.unraid.net/bug-reports/stable-releases/crashes-since-updating-to-v611x-for-qbittorrent-and-deluge-users-r2153/
 
Should also change docker network type to ipvlan, since there's a related call trace.

It was, so replacing cables might also fix the other one, you should also replace cables for disk2, if it happen once it might happen again.

Is the monitor connected to the RTX or iGPU? Does it boot without the RTX?

Most likely because it's an SMR drive.

Jul 15 15:53:02 RussellUnraid kernel: critical medium error, dev nvme0n1, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 2  
It's logged as a device problem, do you have a different slot/PC to retest?

If you mean like an instant power off it's usually hardware related, trying a different PSU would be a good place to start.

Difficult to say for sure, but it's not good.

Use -L

Since the problem occurred on spin up looks like this issue:
https://forums.unraid.net/topic/103938-69x-lsi-controllers-ironwolf-disks-disabling-summary-fix/
 
Alternatively connect that disk to an onboard SATA port instead, you can swap with a another disk.

Yes, as long the the emulated disks are mounting and contests look correct, since the diags you posted are with the array stopped.

Try this:
https://forums.unraid.net/topic/118286-nvme-drives-throwing-errors-filling-logs-instantly-how-to-resolve/?do=findComment&comment=1165009
 

Try switching to ipvlan (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enabled, top right)).

There are ATA errors logged for parity, replace cables (power and SATA) and try again.

You likely have a cooling problem, like a fan issue, or the cooler not making good contact, or the temps are being reported incorrectly.

It appears to be this:
Jul 20 11:48:37 Serveur-Maison rc.swapfile[6077]: Starting swap file during array mount ... Jul 20 11:48:37 Serveur-Maison rc.swapfile[6084]: Creating swap file /mnt/cache/swapfile please wait ...  

Jul 19 22:17:10 bob kernel: XFS (sdl1): device supports 4096 byte sectors (not 512)  
This disk it 4K native, due to that, and the array formatting the disk with 512e I believe the only option is to mount it in the array again, you can use a different PC with a trial key if more practical, then transfer the data over LAN.

Select the correct pool as the primary storage, the array as secondary storage and mover action from pool to array, that 's the same as the old cache=yes.

Except for some hardware issue like bad RAM or firmware don't know of any direct causes, possibly an unclean shutdown also.

Does it boot if you blacklist the iGPU driver?
https://docs.unraid.net/unraid-os/release-notes/6.10.0#linux-kernel

If the log tree is the only problem this may help:
 
btrfs rescue zero-log /dev/nvme0n1p1  
 

Unraid formats disks with the partition starting on sector 64, SSDs are partitioned on sector 2048 (for performance reasons) so you can never direct replace a HDD with an SDD of the same capacity, would need to do it manually.

Syslog in the diags starts over after every boot, if it happens again you can enable the syslog server to see if that catches something.

Apps segfaulting and zfs panic suggest a hardware problem, try running with just 1 stick of RAM, if issues persist try the other one, that would basically rule out bad RAM, memtest doesn't always find all issue, if errors with either stick CPU and/or board would be the next suspects.

Kernel change can change things, though usually it's the other way around, with newer kernels it's much less likely to happen, but tit still does to some, BIOS update may also help.