Skip to main content

Windows BSOD loop: "INACCESSIBLE_BOOT_DEVICE" after repartitioning and installing Ubuntu Gnome


Windows 10 x64 v1607 won't boot after I reprtition my single 1TB HDD and installed Ubuntu Gnome 16.04.1 LTS amd64. it keeps doing a BSOD "INACCESSIBLE_BOOT_DEVICE".


My exact steps:



  1. Boot from Ubuntu Gnome 16.04.1 LTS amd64 on USB drive.

  2. 'Try Ubuntu Gnome' option.

  3. Shrink Windows partition from 850GB to ~= 350GB in GParted.

  4. Move recovery partition (I have created a System Repair Disk) (also in GParted)

  5. Create new ~=350GB FAT32 Partition.

  6. Use Ubuntu Gnome installer; use 'install alongside Windows' option. Installer succeeds.

  7. Restart. Grub menu comes up, select Windows. Windows shuts down. I didn't see exactly what happened, but I came back and my PC was competely off. Turn back on.

  8. Grub comes back, Windows again. Windows bluescreens with 'INACCESSIBLE_BOOT_DEVICE'. Restarts. Automatic Repair fails. Restart.

  9. Choose Windows at Grub again. Same bluescreen. This time no Automatic Repair - just shuts down.

  10. Choose Ubuntu Gnome at grub. Boots successfully.

  11. Restart, choose Windows. Again, bluescreen, no automatic repair.


I can access my Windows partition from Ubuntu Gnome. I created a Restore Point before I started the steps above. Can I use my Restore Point, and if so, how? Or should I use my recovery drive? Or get a fresh Windows image and reinstall?



Answer



It turned out that my disk had been converted to a Dynamic Disk somehow. This prevents you from having two boot partitions on one disk.



Multi-boot environments


If you're running a multi-boot configuration on a computer, you should not convert basic disks to dynamic disks. Windows XP, Windows Vista and Windows 2000 all support dynamic disks; however, you will cause problems if you upgrade a basic disk to a dynamic disk if you have all of these operating systems installed on the same machine.



Source: http://searchenterprisedesktop.techtarget.com/tip/When-not-to-convert-basic-disks-to-dynamic-disks


I had to completely reinstall Windows using a recovery drive and gave up trying to dual boot; I just virtualised instead. I suspect dual-booting could still work, but I can't really be bothered to go through that. If anyone does have any experience in this, I'm sure that would be helpful for others with this problem, but, like I said, I don't want to do that.


If you has this problem, it is almost definitely because your disk is dynamic. It can be converted to basic but the disk must be emptied (cleaned and all volumes deleted) first. If using option 2, 3 or 4 in the tutorial linked below, all data on the disk will be deleted, including the operating system(s). Backup any data you do not want to lose. If using option 1, backup the drive anyway if it contains any important data.


How to convert a dynamic disk to a basic disk: http://www.sevenforums.com/tutorials/26829-convert-dynamic-disk-basic-disk.html


Comments

Post a Comment

Popular Posts

How do I transmit a single hexadecimal value serial data in PuTTY using an Alt code?

I am trying to sent a specific hexadecimal value across a serial COM port using PuTTY. Specifically, I want to send the hex codes 9C, B6, FC, and 8B. I have looked up the Alt codes for these and they are 156, 182, 252, and 139 respectively. However, whenever I input the Alt codes, a preceding hex value of C2 is sent before 9C, B6, and 8B so the values that are sent are C2 9C, C2 B6, and C2 8B. The value for FC is changed to C3 FC. Why are these values being placed before the hex value and why is FC being changed altogether? To me, it seems like there is a problem internally converting the Alt code to hex. Is there a way to directly input hex values without using Alt codes in PuTTY? Answer What you're seeing is just ordinary text character set conversion. As far as PuTTY is concerned, you are typing (and reading) text , not raw binary data, therefore it has to convert the text to bytes in whatever configured character set before sending it over the wire. In other words, when y...
Post a Comment
Read more

linux - Extract/save a mail attachment using bash

Using normal bash tools (ie, built-ins or commonly-available command-line tools), is it possible, and how to extract/save attachments on emails? For example, say I have a nightly report which arrives via email but is a zip archive of several log files. I want to save all those zips into a backup directory. How would I accomplish that? Answer If you're aiming for portability, beware that there are several different versions of mail(1) and mailx(1) . There's a POSIX mailx command, but with very few requirements. And none of the implementations I have seem to parse attachments anyway. You might have the mpack package . Its munpack command saves all parts of a MIME message into separate files, then all you have to do is save the interesting parts and clean up the rest. There's also metamail . An equivalent of munpack is metamail -wy .
Post a Comment
Read more

ubuntu - Why does my USB hdd returns SG_IO: bad/missing sense data?

I am able to boot and run commands from external USB hdd; the message in question appears for about 45 seconds then booting continues. GRUB2 is installed on internal HDD. When choosing to boot directly to /dev/sdb the message doesn't appear, however boot time is about the same as booting to internal HDD. /dev/sdb: Timing cached reads: 1018 MB in 2.00 seconds = 508.97 MB/sec Timing buffered disk reads: 80 MB in 3.03 seconds = 26.37 MB/sec pfeiffep@de:~$ sudo hdparm -i /dev/sdb /dev/sdb: SG_IO: bad/missing sense data, sb[]: 70 00 05 00 00 00 00 10 00 00 00 00 20 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 HDIO_GET_IDENTITY failed: Invalid argument Gparted correctly identifies the drive as SAMSUNG MP0402H. Any ideas how to remedy the HDIO & SG_IO messages?
Post a Comment
Read more

Desktop reboots itself on sleep or hibernate

I have been using an ASUS M2NPV-VM motherboard for main home desktop workstation, operating Windows Vista x64. This computer has right from day one not been able to enter hibernate or standby; after Windows performs its final actions and brings the machine down, it would automatically revive itself for a reboot. Updating to the second latest BIOS (1201)has not helped (the latest BIOS revision would induce video refresh problems rendering it unusable). I have been reading related discussions on incidents similar to mine to no avail of a true workable solution. They appear to be more speculative guesses rather than actual knowledge on the inner workings of motherboard hardware. Does anybody have any electronic engineering experience on PC energy-saving standards to provide a more informed opinion how to go about getting this to work? More stories: this motherboard could not even reboot properly the first thing i used it. It was due to refresh rate of the onboard GPU, which had no influe...
Post a Comment
Read more