Array is rebuilding with one disk shown as 'Unmountable', is it ok?


Go to solution Solved by JorgeB,

Recommended Posts

Hi,

 

I've just got a weird issue, not sure if it's ok, so I'd like to ask here to see if anyone knows it.

 

My array has 2 parity disks (one 16TB, one 8TB), recently one of the array disks (disk9, 3TB) was broken, so I bought a new 16TB, assigned it as the parity disk (to replace the old 8TB one), and re-assigned the old 8TB parity disk as disk9. When I started the array, everything seemed ok, the array first copied the parity data from the old 8TB disk to the new 16TB disk, then the array started rebuilding disk9.

 

But here comes a weird thing: one of my array disks (disk2) was marked as 'Unmountable: Wrong or no file system', but the array was still reading data from it to rebuild the disk9, is this even normal? Will the rebuild be good?

 

Thanks for your time.

 

array_screen_snapshot.thumb.jpg.50e2ec315ea59f5087c0af1ecb1bde45.jpg

unraid-diagnostics-20220706-1744.zip

Link to comment

Ah I get your point! I need to scan 1st partition (/dev/sdn1) instead of the whole disk (/dev/sdn). I restarted the xfs_repair, this time it ends quickly with some kind of issue (shown in screenshot), I guess the next step is to re-run the xfs_repair to fix that?

xfs_repair_found_issues.jpg

Link to comment
11 minutes ago, JorgeB said:

Still not the correct way of doing, you must use the md device, or parity will become out of sync, use:

 

xfs_repair -v /dev/md2

 

 

Thanks for the clarification. Now the disk is fixed, I'm running a parity check with 'Write the corrections to parity' option checked, I assume it's the right way because their must be some mismatch between the parity and the disk being fix, so the parity needs to be updated.

Link to comment
3 minutes ago, georgez said:

Now the disk is fixed, I'm running a parity check with 'Write the corrections to parity' option checked, I assume it's the right way because their must be some mismatch between the parity and the disk being fix, so the parity needs to be updated.

Not if you the ‘md’ device.    When you use that it will keep parity in sync.

 

it would have been easier to do it from the GUI then you do not need to worry about getting device names right.

 

Link to comment
Just now, itimpi said:

Not if you the ‘md’ device.    When you use that it will keep parity in sync.

 

Now I see how those device names work. Unfortunately I already did the xfs_repair on /dev/sdn1, hence have to do a parity-check.

 

Thank you all for your help! You guys are awesome!

  • Like 1
Link to comment

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.