VMware

This Question is Answered

1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
6 Replies Last post: Jun 5, 2009 2:26 PM by ebonick  

Converted Solaris image panics "cannot mount root path" posted: Aug 18, 2007 4:16 PM

Click to view radman's profile Enthusiast 75 posts since
Aug 9, 2006
I'm migrating some machines from VMware Server to ESX. I converted a Solaris 10 machine that had an IDE disk, using Converter.

The failsafe kernel boots fine. But, when I try to boot the real kernel, it immediately panics with "cannot mount root path". I took a look (under the failsafe kernel) at the vfstab, and it looked funky (the / device name was something like /dev/dsk/c1td1s0), so I changed it to match the name mounted for root under the failsafe kernel: /dev/dsk/c1t0d0s0, and even rebuilt the boot archive, but the same panic recurs. I also tried booting with -r, but that didn't help either.

There was some kind of message during the conversion saying that the image couldn't be customized I think but I didn't write it down I'm afraid. It said it completed successfully.

Anybody have any idea what might be going wrong here? The Hard Disk is "SCSI(0:0) Hard Disk 1" according to Settings. Could the device naming be different between the failsafe and regular kernels?

It's panicing when vfs_mountroot calls rootconf.

Any tips much appreciated!
Click to view tom.elder's profile Novice 12 posts since
Aug 11, 2005

step 10) should read /a/etc/vfstab

but thanks for figuring the rest out; very helpful

Tom

Click to view publish_or_perish's profile Lurker 3 posts since
Apr 7, 2008
That was an extremely helpful starting point. Though most of it was relevant, the instructions
didn't work for me migrating my Solaris 10 Update 4 (w/Trusted Extension) IDE-based VM from
Fusion 1.1.1 to ESX 3.5. It took quite bit of research experimentation to figure make it work.

The following are a combination of your recommendations, along with the changes & clarifications
I added to get it to work for my VM migration from Fusion to ESX.

Picture 15.png

Click to view acruizu's profile Enthusiast 29 posts since
May 13, 2008
Thank you very much. Your post was very helpfull.
Click to view MPowerLabs's profile Lurker 1 posts since
Nov 10, 2008

The above posts where very helpful. This is what I ended up doing when I had a similar problem after updating ESX from 3.0 to 3.5:

  1. boot to failsafe
  2. add swap space --- swap -a /dev/dsk/cxtxdxsx
  3. cp /etc/path_to_inst /a/etc/path_to_inst
  4. edit /a/boot/solaris/bootenv.rc with the proper boot device
  5. rm /a/etc/devices/*
  6. rm /a/dev/rdsk/c*
  7. rm /a/dev/dsk/c*
  8. rm /a/dev/cfg/c*
  9. devfsadm -v -r /a
  10. reboot /w -arvs
If the reboot fails, go back and check bootenv.rc. I had a problem with the file reverting back to the original boot device.
Click to view ebonick's profile Novice 21 posts since
Aug 15, 2006
I have a similar issue where after a short while the vm will go into a reboot loop but will boot into failsafe fine. I tried all of the above steps, but nothing helped. I do a see W real quick before the vm reboots. I have never used Solaris before and am in charge of keeping this vm running, but the reboot loop is stunmping me. Anyone have any suggestions?

VMware Developer

SDKs, APIs, Videos, Learn and much more in the Developer community.

Learn More

Developer Sample Code

Increase your developer productivity with VMware API sample code.

Learn More

VMworld Sessions & Labs

Online access to the latest VMworld Sessions & Labs and online services.

Learn more

Purchase PSO Credits Online

Purchase credits to redeem training and consulting services online.

Buy Now

Community Hardware Software

View reported configurations or report your own.

Learn More

VMware vSphere

Come witness the next giant leap in virtualization.

Register Today

Communities