3560freak

Just wanted to thank you again for all of the help. Running smoothly with new parity drives and old parity drives formatted for data storage.

Thank you. Additional (possibly dumb) question. Can I simply keep disk4 where it is (with all data intact) and replace disk3 (the 4TB drive with no data on it) with the old parity 10TB drive (formatted) and add the second old parity 10TB drive (formatted) as Disk5? I have fixed the drive layout that I displayed above to accurately reflect the drive assignments. Current drive layout Parity 1 (10TB) Parity 2 (10TB) Data Drive 1 (10TB) Data Drive 2 (10TB) Data Drive 3 (4TB) Data Drive 4 (10TB) Desired drive layout Parity 1 (14TB) Parity 2 (14TB) Data Drive 1 (10TB) Data Drive 2 (10TB) Data Drive 3 (10TB) * old parity 1 Data Drive 4 (10TB) Data Drive 5 (10TB) * old parity 2

You are correct. I meant disk 3 and not 4. I had it labeled as 3 (on the physical drive) from another build that I had pulled it from. Any different procedure to follow after view the diagnostics? Thank you again for your time.

Updated diagnostics as requested. Thank you diagnostics-20230205-1415.zip

I appreciate the second look. Here are my diagnostics

I have read over the wiki process but am still not 100% confident. Would someone mind confirming that I am taking the correct steps? Current drive layout Parity 1 (10TB) Parity 2 (10TB) Data Drive 1 (10TB) Data Drive 2 (10TB) Data Drive 3 (10TB) Data Drive 4 (4TB) Desired drive layout Parity 1 (14TB) Parity 2 (14TB) Data Drive 1 (10TB) Data Drive 2 (10TB) Data Drive 3 (10TB) Data Drive 4 (10TB) * old parity 1 Data Drive 5 (10TB) * old parity 2 My understanding is that I should remove current Parity 1 drive (10TB) from it's assignment and then assign one of the new 14TB drives. This will rebuild parity for the array. After that is completed, I then remove current Parity 2 drive (10TB) from it's assignment and then assign the other new 14TB drive. Allow this parity to rebuild and then I can assign both old parity drive to data slot 4 and 5 respectively. There is currently no data on the Data Drive 4 (4TB) so a copy wouldn't be necessary. Does this seem like the correct process or can I do more steps at the same time to reduce the overall time to complete the process? Thank you for any assistance holding my hand through this.

I am the reason that they say measure twice, cut once (SMH). I ordered the M.2 to SATA adapter only to realize that my MB has a half length M.2 slot (2242). The case/drives block my from using this longer/standard card. I will need to go with the M.2 to PCIe riser solution. I am going to make the assumption that I can trim down the PCB since the cabling/components are all in the base of the card (hopefully this is accurate, see image). Thanks again for all of your help, JorgeB.

Thanks for the reply. My only other question was to confirm that the ASM1166 chipset is desired over the JMicron JMB585, due to compatibility with UnRAID, correct? My inclination is to go with a Silverstone ECS07, because they seem like the most reliable company selling these M.2 adapters, but if the chipset that they use does not play well with UnRAID then that is a moot point.

I am not in the market to change boards/case/CPU etc right now so I have been looking at these m.2 to SATA expansion cards (specifically ones using the ASM1166 chipset) to add storage to my array. I am currently on mITX (so only one PCIe slot) and cannot afford to give up my NVIDIA card to cover PLEX transcoding (my ASUS P11C-I with it's C242 chipset doesn't allow for iGPU passthrough). Question 1: Can anyone tell me if there is any downside to having my two parity drives (currently run dual parity) on the expansion card vs the motherboard's onboard controller? Question 2: Seeing reports about flimsy PCBs on these expanders, potentially being the point of failure. Would it make more sense to get an m.2 to PCIe riser card and use my existing ECS06? Cost is small enough with either option, just wanted the one that is the most reliable of the two. Thanks for any suggestions/tips.

I appreciate the tip. I'll contact ASUS to see if there are any workarounds.

I might possibly be in a similar situation. My MOBO is an ASUS P11C-I with an i3-8100 and the newest BIOS. I don't see anywhere in the BIOS settings where I can enable iGPU, and there is mention in the manual about using a jumper to enable/disable the onboard VGA controller (ASUS manual pg 2-23). Is my only option at this point to get a NVIDIA GPU to support HW transcoding? Thanks for any support that you can provide.

Finally fixed this with a new Microserver backplane. Thanks to all who helped get me going again.

Here is an updated diagnostic (failed right before it completed the entire 4TB rebuild). This should have the SMART data. Same error? tower2-diagnostics-20190606-2203.zip

So I have decided to go the i3-8100 route for now, but I wish to buy a Xeon compatible board and ECC ram so that I can just drop in the Xeon 2146G at a later time. My final question before purchasing is about the RAM. What do you think about this setup? i3-8100 ASUS P11C-I (so I have the option to upgrade to Xeon later) 16GB ECC (8gb x 2 - would this RAM work well with the CPU/MB? ) https://www.newegg.com/crucial-8gb-288-pin-ddr4-sdram/p/1B4-00M3-00040?Item=1B4-00M3-00040 This RAM is rated at 2666Mhz, although the i3-8100 only supports 2400Mhz. I wanted to get this so that when I go to the Xeon later I don't have to buy new RAM. Full disclosure: I posted this on another hardware forum but haven't received any feedback.

PreClear completed successfully (2 full passes) and as I started to bring the array back online my server froze up (completely). After rebooting I am now getting errors on DISK1 again (this is the brand new disk that passed), so at this point it has to be either the cabling or the controller. Without me re-buying everything here, is there any way to check this? I have attached the updated diagnostics. Thank you tower2-diagnostics-20190604-1906.zip

My server has been out of commission for almost 2 months now due to this issue, but I have finally ordered/received a replacement drive (I will RMA the questionable one later for a backup). However, should I just let UnRAID rebuild the image on this new disk, or should I attach the old disk via USB and try and copy data from it to the new drive? I assume there is the potential issue of data not copying correctly due to the disk in question failing, but wasn't sure if this was better than letting UnRAID rebuild. Thanks for the info.

So it seems that the E-2146G has not had a widespread release and, according to a leak, Intel is going to release a refresh (as the Xeon 22xx) of the series later this year. Since I am not planning on waiting for Intel to announce these new chips, any thoughts on the i3-9100 vs i3-8100 or i3-8300?

The longer I wait to purchase the more options that begin to pop-up. Any thoughts on an i3-8100 vs Xeon E-2146G? Obvously the 8100 would save me money that could be applied elsewhere, but is it really adequate for my use case?

To follow up on this, I am now looking at the ASUS P10S-I paired with a Xeon E3-1275 v6. Any thoughts on these components for my use case?

Looking for some recommendations on a new build (primarily media server). Currently have an HP MicroServer gen 8 with a low power Xeon 1265L v2 and 16 GB of ECC ram. I am still in need of a small form case (due to space constraints), so will likely be going with the Fractal Node 304, which limits me to Mini-ITX. Transcoding (Plex): I am typically direct playing a good amount of my media (locally) and transcoding 2-3 streams max remotely (1080p files being transcoded to 720p for bandwidth reasons - some x265 and some x264) and am looking at Xeon again. Best options for price/performance. Obviously a Xeon with QuickSync would benefit the transcoding, so within that constraint. Power: Not overly concerned with power usage, but I do leave the server running 24/7, and would hopefully not see double or more increase in power consumption/cost, so a 2x Xeon CPU build would not be my ideal option. I already have a handful of 10GB (shucked) drives and a few 500GB SSDs for cache, but would like to keep the total cost for CPU/MB under $550 if possible. Any suggestions would be appreciated.

Is there a good/proper way to test the drive outside of the server? I moved the drive to another spot on the backplane and still have the issue, so I am trying to completely rule out the backplane.

Update: Ended up moving DISK1 to another spot in the backplane and still having issues, so now I am sure that it is the drive. Cannot run extended SMART test now b/c the drive is disabled/offline, but I did get this from the disk log information tab. Does this mean anything in regards to the drive health, or are they just communication message errors from Unraid? Apr 24 20:37:58 Tower2 kernel: ata2: SATA max UDMA/133 abar m2048@0xfacd0000 port 0xfacd0180 irq 33 Apr 24 20:37:58 Tower2 kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Apr 24 20:37:58 Tower2 kernel: ata2.00: ATA-10: WDC WD40EFRX-68N32N0, WD-WCC7K7EPCH2V, 82.00A82, max UDMA/133 Apr 24 20:37:58 Tower2 kernel: ata2.00: 7814037168 sectors, multi 16: LBA48 NCQ (depth 32), AA Apr 24 20:37:58 Tower2 kernel: ata2.00: configured for UDMA/133 Apr 24 20:37:58 Tower2 kernel: sd 2:0:0:0: [sdc] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB) Apr 24 20:37:58 Tower2 kernel: sd 2:0:0:0: [sdc] 4096-byte physical blocks Apr 24 20:37:58 Tower2 kernel: sd 2:0:0:0: [sdc] Write Protect is off Apr 24 20:37:58 Tower2 kernel: sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00 Apr 24 20:37:58 Tower2 kernel: sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Apr 24 20:37:58 Tower2 kernel: sdc: sdc1 Apr 24 20:37:58 Tower2 kernel: sd 2:0:0:0: [sdc] Attached SCSI disk Apr 24 20:38:25 Tower2 emhttpd: WDC_WD40EFRX-68N32N0_WD-WCC7K7EPCH2V (sdc) 512 7814037168 Apr 24 20:38:25 Tower2 kernel: mdcmd (2): import 1 sdc 64 3907018532 0 WDC_WD40EFRX-68N32N0_WD-WCC7K7EPCH2V Apr 24 20:38:25 Tower2 kernel: md: import disk1: (sdc) WDC_WD40EFRX-68N32N0_WD-WCC7K7EPCH2V size: 3907018532 Apr 24 20:38:26 Tower2 emhttpd: shcmd (27): /usr/local/sbin/set_ncq sdc 1 Apr 24 20:38:26 Tower2 root: set_ncq: setting sdc queue_depth to 1 Apr 24 20:38:26 Tower2 emhttpd: shcmd (28): echo 128 > /sys/block/sdc/queue/nr_requests Apr 24 20:59:03 Tower2 emhttpd: WDC_WD40EFRX-68N32N0_WD-WCC7K7EPCH2V (sdc) 512 7814037168 Apr 24 21:00:07 Tower2 emhttpd: WDC_WD40EFRX-68N32N0_WD-WCC7K7EPCH2V (sdc) 512 7814037168 Apr 24 21:00:07 Tower2 kernel: mdcmd (2): import 1 sdc 64 3907018532 0 WDC_WD40EFRX-68N32N0_WD-WCC7K7EPCH2V Apr 24 21:00:07 Tower2 kernel: md: import disk1: (sdc) WDC_WD40EFRX-68N32N0_WD-WCC7K7EPCH2V size: 3907018532 Apr 24 21:00:14 Tower2 emhttpd: shcmd (1436): /usr/local/sbin/set_ncq sdc 1 Apr 24 21:00:14 Tower2 emhttpd: shcmd (1437): echo 128 > /sys/block/sdc/queue/nr_requests Apr 24 21:00:52 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Apr 24 21:00:52 Tower2 kernel: ata2.00: irq_stat 0x40000001 Apr 24 21:00:52 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT Apr 24 21:00:52 Tower2 kernel: ata2.00: cmd 35/00:40:40:8d:03/00:05:00:00:00/e0 tag 1 dma 688128 out Apr 24 21:00:52 Tower2 kernel: ata2.00: status: { DRDY DF ERR } Apr 24 21:00:52 Tower2 kernel: ata2.00: error: { ABRT } Apr 24 21:00:52 Tower2 kernel: ata2.00: failed to read native max address (err_mask=0x1) Apr 24 21:00:52 Tower2 kernel: ata2.00: HPA support seems broken, skipping HPA handling Apr 24 21:00:52 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:52 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:52 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored) Apr 24 21:00:52 Tower2 kernel: ata2: EH complete Apr 24 21:00:52 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Apr 24 21:00:52 Tower2 kernel: ata2.00: irq_stat 0x40000001 Apr 24 21:00:52 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT Apr 24 21:00:52 Tower2 kernel: ata2.00: cmd 35/00:40:40:8d:03/00:05:00:00:00/e0 tag 2 dma 688128 out Apr 24 21:00:52 Tower2 kernel: ata2.00: status: { DRDY DF ERR } Apr 24 21:00:52 Tower2 kernel: ata2.00: error: { ABRT } Apr 24 21:00:52 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:52 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:52 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored) Apr 24 21:00:52 Tower2 kernel: ata2: EH complete Apr 24 21:00:52 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Apr 24 21:00:52 Tower2 kernel: ata2.00: irq_stat 0x40000001 Apr 24 21:00:52 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT Apr 24 21:00:52 Tower2 kernel: ata2.00: cmd 35/00:40:40:8d:03/00:05:00:00:00/e0 tag 3 dma 688128 out Apr 24 21:00:52 Tower2 kernel: ata2.00: status: { DRDY DF ERR } Apr 24 21:00:52 Tower2 kernel: ata2.00: error: { ABRT } Apr 24 21:00:52 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:52 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:52 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored) Apr 24 21:00:52 Tower2 kernel: ata2: EH complete Apr 24 21:00:52 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Apr 24 21:00:52 Tower2 kernel: ata2.00: irq_stat 0x40000001 Apr 24 21:00:52 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT Apr 24 21:00:52 Tower2 kernel: ata2.00: cmd 35/00:40:40:8d:03/00:05:00:00:00/e0 tag 4 dma 688128 out Apr 24 21:00:52 Tower2 kernel: ata2.00: status: { DRDY DF ERR } Apr 24 21:00:52 Tower2 kernel: ata2.00: error: { ABRT } Apr 24 21:00:52 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:52 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:52 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored) Apr 24 21:00:52 Tower2 kernel: ata2: EH complete Apr 24 21:00:53 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Apr 24 21:00:53 Tower2 kernel: ata2.00: irq_stat 0x40000001 Apr 24 21:00:53 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT Apr 24 21:00:53 Tower2 kernel: ata2.00: cmd 35/00:40:40:8d:03/00:05:00:00:00/e0 tag 5 dma 688128 out Apr 24 21:00:53 Tower2 kernel: ata2.00: status: { DRDY DF ERR } Apr 24 21:00:53 Tower2 kernel: ata2.00: error: { ABRT } Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:53 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored) Apr 24 21:00:53 Tower2 kernel: ata2: EH complete Apr 24 21:00:53 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Apr 24 21:00:53 Tower2 kernel: ata2.00: irq_stat 0x40000001 Apr 24 21:00:53 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT Apr 24 21:00:53 Tower2 kernel: ata2.00: cmd 35/00:40:40:8d:03/00:05:00:00:00/e0 tag 6 dma 688128 out Apr 24 21:00:53 Tower2 kernel: ata2.00: status: { DRDY DF ERR } Apr 24 21:00:53 Tower2 kernel: ata2.00: error: { ABRT } Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:53 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored) Apr 24 21:00:53 Tower2 kernel: sd 2:0:0:0: [sdc] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Apr 24 21:00:53 Tower2 kernel: sd 2:0:0:0: [sdc] tag#6 Sense Key : 0x5 [current] Apr 24 21:00:53 Tower2 kernel: sd 2:0:0:0: [sdc] tag#6 ASC=0x21 ASCQ=0x4 Apr 24 21:00:53 Tower2 kernel: sd 2:0:0:0: [sdc] tag#6 CDB: opcode=0x8a 8a 00 00 00 00 00 00 03 8d 40 00 00 05 40 00 00 Apr 24 21:00:53 Tower2 kernel: print_req_error: I/O error, dev sdc, sector 232768 Apr 24 21:00:53 Tower2 kernel: ata2: EH complete Apr 24 21:00:53 Tower2 kernel: ata2: limiting SATA link speed to 3.0 Gbps Apr 24 21:00:53 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 Apr 24 21:00:53 Tower2 kernel: ata2.00: irq_stat 0x40000001 Apr 24 21:00:53 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT Apr 24 21:00:53 Tower2 kernel: ata2.00: cmd 35/00:08:f8:50:0f/00:00:e9:00:00/e0 tag 9 dma 4096 out Apr 24 21:00:53 Tower2 kernel: ata2.00: status: { DRDY DF ERR } Apr 24 21:00:53 Tower2 kernel: ata2.00: error: { ABRT } Apr 24 21:00:53 Tower2 kernel: ata2: hard resetting link Apr 24 21:00:53 Tower2 kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:53 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored) Apr 24 21:00:53 Tower2 kernel: ata2: EH complete Apr 24 21:00:53 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Apr 24 21:00:53 Tower2 kernel: ata2.00: irq_stat 0x40000001 Apr 24 21:00:53 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT Apr 24 21:00:53 Tower2 kernel: ata2.00: cmd 35/00:08:f8:50:0f/00:00:e9:00:00/e0 tag 10 dma 4096 out Apr 24 21:00:53 Tower2 kernel: ata2.00: status: { DRDY DF ERR } Apr 24 21:00:53 Tower2 kernel: ata2.00: error: { ABRT } Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:53 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored) Apr 24 21:00:53 Tower2 kernel: ata2: EH complete Apr 24 21:00:53 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Apr 24 21:00:53 Tower2 kernel: ata2.00: irq_stat 0x40000001 Apr 24 21:00:53 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT Apr 24 21:00:53 Tower2 kernel: ata2.00: cmd 35/00:08:f8:50:0f/00:00:e9:00:00/e0 tag 11 dma 4096 out Apr 24 21:00:53 Tower2 kernel: ata2.00: status: { DRDY DF ERR } Apr 24 21:00:53 Tower2 kernel: ata2.00: error: { ABRT } Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:53 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored) Apr 24 21:00:53 Tower2 kernel: ata2: EH complete Apr 24 21:00:53 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Apr 24 21:00:53 Tower2 kernel: ata2.00: irq_stat 0x40000001 Apr 24 21:00:53 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT Apr 24 21:00:53 Tower2 kernel: ata2.00: cmd 35/00:08:f8:50:0f/00:00:e9:00:00/e0 tag 12 dma 4096 out Apr 24 21:00:53 Tower2 kernel: ata2.00: status: { DRDY DF ERR } Apr 24 21:00:53 Tower2 kernel: ata2.00: error: { ABRT } Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:53 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored) Apr 24 21:00:53 Tower2 kernel: ata2: EH complete Apr 24 21:00:53 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Apr 24 21:00:53 Tower2 kernel: ata2.00: irq_stat 0x40000001 Apr 24 21:00:53 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT Apr 24 21:00:53 Tower2 kernel: ata2.00: cmd 35/00:08:f8:50:0f/00:00:e9:00:00/e0 tag 13 dma 4096 out Apr 24 21:00:53 Tower2 kernel: ata2.00: status: { DRDY DF ERR } Apr 24 21:00:53 Tower2 kernel: ata2.00: error: { ABRT } Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:53 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored) Apr 24 21:00:53 Tower2 kernel: ata2: EH complete Apr 24 21:00:53 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Apr 24 21:00:53 Tower2 kernel: ata2.00: irq_stat 0x40000001 Apr 24 21:00:53 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT Apr 24 21:00:53 Tower2 kernel: ata2.00: cmd 35/00:08:f8:50:0f/00:00:e9:00:00/e0 tag 14 dma 4096 out Apr 24 21:00:53 Tower2 kernel: ata2.00: status: { DRDY DF ERR } Apr 24 21:00:53 Tower2 kernel: ata2.00: error: { ABRT } Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:53 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored) Apr 24 21:00:53 Tower2 kernel: sd 2:0:0:0: [sdc] tag#14 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Apr 24 21:00:53 Tower2 kernel: sd 2:0:0:0: [sdc] tag#14 Sense Key : 0x5 [current] Apr 24 21:00:53 Tower2 kernel: sd 2:0:0:0: [sdc] tag#14 ASC=0x21 ASCQ=0x4 Apr 24 21:00:53 Tower2 kernel: sd 2:0:0:0: [sdc] tag#14 CDB: opcode=0x8a 8a 00 00 00 00 00 e9 0f 50 f8 00 00 00 08 00 00 Apr 24 21:00:53 Tower2 kernel: print_req_error: I/O error, dev sdc, sector 3910095096 Apr 24 21:00:53 Tower2 kernel: print_req_error: I/O error, dev sdc, sector 3910095096 Apr 24 21:00:53 Tower2 kernel: ata2: EH complete Apr 24 21:00:53 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Apr 24 21:00:53 Tower2 kernel: ata2.00: irq_stat 0x40000001 Apr 24 21:00:53 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT Apr 24 21:00:53 Tower2 kernel: ata2.00: cmd 35/00:40:80:92:03/00:05:00:00:00/e0 tag 17 dma 688128 out Apr 24 21:00:53 Tower2 kernel: ata2.00: status: { DRDY DF ERR } Apr 24 21:00:53 Tower2 kernel: ata2.00: error: { ABRT } Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:53 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:53 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored) Apr 24 21:00:53 Tower2 kernel: ata2: EH complete Apr 24 21:00:53 Tower2 kernel: ata2: limiting SATA link speed to 1.5 Gbps Apr 24 21:00:53 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 Apr 24 21:00:53 Tower2 kernel: ata2.00: irq_stat 0x40000001 Apr 24 21:00:53 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT Apr 24 21:00:53 Tower2 kernel: ata2.00: cmd 35/00:40:80:92:03/00:05:00:00:00/e0 tag 18 dma 688128 out Apr 24 21:00:53 Tower2 kernel: ata2.00: status: { DRDY DF ERR } Apr 24 21:00:53 Tower2 kernel: ata2.00: error: { ABRT } Apr 24 21:00:53 Tower2 kernel: ata2: hard resetting link Apr 24 21:00:54 Tower2 kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Apr 24 21:00:54 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:54 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:54 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored) Apr 24 21:00:54 Tower2 kernel: ata2: EH complete Apr 24 21:00:54 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Apr 24 21:00:54 Tower2 kernel: ata2.00: irq_stat 0x40000001 Apr 24 21:00:54 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT Apr 24 21:00:54 Tower2 kernel: ata2.00: cmd 35/00:40:80:92:03/00:05:00:00:00/e0 tag 19 dma 688128 out Apr 24 21:00:54 Tower2 kernel: ata2.00: status: { DRDY DF ERR } Apr 24 21:00:54 Tower2 kernel: ata2.00: error: { ABRT } Apr 24 21:00:54 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:54 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:54 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored) Apr 24 21:00:54 Tower2 kernel: ata2: EH complete Apr 24 21:00:54 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Apr 24 21:00:54 Tower2 kernel: ata2.00: irq_stat 0x40000001 Apr 24 21:00:54 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT Apr 24 21:00:54 Tower2 kernel: ata2.00: cmd 35/00:40:80:92:03/00:05:00:00:00/e0 tag 20 dma 688128 out Apr 24 21:00:54 Tower2 kernel: ata2.00: status: { DRDY DF ERR } Apr 24 21:00:54 Tower2 kernel: ata2.00: error: { ABRT } Apr 24 21:00:54 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:54 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:54 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored) Apr 24 21:00:54 Tower2 kernel: ata2: EH complete Apr 24 21:00:54 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Apr 24 21:00:54 Tower2 kernel: ata2.00: irq_stat 0x40000001 Apr 24 21:00:54 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT Apr 24 21:00:54 Tower2 kernel: ata2.00: cmd 35/00:40:80:92:03/00:05:00:00:00/e0 tag 21 dma 688128 out Apr 24 21:00:54 Tower2 kernel: ata2.00: status: { DRDY DF ERR } Apr 24 21:00:54 Tower2 kernel: ata2.00: error: { ABRT } Apr 24 21:00:54 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:54 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:54 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored) Apr 24 21:00:54 Tower2 kernel: ata2: EH complete Apr 24 21:00:54 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Apr 24 21:00:54 Tower2 kernel: ata2.00: irq_stat 0x40000001 Apr 24 21:00:54 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT Apr 24 21:00:54 Tower2 kernel: ata2.00: cmd 35/00:40:80:92:03/00:05:00:00:00/e0 tag 22 dma 688128 out Apr 24 21:00:54 Tower2 kernel: ata2.00: status: { DRDY DF ERR } Apr 24 21:00:54 Tower2 kernel: ata2.00: error: { ABRT } Apr 24 21:00:54 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:54 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:54 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored) Apr 24 21:00:54 Tower2 kernel: sd 2:0:0:0: [sdc] tag#22 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Apr 24 21:00:54 Tower2 kernel: sd 2:0:0:0: [sdc] tag#22 Sense Key : 0x5 [current] Apr 24 21:00:54 Tower2 kernel: sd 2:0:0:0: [sdc] tag#22 ASC=0x21 ASCQ=0x4 Apr 24 21:00:54 Tower2 kernel: sd 2:0:0:0: [sdc] tag#22 CDB: opcode=0x8a 8a 00 00 00 00 00 00 03 92 80 00 00 05 40 00 00 Apr 24 21:00:54 Tower2 kernel: print_req_error: I/O error, dev sdc, sector 234112 Apr 24 21:00:54 Tower2 kernel: ata2: EH complete Apr 24 21:00:54 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Apr 24 21:00:54 Tower2 kernel: ata2.00: irq_stat 0x40000001 Apr 24 21:00:54 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT Apr 24 21:00:54 Tower2 kernel: ata2.00: cmd 35/00:80:c0:97:03/00:01:00:00:00/e0 tag 25 dma 196608 out Apr 24 21:00:54 Tower2 kernel: ata2.00: status: { DRDY DF ERR } Apr 24 21:00:54 Tower2 kernel: ata2.00: error: { ABRT } Apr 24 21:00:54 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:54 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:54 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored) Apr 24 21:00:54 Tower2 kernel: ata2: EH complete Apr 24 21:00:54 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Apr 24 21:00:54 Tower2 kernel: ata2.00: irq_stat 0x40000001 Apr 24 21:00:54 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT Apr 24 21:00:54 Tower2 kernel: ata2.00: cmd 35/00:80:c0:97:03/00:01:00:00:00/e0 tag 26 dma 196608 out Apr 24 21:00:54 Tower2 kernel: ata2.00: status: { DRDY DF ERR } Apr 24 21:00:54 Tower2 kernel: ata2.00: error: { ABRT } Apr 24 21:00:54 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:54 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:54 Tower2 kernel: ata2.00: configured for UDMA/133 (device error ignored) Apr 24 21:00:54 Tower2 kernel: ata2: EH complete Apr 24 21:00:54 Tower2 kernel: ata2.00: limiting speed to UDMA/100:PIO4 Apr 24 21:00:54 Tower2 kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 Apr 24 21:00:54 Tower2 kernel: ata2.00: irq_stat 0x40000001 Apr 24 21:00:54 Tower2 kernel: ata2.00: failed command: WRITE DMA EXT Apr 24 21:00:54 Tower2 kernel: ata2.00: cmd 35/00:80:c0:97:03/00:01:00:00:00/e0 tag 27 dma 196608 out Apr 24 21:00:54 Tower2 kernel: ata2.00: status: { DRDY DF ERR } Apr 24 21:00:54 Tower2 kernel: ata2.00: error: { ABRT } Apr 24 21:00:54 Tower2 kernel: ata2: hard resetting link Apr 24 21:00:54 Tower2 kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Apr 24 21:00:54 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:54 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:00:54 Tower2 kernel: ata2.00: failed to set xfermode (err_mask=0x1) Apr 24 21:00:59 Tower2 kernel: ata2: hard resetting link Apr 24 21:01:00 Tower2 kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Apr 24 21:01:00 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:01:00 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:01:00 Tower2 kernel: ata2.00: failed to set xfermode (err_mask=0x1) Apr 24 21:01:00 Tower2 kernel: ata2.00: limiting speed to UDMA/100:PIO3 Apr 24 21:01:05 Tower2 kernel: ata2: hard resetting link Apr 24 21:01:05 Tower2 kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Apr 24 21:01:05 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:01:05 Tower2 kernel: ata2.00: failed to enable AA (error_mask=0x1) Apr 24 21:01:05 Tower2 kernel: ata2.00: failed to set xfermode (err_mask=0x1) Apr 24 21:01:05 Tower2 kernel: ata2.00: disabled Apr 24 21:01:05 Tower2 kernel: ata2: EH complete Apr 24 21:01:05 Tower2 kernel: sd 2:0:0:0: [sdc] tag#28 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 24 21:01:05 Tower2 kernel: sd 2:0:0:0: [sdc] tag#28 CDB: opcode=0x8a 8a 00 00 00 00 00 00 03 97 c0 00 00 01 80 00 00 Apr 24 21:01:05 Tower2 kernel: print_req_error: I/O error, dev sdc, sector 235456 Apr 24 21:01:05 Tower2 kernel: sd 2:0:0:0: [sdc] Read Capacity(16) failed: Result: hostbyte=0x04 driverbyte=0x00 Apr 24 21:01:05 Tower2 kernel: sd 2:0:0:0: [sdc] Sense not available. Apr 24 21:01:05 Tower2 kernel: sd 2:0:0:0: [sdc] Read Capacity(10) failed: Result: hostbyte=0x04 driverbyte=0x00 Apr 24 21:01:05 Tower2 kernel: sd 2:0:0:0: [sdc] Sense not available. Apr 24 21:01:05 Tower2 kernel: sd 2:0:0:0: [sdc] 0 512-byte logical blocks: (0 B/0 B) Apr 24 21:01:05 Tower2 kernel: sd 2:0:0:0: [sdc] 4096-byte physical blocks Apr 24 21:01:05 Tower2 kernel: sdc: detected capacity change from 4000787030016 to 0 Apr 25 00:13:10 Tower2 kernel: sd 2:0:0:0: [sdc] tag#9 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 25 00:13:10 Tower2 kernel: sd 2:0:0:0: [sdc] tag#9 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Apr 25 00:13:10 Tower2 kernel: sd 2:0:0:0: [sdc] tag#11 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 25 00:13:10 Tower2 kernel: sd 2:0:0:0: [sdc] tag#11 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Apr 25 00:13:10 Tower2 kernel: sd 2:0:0:0: [sdc] tag#14 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 25 00:13:10 Tower2 kernel: sd 2:0:0:0: [sdc] tag#14 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Apr 25 00:13:10 Tower2 kernel: sd 2:0:0:0: [sdc] tag#16 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 25 00:13:10 Tower2 kernel: sd 2:0:0:0: [sdc] tag#16 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Apr 25 00:13:28 Tower2 emhttpd: shcmd (1890): /usr/local/sbin/set_ncq sdc 1 Apr 25 00:13:28 Tower2 emhttpd: shcmd (1891): echo 128 > /sys/block/sdc/queue/nr_requests Apr 25 00:13:28 Tower2 kernel: sd 2:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 25 00:13:28 Tower2 kernel: sd 2:0:0:0: [sdc] tag#0 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Apr 25 00:13:28 Tower2 kernel: sd 2:0:0:0: [sdc] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 25 00:13:28 Tower2 kernel: sd 2:0:0:0: [sdc] tag#2 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Apr 25 00:13:29 Tower2 emhttpd: shcmd (1900): /usr/local/sbin/set_ncq sdc 1 Apr 25 00:13:29 Tower2 emhttpd: shcmd (1901): echo 128 > /sys/block/sdc/queue/nr_requests Apr 25 00:13:50 Tower2 emhttpd: shcmd (1911): /usr/local/sbin/set_ncq sdc 1 Apr 25 00:13:50 Tower2 emhttpd: shcmd (1912): echo 128 > /sys/block/sdc/queue/nr_requests Apr 25 00:13:50 Tower2 kernel: sd 2:0:0:0: [sdc] tag#25 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 25 00:13:50 Tower2 kernel: sd 2:0:0:0: [sdc] tag#25 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Apr 25 00:13:50 Tower2 kernel: sd 2:0:0:0: [sdc] tag#27 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 25 00:13:50 Tower2 kernel: sd 2:0:0:0: [sdc] tag#27 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Apr 25 00:13:50 Tower2 emhttpd: shcmd (1921): /usr/local/sbin/set_ncq sdc 1 Apr 25 00:13:50 Tower2 emhttpd: shcmd (1922): echo 128 > /sys/block/sdc/queue/nr_requests Apr 25 00:17:41 Tower2 emhttpd: device /dev/sdc has size zero Apr 25 00:17:41 Tower2 emhttpd: device /dev/sdc has size zero Apr 25 00:17:42 Tower2 emhttpd: device /dev/sdc has size zero Apr 25 00:17:42 Tower2 kernel: sd 2:0:0:0: [sdc] tag#17 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 25 00:17:42 Tower2 kernel: sd 2:0:0:0: [sdc] tag#17 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00 Apr 25 00:17:42 Tower2 kernel: sd 2:0:0:0: [sdc] tag#19 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Apr 25 00:17:42 Tower2 kernel: sd 2:0:0:0: [sdc] tag#19 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 98 00 Apr 25 00:17:43 Tower2 emhttpd: device /dev/sdc has size zero Apr 25 00:17:44 Tower2 emhttpd: device /dev/sdc has size zero Apr 25 00:17:45 Tower2 emhttpd: device /dev/sdc has size zero Apr 25 00:17:46 Tower2 emhttpd: device /dev/sdc has size zero Apr 25 00:17:47 Tower2 emhttpd: device /dev/sdc has size zero Apr 25 00:17:48 Tower2 emhttpd: device /dev/sdc has size zero Apr 25 00:17:49 Tower2 emhttpd: device /dev/sdc has size zero Apr 25 00:17:50 Tower2 emhttpd: device /dev/sdc has size zero Apr 25 00:17:51 Tower2 emhttpd: device /dev/sdc has size zero Apr 25 00:17:52 Tower2 emhttpd: device /dev/sdc has size zero Apr 25 00:17:54 Tower2 emhttpd: device /dev/sdc has size zero Apr 25 00:17:55 Tower2 emhttpd: device /dev/sdc has size zero Apr 25 00:17:56 Tower2 emhttpd: device /dev/sdc has size zero

Well did another reboot/reseating of drives and parity check, then all came up as normal... but after about 12 hours DISK1 is showing errors again. I guess I will begin the search for a new backplane cabling harness. I've got the server running off of an APC (1500VA / 900W) UPS, so with such a relatively low power microserver likely not a voltage sag.

The read only message is coming from an error when trying to update my dockers (PLEX, etc) Updated diagnostics attached. tower2-diagnostics-20190419-1619.zip

Ran the extended SMART test on the PARITY drive and it reported back no errors. Then did a parity check (which completed successfully) but the status on the MAIN page still shows ERRORS as 1, causing the system to respond as READ ONLY. How do I get UnRaid to drop the error marker and allow writes to the system again?