Parity Failed with error: Apr 18 19:28:02 ZALMAN kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

[Jean-Francois Masson]

Hi,

For the past few weeks, I've had problems with my parity disk. I think the parity fails during a SpinUp when writing data? Several months ago, I added a 4T disk to possibly add it to my array. During this time it was in my Unassing disk and almost always Spin Down. A few weeks ago I added this disk and once in a while when I want to write data to my pool it goes failed with these errors.

Apr 18 19:27:43 ZALMAN kernel: ata4.00: exception Emask 0x0 SAct 0x80000000 SErr 0x0 action 0x0
Apr 18 19:27:43 ZALMAN kernel: ata4.00: irq_stat 0x40000008
Apr 18 19:27:43 ZALMAN kernel: ata4.00: failed command: WRITE FPDMA QUEUED
Apr 18 19:27:43 ZALMAN kernel: ata4.00: cmd 61/40:f8:48:a8:48/05:00:03:00:00/40 tag 31 ncq dma 688128 out
Apr 18 19:27:43 ZALMAN kernel: ata4.00: status: { DRDY ERR }
Apr 18 19:27:43 ZALMAN kernel: ata4.00: error: { IDNF }
Apr 18 19:27:43 ZALMAN kernel: ata4.00: configured for UDMA/133
Apr 18 19:27:43 ZALMAN kernel: ata4: EH complete
Apr 18 19:27:46 ZALMAN kernel: ata4.00: exception Emask 0x0 SAct 0x3ec0 SErr 0x0 action 0x0
Apr 18 19:27:46 ZALMAN kernel: ata4.00: irq_stat 0x40000008
Apr 18 19:27:46 ZALMAN kernel: ata4.00: failed command: READ FPDMA QUEUED
Apr 18 19:27:46 ZALMAN kernel: ata4.00: cmd 60/40:38:08:b9:48/05:00:03:00:00/40 tag 7 ncq dma 688128 in
Apr 18 19:27:46 ZALMAN kernel: ata4.00: status: { DRDY DF ERR }
Apr 18 19:27:46 ZALMAN kernel: ata4.00: error: { ABRT }
Apr 18 19:27:46 ZALMAN kernel: ata4.00: Read log 0x00 page 0x00 failed, Emask 0x1
Apr 18 19:27:46 ZALMAN kernel: ata4.00: ATA Identify Device Log not supported
Apr 18 19:27:52 ZALMAN kernel: ata4.00: qc timeout (cmd 0xec)
Apr 18 19:27:52 ZALMAN kernel: ata4.00: failed to IDENTIFY (I/O error, err_mask=0x5)
Apr 18 19:27:52 ZALMAN kernel: ata4.00: revalidation failed (errno=-5)
Apr 18 19:27:52 ZALMAN kernel: ata4: hard resetting link
Apr 18 19:27:52 ZALMAN kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Apr 18 19:27:52 ZALMAN kernel: ata4.00: ACPI cmd ef/10:06:00:00:00:00(SET FEATURES) rejected by device (Stat=0x61 Err=0x04)
Apr 18 19:27:52 ZALMAN kernel: ata4.00: ACPI cmd f5/00:00:00:00:00:00(SECURITY FREEZE LOCK) filtered out
Apr 18 19:27:52 ZALMAN kernel: ata4.00: ACPI cmd b1/c1:00:00:00:00:00(DEVICE CONFIGURATION OVERLAY) filtered out
Apr 18 19:27:52 ZALMAN kernel: ata4.00: ACPI cmd 00/00:00:00:00:00:a0(NOP) rejected by device (Stat=0x61 Err=0x04)
Apr 18 19:27:52 ZALMAN kernel: ata4.00: ACPI cmd ef/10:06:00:00:00:00(SET FEATURES) rejected by device (Stat=0x61 Err=0x04)
Apr 18 19:27:52 ZALMAN kernel: ata4.00: ACPI cmd f5/00:00:00:00:00:00(SECURITY FREEZE LOCK) filtered out
Apr 18 19:27:52 ZALMAN kernel: ata4.00: ACPI cmd b1/c1:00:00:00:00:00(DEVICE CONFIGURATION OVERLAY) filtered out
Apr 18 19:27:52 ZALMAN kernel: ata4.00: ACPI cmd 00/00:00:00:00:00:a0(NOP) rejected by device (Stat=0x61 Err=0x04)
Apr 18 19:27:52 ZALMAN kernel: ata4.00: configured for UDMA/133 (device error ignored)
Apr 18 19:27:52 ZALMAN kernel: ata4: EH complete
Apr 18 19:27:52 ZALMAN kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Apr 18 19:27:52 ZALMAN kernel: ata4.00: irq_stat 0x40000001
Apr 18 19:27:52 ZALMAN kernel: ata4.00: failed command: FLUSH CACHE EXT

........... Many error after

 

I have a Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 and 4 port Sata card on the motherboard. The problem disk is on one of the onboard Sata ports. I suspect maybe a problem with a Sata port but the disk in error has been working on this port for a long time. Only since the addition in the pool (with spinup) more often of the new disk which is also on one of the Sata ports. I'm adding my diag to check if anyone has had this problem before. In the meantime, I will try to change the port of my parity disk and/or my new disk.

 

Thanks in advance.

zalman-diagnostics-20230418-1954.zip

[Squid]

You probably dislodged slightly the cable to the drive.  Reseat the cabling (both ends)

[Jean-Francois Masson]

Yes,

Indeed, I had a cable that moved. I changed this cable for one that locks but I still had the problem. Yesterday, I tried to change it on my SAS card and I redid my parity. I also disabled the SpinOff of this disk just to see. I suspect maybe a problem with my power cable powering multiple disks and maybe loss of power when more than one SpinUp disk at the same time? Thank you for your comment. I'll get back to you after my tests.

[Jean-Francois Masson]

@SquidWith cable changed et chanhed disk from Motherboard Sata port to Raid card and SpinOff disabled on party disk, i just had the same error. I will try another power port/connector. All my sata cable are ok and well connected. It's very weird problem. 

[Jean-Francois Masson]

Finally, my problem is too many splitter cable on my 2 problem HDD. 

Thanks for help.