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.

Unmountable Disk After Parity Rebuild

Featured Replies

  • Community Expert

I recently replaced a failing 4TB drive with a 14TB drive (14TB is the size of my parity disk and the largest disk size in my array) and after the rebuild completed it stated that the new drive was unmountable. I have followed the steps of running xfs_repair and am receving the following failure message. Is the data lost? 

 

root@unRaidInBlood:~# xfs_repair /dev/md9p1
Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - zero log...
        - scan filesystem freespace and inode maps...
clearing needsrepair flag and regenerating metadata
sb_icount 6720, counted 32
sb_ifree 270, counted 29
sb_fdblocks 310106776, counted 976277675
        - 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
        - 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
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...
SB summary counter sanity check failed
Metadata corruption detected at 0x47c2cb, xfs_sb block 0x0/0x200
libxfs_bwrite: write verifier failed on xfs_sb bno 0x0/0x1
SB summary counter sanity check failed
Metadata corruption detected at 0x47c2cb, xfs_sb block 0x0/0x200
libxfs_bwrite: write verifier failed on xfs_sb bno 0x0/0x1
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.

unraidinblood-diagnostics-20240107-0123.zip

Edited by jekupka
Diagnostics Upload

Solved by JorgeB

  • Community Expert
4 hours ago, jekupka said:

Re-run xfs_repair.

Try again.

  • Author
  • Community Expert

I've run it ten times in a row with the same error message.

  • Community Expert
  • Solution

If xfs_repair cannot fix the filesystem your options are limited, you can restore from a backup or use something like UFS explorer to see if it can recover most data.

On 1/7/2024 at 2:18 AM, jekupka said:

failing 4TB drive

See if that drive is still readable.

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.