JorgeB

loop2 is usually the docker image, was that created new?

Should be fixed now.

That one shows the server running out of memory.

https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui

You still need to:

Disk wasn't offline during the boot, it dropped offline during the rebuild, and again, since single parity can't emulate 2 disks both disks currently have invalid data, now either disk5 died making recovery more difficult, or more likely it's just a connection problem, but we need the SMART to have a better idea, nothing you can do before rebooting/power cycling to see what's what.

Changed Status to Closed Changed Priority to Other

This is a general support issue, first thing to do is to update the LSI firmware since it's on a very old release: Jun 23 06:41:02 fileserver kernel: mpt2sas_cm0: LSISAS2008: FWVersion(07.15.08.00), ChipRevision(0x03), BiosVersion(07.39.00.00) Current one is 20.00.07.00, if after that you still need help please start a thread on the general support forum.

It will work with an older Unraid version, and possibly with the new beta, so you can run a long test and check the result.

Since the filesystem is corrupt it affects both devices, redundancy can only help when a device fail, look for the CA appdata backup/restore plugin.

Best bet is to use the docker dedicated support thread, you can find it by clicking on the docker:

Is current cache xfs or btrfs?

Problem with the Asmedia SATA controller that ended up dropping both cache devices: Jun 23 02:54:05 UnRAIDSVR kernel: DMAR: [DMA Read] Request device [0a:00.0] fault addr 7fffff00000 [fault reason 06] PTE Read access is not set Jun 23 02:54:35 UnRAIDSVR kernel: ata1.00: exception Emask 0x0 SAct 0x3c0007e SErr 0x0 action 0x6 frozen ... Jun 23 02:55:31 UnRAIDSVR kernel: ata2: softreset failed (1st FIS failed) Jun 23 02:55:31 UnRAIDSVR kernel: ata2: limiting SATA link speed to 3.0 Gbps Jun 23 02:55:31 UnRAIDSVR kernel: ata2: hard resetting link Jun 23 02:55:35 UnRAIDSVR kernel: ata1: softreset failed (1st FIS failed) Jun 23 02:55:35 UnRAIDSVR kernel: ata1: reset failed, giving up Jun 23 02:55:35 UnRAIDSVR kernel: ata1.00: disabled ... Jun 23 02:55:36 UnRAIDSVR kernel: ata2: softreset failed (1st FIS failed) Jun 23 02:55:36 UnRAIDSVR kernel: ata2: reset failed, giving up Jun 23 02:55:36 UnRAIDSVR kernel: ata2.00: disabled Jun 23 02:55:36 UnRAIDSVR kernel: ata2: EH complete Try using the Intel ports instead.

Cache filesystem is corrupt and needs to be re-done, you also need to check filesystem on disk4, but these are likely a consequence of all the crashing, not the reason for it, after it's fixed you can enable the syslog server/mirror feature to see if it catches something, but if the problem is hardware related it likely won't.

SMART report is incomplete due to a likely bug with smatmoontools, not sure if the new beta uses a newer version, you could try that.

Not on the syslog, there might be if you post the complete diagnostics instead.

Logs are after rebooting so not much help, you can try this but if it's a hardware issue there might not be anything logged when it crashes.

Did it also crash with the old hardware?

Macvlan call traces are usually caused by having dockers with a custom IP address:

Best bet for that is to start a new thread on the KVM forum, don't forget to include the diagnostics.

Again this is a general support issue, but looking at the diags you have something crashing Samba: Jun 23 13:24:07 KNORRHANE kernel: traps: smbd[19654] general protection ip:149efb96af94 sp:7fff9501b5e0 error:0 in ld-2.30.so[149efb95f000+20000] Jun 23 13:24:07 KNORRHANE root: /etc/rc.d/rc.samba: line 12: 19654 Segmentation fault /usr/sbin/smbd -D Start by booting in safe mode, and if you need more help please start a thread in the general support forum.

Again this is a general support issue, but looking at the diags you have something crashing Samba: Jun 23 13:24:07 KNORRHANE kernel: traps: smbd[19654] general protection ip:149efb96af94 sp:7fff9501b5e0 error:0 in ld-2.30.so[149efb95f000+20000] Jun 23 13:24:07 KNORRHANE root: /etc/rc.d/rc.samba: line 12: 19654 Segmentation fault /usr/sbin/smbd -D Start by booting in safe mode, and if you need more help please start a thread in the general support forum.

Changed Status to Closed Changed Priority to Other

This is a general support issue, please start by looking at this thread, there is no one-size-fits-all solution but there are several thing you can try:

This is a general support issue, please start by looking at this thread, there is no one-size-fits-all solution but there are several thing you can try: