SSD name is not correctly recognized after recovery
Hello,
I replaced my Toshiba HDD with a new Samsung Evo 850 500 GB SSD today with True Image 2017. The original Toshiba HDD had Windows 10 in GPT/UEFI mode, and its Windows 10 OS image was recovered onto the SSD using WinPE bootable media. For the recovery, I did not clone the HDD, and instead recovered the OS and two hidden system partitions. In BIOS, the Samsung Evo 850 SSD was recognized. After the recovery, the SSD was successfully bootable. But, on Windows 10, the SSD is not recognized as Samsung Evo 850, and instead is recognized as the original Toshiba HDD under the Device Manager of Control Panel. What could be wrong? Is there any Toshiba HDD signature included in the backup image? When I recovered the image, I did not select the "MBR and Track 0" box as recommended on p74 of the TI manual. Thanks.


- Log in to post comments

Yes, I am sure I am booted to the Samsung SSD drive as I see the partitions that I created on the Samsung drive. I shut down and restarted the PC after the recovery.
I did not remove the Toshiba drive from the desktop, and thus see two Toshiba drive names under Device Manager. But, I removed the original paritions on the Toshiba drive, and thus have only one OS partition on the SSD. I will disconnect the Toshiba drive to see what happens. But, I see Toshiba HDD and Samsung SSD under BIOS. if there is any other possibility, please suggest. Thanks.
- Log in to post comments

The drive boots because the EFI partiton on the SSD is what holds the BCD file which instructs the boot loader where the boot partition is. This is very good.
Without removing the Toshiba drive that drive is still appearing to Windows to be an attached device. Some fault in that is likely attributable to Windows Fast Startup feature.
I recommend that once the Toshiba drive is disconnected you perform a complete full shutdown of windows by running shutdown command from an admin command prompt, type: shutdown /p /f, This will force close all background and memory loaded applications and services including the base Windows kernel and all hardware ID's. When you again start Windows after this all attached hardware will reinitialize and applications and services will be reloaded fresh. See if that changes what you see.
- Log in to post comments

Thanks for your suggestion. I forced Windows 10 to shut down using the above command after disconnecting the Toshiba HDD. Then I started Windows again, but still see that Windows 10 recognizes the Samsung SSD as the Toshiba HDD. If there are other suggestions, please let me know. Thanks again.
- Log in to post comments

JY,
You are seeing this name in Windows Device Manager viewing the drive under the Disk drives branch of the Device Manager tree?
It is very strange that you do not see the Samsung drive listed in Device Manager. Can you post an attachment of a Disk Management view screenshot here?
- Log in to post comments

Here they are. I also attach a screenshot for Windows Explorer. The Toshiba HDD has G partition, and the Samsung SSD has C, D, and E partitions. Another weird thing is the DVD drive. I don't know why the DVD drive has a compact flash icon and its name ends with "CF".
Attachment | Size |
---|---|
399550-135496.jpg | 1.17 MB |
399550-135499.jpg | 785.91 KB |
- Log in to post comments

This problem was most probably caused because you booted the system with the two identical drives still connected, before you removed the original partitions from the source drive. Booting with two drives that Windows will consider to be identical will confuse and potentially corrupt the system.
If you still have the drive backup that you used to restore to the SSD, then it may be easiest to repeat that restore again, without having the Toshiba drive connected. Once you have restored and rebooted into Windows, and check that all looks correct again, then you can reconnect the Toshiba drive.
- Log in to post comments

The Images you provided are of no help. I asked for a screenshot of a Wndows Disk Management view. In Windows 10 right click on the Windows start button and select Disk Management from the resultant menu.
Are you taking screenshots with a camera? certainly looks that way to me. You should learn to use the Snipping Tool provided in Windows 10, in the 1607 Anniversary update this tool has become a bit hidden. I will assume you are running the 1607 update version of Windows 10 here. To locate the Snipping tool open Windows File Explorer and navigate to C:\Windows\System32\, locate the Application SnippingTool.exe. Right click on the file and select Pin to Task Bar which will create a shortcut to the app on your task bar making it handy to get to.
There is also new to Windows 10, Microsoft Snip. The link below will provide more details and tips on each tools usage:
http://www.thewindowsclub.com/snipping-tool-capture-screenshots-windows…
I am pretty much in agreement with Steve on the solution for this but would like to see a Disk Management screenshot as well.
- Log in to post comments

Well, I actually restored the back-up image after disconnecting the Toshiba HDD. I did not pay attention to the SSD drive name under Device Manager before reconnecting the Toshiba HDD. Since I still have the back-up image, I think it is worthwhile to re-try to recover it. I will share the outcome.
- Log in to post comments

What specific information can we find from a Disk Management view? Disk Management does not show the names of HDD or SSD, does it? It shows drives and their partitions like the screenshots that I posted using Device Manager. If you need a specific view from Disk Management, I can post it using the snipping tool. But, as I said above, I restored the image with the HDD being disconnected.
- Log in to post comments

The default Disk Managment view will show us all disk drives connected to your machine. It will also show all partitions of those disks as well as if a specific disk is a basic disk, if the disk is online or not and what drive letters have been assigned to each drive. Additionally, some additional details about each drive will be shown.
When you open Disk Management make sure you expand the window so that all connected disks are viewable before taking the screenshot.
The reason for you problem is more than likely because with both disks attached the Device ID of both drives is now the same because you restored the image of one to the other. This confuses Windows and will cause what is known as a Signature Collision. When this happens Windows will take one of the drives offline. Since you are able to boot the Samsung it is obvious that Windows boot routine decided that was the correct drive to boot from being that it was selected as the priority device in the bios and took the Toshiba offline however, because the Device ID originally belonged to the Toshiba drive that information remained unchanged in Windows because of that drive still being connected to the machine.
The question now is how to undo the naming errors that occured by your actions? In my view the simplest would be to rerun the restore to the Samsung drive and once completed boot to that drive again without the Toshiba connected.
You say that you are using the WinPE rescue media to perform the image recovery. How are you exiting or closing out the WinPE instance after the recovery is completed? The best way to end the WinPE session is to first close the Acronis True Image application window. What will remain is the command window for WinPE. At the prompt type wpeutil shutdown. This will end the WinPE session and shutdown your computer allowing you to safely remove the WinPE media and make other hardware changes if necessary prior to restarting the machine.
- Log in to post comments

I re-ran the recovery operation after disconnecting the Toshiba drive. I still see the naming error from Device Manager: the Samsung SSD is still recognized as the Toshiba HDD although the original Toshiba drive is not connected. It's not a Windows collision issue. I have attached the default Disk Management view.
I usually exit the WinPE bootable media by selecting the "shutdown" option after recovery. But, I followed the command option that you suggested above at this time.
Attachment | Size |
---|---|
399597-135508.jpg | 162.78 KB |
- Log in to post comments

JY,
What storage controller drivers are you using? Are the drivers Microsoft default drivers or are they drivers that you installed from your computer manufacturer?
If you have not installed the SATA controller drivers from your computer manufacturer I would recommedn doing that. I think that might solve this issue. Can you verify now that only 1 disk with the Toshiba name appears in your Device Manager?
- Log in to post comments

I was using a MS default drivers. I just installed SATA controller and chipset drivers from Dell (it's Dell XPS 8900 desktop), but the issue still persists.
Yes, I see 1 Toshiba HDD under Device Manager for Samsung SSD.
- Log in to post comments

Ok, did you try my earlier suggestion about uninstalling the drive in Device Manager using the right click menu? You might try that as Windows will reinstall the current drive attached upon restart. That is the last suggestion I have for this issue. If you choose to do this you will be asked if you would like to uninstall the driver for the device as well. If you choose no then the drivers you just installed will remain and Windows will use them for the drive controller when you restart the computer. If you choose yes to remove the drivers then the default Microsoft drivers will be used again on restart.
- Log in to post comments

I thought about it, but did not try it because it's the drive with an OS partition. If I choose yes to uninstall the current driver, is Windows going to reboot to select a default driver for a drive?
I have been contacted by Acronis tech support, and was asked to provide them with the same kind of device driver, BIOS images, and Acronis system report. Their first suggestion was to install Dell's SATA controller and chipset drivers, which did not resolve the issue. They say this can happen due to a few reasons, but rarely happens. If I get to resolve this, I will post the solutions to share.
- Log in to post comments

Good enough, hope you get it sorted.
- Log in to post comments