Unmountable boot volume win10 after VB upgrade

[bazagee]

My Bad here. Should have done some asking before upgrading...
I had VB 4.3.32 running on linux mint 17 with a fairly new Windows 10 vmdk build up and running. Now that win10 build was built using windows 8.1 which was the newest OS 4.3.32 offered. I tried changing that to windows 10 after the upgrade to VB 5.2. Likely my biggest error...

Win10 spins its wheels for a long time on the boot up screen before saying it can boot. It did try to fix itself, maybe running chkdsk in the background? But eventually can not start.

Any ideas before I start from scratch?
Thanks

[mpack]

I think you're barking up the wrong tree. As far as I know, the Windows 8.1 and Window 10 templates are equivalent - and VirtualBox provides a Win10 template not because one is really needed, but because otherwise noobs would choose totally inappropriate ones, like "Windows Other".

To me it sounds like you have some kind of problem with the VDI file, but you'd have to provide more diagnostic info, such as precise error messages and behaviour.

[loukingjr]

I'm with Don. Changing the template from 8.1 to 10 shouldn't affect anything. I've done it on a couple hosts and mine are still running.

[bazagee]

OK. Apart from the VB log viewer, what other diag files would be useful and where would I find them.

Thanks

[bazagee]

OK. Apart from the VB log viewer, what other diag files would be useful and where would I find them.

Thanks

Possible problem? Full log attached...

Code: Select all

00:04:24.437055 VMMDev: Guest Log: VBoxGuest: Windows version 10.0, build 10240
00:04:24.442428 VMMDev: Guest Additions information report: Version 4.3.32 r103443 '4.3.32'
00:04:24.442464 VMMDev: Guest Additions information report: Interface = 0x00010004 osType = 0x0003B100 (64-bit)
00:04:24.442530 VMMDev: Guest Additions capability report: (0x0 -> 0x0) seamless: no, hostWindowMapping: no, graphics: no
00:04:24.442573 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners.
00:04:24.442583 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
00:04:24.442603 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners.
00:04:24.442606 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
00:04:24.443069 VMMDev: Guest reported fixed hypervisor window at 0003fc00000 (size = 0x2400000, rc = VINF_SUCCESS)
00:04:24.443136 GUI: UISession::sltAdditionsChange: GA state really changed, notifying listeners.
00:04:24.443148 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary.
00:04:24.443154 GUI: UIMachineViewNormal::adjustGuestScreenSize: Adjust guest-screen size if necessary.
00:04:24.443157 GUI: UISession::sltAdditionsChange: GA state change event came, notifying listeners.
00:04:24.443160 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
00:04:24.818250 AioMgr1-N: Request 0x007f4528008120 failed with rc=VERR_INVALID_HANDLE, migrating endpoint /media/bgeorge/DataR5ext01/VMStore/PHW7/PHW7-flat.vmdk to failsafe manager.
00:04:24.818300 AIOMgr: I/O manager 0x007f452d8e6cc0 encountered a critical error (rc=VERR_FILE_AIO_NO_REQUEST) during operation. Falling back to failsafe mode. Expect reduced performance
00:04:24.818308 AIOMgr: Error happened in /home/vbox/vbox-5.0.2/src/VBox/VMM/VMMR3/PDMAsyncCompletionFileNormal.cpp:(1664){int pdmacFileAioMgrNormal(RTTHREAD, void*)}
00:04:24.818313 AIOMgr: Please contact the product vendor

Although the guest additions were upgraded to 5.x they haven't been able to be installed as there hasn't been a successful boot to do so.

Thanks for any suggestions

[mpack]

Notes on the log.

00:00:00.355213 File system of '/media/bgeorge/DataR5ext01/VMStore/PHW7/PHW7.vmdk' is ext4

What kind of storage does "/media/bgeorge/DataR5ext01/VMStore" refer to?

00:00:00.428275 AIOMgr: Endpoint for file '/media/bgeorge/DataR5ext01/VMStore/PHW7/PHW7.vmdk' (flags 00000723) created successfully
00:00:00.428479 AIOMgr: Endpoint for file '/media/bgeorge/DataR5ext01/VMStore/PHW7/PHW7-flat.vmdk' (flags 000c0781) created successfully

Oh no, not someone else who's fallen for fixed sized drive myths. Fixed size drive for performance? So naturally you were concerned about disk space, so you limited the size of the drive to 25GB which will lead to congestion and reduced performance. Nice one.

00:00:00.396081 GIM: Using provider 'HyperV' (Implementation version: 0)

What happens if you turn off the "Hyper-v" bit in the settings? I can't imagine any reason for needing this in an established (pre v5) VM.

00:04:19.389015 PIIX3 ATA: LUN#0: CD-ROM passthrough cmd=0x28 sense=2 ASC=0x3a ASCQ=0x1 VERR_DEV_IO_ERROR
00:04:19.389357 PIIX3 ATA: LUN#0: CD-ROM passthrough cmd=0x28 sense=2 ASC=0x3a ASCQ=0x1 VERR_DEV_IO_ERROR
00:04:19.389643 PIIX3 ATA: LUN#0: CD-ROM passthrough cmd=0x28 sense=2 ASC=0x3a ASCQ=0x1 VERR_DEV_IO_ERROR
00:04:19.389972 PIIX3 ATA: LUN#0: CD-ROM passthrough cmd=0x28 sense=2 ASC=0x3a ASCQ=0x1 VERR_DEV_IO_ERROR
00:04:19.390232 PIIX3 ATA: LUN#0: CD-ROM passthrough cmd=0x28 sense=2 ASC=0x3a ASCQ=0x1 VERR_DEV_IO_ERROR

You should probably unmount that host DVD drive.

00:04:24.818250 AioMgr1-N: Request 0x007f4528008120 failed with rc=VERR_INVALID_HANDLE, migrating endpoint /media/bgeorge/DataR5ext01/VMStore/PHW7/PHW7-flat.vmdk to failsafe manager.
00:04:24.818300 AIOMgr: I/O manager 0x007f452d8e6cc0 encountered a critical error (rc=VERR_FILE_AIO_NO_REQUEST) during operation. Falling back to failsafe mode. Expect reduced performance
00:04:24.818308 AIOMgr: Error happened in /home/vbox/vbox-5.0.2/src/VBox/VMM/VMMR3/PDMAsyncCompletionFileNormal.cpp:(1664){int pdmacFileAioMgrNormal(RTTHREAD, void*)}
00:04:24.818313 AIOMgr: Please contact the product vendor

Something up with that strange folder.

00:35:23.660394 AHCI#0: Port 0 reset
00:35:23.661495 AHCI#0P0: Cancelled task 21
00:35:53.660609 AHCI#0: Port 0 reset
00:35:53.661731 AHCI#0P0: Cancelled task 22
00:36:23.660810 AHCI#0: Port 0 reset
00:36:23.661868 AHCI#0P0: Cancelled task 23
00:36:54.692055 AHCI#0: Port 0 reset
00:36:54.693128 AHCI#0P0: Cancelled task 24
00:37:25.722928 AHCI#0: Port 0 reset
00:37:25.723987 AHCI#0P0: Cancelled task 25
00:37:56.738600 AHCI#0: Port 0 reset
00:37:56.739703 AHCI#0P0: Cancelled task 26
00:38:27.754493 AHCI#0: Port 0 reset
00:38:27.755595 AHCI#0P0: Cancelled task 27
00:38:57.754671 AHCI#0: Port 0 reset
00:38:57.755803 AHCI#0P0: Cancelled task 28
00:39:28.784849 AHCI#0: Port 0 reset
00:39:28.785901 AHCI#0P0: Cancelled task 29

Lots of these. Something very up with this host folder.

Incidentally - this has nothing to do with the guest OS, which hasn't tried to boot at this point.