Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Multible Drive failure crisis - What can I save?

Featured Replies

  • Author

The Check returned with 10 pages of errors. Should I fix?

A small cut

---

xfs_repair status:

Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... Log inconsistent (didn't find previous header) failed to find log head zero_log: cannot find log head/tail (xlog_find_tail=5) - scan filesystem freespace and inode maps... Metadata CRC error detected at 0x474fd0, xfs_agi block 0x37fffffd8/0x1000Metadata CRC error detected at 0x485fcd, xfs_rmapbt block 0x40/0x1000 Metadata CRC error detected at 0x48a5d7, xfs_sb block 0x7ffffff8/0x1000 btree block 0/8 is suspect, error -74 bad magic # 0 in btrmap block 0/8 bad rmapbt block count 0, saw 1 superblock has bad CRC for ag 1 agi has bad CRC for ag 7 bad magic # 0x41423343 for agi 7 bad version # 196 for agi 7 bad sequence # -1 for agi 7 bad length # -1 for agi 7, should be 268435455 Metadata CRC error detected at 0x48196d, xfs_refcountbt block 0x48/0x1000 bad uuid 00d7cb2e-0000-0002-00d7-cf0a00000002 for agi 7 Metadata CRC error detected at 0x447820, xfs_agf block 0x80000000/0x1000 would reset bad agi for ag 7 btree block 0/9 is suspect, error -74 bad magic # 0x58444233 in refcount btree b

...

- agno = 1 - agno = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - 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 = 2 - agno = 3 - agno = 4 - agno = 5 - agno = 7 - agno = 9 - agno = 8 - agno = 6 - agno = 10 would rebuild corrupt rmap btrees. would rebuild corrupt refcount btrees. No modify flag set, skipping phase 5 Inode allocation btrees are too corrupted, skipping phases 6 and 7 Maximum metadata LSN (1684631143:1025660244) is ahead of log (0:0). Would format log to cycle 1684631146. No modify flag set, skipping filesystem flush and exiting.

---

And a lot more.

  • Community Expert

Click the FIX button

  • Author

“Dirty log detected.”

Should I “Zero log”?

 

Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... Log inconsistent (didn't find previous header) failed to find log head zero_log: cannot find log head/tail (xlog_find_tail=5) ERROR: The log head and/or tail cannot be discovered. Attempt to mount the filesystem to replay the log or use the -L option to destroy the log and attempt a repair.

 

 

  • Author

“File system corruption detection “ :-O

IMG_2092.png

IMG_2091.png

  • Community Expert

Try running from the CLI, just to see if it's any different, with the array still in maintenance mode, type:

 

xfs_repair -vL /dev/md3p1

 

  • Author

Hey, I ran it three times. Keep getting Fatal Error in phase 7:

 

Phase 6 - check inode connectivity...
        - resetting contents of realtime bitmap and summary inodes
        - traversing filesystem ...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - agno = 8
        - agno = 9
        - agno = 10
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify and correct link counts...
SB summary counter sanity check failed
Metadata corruption detected at 0x48a218, xfs_sb block 0x0/0x1000
libxfs_bwrite: write verifier failed on xfs_sb bno 0x0/0x8
Maximum metadata LSN (1:80) is ahead of log (1:8).
Format log to cycle 4.
SB summary counter sanity check failed
Metadata corruption detected at 0x48a218, xfs_sb block 0x0/0x1000
libxfs_bwrite: write verifier failed on xfs_sb bno 0x0/0x8
xfs_repair: Releasing dirty buffer to free list!
xfs_repair: Refusing to write a corrupt buffer to the data device!
xfs_repair: Lost a write to the data device!

fatal error -- File system metadata writeout failed, err=117.  Re-run xfs_repair.

  • Community Expert

xfs_repair is unable to fix the filesystem, the damage likely happened after mounting the empty disk, it would have updated parity.

 

The best option to try and recover the data may be to rebuild like that using a new disk, then run a file recovery app on it, like UFS explorer.

  • Author

Thanks! I will try.

  • Author

Quick Q. It seems I have all my most important personal media still intact, and its probably TV/Movies that are gone. Is there anyway to see what is missing? And for the media that shows, is there, do I know it's not corrupted? In other words, will the lost data just not show, or will it show and then be corrupted?

  • Community Expert
21 minutes ago, IWasJustHere said:

Is there anyway to see what is missing?

Only if you have a list with everything for comparison.

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...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.