Share via

"Device not migrated" issue on drive after installing second HDD

Anonymous
2018-08-30T19:45:59+00:00

I've recently acquired a second HDD, and wanted to set up a Storage Spaces Two-way Mirror. I initially had both drives plugged in and visible in the Disk Management interface (with the new disk unallocated) while I backed-up the contents of my original drive as I knew this process would wipe both drives.

Today, when I went to use the Storage Spaces tool it only showed the original drive in the list. Looking into Disk Management now, the new disk isn't visible any more - but it's still visible in the BIOS. When I look in Device Manager, viewing the Properties > Events for the drive had the following event listed:

Device not migrated

Device IDE\DiskST1000DM010-2EP102______________________CC43____\5&22a8ae90&0&0.0.0 was not migrated due to partial or ambiguous match.

Last Device Instance Id: USBSTOR\Disk&Ven_Generic&Prod_Flash_Disk&Rev_8.07\4B1F0FBC&0

Class Guid: {4D36E967-E325-11CE-BFC1-08002BE10318}

Location Path:

Migration Rank: 0xF000F8008000F130

Present: false

Status: 0xC0000719

This originally complained about an old (since removed) Garmin USB device, so I manually went through the registry and removed all reference to it. The above message is now for the generic USB device listed after the Garmin USB device in the registry at all points, and appeared after I uninstalled the disk and restarted the computer.

I'm at a loss, could anyone assist please?

Windows for home | Windows 10 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

4 answers

Sort by: Most helpful
  1. Anonymous
    2018-09-04T08:21:36+00:00

    I've just run the Hardware & Devices Troubleshooter and it reported "Troubleshooting couldn't identify the problem".

    The PC was self-built 6 years ago, using an Asus P8H61-MX motherboard.  It's run without issue for 6 years, initially with a small SSD as the C: drive and a 2.5" 120Gb HDD for data (D:), and over the years I've upgraded the C: drive SSD to 250Gb and the data drive to 1Tb 3.5".  This failed after 6 months, and while waiting for the warranty replacement from Seagate, I bought a WD 1Tb drive.  That is (still) working fine.  Having got the replacement from Seagate, I thought I'd set up a Storage Pool for disk mirroring of my data drive - and that's when I found that it wouldn't let me configure the Seagate drive, even though it was visible in the BIOS on my PC - and visible at the Windows level for configuration in Disk Management when installed in a different PC.

    I've also tried all the obvious things like swapping leads and SATA ports in my PC, and in all cases it can see the WD drive at Windows level, but never the Seagate one, even though that is visible to Windows when plugged into another PC. 

    I think I'm stuck!  Any help appreciated.  Martin

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2018-09-02T21:34:04+00:00

    Thanks for the updates, Martin. Sorry about the long delay.

    Can you tell us the exact make and model of your PC? Or if not, at least the motherboard? 

    We agree that when the device is being recognized completely by the BIOS and by another PC, the issue must be lurking with the system. Please perform Harware and Devices Troubleshooter: Go to Settings > Update & Security > Troubleshoot. Scroll down and look for Harware and Devices.

    Please let us know the message return so we may know which steps to try next. Please remember to include the PC make and model / Motherboard on your next reply.

    Kind regards.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-09-01T16:35:17+00:00

    Hi Marc,

    We'd already done A and B, and no BIOS changes have been made in months. Aside from that, we've also since confirmed that the drive works fine in a different PC.

    An additional piece of information, we looked at the functional drive's Event log in Device Manager, and found that it has the same "device not migrated" warning despite it working fine... so we're back to square one.

    Thanks,

    Martin

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-08-31T05:58:50+00:00

    Thanks for posting, Martin. 

    It is a bit of a surprise because you were able to use the HDD initially before it fail. I hope that the ideas below will be able to help. 

    A. Run Windows Update while the new HDD is on - To check for updates now, select the Start  button, and then go to Settings  > Update & security  > Windows Update, and select Check for updates. If Windows Update says your device is up to date, please proceed to method B.

    B. Check your motherboard manufacturer for driver updates - Or you still have the CD that came with your motherboard, please look for any USB device related drivers and install them. The PC will reject the installation if the driver being installed is already installed. Once done, and the HDD is still not recognized, you will need to unplug it from the motherboard, and plug it back. - you will also need to double-check the wires. 

    C. Double check the BIOS settings, or bring back any settings that were changed right before the issue happened. BIOS user interface may vary on bran and model of he unit. Please ask your PC/motherboard maker for clear guidelines.

    While the suggestions have the potential to resolve the issue, please understand that the steps are also like to help us with the isolation. These are yet to be the concrete fix, but should help. Please respond to this thread to let me know how the issue progresses. Similarly, if you have more questions, please inform me by replying to this post.

    Kind regards.

    Was this answer helpful?

    0 comments No comments