Herdie27 Posted August 1 Share Posted August 1 (edited) So I recently upgraded my server from an old dell to a newer HP server and transferred all my drives from one to the other. I have 7 total drives plus a cache drive. After working through some other problems (I'll list them for reference) and solving them via googling there's one thing I can't figure out/ wanted to make sure of because I'm pretty sure of what to do. Problems fixed before this point: 1. Had to swap USB drives my new server didn't like my kingston USB and wouldn't boot. Got Unraid on a new USB and it's working and booting fine 2. Couldn't connect to the internet with on board ethernet ports and used the 2.5 Gig Nic I installed to connect to the internet so I could accomplish problem 3 (During this time I also upgraded Unraid to version 6.12.11). 3. Had to replace the key for my UNRAID OS as the new license had to be attached to the new GUID of the new USB After booting up the new server all of the drives are labeled as "wrong". This is stopping me from spinning up the drives and starting the array. Even though every single drive has the exact same name/ serial number attached to it and they are reassigned in the exact same way. From what I can gather I have to "new config" the whole thing. From what I can gather this won't do anything to the data on my drives. FYI, I'm a photographer/ videographer and the family data hoarder so the data drives need to stay intact, this is also why I have 2 parity drives. If anyone can detail out what I should do/ point me in the right direction it'd be much appreciated. Please let me know if you have any questions for me. warlock-diagnostics-20240802-1528.zip Edited August 3 by Herdie27 More detailed info Quote Link to comment
JorgeB Posted August 1 Share Posted August 1 This can happen if a RAID controller was used before or now, please post the diagnostics. Quote Link to comment
Herdie27 Posted August 3 Author Share Posted August 3 On 8/1/2024 at 1:22 AM, JorgeB said: This can happen if a RAID controller was used before or now, please post the diagnostics. Updated my post with the diagnostics Quote Link to comment
Solution JorgeB Posted August 3 Solution Share Posted August 3 The names changed, likely due to a RAID controller being used before, if that's the only thing that changed, you can do a new config and re-assign all devices as thet were, then check parity is already valid before array start, if any of the disks comes up unmountable post new diags. P.S. you can still see the serial in the old vs new names, to assign them correctly ST12000VN0008-2YS101_ZV70E7A4 ST12000VN0008-2Y_ZV70E7A4_35000c500e7a464f1 Quote Link to comment
Herdie27 Posted August 3 Author Share Posted August 3 Thanks very much! I've done more reading about the new config tool and everything went through just fine. Everything looks like it's working perfectly. 1 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.