JorgeB

Was there any data on that NVMe device? To maintain parity valid any device added to the array will be cleared, hence the "all data will be lost" warning, and since NVMe devices are fast just letting the clear run for a few seconds will make any data recovery attempt very difficult.

A SMART read happens when the GUI detects a disk spins up, something is making them spin up before that.

Post new diags with drives connected.

Then I think your best bet it to use old disk2 and force Unraid to rebuild disk4, parity still won't be 100% in sync, so some fs corruption is possible, you can do that by: -Tools -> New Config -> Retain current configuration: All -> Apply -Check all assignments and assign any missing disk(s) if needed, including old disk2 and new disk4, replacement disk4 should be same size or larger than the old one -IMPORTANT - Check both "parity is already valid" and "maintenance mode" and start the array (note that the GUI will still show that data on parity disk(s) will be overwritten, this is normal as it doesn't account for the checkbox, but it won't be as long as it's checked) -Stop array -Unassign disk4 -Start array (in normal mode now), ideally the emulated disk4 will now mount and contents look correct, if it doesn't you should run a filesystem check on the emulated disk -If the emulated disk mounts and contents look correct stop the array -Re-assign the disk4 and start array to begin. For now keep old disk4 intact in case it's needed.

Yes, disk4 appears to be failing, based on the screenshot above looks like there weren't any writes to the array after you upgraded disk2, can you confirm that?

Those controllers work well with Unraid, try connecting a different disk there, but there could also be some compatibility issue with the board.

Like mentioned above running memtest is a good place to start, Unraid driver is crashing in the syslog.

Delete/replace affected files, then reset the stats and keep monitoring for more errors.

Unraid doesn't support SAS multipath, connect just one cable from the HBA to each enclosure, i.e., only use one module in the enclosure.

There's no SMART for disk4 since it dropped, cancel the rebuild, check/replace cables for disk4 and post new diags.

Macvlan call traces are usually the result of having dockers with a custom IP address, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more info. 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/

Changed Status to Closed Changed Priority to Other

Have you done any changes to ssh behavior, like adding something to the go filed? Or post the diagnostics.

I believe it's not even trying to check the keys, does root have a password?

Start by posting the output of: ssh -v Target_Host

That's normal if disk shares are enabled (Settings -> Global Share Settings).

You can run ane extended SMART test, if it passes check/replace cables. Diags are after that error, they start over after every reboot, so cannot comment.

Enable the syslog server and post that after a crash.

Looks like a power/connection problem.

Start by running memtest, also a good idea to replace that old JMB controller, it's causing ATA errors on both connected devices.

You'll likely have some data corruption on disk3, unless the read errors coincided with empty space. Disk1 looks OK, looks more like a power/connection problem.

Based on the dates those diags look old, if Unraid is not finishing boot start by trying to boot in safe mode, if still the same try with a new trial flash drive, just to see if it boots.

That would be the other way around, macvlan is usually the problem, but looks unrelated to your current issues. Do mean it's not running at 3000MT/s? Diags would show. In any case and because of btrfs detecting data corruption I would start by running memtest.

Please post the diagnostics.

Enable the syslog server and post that after a crash. P.S. next time please post the single diagnostics.zip, not all the files inside it.