JorgeB

You can add cache at any time, it's just a question of then moving the appropriate shares there. Only you can answer that.

Possibly, unfortunately no way of knowing which one, you'd need to test one by one, but if you do a replacement there's a chance of data corruption, if possible I would recommend first trying a new parity disk, if still errors create a new array with the new parity without one of the existing data disks, re-sync parity then run a check, repeat without a different data disk to see if you find the culprit.

Since there are only 4 SATA ports using an M.2 SATA device shouldn't disable those, but if it does that info would (or should) be in the manual.

Those entries are normal.

The it's likely a drive problem.

Assuming it crashed there's nothing on the log, so most likely a hardware issue.

Issues are affecting both SSDs, try using the AMD SATA controller instead of the Asmedia. For some reason the board isn't displaying the model, but if it has IPMI these look like virtual devices.

You should run an extended SMART test on disk2.

Yes, if it supports SATA devices, note that depending on the board it might disable one of the regular SATA ports.

Swap cables with another the drive to confirm.

Diags are after rebooting so not much to see, try this and then post that syslog after it happens again.

There are previous reports of the syslog server not working with latest betas, I think I saw a workaround, but can't find it now.

Changed Status to Closed Changed Priority to Other

You'll need to boot in a different PC and delete the LSI BIOS.

Try this and then post that log.

This is a known issue with older firmwares: mpt3sas_cm0: LSISAS3008: FWVersion(05.00.00.00) Update to latest.

Testdisk should recover the partition easily, if the only thing that was done was deleting it.

Cache device dropped offline: Nov 12 10:30:37 Tower kernel: ata2: hard resetting link Nov 12 10:30:37 Tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Nov 12 10:30:37 Tower kernel: ata2.00: failed to set xfermode (err_mask=0x1) Nov 12 10:30:37 Tower kernel: ata2.00: limiting speed to UDMA/100:PIO3 Nov 12 10:30:42 Tower kernel: ata2: hard resetting link Nov 12 10:30:43 Tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Nov 12 10:30:43 Tower kernel: ata2.00: failed to set xfermode (err_mask=0x1) Nov 12 10:30:43 Tower kernel: ata2.00: disabled With SSDs this is usually a connection problem. If both devices have been dropping it might be difficult to recover, some options here, also make sure to check this.

Yep.

See here.

Use the option that skips errors.

You didn't answer my question but I assume you're using option 1 in the FAQ, i/o errors during copy suggest checksum errors or another hardware issue, try option 2 (btrfs restore).

Cache pool is completely allocated, you need to run a balance, see here, you'll also need to recreate the docker image once it's fixed. P.S. you should update to latest beta and the docker image is very large, probably something configured.

Tools -> Registration

Depends where the appdata folder is, if it's in the system share or any other share set to NOCOW, yes it might be corrupt, no way to know.