Installing Solaris 10 on ESX 3.0.2 fails with Disks No Found Error

[mysza78]

I am trying to install Solaris 10 x86 on one of our ESX Servers (running 3.0.2). I am able to successfully boot an installation DVD or CD (tried both) to start the installer, go through IP Address, hostname etc setup and start the installer. However, shortly after I get an error saying "No Disks found. Check to make sure disks are cabled and powered up. Press OK to Exit." I am using a local storage on the server. Has anyone else ran into that issue and found a solution for it?

[mike_laspina]

Post your vmx and I will try it over here.

[mike_laspina]

This attached vmx works on my hosts with the LSI adaptor but its from an ESX 3.5.0 server.

[mysza78]

Sorry, I will be away from the office this week on a training so I won't have access to the server to look into it. I will return to it next week.

Attached is my vmx file.

Thanks!

Ps. For some reason I cannot see my attachment so just in case here is the content:

#!/usr/bin/vmware

config.version = "8"

virtualHW.version = "4"

floppy0.present = "true"

nvram = "UX3.nvram"

deploymentPlatform = "windows"

virtualHW.productCompatibility = "hosted"

tools.upgrade.policy = "useGlobal"

powerType.powerOff = "default"

powerType.powerOn = "default"

powerType.suspend = "default"

powerType.reset = "default"

displayName = "UX3"

extendedConfigFile = "UX3.vmxf"

numvcpus = "2"

scsi0.present = "true"

scsi0.sharedBus = "none"

scsi0.virtualDev = "lsilogic"

memsize = "512"

scsi0:0.present = "true"

scsi0:0.fileName = "UX3.vmdk"

scsi0:0.deviceType = "scsi-hardDisk"

ide0:0.present = "true"

ide0:0.clientDevice = "true"

ide0:0.deviceType = "cdrom-raw"

ide0:0.startConnected = "false"

floppy0.startConnected = "false"

floppy0.clientDevice = "true"

ethernet0.present = "true"

ethernet0.networkName = "Internal"

ethernet0.addressType = "vpx"

ethernet0.generatedAddress = "00:50:56:ab:0a:42"

guestOSAltName = "Sun Solaris 10 (32-bit)"

guestOS = "solaris10"

uuid.bios = "50 2b c7 b6 6d 12 0d 37-a0 f9 03 c3 e3 68 4e 77"

toolScripts.afterPowerOn = "true"

toolScripts.afterResume = "true"

toolScripts.beforeSuspend = "true"

toolScripts.beforePowerOff = "true"

scsi0:0.redo = ""

uuid.location = "56 4d 23 07 0c 80 aa 10-d7 32 ce c6 e3 15 1a 79"

sched.swap.derivedName = "/vmfs/volumes/47151d6d-4cc13d78-820b-00025567144e/UX3/UX3-99f698d3.vswp"

hostCPUID.0 = "00000002756e65476c65746e49656e69"

guestCPUID.0 = "00000002756e65476c65746e49656e69"

userCPUID.0 = "00000002756e65476c65746e49656e69"

hostCPUID.1 = "00000f240002080b000000003febfbff"

guestCPUID.1 = "00000f280001080b000000000febbbff"

userCPUID.1 = "00000f240002080b000000003febfbff"

hostCPUID.80000001 = "00000000000000000000000000000000"

guestCPUID.80000001 = "00000000000000000000000000000000"

userCPUID.80000001 = "00000000000000000000000000000000"

evcCompatibilityMode = "FALSE"

[dmadden · Accepted solution]

Apply esx 3.0.2 patches 1005190 and 1005110. These provide Solaris 10 U5 support. They also require a VM and host reboot. I had the same problem until I applied these patches.

[mysza78]

Thanks, I will give it a shot. I was going to upgrade it to 3.5 within next few weeks but I have to test it first on another box so instead of waiting to see the results, I will apply those patches. I will let you know if that changed anything.

Thank you!

[mikepodoherty]

We are in the process of upgrading to ESX 3.5 and will test the Solaris 10 x86 U5 (05/08) update shortly. I'll let you know if we run into any issues. We have successfully installed U5 on 3.0.1.

I'll also check with the Solaris Admins to see if there were any issues with the install of U5 onESX 3.0.1. My memory is that they needed to be sure that LSI Logic was set and that we needed to use the DMX SAN and not the Clariion SAN. Not sure why the Clariion was a problem but the install on the DMX was without issues.

Mike

[mysza78]

We will be using local HD so storage should not be a problem.

Thanks for checking!

[mysza78]

Looks like the patches fixed the issue. I am 10% into installation and not expecting any more issues. Thank you all who helped to get the issue resolved. Your help is very much appreciated!