ata3.00: failed command: READ FPDMA QUEUED


Go to solution Solved by itimpi,

Recommended Posts

I am seeing a lot of these errors in Tools/Syslog

 

ata3.00: failed command: READ FPDMA QUEUED

ata3.00: exception Emask 0x10 SAct 0x3ff8 SErr 0x4090000 action 0xe frozen

 

I assume I have one or more bad disks -OR- bad SATA cables, or worse yet a bad mobo.  Can someone tell me which drive to focus on?

 

If I am totally wrong, can someone point me to what the culprit is?

 

wideglide-diagnostics-20220628-1126.zip

Edited by PapaThiele
Grammer
Link to comment

This is usually a power/connection issue, and since it's affecting 4 disks connected to the motherboard, disks 7, 8, 9 and 10, see if they have something in common, like a power splitter, could also be a board issue but it's not very likely, also the other two disks connect to the same controller don't show any issues.

Link to comment

Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - zero log...
ALERT: The filesystem has valuable metadata changes in a log which is being
ignored because the -n option was used.  Expect spurious inconsistencies
which may be resolved by first mounting the filesystem to replay the log.
        - scan filesystem freespace and inode maps...
        - found root inode chunk
Phase 3 - for each AG...
        - scan (but don't clear) agi unlinked lists...
        - process known inodes and perform inode discovery...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - check for inodes claiming duplicate blocks...
        - agno = 0
        - agno = 5
        - agno = 1
        - agno = 3
        - agno = 4
        - agno = 7
        - agno = 6
        - agno = 2
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
        - traversing filesystem ...
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify link counts...
Maximum metadata LSN (1:2822794) is ahead of log (1:2820534).
Would format log to cycle 4.
No modify flag set, skipping filesystem flush and exiting.

 

Link to comment

Dangit!  It went back to:

"Unmountable disk present:
Disk 7 • WDC_WD80EMAZ-00WJTA0_2SG6B9AJ (sds)"

Befotre thiss happened I notice a s#!t-ton of errors being written while the parity was rebuilding.

 

I have another disk pre-clearing.  I'll let that finish then replace #7, or at least let it run for now.  It's late & I'm too tired to try anything but if anyon leaves unstructions, I'll run through them in the mornin.  

 

 

wideglide-diagnostics-20220628-2310.zip

Link to comment

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.