Jump to content
We're Hiring! Full Stack Developer ×

Forgot to preserve previous drive assignments (New Config) (SOLVED)


Anthwerp

Recommended Posts

Boneheaded move on my part. I was removing an unused drive on my unraid server. I went over to New Config and wiped my drive assignments without electing to preserve previous assignments.

 

I know which one my parity drive is. If I just restore it in random order (except assign my parity to parity) will I be ok?

Link to comment
2 minutes ago, Anthwerp said:

Boneheaded move on my part. I was removing an unused drive on my unraid server. I went over to New Config and wiped my drive assignments without electing to preserve previous assignments.

 

I know which one my parity drive is. If I just restore it in random order (except assign my parity to parity) will I be ok?

If you only have parity1 then you can tick the option to say parity is already valid after assigning the disks before you start the array as parity1 is not sensitive to disk order.    If you have parity2 then disk order DOES matter and you would need to rebuild parity.

Link to comment

Awesome, thanks. Yes only 1 parity drive and I'm sure that's the one (It's got no valid file system and it's the same size as previous)

I ran a non-correcting parity check and it was seeing a bunch of errors so I am sure I messed up the order. That's what concerns me, but everything SEEMS to be working fine... 

Link to comment
Just now, Anthwerp said:

Awesome, thanks. Yes only 1 parity drive and I'm sure that's the one (It's got no valid file system and it's the same size as previous)

I ran a non-correcting parity check and it was seeing a bunch of errors so I am sure I messed up the order. That's what concerns me, but everything SEEMS to be working fine... 

Just realised you said you had removed a drive, and this cannot be done without invalidating parity.

Link to comment
  • Anthwerp changed the title to Forgot to preserve previous drive assignments (New Config) (SOLVED)
26 minutes ago, Anthwerp said:

Yes that's fine, just wanted to ensure that everything is fine even if I mess up the drive order. (drive I removed had nothing in it)

It would probably be faster to do a new config preserving all, make sure the parity is valid ISN'T checked, and let it build parity. That way you don't have to wait for it to read, compare and correct the parity during the currently necessary correcting parity check.

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

×
×
  • Create New...