- Feb 9, 2012
- 7
- 0
- 18,510
This is an odd problem I cannot seem to find an answer for.
I have replicated this on 3 different pcs. 2 running windows 7, 1 Windows 10
Scenario=
PC has internal 500gb Samsung EVO SSD
Attached at various times are a selection of external HDs. WD, Seagate, Toshiba, various mfg.
I perform a clone upgrade from 500gb SSD to 1tb SSD. Same Samsung EVO.
After the clone, the external HDs will not recognize. in disk management, will not show up.
In device manager the WD will install the WD SES Device, but that's it.
They will often pop up under the disk drives section of device manager, but only with exclamation mark, and says device cannot start.
Remove usb controller drivers, reinstall, no change.
Plug the external HD into a different pc, comes up no problem.
Replace the new ssd with the original 500gb, reboot and devices come up, no problem.
It must be something with hd signatures? I can't find any reference to this issue.
The cloning was done with software , EaseToDo , then With Acronis, and then with a standalone hardware cloning unit.
All 3 methods have the same result.
If anyone has seen this or can offer a clue, it would be greatly appreciated.
Mark
I have replicated this on 3 different pcs. 2 running windows 7, 1 Windows 10
Scenario=
PC has internal 500gb Samsung EVO SSD
Attached at various times are a selection of external HDs. WD, Seagate, Toshiba, various mfg.
I perform a clone upgrade from 500gb SSD to 1tb SSD. Same Samsung EVO.
After the clone, the external HDs will not recognize. in disk management, will not show up.
In device manager the WD will install the WD SES Device, but that's it.
They will often pop up under the disk drives section of device manager, but only with exclamation mark, and says device cannot start.
Remove usb controller drivers, reinstall, no change.
Plug the external HD into a different pc, comes up no problem.
Replace the new ssd with the original 500gb, reboot and devices come up, no problem.
It must be something with hd signatures? I can't find any reference to this issue.
The cloning was done with software , EaseToDo , then With Acronis, and then with a standalone hardware cloning unit.
All 3 methods have the same result.
If anyone has seen this or can offer a clue, it would be greatly appreciated.
Mark
Facebook
Twitter
Instagram