JorgeB

This should no longer happen with recent kernels, but in some circumstances it does, you're not the first.

Not that I know of.

You'll need to re-start the docker service, that should do it, if it doesn't recreate the docker image.

Pool fs is fully allocated, you need to run a balance, see here for more info, king of strange this is happening in a new filesystem, did you fill it up completely before?

Oh, and you need to run a filesystem check on the disk being rebuilt (disk19).

Looks like a connection problem, replace cables on disk1.

I don't recommend using USB for array/pool devices, so don't think it's a high prioruty issue, still not my decision of course, it's up to LT.

That's normal, it just means shares are unprotected if another disk fails.

It doesn't, if parity was valid.

Please post the diagnostics: Tools -> Diagnostics

ATA is the first MB port, some boards call it port0, others port1.

ATA errors can cause timeouts that can make the system unresponsive for several minutes and sometimes appear to have crashed.

Yes, swap cables/bays with another device.

It's an issue, that should be fixed.

Two of the Asmedia 6/10 port controllers you're using are a 2 port controller with SATA port multipliers that have various known issues, don't use those with Unraid. Also, why are you not using the Intel SATA ports, those are rock solid.

Any working add-on NIC will help, one that is supported by Unraid of course.

In this case it's SATA port1, currently connected to cache1.

Start in safe mode and stop all dockers/VMs, run it like that for a couple of days, if no issues start turning on the other services one by one.

Changed Status to Closed Changed Priority to Other

Changed Priority to Other

Depends on what the use cache setting is for that share, if it's cache only it will abort immediately with ENOSPC.

Please don't crosspost, going to lock this one since the other is the more appropriate place for this.

Oct 16 18:14:16 GLaDOS kernel: ata1.00: configured for UDMA/133 Oct 16 18:14:16 GLaDOS kernel: ata1: EH complete Oct 16 18:16:59 GLaDOS kernel: ata1.00: exception Emask 0x10 SAct 0x10000 SErr 0x400100 action 0x6 frozen Oct 16 18:16:59 GLaDOS kernel: ata1.00: irq_stat 0x08000000, interface fatal error Oct 16 18:16:59 GLaDOS kernel: ata1: SError: { UnrecovData Handshk } Oct 16 18:16:59 GLaDOS kernel: ata1.00: failed command: WRITE FPDMA QUEUED Oct 16 18:16:59 GLaDOS kernel: ata1.00: cmd 61/00:80:c0:d4:af/0a:00:12:00:00/40 tag 16 ncq dma 1310720 ou Oct 16 18:16:59 GLaDOS kernel: res 40/00:80:c0:d4:af/00:00:12:00:00/40 Emask 0x10 (ATA bus error) Oct 16 18:16:59 GLaDOS kernel: ata1.00: status: { DRDY } Oct 16 18:16:59 GLaDOS kernel: ata1: hard resetting link Check/replace cables on this drive, if you don't how to find it please post complete diags.

Everything looks fine to me on the Unraid side, so likely a VM issue, moving this to the VM section to see if anyone else can help.

Not much point on using flash parity for HDD array, unless you plan on writing to multiple disks at the same time.