MrMoosieMan Posted October 18, 2017 Share Posted October 18, 2017 Hello! I was not getting SMART info within unRAID when using a RAID controller so I swapped it out for an HBA. When I start unRAID with the HBA, unRAID it's needing me to reassign the drives but the drives are now renamed. When I try to reassign the drives, unRAID is not recognizing them. Is there a workaround I can use to assign the drives with their new names and have unRAID accept them? Screenshot of the issue Thank you! Quote Link to comment
JorgeB Posted October 18, 2017 Share Posted October 18, 2017 Tools -> New config Reassign all disks, double check that the parity disk is in the parity slot, and check "parity is already valid" before starting the array. Quote Link to comment
MrMoosieMan Posted October 18, 2017 Author Share Posted October 18, 2017 I just want to make sure I'm doing this correctly so I don't erase my data. Will you please take a look at this screenshot and confirm I should hit "done"? Quote Link to comment
JorgeB Posted October 18, 2017 Share Posted October 18, 2017 Doing a new config doesn't touch your data, only thing you need to be careful of is not assigning a data disk to the parity slot after doing it. Quote Link to comment
MrMoosieMan Posted October 18, 2017 Author Share Posted October 18, 2017 Is there a way of determining which drive was my old parity drive? I've noticed that the letters at the end of the drive names have changed. Quote Link to comment
JorgeB Posted October 18, 2017 Share Posted October 18, 2017 Not using the identifications of the raid controller, if you don't know which one is parity by its serial number the best way it to do the new config but assign all disks as data disks, start the array and only one disk should be unmountable, that is your parity, if there's more than one unmoutable disk post diagnostics. After identifying parity do another new config, this time assigning parity to the parity slot, check "parity is already valid" before array start, but now will need to do a parity check because there will be a few sync errors. Quote Link to comment
MrMoosieMan Posted October 18, 2017 Author Share Posted October 18, 2017 Thank you very much for the speedy help. When building the first new config, what options should I select? Sorry if this is obvious, I'm very novice. Quote Link to comment
JorgeB Posted October 18, 2017 Share Posted October 18, 2017 It doesn't matter for the first, you can select all for the second new config and then just reassign parity (and reorder data disks if needed). Quote Link to comment
MrMoosieMan Posted October 18, 2017 Author Share Posted October 18, 2017 32 minutes ago, johnnie.black said: After identifying parity do another new config, this time assigning parity to the parity slot, check "parity is already valid" before array start, but now will need to do a parity check because there will be a few sync errors. I was able to ID my parity drive using your method. I just need to be clear on the last part - I should select "parity is already valid", start the array and unRAID will automatically start a parity check? Is there any else I need to do after starting the array? Again, thank you very much. Quote Link to comment
JorgeB Posted October 18, 2017 Share Posted October 18, 2017 I should select "parity is already valid", start the array Yes and unRAID will automatically start a parity check? No, you'll need to start one manually, there will be be a few sync errors, it's normal after this. Quote Link to comment
MrMoosieMan Posted October 18, 2017 Author Share Posted October 18, 2017 It's up now and running a parity check. Can I buy you a case of beer (not kidding)? If you have a PayPal account, private message me your email and I'll send one over. Thanks, again! Quote Link to comment
JorgeB Posted October 18, 2017 Share Posted October 18, 2017 Thanks for the beer ! Quote Link to comment
Recommended Posts
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.