CI 115925 - Created file, images, TOC entry

Author: v-miegge

articles/virtual-machines/troubleshooting/media/troubleshoot-guide-not-a-bootable-disk/1.jpg

@@ -70,18 +70,20 @@
       href: boot-diagnostics.md
     - name: BitLocker errors
       href: troubleshoot-bitlocker-boot-error.md
-    - name: Checking file system errors
-      href: troubleshoot-check-disk-boot-error.md
     - name: Blue screen errors
       href: troubleshoot-common-blue-screen-error.md
-    - name: VM startup is stuck
-      href: troubleshoot-vm-boot-configure-update.md
+    - name: Checking file system errors
+      href: troubleshoot-check-disk-boot-error.md
     - name: Critical service failed
       href: troubleshoot-critical-service-failed-boot-error.md
+    - name: Not a bootable disk
+      href: troubleshoot-guide-not-a-bootable-disk.md
     - name: Reboot loop
       href: troubleshoot-reboot-loop.md
     - name: Stuck at Windows update
       href: troubleshoot-stuck-updating-boot-error.md
+    - name: VM startup is stuck
+      href: troubleshoot-vm-boot-configure-update.md
 - name: Cannot connect to my VM
   items:
   - name: RDP

articles/virtual-machines/troubleshooting/media/troubleshoot-guide-not-a-bootable-disk/2.jpg

@@ -0,0 +1,150 @@
+---
+title: Boot Error – This is not a Bootable Disk | Microsoft Docs
+description: This article provides steps to resolve issues where the disk isn't bootable in an Azure Virtual Machine
+services: virtual-machines-windows
+documentationcenter: ''
+author: v-miegge
+manager: dcscontentpm
+editor: ''
+tags: azure-resource-manager
+
+ms.assetid: 5d6db4e3-c2f5-40c7-afea-54edf745f5eb
+ms.service: virtual-machines-windows
+ms.workload: infrastructure-services
+ms.tgt_pltfrm: na
+
+ms.topic: troubleshooting
+ms.date: 03/25/2020
+ms.author: v-mibufo
+
+---
+
+# Boot Error – This is not a Bootable Disk
+
+This article provides steps to resolve issues where the disk isn't bootable in an Azure Virtual Machine (VM).
+
+## Symptoms
+
+When you use [Boot diagnostics](https://docs.microsoft.com/azure/virtual-machines/troubleshooting/boot-diagnostics) to view the screenshot of the VM, you will see that the screenshot displays a prompt with the message 'This is not a bootable disk. Please insert a bootable floppy and press any key to try again...'.
+
+   Figure 1
+
+   ![Figure 1 shows the message *"This is not a bootable disk. Please insert a bootable floppy and press any key to try again..."*](media/troubleshoot-guide-not-a-bootable-disk/1.jpg)
+
+## Cause
+
+If you encounter this error message, it means that the OS boot process could not locate an active system partition. Alternatively, it could mean that there is a missing reference in the Boot Configuration Data (BCD) store, which is preventing it from locating the Windows partition.
+
+## Solution
+
+### Process Overview
+
+1. Create and Access a Repair VM
+2. Set Partition Status to Active
+3. Fix the Disk Partition
+4. **Recommended**: Before you rebuild the VM, enable serial console and memory dump collection
+5. Rebuild the Original VM
+
+   > [!NOTE]
+   > When encountering this boot error, the Guest OS is not operational. You will be troubleshooting in offline mode to resolve this issue.
+
+### Create and Access a Repair VM
+
+1. Use steps 1-3 of the [VM Repair Commands](https://docs.microsoft.com/azure/virtual-machines/troubleshooting/repair-windows-vm-using-azure-virtual-machine-repair-commands) to prepare a Repair VM.
+2. Using Remote Desktop Connection connect to the Repair VM.
+
+### Set Partition Status to Active
+
+Generation 1 VMs should first verify that the OS partition which holds the BCD store is marked as *active*. If you have a Generation 2 VM, skip ahead to [Fix the Disk Partition](https://docs.microsoft.com/azure/virtual-machines/troubleshooting/repair-windows-vm-using-azure-virtual-machine-repair-commands), as the *Status* flag was deprecated in the later generation.
+
+1. Open an elevated command prompt *(cmd.exe)*.
+2. Enter *diskpart* to launch the DISKPART tool.
+3. Enter *list disk* to list the disks on the system and identify the attached OS VHD.
+4. Once the attached OS VHD is located, enter *sel disk #* to select the disk.  See Figure 2 for example where Disk 1 is the attached OS VHD.
+
+   Figure 2
+
+   ![Figure 2 shows the *diskpart* window showing the output of list disk command, Disk 0 and Disk 1 displayed in the table.  Also shows output of the sel disk 1 command, Disk 1 is the selected disk](media/troubleshoot-guide-not-a-bootable-disk/2.jpg)
+
+5. Once the disk is selected, enter *list partition* to list the partitions of the selected disk
+6. Once the boot partition is identified, enter *sel partition #* to select the partition.  Usually the boot partition will be around 350 MB in size.  See Figure 3 for example where Partition 1 is the boot partition.
+
+   Figure 3
+
+   ![Figure 3 shows the diskpart window with the output of the *list partition* command. Partition 1 and Partition 2 are displayed in the table. It also shows the output of the *sel partition 1* command, when Partition 1 is the selected disk.](media/troubleshoot-guide-not-a-bootable-disk/3.jpg)
+
+7. Enter 'detail partition' to check the status of the partition. See Figure 4 for example where the partition is *Active: No* or Figure 5 for example where the partition is 'Active: Yes'.
+
+   Figure 4
+
+   ![Figure 4 shows the diskpart window with the output of the *detail partition* command, when Partition 1 is set to *Active: No*](media/troubleshoot-guide-not-a-bootable-disk/4.jpg)
+
+   Figure 5
+
+   ![Figure 5 shows the diskpart window with the output of the *detail partition* command, when Partition 1 is set to *Active:  Yes*.](media/troubleshoot-guide-not-a-bootable-disk/5.jpg)
+
+8. If the partition is **Not Active**, enter *active* to change the *Active* flag.
+9. Check that the status change was done properly by typing *detail partition*.
+
+   Figure 6
+
+   ![Figure 6 shows the diskpart window with the output of *detail partition* command, when Partition 1 is set to *Active: Yes*](media/troubleshoot-guide-not-a-bootable-disk/6.jpg)
+
+10. Enter *exit* to close the DISKPART tool and save your configuration changes.
+
+### Fix the Disk Partition
+
+1. Open an elevated command prompt (cmd.exe).
+2. Use the following command to run *CHKDSK* on the disk(s) and perform error fixes:
+
+   `chkdsk <DRIVE LETTER>: /f`
+
+   Adding the '/f' command option will fix any errors on the disk. Make 
+sure to replace <DRIVE LETTER> with the letter of the attached OS VHD.
+
+### Recommended: Before you rebuild the VM, enable serial console and memory dump collection
+
+To enable memory dump collection and Serial Console, run the following script:
+
+1. Open an elevated command prompt session (Run as administrator).
+2. Run the following commands:
+
+   Enable Serial Console
+
+   `bcdedit /store <VOLUME LETTER WHERE THE BCD FOLDER IS>:\boot\bcd /ems {<BOOT LOADER IDENTIFIER>} ON`
+
+   `bcdedit /store <VOLUME LETTER WHERE THE BCD FOLDER IS>:\boot\bcd /emssettings EMSPORT:1 EMSBAUDRATE:115200`
+
+3. Verify that the free space on the OS disk is as much as the memory size (RAM) on the VM.
+
+   If there's not enough space on the OS disk, you should change the location where the memory dump file will be created and refer that to any data disk attached to the VM that has enough free space. To change the location, replace "%SystemRoot%" with the drive letter (e.g. "F:") of the data disk in the below commands.
+
+#### Suggested configuration to enable OS Dump
+
+**Load Broken OS Disk**:
+
+`REG LOAD HKLM\BROKENSYSTEM <VOLUME LETTER OF BROKEN OS DISK>:\windows\system32\config\SYSTEM`
+
+**Enable on ControlSet001:**
+
+`REG ADD "HKLM\BROKENSYSTEM\ControlSet001\Control\CrashControl" /v CrashDumpEnabled /t REG_DWORD /d 1 /f`
+
+`REG ADD "HKLM\BROKENSYSTEM\ControlSet001\Control\CrashControl" /v DumpFile /t REG_EXPAND_SZ /d "%SystemRoot%\MEMORY.DMP" /f`
+
+`REG ADD "HKLM\BROKENSYSTEM\ControlSet001\Control\CrashControl" /v NMICrashDump /t REG_DWORD /d 1 /f`
+
+**Enable on ControlSet002:**
+
+`REG ADD "HKLM\BROKENSYSTEM\ControlSet002\Control\CrashControl" /v CrashDumpEnabled /t REG_DWORD /d 1 /f`
+
+`REG ADD "HKLM\BROKENSYSTEM\ControlSet002\Control\CrashControl" /v DumpFile /t REG_EXPAND_SZ /d "%SystemRoot%\MEMORY.DMP" /f`
+
+`REG ADD "HKLM\BROKENSYSTEM\ControlSet002\Control\CrashControl" /v NMICrashDump /t REG_DWORD /d 1 /f`
+
+**Unload Broken OS Disk:**
+
+`REG UNLOAD HKLM\BROKENSYSTEM`
+
+### Rebuild the Original VM
+
+Use [step 5 of the VM Repair Commands](https://docs.microsoft.com/azure/virtual-machines/troubleshooting/repair-windows-vm-using-azure-virtual-machine-repair-commands#repair-process-example) to reassemble the VM.