JorgeB

Please post the diagnostics: Tools -> Diagnostics

Diags are after rebooting so not much to see, if you need more help in the future remember we need them before rebooting.

Since data disk order doesn't matter with single parity these will assume the missing disk is disk3, you need to be on Unraid 6.2.4 or newer. -Tools -> New Config -> Apply -Assign parity plus the other 2 existing data disks, assign the new disk as disk3, double check all assignments. -Important - After checking the assignments leave the browser on that page, the "Main" page. -Open an SSH session/use the console and type (don't copy/paste directly from the forum, as sometimes it can insert extra characters): mdcmd set invalidslot 3 29 -Back on the GUI and without refreshing the page, just start the array, do not check the "parity is already valid" box (GUI will still show that data on parity disk(s) will be overwritten, this is normal as it doesn't account for the invalid slot command, but they won't be as long as the procedure was correctly done), disk3 will start rebuilding, disk should mount immediately but if it's unmountable don't format, wait for the rebuild to finish and then run a filesystem check

Yes, you can also get it from Broadcom's support site, under legacy, search for 9211-8i

Type this on the console: btrfs device delete missing /mnt/cache When the cache activity stops please post new diags.

There could be but since this is an unsupported configuration it might be tricky, and since there are only 85GB of data on disk1 much easier to just re-format it.

Disk are: Formatted with type 2 protection See her: https://forums.unraid.net/topic/93432-parity-disk-read-errors/?do=findComment&comment=864078

Thanks for the update. Most likely.

Good it worked, but since you mentioned before Did the jumper allow you to flash it with LSI IT firmware or the previous flash just wasn't working?

EL2 are dual expander models, but that's for redundancy, not faster i/o, you can still use dual link with the EL1 models to double the available bandwidth.

Thanks for reporting back, if you don't mind I'm going to tag this solved.

Look in the syslog for error like these: Jun 7 14:24:30 Tower kernel: ata3.00: exception Emask 0x10 SAct 0x0 SErr 0x4090000 action 0xe frozen Jun 7 14:24:30 Tower kernel: ata3.00: irq_stat 0x00400040, connection status changed Jun 7 14:24:30 Tower kernel: ata3: SError: { PHYRdyChg 10B8B DevExch } Jun 7 14:24:30 Tower kernel: ata3.00: failed command: FLUSH CACHE EXT Jun 7 14:24:30 Tower kernel: ata3.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 7 Jun 7 14:24:30 Tower kernel: res 40/00:34:20:86:36/00:00:00:00:00/40 Emask 0x10 (ATA bus error) Jun 7 14:24:30 Tower kernel: ata3.00: status: { DRDY } Jun 7 14:24:30 Tower kernel: ata3: hard resetting link Jun 7 14:24:35 Tower kernel: ata3: link is slow to respond, please be patient (ready=0) Jun 7 14:24:37 Tower kernel: ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jun 7 14:24:37 Tower kernel: ata3.00: failed to IDENTIFY (I/O error, err_mask=0x100) Jun 7 14:24:37 Tower kernel: ata3.00: revalidation failed (errno=-5) Jun 7 14:24:42 Tower kernel: ata3: hard resetting link Jun 7 14:24:44 Tower kernel: ata3: SATA link down (SStatus 0 SControl 300) Jun 7 14:24:44 Tower kernel: ata3.00: link offline, clearing class 1 to NONE Jun 7 14:24:44 Tower kernel: ata3: hard resetting link Jun 7 14:24:44 Tower kernel: ata3: SATA link down (SStatus 0 SControl 300) Jun 7 14:24:44 Tower kernel: ata3.00: link offline, clearing class 1 to NONE Jun 7 14:24:44 Tower kernel: ata3.00: disabled Previous lines show the connection issues, last line is the device dropping offline "ata3.00: disabled"

I'm sorry, but you are worried about 3TB of extra writes per year? My cache drive is currently writing around 2TB per day and don't really worry about it, but I do understand users worried about that, not about 3TB per year.

No, I would start by updating the LSI firmware, it's on a very old one, current one is 20.00.07.00, if errors persist check all connections, both SATA and power.

I didn't realize you were talking about the array devices, I don't know how you accomplished that but currently there's no disk2, disk1 is disk1+disk2 in raid1, possibly those devices were used on the cache pool before and not properly wiped, since there's not much data easier to wipe them and start over.

Than all I can say is that it doesn't appear to be a disk problem, start by checking all connections and then try rebuilding the disable disk, if more errors post new diags.

Did you save the diags before rebooting? If yes please post those instead.

Basically it won't make any noticeable difference.

Please don't double post, your original post was moved to the more appropriate storage section:

Thanks for reporting back, and if you don't mind going to tag this as solved.

Best bet is to use the existing docker support thread:

Sorry, no, but you can ask on the Crashplan support thread.

Like itimpi mentioned syslog before rebooting might provide more clues, still there are a few visible issues: Jun 13 09:06:45 Tower kernel: usb 1-9: reset high-speed USB device number 2 using xhci_hcd Jun 13 09:06:45 Tower kernel: sd 0:0:0:0: [sda] 30253056 512-byte logical blocks: (15.5 GB/14.4 GiB) Flash is dropping, use a USB 2.0 port instead (if available). You are overclocking the RAM for the CPU used, it's a known issue with Ryzen see here: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=819173

Controller is detected Jun 13 09:30:21 Tower kernel: megasas: 07.706.03.00-rc1 Jun 13 09:30:21 Tower kernel: megaraid_sas 0000:2b:00.0: FW now in Ready state Jun 13 09:30:21 Tower kernel: megaraid_sas 0000:2b:00.0: 32 bit DMA mask and 32 bit consistent mask Jun 13 09:30:21 Tower kernel: megaraid_sas 0000:2b:00.0: firmware supports msix : (96) Jun 13 09:30:21 Tower kernel: megaraid_sas 0000:2b:00.0: current msix/online cpus : (12/12) Jun 13 09:30:21 Tower kernel: megaraid_sas 0000:2b:00.0: RDPQ mode : (disabled) Jun 13 09:30:21 Tower kernel: megaraid_sas 0000:2b:00.0: Current firmware supports maximum commands: 272 LDIO threshold: 237 Jun 13 09:30:21 Tower kernel: megaraid_sas 0000:2b:00.0: Configured max firmware commands: 271 Jun 13 09:30:21 Tower kernel: megaraid_sas 0000:2b:00.0: FW supports sync cache : Yes but it's failing to initialize: Jun 13 09:30:21 Tower kernel: megaraid_sas 0000:2b:00.0: Init cmd return status FAILED for SCSI host 3 Jun 13 09:30:21 Tower kernel: megaraid_sas 0000:2b:00.0: Failed from megasas_init_fw 5637 Best bet would be to get a different one, 9300-8i is a good option, and IT mode only.

Post the complete zip file.