0

I installed Windows 8.1 64B in a VM on Proxmox-VE. It was running fine for a few days until it needed to be rebooted (updates). First I tried reinstalling the OS which worked, until it needed to be rebooted and then it fell back into the loop of Automatic repair. It eventually ends in "Automatic repair couldn't repair your PC". I can't get it to boot at all.

What's even more concerning is that C:\ is listed as "System Reset" and I believe D:\ is my "boot" partition.

Output of diskpart

The bootrec command doesn't find an OS either. Output of bootrec /ScanOS

Any ideas on how to fix this? How could this have happened? I let Windows automatically partition the drive during install.

Proxmox settings for the VM: Proxmox Settings 1 Proxmox Settings 2

I believe this issue is Proxmox related. Others have had these specific issues running Windows 8 in Proxmox. Ex. forum.proxmox.com/threads/14310-windows-8-1

6
  • Your question is off topic for Serverfault because it doesn't appear to relate to servers/networking or desktop infrastructure in a professional environment. It may be on topic for Superuser but please search their site for similar questions that may already have the answer you're looking for.
    – masegaloeh
    Nov 26, 2014 at 3:17
  • Proxmox is a server virtualization management tool. proxmox.com/proxmox-ve
    – 에이바
    Nov 26, 2014 at 14:25
  • Yes, I aware of that :). However, judging from your problem description and your conversation with Somescout below, it doesn't related to proxmox but to windows itself
    – masegaloeh
    Nov 26, 2014 at 14:32
  • I believe it is Proxmox related. Others have had these specific issues running Windows 8 in Proxmox. Ex. forum.proxmox.com/threads/14310-windows-8-1
    – 에이바
    Nov 26, 2014 at 14:34
  • Ahh... I wasn't aware of that. Please include that links in your question too, so other user/mod consider to reopen this question.
    – masegaloeh
    Nov 26, 2014 at 14:46

1 Answer 1

1

Check if there crash dump file in windows folder (%SystemDrive%:\Windows\MEMORY.DMP or file in \Windows\MiniDump) with corresponding date.

If file is there, you can analyze it with WinDbg (Open crash dump and !analyze) and see why system not starting.

10
  • I found the MEMORY.DMP file in D:\Windows, but how can I open it or take it out of the VM? I'm not actually logged into the PC, I got to the command prompt through the "Repair Your PC" recovery option.
    – 에이바
    Nov 25, 2014 at 19:24
  • 1
    Simplest way to copy it over network (if available): 1) use wpeutil InitializeNetwork to start network stack, 2) check if it got address over dhcp: ipconfig 3) authenticate on target share net use \\computername\sharename /user:username password 4) Copy file. If somehow it not working, you can either mount virtual hard disk with system volume to another VM or mount some temporary virtual drive to this VM.
    – Somescout
    Nov 25, 2014 at 19:29
  • i.imgur.com/E6pCGQT.png
    – 에이바
    Nov 25, 2014 at 19:35
  • 1
    Volume 1 contains BootManager. Normally (if system started successfully) it have no drive letter assigned, but during repair or WinPE boot - it will get it. So, it's not issue.
    – Somescout
    Nov 25, 2014 at 19:44
  • 1
    Maybe it's network driver issues (but still, you can ping gateway... try checking route tables). If you can boot from live cd and network works there, you can just mount system drive (in Windows or via NTFS3G in Linux) and transfer crash dump to another host. Or, again, you can mount system drive to another Windows VM and access it from there.
    – Somescout
    Nov 26, 2014 at 6:48

Not the answer you're looking for? Browse other questions tagged .