1st time I had parity errors it seems, I did see that all was running a bit hotter than usual today


Anubclaw

Recommended Posts

Dear Support,

I had today 446 parity errors on one of my Servers. Can you have a look at the diagnostics if you can see what type of issues came up ?

Drives seem ok and the parity too but I just wanted to check where the issue is and how can I fix it if possible.

Since this is the 1st time errors were seen I am a bit nervous. I had to replace one of the drives a few weeks ago.

Thank you for your help.

 

Best regards,

Harald Weiss

dellnas-diagnostics-20211128-1555.zip

Link to comment

Looks like this was a correcting parity check. It is recommended that you only do a correcting parity check after you have already determined there are parity errors that need correcting, and after you have already determined that those errors don't have some other obvious cause. You don't want a bad connection on another disk to cause parity to be modified, for example.

 

Nov  9 15:38:09 dellnas kernel: ata2.00: ATA-10: ST4000VN008-2DR166,             ZGY6V45R, SC60, max UDMA/133
Nov  9 15:38:56 dellnas kernel: md: import disk0: (sdd) ST4000VN008-2DR166_ZGY6V45R size: 3907018532 
Nov 28 07:18:56 dellnas kernel: ata2.00: exception Emask 0x50 SAct 0x700000 SErr 0x4090800 action 0xe frozen
Nov 28 07:18:56 dellnas kernel: ata2.00: irq_stat 0x00400040, connection status changed
Nov 28 07:18:56 dellnas kernel: ata2: SError: { HostInt PHYRdyChg 10B8B DevExch }
Nov 28 07:18:56 dellnas kernel: ata2.00: failed command: READ FPDMA QUEUED
Nov 28 07:18:56 dellnas kernel: ata2.00: cmd 60/40:a0:98:e8:2a/05:00:0c:01:00/40 tag 20 ncq dma 688128 in
Nov 28 07:18:56 dellnas kernel:         res 40/00:b0:78:f0:2a/00:00:0c:01:00/40 Emask 0x50 (ATA bus error)
Nov 28 07:18:56 dellnas kernel: ata2.00: status: { DRDY }

Since that is the parity disk in this case, I guess you could say you haven't caused parity to be corrupted by a problem on another disk.

 

Check connections, SATA and power, both ends, including splitters. Then run a non-correcting parity check. Possibly it will still find sync errors since there were problems during those earlier corrections.

 

Let us know the results of that non-correcting check and post new diagnostics.

 

 

Link to comment
  • 2 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.