dkraut
asked on
ESX 3.5 Upgrade Failed - Cannot Boot
attempted to upgrade from "ESX 3.5 Update 3" to "ESX 3.5 update 5" using a CD locally at the server. Shortly after the Install process began, it failed with a fatal error (see attached image). We tried differerent media and ran the media test, which passed. We then decided to backout and just reboot, but now the server will not even boot! I'm getting an error 15 file cannot be found? See attached image. Any ideas on what went wrong on how to resolve?
Are the VMs on the local datastore or on shared storage (NAS/SAN)?
ASKER
Local Datastore. No connection to SAN for this server.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
No backups since it's a dev server, but losing the VM's would be painful. It's an IBM x3650 with (5) 500GB SATA drives in a RAID 5 array. I've considered reinstalling, but how do you do that while preserving the datastore?
So I guess I'm the only one that's run into this lovely upgrade oddity? :)
So I guess I'm the only one that's run into this lovely upgrade oddity? :)
ASKER
OK Thanks, before I try the reinstall, one other thought came up... Is it still possible to obtain ESX 3.5 Update 4? I'm thinking that possibly it will perform the upgrade without error. I've searched but cannot find any version other than Update 5.
I would install ESX Update 5 straight off, this way you kill 2 birds with one stone
ASKER
ok guys, based on some info I found on the HCL regarding the IBM x3650, I decided to install ESX 4 Update 2 and it found and allowed me to preserve the datatstore. I have it back in vcenter and it appears to be fine now. The only issue is that the vm's are all showing as orphaned, but I was able to remove them and then add to Inventory to resolve. Thanks for the guidance!! Cheers!
If you're feeling lucky you can now go to ESX 4.1 and you'll be able to connect the ESX hosts to your domain...good stuff. Now you've got the warm and fuzzies since everything came up, nice.