JorgeB

You cannot have a new parity a a new disk at the same time, what was the original array state? If there's no data to recover do a new config

Just rebooting should not cause issues, enable mover mover logging, run the mover, post the diagnostics.

Please use the existing plugin support thread:

It will work with a single DIMM, at least it should.

Stop the array unassign parity start array stop array re-assign parity start array

poll cfg is still showing as a mirror, try this: unassign all pool devices start array stop array assign only the old device start array stop array now assign the new device together with the old one start array If this doesn't work post the output of zpool import

Usually it won't accept any value, try 300, or 150.

If you are using a different flash drive the license needs to be transferred, you can do that yourself or contact support and have them do it.

Looks like it needs this module: https://cateee.net/lkddb/web-lkddb/QEDE.html I've asked LT to add it, hopefully for the next release.

It does appear to happen with some flash drives, I see it with one of mine.

Please post the diagnostics.

Previous syslog shows multiple apps crashing, suggest starting by running memtest.

Please post new diagnostics just to confirm the pool looks good.

Disk is not giving a valid SMART report, if you have already replaced cables it's likely a disk problem: Read SMART Data failed: scsi error badly formed scsi parameters

df is reporting the same, check filesystem on disk1, run it without -n, just in case there's weird filesystem corruption.