Jump to content

Unmountable disk after adding a new disk


Recommended Posts

I’ve added a new drive to my unraid array by replacing a smaller one. However, another drive, not included in the transaction, became unmountable. It said it was dissbled. I’ve done short and long SMART tests and both gave no errors. Here’s the output of “xfs_repair -v /dev/md5” and my diagnostics.


 

Quote
Phase 1 - find and verify superblock... couldn't verify primary superblock - not enough secondary superblocks with matching geometry !!! attempting to find secondary superblock... ...found candidate secondary superblock... unable to verify superblock, continuing... ....found candidate secondary superblock... unable to verify superblock, continuing...
<bunch of dots>
unable to verify superblock, continuing...
<bunch of dots>
Exiting now.

 

g1-diagnostics-20230405-0810.zip

Link to comment

What kind of file recovery util could I use?

 

Do I understand correctly that I’d be recovering files from the unmountable drive using a recovery util, put those files on another drive, and then format the unmountable drive to add it back to the array?

Link to comment
26 minutes ago, Guanyin said:

Do I understand correctly that I’d be recovering files from the unmountable drive using a recovery util, put those files on another drive, and then format the unmountable drive to add it back to the array?

Correct, UFS explorer is one utility often used, but I would first wait for v6.12-rc3 that should be released very soon, possibly during this weekend.

Link to comment
On 4/8/2023 at 9:54 AM, JorgeB said:

Nope, rebuilding a disk won't generally fix filesystem issues.

Could you elaborate on this? Isn't the filesystem issue with that specific disk? Or is a filesystem issue an array issue?

 

Another question: which version of UFS explorer is required? 

 

Another question: What if I forfeit the data on that drive, format the drive and add it back to the array? Would that work? Obviously, I wouldn't know which data I would lose.

Link to comment
7 hours ago, Guanyin said:

Could you elaborate on this? Isn't the filesystem issue with that specific disk? Or is a filesystem issue an array issue?

Rebuild is to replace a failed disk, when there are filesystem issues usually the parity will emulate the same issues, but there have been exceptions, when the parity is not 100% in sync.

 

7 hours ago, Guanyin said:

which version of UFS explorer is required? 

I believe standard version.

 

7 hours ago, Guanyin said:

Another question: What if I forfeit the data on that drive, format the drive and add it back to the array? Would that work? Obviously, I wouldn't know which data I would lose.

Yes.

 

7 hours ago, Guanyin said:

Now I get this notification 🤔

That suggests you are rebuilding the disk, I assume the emulated disk is still unmountable?

 

 

Link to comment
Quote

I assume the emulated disk is still unmountable?

Yes.


I’m going to wait for another xfs_repair (which is giving the same result as my initial post, so far). 
 

When that doesn’t work I’ll await the v6.12-rc3 update.

 

If that doesn’t help I’ll try file recovery.

 

If that doesn’t help I’ll try replacing the disk with a new one.

 

Is that a sound strategy?

 

Thanks for all the help so far!!

 

Link to comment
  • 1 month later...

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

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...