August 14, 20232 yr Hi, suddenly I'm getthing those errors: ``` Tower kernel: ata6.00: failed command: READ FPDMA QUEUED Tower kernel: ata6.00: cmd 60/80:a0:40:60:a8/00:00:24:00:00/40 tag 20 ncq dma 65536 in Tower kernel: res 40/00:80:40:4b:a8/00:00:24:00:00/40 Emask 0x50 (ATA bus error) Tower kernel: ata6.00: status: { DRDY } Tower kernel: ata6: hard resetting link Tower kernel: ata6: found unknown device (class 0) Tower kernel: ata6: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Tower kernel: ata6.00: configured for UDMA/33 Tower kernel: ata6: EH complete Tower kernel: ata6.00: exception Emask 0x50 SAct 0x8f000380 SErr 0x4070802 action 0xe frozen ```tower-diagnostics-20230814-1827.zip But I dont know what drive is the issue here, all of them seem available. A few days ago I had issues with a Cruical SSD freezing (see my post history) but after a firmware update that issue seemed gone Any way for me to figure out what sata controller or drive? Whats the issue exactly?
August 14, 20232 yr Author Okay... after rebooting one disk is not mountable because of a unsupported file format
August 14, 20232 yr Author I removed all SATA cables, reordered them (to ensure it wasn't a dead sata controller) and replaced one sata cable that didnt have a clip to hold it. Sadly the same disk still isnt mountable. I'm guessing I fucked up by running "check parity" and forgot to remove "write corrections" and it fixed one error. Probably ripping disk 2. When I start the array in maintenance mode everything is fine, and when I run a check (without fixing) it only finds 2 errors after a few minutes. but every device shows up, but when I mount them the disk2 isnt mountable. Should I run in maintenance and let it fix the two errors? tower-diagnostics-20230814-1921.zip
August 14, 20232 yr Author Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this. what now? should I do with -L Edited August 14, 20232 yr by lustigpeter
August 14, 20232 yr Author when running with -n (assuming its totally fine because no changes) 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 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 5 - agno = 7 - agno = 2 - agno = 3 - agno = 11 - agno = 4 - agno = 8 - agno = 10 - agno = 9 - agno = 6 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 (7:338172) is ahead of log (7:338100). Would format log to cycle 10. No modify flag set, skipping filesystem flush and exiting.
August 14, 20232 yr Author 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 destroyed because the -L option was used. - scan filesystem freespace and inode maps... clearing needsrepair flag and regenerating metadata - found root inode chunk Phase 3 - for each AG... - scan and 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 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 5 - agno = 8 - agno = 11 - agno = 6 - agno = 7 - agno = 9 - agno = 10 - agno = 4 - agno = 3 - agno = 2 clearing reflink flag on inodes when possible Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Maximum metadata LSN (7:338191) is ahead of log (1:2). Format log to cycle 10. done Mountable again!!! Thank you!!! But I still have two sync errors. Should I just fix em?
August 14, 20232 yr Author I started a non fixing check, I see all of the disks reading but the progress isnt showing
August 14, 20232 yr Community Expert Try refreshing the GUI or using a different browser, but fixing the filesystem keeps parity in sync.
August 14, 20232 yr Author Did a full reboot, and now It's back showing progress, seems like everything works and no further errors in the log, thanks a lot, really a lifesaver.
August 14, 20232 yr Author well now I'm 6% into a non correcting parity check and I have 517 errors, it isnt increasing however which is kinda good? No special errors in the logs tower-diagnostics-20230814-2038.zip Edited August 14, 20232 yr by lustigpeter
August 15, 20232 yr Community Expert No disk/ATA errors which is good, but since there are sync errors already I would cancel and start a correcting check.
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.