JorgeB

This should have been posted on the UD support thread but you just need to click on the name to change it.

Upgrade to v6.9-rc1 when available and see how it goes.

The original problem wouldn't disable disk1, that was something else you did, I'd suggest at least start with disk1 unassigned to make sure the emulated disk1 is mounting and showing the expected data, if yes then re-assign it to rebuild.

No No, but it's worth trying, I would suggest backing up current flash, re-creating it with latest release then restore just the config folder.

Never seen it before, just changing the Unraid IP should never cause this. Do you have any VMs? No idea if it would help but you could try recreating libvirt.img but that would mean re-creating all VMs, though you could backup current image first.

If doing it then also look for the AMD IDE driver "pata_atiixp", since that one can be even more problematic, sometimes disks can't even be used in the array when it's in use.

They won't help, were so many errors expected?

Please post the diagnostics: Tools -> Diagnostics

You can, see here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=480419

With valid parity you should be able to rebuild one disk at a time to make them work outside the enclosure.

Those two SATA ports are set to IDE, and that is known to cause issues with those AMD chipsets, change them to AHCI/SATA, there's usually a separate setting on the BIOS for ports 5/6.

Same.

Initial write speed is high since it's being cached to RAM, then is limited by the device actual write speed, not all SSDs (very few in fact) are capable of sustaining 500MB/s writes, lower capacity models even less likely to do it, announced speeds can usually only be accomplished for low burst writes.

Not impossible but unlikely or I suspect there would be a lot more reports.

If you have issues with the plugin best bet is to post on its support thread:

There's a problem identifying that disk, try replacing/swapping both cables. May 23 15:50:05 server kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 May 23 15:50:05 server kernel: ata10.00: irq_stat 0x40000001 May 23 15:50:05 server kernel: ata10.00: failed command: READ DMA May 23 15:50:05 server kernel: ata10.00: cmd c8/00:20:00:00:00/00:00:00:00:00/e0 tag 10 dma 16384 in May 23 15:50:05 server kernel: res 61/04:20:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error) May 23 15:50:05 server kernel: ata10.00: status: { DRDY DF ERR } May 23 15:50:05 server kernel: ata10.00: error: { ABRT } May 23 15:50:05 server kernel: ata10.00: failed to enable AA (error_mask=0x1) ### [PREVIOUS LINE REPEATED 1 TIMES] ### May 23 15:50:05 server kernel: ata10.00: configured for UDMA/133 (device error ignored) May 23 15:50:05 server kernel: sd 10:0:0:0: [sdg] tag#10 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=0s May 23 15:50:05 server kernel: sd 10:0:0:0: [sdg] tag#10 Sense Key : 0x5 [current] May 23 15:50:05 server kernel: sd 10:0:0:0: [sdg] tag#10 ASC=0x21 ASCQ=0x4 May 23 15:50:05 server kernel: sd 10:0:0:0: [sdg] tag#10 CDB: opcode=0x88 88 00 00 00 00 00 00 00 00 00 00 00 00 20 00 00 May 23 15:50:05 server kernel: blk_update_request: I/O error, dev sdg, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0 May 23 15:50:05 server kernel: ata10: EH complete May 23 15:50:05 server kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 May 23 15:50:05 server kernel: ata10.00: irq_stat 0x40000001 May 23 15:50:05 server kernel: ata10.00: failed command: READ DMA May 23 15:50:05 server kernel: ata10.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 12 dma 4096 in May 23 15:50:05 server kernel: res 61/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error) May 23 15:50:05 server kernel: ata10.00: status: { DRDY DF ERR } May 23 15:50:05 server kernel: ata10.00: error: { ABRT } May 23 15:50:05 server kernel: ata10.00: failed to enable AA (error_mask=0x1) ### [PREVIOUS LINE REPEATED 1 TIMES] ### May 23 15:50:05 server kernel: ata10.00: configured for UDMA/133 (device error ignored) May 23 15:50:05 server kernel: ata10: EH complete May 23 15:50:05 server kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 May 23 15:50:05 server kernel: ata10.00: irq_stat 0x40000001 May 23 15:50:05 server kernel: ata10.00: failed command: READ DMA May 23 15:50:05 server kernel: ata10.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 7 dma 4096 in May 23 15:50:05 server kernel: res 61/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error) May 23 15:50:05 server kernel: ata10.00: status: { DRDY DF ERR } May 23 15:50:05 server kernel: ata10.00: error: { ABRT } May 23 15:50:05 server kernel: ata10.00: failed to enable AA (error_mask=0x1) ### [PREVIOUS LINE REPEATED 1 TIMES] ### May 23 15:50:05 server kernel: ata10.00: configured for UDMA/133 (device error ignored) May 23 15:50:05 server kernel: ata10: EH complete May 23 15:50:05 server kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 May 23 15:50:05 server kernel: ata10.00: irq_stat 0x40000001 May 23 15:50:05 server kernel: ata10.00: failed command: READ DMA May 23 15:50:05 server kernel: ata10.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 28 dma 4096 in May 23 15:50:05 server kernel: res 61/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error) May 23 15:50:05 server kernel: ata10.00: status: { DRDY DF ERR } May 23 15:50:05 server kernel: ata10.00: error: { ABRT } May 23 15:50:05 server kernel: ata10.00: failed to enable AA (error_mask=0x1) ### [PREVIOUS LINE REPEATED 1 TIMES] ### May 23 15:50:05 server kernel: ata10.00: configured for UDMA/133 (device error ignored) May 23 15:50:05 server kernel: ata10: EH complete May 23 15:50:05 server kernel: ata10.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 May 23 15:50:05 server kernel: ata10.00: irq_stat 0x40000001 May 23 15:50:05 server kernel: ata10.00: failed command: READ DMA May 23 15:50:05 server kernel: ata10.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 18 dma 4096 in May 23 15:50:05 server kernel: res 61/04:08:00:00:00/00:00:00:00:00/e0 Emask 0x1 (device error) May 23 15:50:05 server kernel: ata10.00: status: { DRDY DF ERR } May 23 15:50:05 server kernel: ata10.00: error: { ABRT }

Run a long SMART test on the drive and replace it if it fails, next time please post the complete diagnostics instead.

If you currently start the array it will rebuild disk1 from parity, is that what you want?

If it's just Plex failing to start that's likely a problem with its config.

You need to lower the thresholds, they can be lowered on the IMPI plugin for low spinning fans, I had to do the same to some of mine: Note that not all values are valid, some boards might only accept for example multiples of 150, (150. 300, 450 and so on).

That looks dead, likely impossible to recover anything without using a data recovery service, and even with those it might not be possible.

That's done in the board BIOS, check the manual if you can't find it.

See here (or turn on the GUI help).

Docker image is failing a checksum, this means there was data corruption, re-create the docker image but if this keeps happen you might have a hardware issue, like bad RAM.

Errors on multiple disks like that suggests a connection/power or controller problem, check/replace cables first, it it doesn't help try a different controller if available. P.S. Onboard SATA is set to IDE, change it to AHCI for best performance and reliability.