- 0xed unmmountable boot volume how to#
- 0xed unmmountable boot volume install#
- 0xed unmmountable boot volume drivers#
mpack Site Moderator Posts: 36667 Joined: 4.
0xed unmmountable boot volume how to#
What was inside the boot partition? ISTM if you knew enough to configure XP to use a boot manager, you should know how to reconfig the boot manager to use a new disk. You should be able to view sector 1028160 in CloneVDI and "View as MBR" to see the secondary "logical" partitions (of which there should again be two): in fact I'd appreciate if you posted a picture of that since I haven't seen logical partitions being used since DOS days.Ĭan you explain to me why this XP image had a separate boot partition? That isn't a typical layout for an XP system disk, because XP doesn't typically expose a separate boot manager. Īlso, didn't you say there was 3 partitions? So I assume that your second partition is an extended paritition containing a further partition map in the first sector. I assume you're using a boot manager that's attemption to locate the system partition by a address, and it isn't finding. Neither CloneVDI, nor apparantly the boot code in your VM, understands the contents of that second partition. "FAT16, Unknown(0f)" explains your problem. The VDI is a clone, so naturally it has the same content as the VHD. There's no need to show partition maps from both files. Sep 2008, 17:09 Primary OS: MS Windows 10 VBox Version: PUEL Guest OSses: Mostly XP
0xed unmmountable boot volume install#
Oh, and it will want to be reactivated, which usually isn't a problem provided it wasn't a branded OEM install (e.g.
0xed unmmountable boot volume drivers#
There is no correct value for this, it simply has to match what your XP image needs - so don't do anything unless you have the problem.įinal note: P2V is not a substitute for having a full setup CD: assuming you get XP to boot then it will go nuts with all the hardware changes, and it will need the setup CD to get drivers for hardware that wasn't present when it was first installed. If that happens then go into the VM settings and toggle the "IO APIC" setting. The next problem people encounter with an XP P2V is a black screen on boot. including boot sector? If so then I imagine that failure to run MergeIDE is your problem. I would also take the other steps (deleted intelppm.sys and agp400.sys) without waiting to find out if they actually cause trouble.Īre you absolutely sure you imaged the entire source drive, i.e. It is essential to run MergeIDE prior to the P2V imaging process, otherwise XP will be unable to identify the system drive on boot. It helps to have read the XP migration FAQ - though you should ignore the quaint advice about using dd - your Disk2VHD route is superior. That said, I've done it with XP several times with no problems. First, migration of an existing physical system to virtual (P2V) is not guaranteed to work.
0 kommentar(er)
