[SOLVED] "Device not migrated" - but my SSD works fine

[jchillin111]

Hello all. I have a Lenovo Legion Y530 15. This device came with a 1 TB HDD as the C:\ boot drive, no other storage. I then decided to upgrade and install an SSD Nvme, so now I have both a HDD and an SSD in my laptop. I then cloned the HDD to the SSD, and now I'm booting from my SSD (I even checked to make sure my SSD can boot without the HDD put in) - used Macrium Reflect.

So everything seems to be working fine; however, I keep seeing this message when checking the SSD out:

It says "Device not migrated" - but the device is working fine. Keep in mind, I believe this message appeared BEFORE I even cloned my SSD to have Windows - I believe it appeared the moment I put the SSD into the Laptop and started it up; however, the device is recognized in the Device manager and Disk Management areas, and it says it's working properly and healthy:

Is this something to worry about- what exactly does "Device not migrated" mean? It seems like the device works fine... Not sure what's happening. I'm guessing it's just a weird mistake, but I'm not sure. I don't want this to be an issue down the line.

 

[SteveRX4]

Is this a repeat post?

Try without the hdd. Make sure the ssd is first in the boot priority in bios?

 

[jchillin111]

Is this a repeat post?

Try without the hdd. Make sure the ssd is first in the boot priority in bios?

- I forgot to mark it as solved. Sorry. This is a different question. It's not really an issue, it's just I'm concerned.

Also, how did I fix the boot issue you may ask? I used the bcdboot commands (and diskpart) to rebuild the booting files, and also set the windows SSD drive to the c:\ drive (since it was the D:\ drive). The command was:

bcdboot D:\Windows /s w: /f UEFI

Note in regards to the code:
The D:\ drive was my solid state drive with all the proper windows partitions
W:\ is the volume that contains the SYSTEM module for booting. - I set it doing the "assign volume=w" command after selecting it. Issue fixed. No problem now. My C:\ was my HDD, but it had no partitions on it since I wiped it clean, so the PC was unable to boot. I put in a USB in my PC with Windows Recovery on it to go to the Command Prompt and switch my D:\ drive (SSD) to my C:\ boot drive (since it had all the necessary partitions). PC boots fine now.

SSD is first boot priority. The HDD doesn't have any partitions, it literally cannot boot - it doesn't even show up in the BIOS as a bootable option since it has no partitions (no boot drive anymore, I wiped it clean).
____
HERE IS MY CONCERN:

I'm just wondering if the message "Device not migrated" is a message I should be worried about, that's all I want to know. I have no issues at this time, just don't want to have issued down the line. And please understand the the Device not migrated message appeared BEFORE I cloned the SSD. It appeared the moment I put the SSD into my laptop and booted it on (no partitions or files inside of it). What does that message mean? The SSD shows up as this in my PC:

So as far as I know, I'm totally fine and there are no problems. PC boots, SSD seems to be working, but I don't want anything to get corrupted. Are there any concerns?

 

[SteveRX4]

Yeah. I think everything is OK. What software did your use for the migration/cloning?

 

[jchillin111]

Yeah. I think everything is OK. What software did your use for the migration/cloning?

I used Macrium Reflect. It worked fine. I just switched the boot module, removed HDD to test SSD booting (it worked), then I wiped the HDD. I think everything is fine too, wish me luck from here on out!

 

[SteveRX4]

I had to use Acronis with my AData. I liked Samsung's migration software better - but the SSDs are a bit too expensive for my liking.
My guess is that Macrium left soemthing weird on your PC.
Good luck. Happy gaming.