COPYP2V ERROR

User discussion and information resource forum for the TeraByte OS Deployment Tool Suite.
ostapvoip
Posts: 58
Joined: Fri Feb 08, 2013 10:32 pm

COPYP2V ERROR

Post by ostapvoip »

Hi,

Error starting virtual machine after creating virtual disk for VMware through COPYP2V.
Windows 8.1 BSOD
Windows 10 BSOD
Windows 7 OK
Apparently the problem is with the script OSDTOOL.
The latest versions of COPYP2V, OSDTOOL, and VMware were used.

Thanks,
Viktor
TeraByte Support
Posts: 3035
Joined: Thu May 05, 2011 10:37 pm

Re: COPYP2V ERROR

Post by TeraByte Support »

What is the bsod?

0x7b is the storage drivers.

On 8/20/2019 11:10 AM, ostapvoip wrote:
> Hi,
>
> Error starting virtual machine after creating virtual disk for VMware through COPYP2V.
> Windows 8.1 BSOD
> Windows 10 BSOD
> Windows 7 OK
> Apparently the problem is with the script OSDTOOL.
> The latest versions of COPYP2V, OSDTOOL, and VMware were used.
>
> Thanks,
> Viktor
>
>

ostapvoip
Posts: 58
Joined: Fri Feb 08, 2013 10:32 pm

Re: COPYP2V ERROR

Post by ostapvoip »

Inaccessible_boot_device
Try it yourself and see.
The script COPYP2V should integrate lsi_sas and lsi_scsi drivers.
Trying to add drivers manually through OSDTOOL did not change anything, again BSOD.
Last edited by ostapvoip on Wed Aug 21, 2019 5:49 am, edited 1 time in total.
TeraByte Support
Posts: 3035
Joined: Thu May 05, 2011 10:37 pm

Re: COPYP2V ERROR

Post by TeraByte Support »

That is 0x7B.

So it's either the driver needed for the controller you chose in the
machine config isn't installed or available (what did you select? You
can run osdtool.tbs against it manually to select a different driver if
one exists in windows or you have the one needed or choose a different
controller) or you didn't setup the VM with enough memory (what did
you select? - select a 2G) or the file system may not be mountable and
need chkdsk/f run against it (boot a recovery iso / media and check).


On 8/20/2019 9:31 PM, ostapvoip wrote:
> Inaccessible_boot_device
> Try it yourself and see
>
>
ostapvoip
Posts: 58
Joined: Fri Feb 08, 2013 10:32 pm

Re: COPYP2V ERROR

Post by ostapvoip »

2G ... 4G memory allocated for virtual machine
Standard configuration for Windows 10 or Windows 8.1 or Windows 7
Example https://i.vgy.me/sF3XaR.gif
Eric
Posts: 212
Joined: Mon Sep 05, 2011 6:53 pm
Location: France

Re: COPYP2V ERROR

Post by Eric »

You can try the new version of TBOSDT (Version 1.91). Your issue has normally been fixed on that version.
ostapvoip
Posts: 58
Joined: Fri Feb 08, 2013 10:32 pm

Re: COPYP2V ERROR

Post by ostapvoip »

Thank you!

I think the problem remains if you use the script OSDTOOL 2 or more times.
Made a little movie https://www.upload.ee/files/10430411/vm ... l.mp4.html
If you restore the registry from a backup in a script OSDTOOL, then Windows will boot normally.
Eric
Posts: 212
Joined: Mon Sep 05, 2011 6:53 pm
Location: France

Re: COPYP2V ERROR

Post by Eric »

Many thanks for this feedback.

Two questions:
- I see that you are installing the lsi_sas driver. According to your test, is it mandatory? What if you don't install it?
- Can you send the SYSTEM registry after the first correct boot?
Thanks in advance.
TeraByte Support
Posts: 3035
Joined: Thu May 05, 2011 10:37 pm

Re: COPYP2V ERROR

Post by TeraByte Support »

Make sure you're using the latest tbosdtw.exe, it wasn't the script, it
was a regression in the .exe on move to unicode version which caused del
key to be treated as del key /s

On 9/1/2019 5:55 AM, ostapvoip wrote:
> Thank you!
>
> I think the problem remains if you use the script OSDTOOL 2 or more times.
> Made a little movie
>
> [
> https://www.upload.ee/files/10430411/vmware_osdtool.mp4.html
> ](https://www.upload.ee/files/10430411/vmware_osdtool.mp4.html)
>
> If you restore the registry from a backup in a script OSDTOOL, then Windows will boot normally.
>
>

ostapvoip
Posts: 58
Joined: Fri Feb 08, 2013 10:32 pm

Re: COPYP2V ERROR

Post by ostapvoip »

Hi, Eric

1. I thought that installing the lsi_sas driver was required, as it was in Windows 7 https://i.vgy.me/rcTb9Y.png
2. Files https://www.upload.ee/files/10432128/SYSTEM_.7z.html

SYSTEM1_PLUS_LSI_SAS - after boot OK, OSDTOOL script removed all the drivers and install LSI_SAS, this is the first use of OSDTOOL
SYSTEM2_PLUS_LSI_SAS_NO_BOOT - after boot FAIL, OSDTOOL script removed all the drivers and install LSI_SAS, this is the second use of OSDTOOL

I also did a second test.
Windows 10 was installed on the virtual machine.
Then I copied VMDK to HDD and applied OSDTOOL for the first time, OK.
Then I copied HDD to VMDK and applied OSDTOOL a second time, BSOD.

SYSTEM1_HDD - after boot OK, OSDTOOL script removed all the drivers, this is the first use of OSDTOOL, Windows was previously copied from VMDK to HDD via IFW
SYSTEM2_VMDK_NO_BOOT - after boot FAIL, OSDTOOL script removed all the drivers, this is the second use of OSDTOOL, Windows was previously copied from HDD to VMDK via IFW

TBOSDT Version 1.91, OSDTOOL 4.35
Thanks,
Viktor
Post Reply