stop 0x0000007b Inaccessible_boot_device

[azerrad]

hello,

i am using the latest version (from vm site) of vm converter,and using esx 3.5i ,after a good import machine of win2000 sp4 to my esx ,i am getting error "stop 0x0000007b Inaccessible_boot_device" ,here is my vmx configuration of the vm :

#!/usr/bin/vmware

config.version = "8"

virtualHW.version = "4"

floppy0.present = "false"

nvram = "RISHON_LZION.nvram"

deploymentPlatform = "windows"

virtualHW.productCompatibility = "hosted"

tools.upgrade.policy = "useGlobal"

powerType.powerOff = "default"

powerType.powerOn = "default"

powerType.suspend = "default"

powerType.reset = "default"

displayName = "RISHON_LZION"

extendedConfigFile = "RISHON_LZION.vmxf"

numvcpus = "2"

scsi0.present = "true"

scsi0.sharedBus = "none"

memsize = "512"

scsi0:0.present = "true"

scsi0:0.fileName = "RISHON_LZION_1.vmdk"

scsi0:0.deviceType = "scsi-hardDisk"

scsi0:1.present = "false"

scsi0:1.fileName = "RISHON_LZION_1.vmdk"

scsi0:1.deviceType = "scsi-hardDisk"

scsi0:2.present = "true"

scsi0:2.fileName = "RISHON_LZION.vmdk"

scsi0:2.deviceType = "scsi-hardDisk"

scsi0:3.present = "false"

scsi0:3.fileName = "RISHON_LZION_2.vmdk"

scsi0:3.deviceType = "scsi-hardDisk"

ide0:0.present = "true"

ide0:0.fileName = ""

ide0:0.deviceType = "atapi-cdrom"

ethernet0.present = "true"

ethernet0.startConnected = "false"

ethernet0.wakeOnPcktRcv = "false"

ethernet0.networkName = "VM Network"

ethernet0.addressType = "vpx"

usb.present = "true"

serial0.present = "false"

serial0.yieldOnMsrRead = "true"

serial0.fileName = "/dev/ttyS0"

serial1.present = "false"

serial1.yieldOnMsrRead = "true"

serial1.fileName = "/dev/ttyS1"

guestOS = "win2000serv"

uuid.location = "56 4d 4c 0b 43 72 0b 44-17 c4 67 69 e4 67 b9 a2"

uuid.bios = "56 4d 4c 0b 43 72 0b 44-17 c4 67 69 e4 67 b9 a2"

sched.cpu.affinity = "all"

sched.mem.affinity = "all"

ethernet0.generatedAddress = "00:50:56:a8:3e:fc"

ide0:0.clientDevice = "true"

ide0:0.startConnected = "false"

guestOSAltName = "Microsoft Windows 2000 Server"

scsi0:0.redo = ""

scsi0:1.redo = ""

scsi0:2.redo = ""

scsi0:3.redo = ""

tools.syncTime = "FALSE"

sched.cpu.min = "0"

sched.cpu.units = "mhz"

sched.cpu.shares = "normal"

sched.mem.minsize = "0"

sched.mem.max = "512"

sched.mem.shares = "normal"

sched.swap.derivedName = "/vmfs/volumes/47f51825-c21df0b2-4ddc-001f2907c728/RISHON_LZION/RISHON_LZION-c1001303.vswp"

sched.scsi0:0.shares = "normal"

scsi0:4.present = "true"

scsi0:4.fileName = "RISHON_LZION_3.vmdk"

scsi0:4.deviceType = "scsi-hardDisk"

sched.scsi0:4.shares = "normal"

scsi0:5.present = "true"

scsi0:5.fileName = "RISHON_LZION_2.vmdk"

scsi0:5.deviceType = "scsi-hardDisk"

sched.scsi0:5.shares = "normal"

scsi0:4.redo = ""

scsi0:5.redo = ""

note : after the migration nothing happened,only after that i changed the disks order only then i got this message...

what can i do ??

respectfully,

avi azerrad

[AWo]

Your guest operating system is configured for the wrong host adapter driver. This is not related to the .vmx file directly as you can see that the Windows boot process has already begun.

As far as I know the converter takes care about changing the driver. Which one have you configured in your guest (LSI or BusLogic)? Has the converter asked you which one you want to convert to?

AWo

[azerrad]

hi,

the converter didnt asked which HD driver i need he just deided for me that the driver will be buslogic ,and as i know buslogic driver is ok for windows 2000 ,i already used the converter many times and he never asked me that...

please continue to guide me...

respectfully,

avi azerrad

[AWo]

Try to add 'scsi0.virtualDev = "buslogic" ' to your guests ".vmx" file for at least the system drive (if it works for all SCSI drives) to make sure that it emualtes this one. Just in case the LSI is used by standard.

You can try to convert again, or...

...if that doesn't work you may use "Cristie CBMR" for configuring the driver. You can boot the guest with the Linux CBMR CD and start the "Dissimilar Hardware Server". With the included "hwwizard.exe" you can connect to CBMR (your guest) from a Windows system (choose the AMD PCnet32 NIC adapter under CBMR for network connectivity) and install the driver you need.

AWo

[azerrad]

hi,

this is the seconed time that i am converting this machine...where (in the vmx file that i uplodaed to the site ) excatly i need to put this line ??

2) it isnt a vm rule that win2000 always using buslogic controller ??

respectfully,

avi azerrad

[AWo]

where (in the vmx file that i uplodaed to the site ) excatly i need to put this line ??

Doesn't matter.

2) it isnt a vm rule that win2000 always using buslogic controller ??

Should...but you'll never know. I guess it's worth a try.

AWo

[continuum]

If scsi0.virtualDev is not defined - it uses scsi0.virtualDev = "buslogic" per default

[azerrad]

hi,

i added the line you told me about the buslogic and i am still getting the blue screen......

maybe i need to uninstall some applications before migration ??

respectfully,

avi azerrad

[theanykey]

Can you attach the converter logs

vmware-converter.log is available in the Source Physical Machine OS’s temp directory (C:\Windows\Temp\vmware-temp)

Can you also attach a full-view screenshot of diskmanagement on the physical machine?

Also, please post the contents of the boot.ini as found on the physical machine.

[aaserv08]

Your message

To: Andrew Servais

Subject: New message: "Re: stop 0x0000007b Inaccessible_boot_device"

Sent: Thu, 17 Apr 2008 05:43:35 -0400

did not reach the following recipient(s):

[aaserv08]

Your message

To: Andrew Servais

Subject: New message: "Re: stop 0x0000007b Inaccessible_boot_device"

Sent: Thu, 17 Apr 2008 06:57:48 -0400

did not reach the following recipient(s):

[aaserv08]

Your message

To: Andrew Servais

Subject: New message: "Re: stop 0x0000007b Inaccessible_boot_device"

Sent: Thu, 17 Apr 2008 11:42:24 -0400

did not reach the following recipient(s):

[azerrad]

hi,

this is the bootini file (after that i reattached the volume to another machine and took from theire the file..) :

timeout=30

default=multi(0)disk(0)rdisk(0)partition(1)\WINNT

multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Server" /fastdetect

2) i uploaded the vmtemp to here

3) hardisk 1 is scsi 0:0 and from this disk (the good one) the vm performing the boot.

[azerrad]

hi,

i just want to remind you that the migration was good 100% ,without any errors...

thank you for the support

respectfully,

avi azerrad

[theanykey]

I am not sure what to make of this ...

I see converter completing a 100% without failures.

However, I also see logging on converter renaming files to short names (this is normal) but with interesting output:

Error 183 renaming
.\vstor2-p2v30-6FBB3C2900FC0000000000000F000000\userlib\çåáåú îôòìéí\2008\Scan 7223 äùìîä ìãåç çåáåú ìáìâåìä àðä.tif to
.\vstor2-p2v30-6FBB3C2900FC0000000000000F000000\userlib\çåáåú îôòìéí\2008\SCAN72~2.TIF.

Error 1 setting SFN

File copied with wrong short name:
.\vstor2-p2v30-6FBB3C2900FC0000000000000F000000\userlib\çåáåú îôòìéí\2008\Scan 7223 äùìîä ìãåç çåáåú ìáìâåìä àðä.tif

Short name was originally SCAN72~2.TIF

This might be fine, but I have a suspicion that these funny characters are infact international keyboard characters (like chinese calligraphy or indian letters). I have not seen this before so I do not know what effect this would have on the result. Assuming that this might or may be the cause, and for testing purposes, you might want to re-do the conversion but opting not to resize but rather maintain the disk sizes (this will then convert the disk block-by-block instead of file-by-file)

[azerrad]

hi,

so you want me to use again vmware converter but this time without changing the parameters of drive c ? (the other drive i suppose can be changed)

2) there is any diffrenet between migrate from converter boot (that is doing everything very very slow) and between the windows version of converter (that i am using it) ,there is any advantage from the boot cd ?

respectfully,

avi

[azerrad]

those logs are from c drive ?

[theanykey]

Hard to say because I am not certain about this error. This is one of those issues I would recommend filing a support request with technical support for. I would not resize any partitions strictly for testing purposes. If we get the same resulting stop7b then we can exclude these warnings as the culprit. However, if we end up resolving the issue, you can choose to go back and select specific drives to resize.

[azerrad]

hi ,

this time i used converter without changing nothing...(i didnt resize the volumes) ,but this time the error :opreating system not found"

so i changed the disks order and again i am getting the same blue screen.

anyway thank you...

respectfully,

avi azerrad