RexMundi727

My apologies as I stopped the check. Attached is the updated diagnostics. templartower-diagnostics-20240515-1903.zip

Attached is the diagnostics templartower-diagnostics-20240514-1609.zip

I have been dealing with this issue on and off for over a year now and thought I had it all working good for the past few months and a few days ago it popped up for me again. I had an issue with real slow cache writes to the array and the content would not move off from cache. I rebooted as then when system came up it started to do a Parity check and the Parity check said it would be 200 plus days to complete. I was advised that this may be a sata cable issue so I bought new sata cables and replaced all 6. This worked for about 10 hours and Parity check was going fine until it stopped and then moved back to 150 plus days. Below is the log when the red error showed up and I have attached is the complete log after a reboot. As mentioned I have been dealing with this on and off for over a year now and whatever I do does not end up in a long term solution. Any help would be appreciated in resolving this issue. May 13 16:21:02 TemplarTower kernel: ata7.00: exception Emask 0x10 SAct 0x800000 SErr 0x4090000 action 0xe frozen May 13 16:21:02 TemplarTower kernel: ata7.00: irq_stat 0x00400040, connection status changed May 13 16:21:02 TemplarTower kernel: ata7: SError: { PHYRdyChg 10B8B DevExch } May 13 16:21:02 TemplarTower kernel: ata7.00: failed command: READ FPDMA QUEUED May 13 16:21:02 TemplarTower kernel: ata7.00: cmd 60/08:b8:d0:4e:b0/00:00:10:04:00/40 tag 23 ncq dma 4096 in May 13 16:21:02 TemplarTower kernel: res 40/00:00:d0:4e:b0/00:00:10:04:00/40 Emask 0x10 (ATA bus error) May 13 16:21:02 TemplarTower kernel: ata7.00: status: { DRDY } May 13 16:21:02 TemplarTower kernel: ata7: hard resetting link May 13 16:21:08 TemplarTower kernel: ata7: link is slow to respond, please be patient (ready=0) May 13 16:21:12 TemplarTower kernel: ata7: COMRESET failed (errno=-16) May 13 16:21:12 TemplarTower kernel: ata7: hard resetting link May 13 16:21:13 TemplarTower kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300) May 13 16:21:13 TemplarTower kernel: ata7.00: supports DRM functions and may not be fully accessible May 13 16:21:14 TemplarTower kernel: ata7.00: supports DRM functions and may not be fully accessible May 13 16:21:14 TemplarTower kernel: ata7.00: configured for UDMA/133 May 13 16:21:14 TemplarTower kernel: ata7: EH complete unRAID Log.txt

Attached are the diagnostics. templartower-diagnostics-20230930-1617.zip

I have been dealing with this issue for 6 months now but here is my most recent issue. I woke up this morning with an 8 TB drive with 2 errors and note that contents are being emulated. I took drive out formatted it and put it back in and when started up the disk was being recreated as expected. The issue is the recreation time change from 30 days to 180 days and is running at 1 Mbps. As mentioned I have been dealing with this issue for 6 months now since I update my system with a new MB and CPU. I operated without Parity for about 4 months as the PArtity build was going to take over a year to build. About a month ago I installed my 3rd MB to see if I could get it working better I was able to do a Parity build in 36 hours or so so I thought all was good. All seemed to be good until this morning when I had a measly 2 errors and now I am back to 6 months to rebuild a drive that had 2 TB of data on it. So I have a couple of questions here. First is what could be the cause that would result in a Parity build taking 2 years or rebuilding 2 TB of lost data on a drive taking 6 months? I am now on my 3rd MB and now have one with 6 Sata ports so all 6 drives on connected to the MB. I have replaced every Sata cable numerous times and have probably have gone through 20 or 30. Again, all was good about a month ago when I crated Parity but now it is a no go. Since I have been trying for 6 months to resolve the above and have no idea on how to resolve the issue is there a way that I can just not do a rebuild from Parity and just be able to add the lost data as that would take a few hours and not 6 months? Thanks in advance for any insight.

I have a 4 port SATA expansion card but for some reason when I try to build Parity or RedCheck it says it will take 200 to 300 days to complete. Obvious problem. It was suggested that I purchase a IBM M5110 LSI 9207-8i IT which I did. I installed and it was working good for about 5 minutes. I then powered off put cover or and restarted at which point the drives that were plugged into the M5110 did not show up. Tried several times with no success. Looked at Bios and it says it is IT which I believe is correct. I do have it in a PCI 16 slot but says it should be PCI 8 which the MB does not have. Any suggestions on how to get this card working?