Diego Spinola Posted June 12, 2021 Share Posted June 12, 2021 Hi there guys, I'm migrating one of my servers to a new motherboard : Turned off array auto start Took a screenshot of the disk order Transported all HDDs and nvme's to the new system booted noticed that one of the cache nvme's was missing (never started the array) powered off and re-seated the missing nvme device from a pci-e slot that seems to be the issue into another booted again, every drive was recognized but the cache pool didn't populate with the missing drive automatically if I try to assign the missing drive in it's original place it shows the following warning "All existing data on this device will be OVERWRITTEN when array is Started" At no point have I started the array so I think I'm still safe...my initial instinct was to rebuild the flash from the online backup...BUT... it seem to have been overwritten just as I booted (even without starting the array...doh...) Seems to me that there is probably a very simple solution here but I'm not seeing it ...maybe because of the scary warning Can anyone give me an insight? Thanks Quote Link to comment
Diego Spinola Posted June 12, 2021 Author Share Posted June 12, 2021 (edited) Here's a couple of screenshots... still haven't dared to start the array out of fear : Now: Before: Edited June 12, 2021 by Diego Spinola Quote Link to comment
JonathanM Posted June 12, 2021 Share Posted June 12, 2021 Remove both cache devices from pool, start array to force Unraid to forget them, stop array and assign both as they were, the all existing... message should go away. Quote Link to comment
Diego Spinola Posted June 12, 2021 Author Share Posted June 12, 2021 Hi there @jonathanm thanks for the reply, just now I found an offsite (B2) "flash backup" generated last night which would certainly contain all config files needed for this to be repaired (don't really know where this cache pool info would be located but i'm sure it is in there right?), do you think that the safest way it is to do what you said even though I have some "cache only" shares on my server? Am I overthinking it and there's no real risk ? Using your plan I would: Turn VM and Dockers off Remove all devices from cache pool Start and Stop array Create a new cache pool with the same drives, in the same order as before Plan B : Try to recover the configs from yesterday's backup Thanks Quote Link to comment
Diego Spinola Posted June 12, 2021 Author Share Posted June 12, 2021 Something really weird just happened: I rebooted the server (Again without starting the array) and it seem to have "remembered" the disk: all by itself... any way to check that it won't destroy my data before staring the array? 1 Quote Link to comment
JonathanM Posted June 12, 2021 Share Posted June 12, 2021 45 minutes ago, Diego Spinola said: 3 minutes ago, Diego Spinola said: 3 minutes ago, Diego Spinola said: any way to check that it won't destroy my data before staring the array? Since the message is gone it should be fine. Quote Link to comment
Diego Spinola Posted June 13, 2021 Author Share Posted June 13, 2021 Thanks @jonathanm , it ended up working perfectly , strange behavior tho , I'll report it as soon as I'm finished with the upgrades 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.