JorgeB

On the other hand I had a user script schedulled to run at 1AM running twice, second time causing an error, just rescheduled it and made sure I have nothing else scheduled between midnight and 1AM.

That's not the permanent syslog, it's the one after rebooting.

Changed Status to Closed Changed Priority to Other

Sorry, I see you were asked to create a new thread, but you forgot to post the diagnostics.

Using a file recovery util, e.g. UFS Explorer

Not familiar with those.

Please use the existing plugin support thread:

Nope.

IIRC it will first write to the largest disk and when there's the same space available on both it will alternated from one to the other, in 1GiB chunks, so any file larger than that will use both.

Best bet is to post in the support thread of the docker you're using:

Yes, they will work like SAS2 drives. Took a quick look and they don't support dual link, there's an out for daisy chain or you can use the second module for redundancy (not supported by Unraid), so for best performance you want to connect each MD1200 to a SAS wide port on the HBA, so get a second HBA or one with 4 ports, bottleneck then will be the PCIe 2.0 slot of the H800, if the board/CPU supports PCIe 3.0 it would be faster with one or two PCIe 3.0 HBAs.

Yes.

There's nothing in those logs, in the first one you posted there's something but nothing relevant before the crashes, that usually suggests a hardware problem, unfortunately it's difficult to diagnose without starting to swap some parts, and if possible try with Intel parts, much better for Linux/Unraid.

Looks more like a board/PCIe problem: Oct 29 00:47:47 DarkTower kernel: pcieport 0000:00:02.2: AER: Uncorrected (Fatal) error received: 0000:00:02.2 Oct 29 00:47:47 DarkTower kernel: pcieport 0000:00:02.2: PCIe Bus Error: severity=Uncorrected (Fatal), type=Transaction Layer, (Receiver ID) Oct 29 00:47:47 DarkTower kernel: pcieport 0000:00:02.2: device [8086:2f06] error status/mask=00000020/00000000 Oct 29 00:47:47 DarkTower kernel: pcieport 0000:00:02.2: [ 5] SDES (First) Oct 29 00:47:47 DarkTower kernel: mpt3sas_cm0: PCI error: detected callback, state(2)!! Oct 29 00:47:48 DarkTower kernel: pcieport 0000:00:02.2: AER: Root Port link has been reset Oct 29 00:47:48 DarkTower kernel: mpt3sas_cm0: PCI error: resume callback!! Oct 29 00:47:48 DarkTower kernel: pcieport 0000:00:02.2: AER: device recovery successful Try using a different PCIe slot if available.

You can easily do it using Unraid, for the GUI issue, yes, probably best to start a thread in the general support forum so it gets more visibility, it's a strange one.

Probably not many people using or familiar with that hardware, you want a SAS3 HBA, and if the MD1200 supports dual link use two cables to connect it to the HBA.

A couple thing you can try: -Update LSI firmware to latests -Connect the disks directly to the LSI, bypassing the Netapp, you can only connect up to 8 but just for testing purposes. If none of that helps you can enable the syslog server and post that log after a crash to see if there are more clues on the problem.

No, that's the standard syslog, it starts over after every reboot. Then probably it wasn't correctly configured, set the syslog server to mirror to the flash drive then post that after the next crash.

Grab it from where you save it to and attach here.

Persistent syslog doesn't come with the diags, you should upload that also.

All seems normal with the HBA, unrelated to current issue but you should update firmware to latest, but have no idea why the GUI isn't working.

Try excluding disk1 from the share you're copying to and see if there's any difference, disk1 is SMR and with some workloads it can slow down things by a lot.

Post new diags after array start.

Just this part, you don't need to re-assign them.

Looks more like a power/connection problem, replace swap cables and try syncing parity again.