DMP-UNRAID Posted January 19 Share Posted January 19 Hi, I'm at a bit of a loss at the moment. I'm running Unraid on a HP Microserver Gen 8 and have wanted for awhile to upgrade the CPU and the RAM & SSD cache drive, got it all up & running bar having the wrong ram, popped back in the old ram and it booted up. I then got an error message "Too Many Wrong And/or Missing Disks!" looked on the forums and they mentioned about "New Config" I did that and now none of my disks are showing in the array. Is it completely wrecked and will I just have to start over again? Some links to screenshots to show my issue and I'll attach my log at the bottom. Any help greatly appreciated, thanks. https://ibb.co/0r3fbbk https://ibb.co/NVVkHk4 https://ibb.co/WvZHHvq dmp-unraid-diagnostics-20240119-1822.zip Quote Link to comment
JorgeB Posted January 19 Share Posted January 19 It would be good to see the diags from before the new config, to known why the disks ere "wrong", but according to the diags the array disks are assigned (new), unlike your screenshot, which one is correct? 1 Quote Link to comment
DMP-UNRAID Posted January 19 Author Share Posted January 19 Is it possible to get previous logs? I seen the disks and was matching them up the way they were previously. There was a message saying that if it was started that all information would be erased so I unassigned them. Quote Link to comment
trurl Posted January 19 Share Posted January 19 Are you sure you know your disk assignments? New Config wants to rebuild parity on any disk assigned to any parity slot. 4 minutes ago, DMP-UNRAID said: There was a message saying that if it was started that all information would be erased Could you post a screenshot of the exact message, I think you probably have misunderstood. 1 Quote Link to comment
trurl Posted January 19 Share Posted January 19 Do you have a current backup of your boot flash? 1 Quote Link to comment
trurl Posted January 19 Share Posted January 19 9 minutes ago, DMP-UNRAID said: Is it possible to get previous logs? Only if you have syslog server setup 1 Quote Link to comment
DMP-UNRAID Posted January 19 Author Share Posted January 19 38 minutes ago, trurl said: Are you sure you know your disk assignments? New Config wants to rebuild parity on any disk assigned to any parity slot. Could you post a screenshot of the exact message, I think you probably have misunderstood. 37 minutes ago, trurl said: Do you have a current backup of your boot flash? 33 minutes ago, trurl said: Only if you have syslog server setup I'd taken a screenshot of the disk array earlier in the day. This is the message that popped up "All existing data on this device will be OVERWRITTEN when array is Started" I've a back up from August (I hit backup after the setup earlier and it then had today's date/time for the backup). Quote Link to comment
Solution JorgeB Posted January 20 Solution Share Posted January 20 If you now the correct assignments, you can re-assign all devices and check "parity is already valid" before array start, then start the array, but since we don't know why the disks were "wrong" there may be other issues, if the disks don't mount post new diags. 1 Quote Link to comment
DMP-UNRAID Posted January 20 Author Share Posted January 20 4 hours ago, JorgeB said: If you now the correct assignments, you can re-assign all devices and check "parity is already valid" before array start, then start the array, but since we don't know why the disks were "wrong" there may be other issues, if the disks don't mount post new diags. This is how it was originally when I screenshot it before everything - https://ibb.co/yWvFsKZ Here it is now when I've reassigned the disks like above - https://ibb.co/9gjhJNr Is this a good sign now that I've added all the drives back like above? https://ibb.co/cxZ8TTT Quote Link to comment
trurl Posted January 20 Share Posted January 20 18 hours ago, DMP-UNRAID said: "All existing data on this device will be OVERWRITTEN when array is Started" Did you understand the specific device it was referring to? Parity has none of your data. 1 Quote Link to comment
DMP-UNRAID Posted January 20 Author Share Posted January 20 12 minutes ago, trurl said: Did you understand the specific device it was referring to? Parity has none of your data. In the second link above it's referencing the parity drive. Quote Link to comment
trurl Posted January 20 Share Posted January 20 19 hours ago, DMP-UNRAID said: all information would be erased 16 minutes ago, trurl said: Parity has none of your data. 4 minutes ago, DMP-UNRAID said: it's referencing the parity drive So none of your data would be involved in New Config. But, follow these instructions 7 hours ago, JorgeB said: re-assign all devices and check "parity is already valid" before array start, then start the array, but since we don't know why the disks were "wrong" there may be other issues, if the disks don't mount post new diags. And post new diagnostics before doing anything else. 1 Quote Link to comment
trurl Posted January 20 Share Posted January 20 Just now, trurl said: So none of your data would be involved in New Config. Unless you assign one of your data disks to a parity slot. This is the main thing we are concerned about. 1 Quote Link to comment
DMP-UNRAID Posted January 21 Author Share Posted January 21 18 hours ago, trurl said: Unless you assign one of your data disks to a parity slot. This is the main thing we are concerned about. Apologies about the delay in getting back to y'all was out of the house for the day. I've assigned all the drives correctly according to what I had previously from the screenshot above. Here's a link to the new diagnostics. I've just assigned the drives and haven't done anything else yet. dmp-unraid-diagnostics-20240121-1053.zip Quote Link to comment
JorgeB Posted January 21 Share Posted January 21 On 1/20/2024 at 8:23 AM, JorgeB said: check "parity is already valid" before array start, then start the array, but since we don't know why the disks were "wrong" there may be other issues, if the disks don't mount post new diags. 1 Quote Link to comment
DMP-UNRAID Posted January 21 Author Share Posted January 21 (edited) 5 hours ago, JorgeB said: Looks to be all back up and running now. Thanks for all the information/help it was greatly appreciated. I think seeing the "All existing data on this device will be OVERWRITTEN when array is Started" really freaked me out. Here's a link to the screenshot of the array - https://ibb.co/yQvfRcg I've attached the new diagnostics if you want to check it out. dmp-unraid-diagnostics-20240121-1751.zip Edited January 21 by DMP-UNRAID Quote Link to comment
trurl Posted January 21 Share Posted January 21 Looks good. You should probably do a parity check just to confirm. Or if you have one scheduled soon you could just wait on that. Unrelated, your appdata has some files on disk2 1 Quote Link to comment
DMP-UNRAID Posted January 21 Author Share Posted January 21 (edited) 4 hours ago, trurl said: Looks good. You should probably do a parity check just to confirm. Or if you have one scheduled soon you could just wait on that. Unrelated, your appdata has some files on disk2 Got that little bit at the end sorted also. Thank you folks for your help, really was greatly appreciated. Edited January 21 by DMP-UNRAID 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.