YouTube Videos

Dual Boot MultiBoot
3 Fast MultiBoot USB3 Sticks
Desktop Screenshots
Dualboot Kubuntu 16.10 & Win-10 USB3
Dualboot Android-x86 Linux USB
Dualboot Windows Linux USB
Dualboot Win-10 and Kubuntu 16.04
Dualboot Win XP and RemixOS
Grub2 Multi-Bootmenus
How Repair GPT Boot Failures?
Linux MultiBoot Grub1
Linux MultiBoot Grub2
Mount Linux in Windows
Mount Windows in Linux
Moving Windows XP Installation
MultiBoot & Backup
MultiBoot - Recap
MultiBoot - Device Mixups
MultiBoot USB-Stick
MultiBoot USB3 Extreme
Ranish Partition Manager
Ranish PM - Installation
Ranish PM - Recap
Ultimate MultiBoot PC
Backup Cloning
Messaging IM SMS
Misc. Soc Media
Music Jazz MPB
Remote Controls
Screen Recording
USB Flash Drives

Krister's Blog
krister at hallergard dot com

Last Updated:

How Repair GPT Boot Failures?

View Video 6 min
My old PC conqed out so I bought a new one with a 2 TB disk drive with a GUID partition table, GPT with Windows 10 preinstalled in UEFI mode. When I tried to convert the new PC into a multiboot device, I encontered this blue disaster screen and not just once!
My Aim:

I tried all the advanced repair options on the Windows 10 installation DVD without success, so I had to reinstall the GPT disk from scratch. I also run chkdsk /f which took about 3 hours. I had some indications that there was possible mixups between the disks sda and sdb. In the end I decided to take a way to old 1 TB disk (sdb) completely and reinstall the GPT disk from scratch. I then installed Kubuntu 16.04 successfully on partition sda5, and have not had any further problems.

I now believe that the too big EFI partition on the MBR disk contributed to the corruption of the partition table on the GPT disk. Can GPT and MBR disks coexist?


The new 2 TB disk (sda) had one big 1.8 TB volume with Windows 10. I have shrunk this and added 4 small partitions for Linux (fomatted with ntfs for now). And a 670 GB storage partition for data and backups. And a small swap area for Linux.

On the old 1 TB MBR disk (sdb), I was surprised to learn that I could boot Windows 10 (sdb1) and Linux (sdb3 and scb4) on the new PC, despite the difference in chipset to the old PC. (Windows XP and Windows 7 would not boot though)

So I wanted to keep the old MBR disk. Thus I hid the XP partition, and created an new EFI partition (much too big - 100 MB would have been enough) with the aim of later converting Windows 10 and the two Linux installations from Legacy mode to UEFI mode and this without reformatting the MBR drive.

Failed attempts to repair: