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.

xfs repair - Sorry, could not find valid secondary superblock Exiting now - next steps

Featured Replies

Added a 2nd hand drive to my array about a month ago and now suddenly its unmountable. Ran xfs check and fix but had no luck. Is my best bet to just replace the drive and rebuild from parity?

thingymabob-diagnostics-20260126-1925.zip

  • Community Expert

Parity is usually in sync with the unmountable disk, so rebuild will only result in unmountable disk.

2 hours ago, bbqchipsy said:

Ran xfs check

Did you use the webUI for this, or did you try to do it from the command line?

  • Author
6 hours ago, trurl said:

Parity is usually in sync with the unmountable disk, so rebuild will only result in unmountable disk.

Did you use the webUI for this, or did you try to do it from the command line?

I used WebUI

  • Community Expert
10 hours ago, bbqchipsy said:

Added a 2nd hand drive to my array about a month ago and now suddenly its unmountable

Are you sure it wasn't always unmountable? You have to format a disk after adding it to a new data slot in the array.

  • Author
25 minutes ago, trurl said:

Are you sure it wasn't always unmountable? You have to format a disk after adding it to a new data slot in the array.

100%, it was precleared and formatted in xfs and was working functionally in the array for a couple weeks before it showed the error. Sorry I forgot, I did also run the xfs fix command in command line as well after GUI didn't work and got the same result.

So at this point would I be best to remove the drive, replace with a new config to 'lose' the unmountability from the parity image, and attempt to recover the data from the disk some other way?

  • Community Expert
12 minutes ago, bbqchipsy said:

Sorry I forgot, I did also run the xfs fix command in command line as well after GUI didn't work and got the same result.

What command line did you use?

  • Author
1 hour ago, trurl said:

What command line did you use?

xfs_repair -v /dev/md1p1

  • Community Expert

You can try updating to 7.2.3 then retry, it has newer xfs-progs, if it still fails, bets bet is using a file recovery app, like UFX Explorer; the free trial should show what it can recover.

  • Author
23 hours ago, JorgeB said:

You can try updating to 7.2.3 then retry, it has newer xfs-progs, if it still fails, bets bet is using a file recovery app, like UFX Explorer; the free trial should show what it can recover.

Just updated, I'll run the fix overnight and check back in with results

  • Author
On 1/29/2026 at 6:50 PM, JorgeB said:

You can try updating to 7.2.3 then retry, it has newer xfs-progs, if it still fails, bets bet is using a file recovery app, like UFX Explorer; the free trial should show what it can recover.

Unfortunately still the same result. Looks like there are a couple different UFX Explorer options, UFS Explorer RAID Recovery what I'm after?

  • Author

hypothetically, worst case scenario if the data is lost and the drive is dead, would a new drive and new config be the next step?

  • Community Expert
7 minutes ago, bbqchipsy said:

new drive and new config be the next step?

Or format emulated disk1, then rebuild to new disk. Either way you have to format the drive assigned as disk1 to make it mountable.

  • Community Expert
9 minutes ago, trurl said:

Or format emulated disk1, then rebuild to new disk

If nothing is assigned as disk1 when the array is started, disk1 is emulated. You can format emulated disk1 before stopping the array, assigning a new disk, then starting the array to begin rebuild.

You don't actually have to start the array with nothing assigned though.

If a new drive is assigned as disk1 then the array is started, it will begin rebuilding disk1 and disk1 is still emulated until rebuild is complete. You can format emulated disk1 while it is rebuilding.

Or, after rebuild is complete, the disk is no longer emulated. You can format disk1 after rebuild completes.

Since you will be using a new disk, you can still work with the original disk to try to recover files with UFS Explorer.

Unraid is not technically RAID since each array disk is an independent filesystem.

UFS Explorer Standard Edition will be fine. You can even use it in Trial mode to see what it will recover before you pay for it.

  • Community Expert
36 minutes ago, bbqchipsy said:

a new drive and new config be the next step?

Or you could do it that way. New Config and assign new disk as disk1, then start the array to begin parity rebuild. You can format disk1 while parity rebuilds or after.

  • Community Expert

When formatting any array disk, make sure it only lists the unmountable drives you want to format in Array Operation. If any drive is listed that you don't want to format, you need to check filesystem and repair it instead, then check the list again before proceeding to format the disks you want formatted.

  • Community Expert
16 hours ago, bbqchipsy said:

Unfortunately still the same result. Looks like there are a couple different UFX Explorer options, UFS Explorer RAID Recovery what I'm after?

The standard version (cheapest) should be enough for array drives where each drive is a free-standing file system.

You would need the RAID variant if trying to recovery files from a multi-drive RAID pool.

The Free trial versions can show you what it could recover before you commit to paying for the selected version.

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.