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 FS after Data-rebuild

Featured Replies

I have only one parity and 2 disks in my system. Recently one of my disk(disk1) had read errors and the system disabled that disk. I have no choice but to replace that bad disk with a new one. As many topics have said. Just replace disk in the array slot and the system will automatically rebuild data with out any other procedures.

While tragedy happened here. When the rebuilding finished. A notice that "Unmountable: no or wrong filesystem." was on the disk. While I used the btrfs in the former disk so I tried to run "btrfs check" to see whether there was a filesystem error. Unfortunately, the tools shows that "cannot read chunk-tree". I tried lots of things including btrfs rescue but nothing happened. It was stiil unmountable. 

 

Is there any way to bring my data back? There was no valuable logs since I've reboot systems for lots of times.

Solved by JorgeB

  • Author

The disk1 reported below when check status of btrfs:

 

Couldn't read tree root
Could not open root, trying backup super
parent transid verify failed on 240418816 wanted 33573 found 33543
parent transid verify failed on 240418816 wanted 33573 found 33543
parent transid verify failed on 240418816 wanted 33573 found 33543
Ignoring transid failure
ERROR: root [1 0] level 2 does not match 0

  • Community Expert
6 hours ago, xyseer said:

parent transid verify failed on 240418816 wanted 33573 found 33543

This error is fatal, it means some writes were lost, it can happen if a storage device lies about flushing it's write cache, this is usually a drive (or controller) firmware problem.

 

You can try btrfs restore (option #2 here) but doubt it will work the way the fs is, if it does then the device will need to be formatted and the data restore.

  • Author

So, you mean that if 'btrfs restore' cannot bring the files back, then all my data will be lost?

(Since I've tried restore yesterday however it cannot restore anything. Even using btrfs-find-root together with btrfs restore in order to manually recover some data has failed😭)

  • Community Expert
  • Solution
7 hours ago, xyseer said:

So, you mean that if 'btrfs restore' cannot bring the files back, then all my data will be lost?

Most likely, you might want and check the old disk, if it's not completely dead most data should be recoverable, ddrescue may help.

  • Author

OK, Thanks for your answer and solutions. I'll try ddrescue to bring data.

 

  • Author

However, this parity is so sucks and I'm not considering use this raw backup method again. It's so unreliable!

Unraid is so that worse than Raid! I trusted in Unraid so much and it treated my data like that inversely. 

 

  • Community Expert

What happened is not normal, it suggests parity was not in sync or the controller/disk firmware lost some writes when the disk got disabled, possibly best to use xfs with your hardware, it's usually more robust.

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.