August 3, 20251 yr Edit: Decided to just go with it. I panicked initially when I didn't see my VMs (wouldn't have been the end of the world, but Window installs are no fun), but then I created a new one and pointed to the vdisk.img file and everything seemed good. But I was having issues connecting to it. I should have taken a screenshot of the settings. But after messing around it finally connected but at half the speed that I have. After additional playing around I'm finally back to where I was.Original post below.I bought a newer cache drive to replace the one I am currently using. I have two cache drives, both NVME. Just need confirmation before I do this:Is the proper way to do this is by:Stop DockerStop any VMsMover rule to take everything in the drive I want to replace to move to my second cache (anything currently showing "cache01>array" or "cache01" alone to change to "cache01>cache02".Invoke MoverUnmount cache01remove physical driveinstall new physical drivemount new drivereversal of step 3 (Mover: cache02>cache01)invoke Moverrevert original state of the shares from step 3I guess I could just stop at step 8, but would I need to make any changes if I did so, like Docker or VM settings (I assume yes, as their settings are looking for a specific drive name (or something). Could I just rename the caches to avoid that (i.e. cache02 is now cache01)?Thank you! Edited August 3, 20251 yr by Sperko
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.