Link to home
Start Free TrialLog in
Avatar of RustyZ32
RustyZ32Flag for United States of America

asked on

VMware Migration Issue Error Device 0:0 - cold migration

VMware migration issue:
 
Migrating a P2V’d  VM that was an original HP DL 380 G5 physical server. The VM is now a virtual machine running Microsoft Server 2003 with SQL 05 with a RDM. The goal is to convert the RDM to a VMDK. We are running VSphere 5 migrating from an IBM 3500 series to an IBM V7000.
 
On the Cold migration, VSphere is showing about 18% complete while the array on the other end continues to increase up to about 580 GB out of the total VM size of approximately 600 GB. The VM continues to show 18% and stops after around a 580 GB transfer with a Device 0:0 error.
 
VMware and Google searches say it’s due to the CD Rom. VMSupport says that it works sometimes and other times it doesn’t. The process is magic per VM support. So, after taking that under advisement, we ran a Storage vMotion again (about 2 more times) with the same error. We tried to remove the CD rom drive completely, Storage vMotion’d with VM powered off with the same results.
Only other option is to V2V and try again. Or, create another VM with SQL 08 and be done with it. I’d rather see if there’s something worth a try to avoid more problems. Also, just need to add, I've done the same with other VMs with RDMs  that completed successfully within the same environment.
 
Any help would be greatly appreciated.
SOLUTION
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of RustyZ32

ASKER

Any idea why this occurs even with a cold migration? Do we know what could be preventing this even with the vCD removed on a cold migration as to take the CD completely out of the picture? Before I run a V2V, can this be resolved any other way? I appreciate the help. Would like to know what might be causing this if we remove the variable causing this.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Great work hanccocka!
To assist others and provide a connection between the original solution, my response and another great solution for others to follow.