JorgeB

Aah, OK, so I assume the old server is not running Unraid?

Diags you posted are after booting in safe mode, not clear the plugin was uninstalled, you can just delete them from the plugins folder in the flash drive.

Not clear if this is another drive, do you have two 4TB drives total, and what is the current parity size?

Cache device wasn't replaced correctly, likely because cache replacement is broken on v6.9.x+, stop array, unassign the new cache device (cache2), start array and post new diags.

No, you can enable the GUI help to see what each option does.

Enable syslog server and post that log after a crash. Old shares on the flash are not a problem, but you can also delete all the cfgs from shares that no longer exist.

Try uninstalling the dynamix.s3.sleep plugin.

It was, but not anymore.

Please post the diagnostics.

This is basically useless, the important part is the SMART test, which failed, so the disk is failing and needs to be replaced. You can't do that since you only have single parity and disk1 is already emulated, do you still have an intact old disk1? I.e., was this an upgrade or a replacement because it failed?

Replace or try with different parts if you have them available, not much else you can do.

Monitor the log for similar errors to the ones posted above to make sure all is good.

Power down check/replace cables/slot on disk 2 and see if it comes back online.

There appear to be multiple browsers open on the GUI, close hem all, reboot and post new diags if there are still issues.

You should run memtest.

Looks like flash drive problems, this will copy the syslog to the flash drive: cp /var/log/syslog /boot/syslog.txt Then attach it here.

You need to re-sync parity2: https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself

It happened before the reboot so we can't see what the problem was, disk looks fine and the emulated disk is mounting, so you can rebuild on top, I would recommend replacing/swapping cables on disk2 before rebuilding to rule that out if it happens again.

There are issues with multiple disks on multiple controllers: Sep 9 23:07:49 Tower kernel: ata4: hard resetting link Sep 9 23:07:55 Tower kernel: ata4: link is slow to respond, please be patient (ready=0) Sep 9 23:07:59 Tower kernel: ata4: COMRESET failed (errno=-16) Sep 9 23:07:59 Tower kernel: ata4: hard resetting link Sep 9 23:08:01 Tower kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Sep 9 23:08:01 Tower kernel: ata4.00: configured for UDMA/33 Sep 9 23:08:42 Tower kernel: ata8: failed to read log page 10h (errno=-5) Sep 9 23:08:42 Tower kernel: ata8.00: exception Emask 0x1 SAct 0x1000 SErr 0x0 action 0x6 Sep 9 23:08:42 Tower kernel: ata8.00: failed command: READ FPDMA QUEUED Sep 9 23:08:42 Tower kernel: ata8.00: cmd 60/00:00:c8:6a:14/01:00:96:00:00/40 tag 12 ncq dma 131072 in Sep 9 23:08:42 Tower kernel: res 01/04:60:c8:6a:14/00:00:96:00:00/40 Emask 0x3 (HSM violation) Sep 9 23:08:42 Tower kernel: ata8.00: status: { ERR } Sep 9 23:08:42 Tower kernel: ata8.00: error: { ABRT } Sep 9 23:10:34 Tower kernel: ata13.00: exception Emask 0x1 SAct 0x1000 SErr 0x0 action 0x6 Sep 9 23:10:34 Tower kernel: ata13.00: failed command: WRITE FPDMA QUEUED Sep 9 23:10:34 Tower kernel: ata13.00: cmd 61/00:00:f8:39:97/01:00:96:00:00/40 tag 12 ncq dma 131072 out Sep 9 23:10:34 Tower kernel: res 01/04:58:f8:38:97/00:00:96:00:00/40 Emask 0x3 (HSM violation) Sep 9 23:10:34 Tower kernel: ata13.00: status: { ERR } Sep 9 23:10:34 Tower kernel: ata13.00: error: { ABRT } Sep 9 23:10:34 Tower kernel: ata13: hard resetting link Sep 9 23:11:03 Tower kernel: sd 6:0:3:0: [sdi] tag#803 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 cmd_age=0s Sep 9 23:11:03 Tower kernel: sd 6:0:3:0: [sdi] tag#803 CDB: opcode=0x88 88 00 00 00 00 01 93 77 f4 70 00 00 00 a0 00 00 Sep 9 23:11:03 Tower kernel: blk_update_request: I/O error, dev sdi, sector 6769079408 op 0x0:(READ) flags 0x0 phys_seg 20 prio class 0 Two of the controllers are Marvell based and have known issues, but ata4 is the onboard SATA, so there might be a power or connection issue, I would recommend replacing the SASLP/SAS2LP controllers with LSI anyway and then check all connections and/or test with a different PSU.

Nothing much of relevance logged, there's a network related crash, so if you changed anything regarding dockers with custom IP address this might be worth checking: See if this applies to you: https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/ See also here: https://forums.unraid.net/bug-reports/stable-releases/690691-kernel-panic-due-to-netfilter-nf_nat_setup_info-docker-static-ip-macvlan-r1356/

Forgot this one: check filesystem Edit: and this one also, turbo write

These repeating errors: Sep 9 11:39:15 Tower kernel: sd 11:0:2:0: device_unblock and setting to running, handle(0x000b) Sep 9 11:39:15 Tower kernel: sd 11:0:2:0: Power-on or device reset occurred Sep 9 11:39:15 Tower rc.diskinfo[11959]: SIGHUP received, forcing refresh of disks info. Sep 9 11:39:33 Tower kernel: sd 11:0:2:0: device_block, handle(0x000b) Sep 9 11:39:33 Tower kernel: mpt3sas_cm0: log_info(0x31120100): originator(PL), code(0x12), sub_code(0x0100)

Check/replace cables(including power)/slot on disk4, there are multiple timeout/reset errors, then try again.

Please post diagnostics.

You should also replace/swap power cable first.