Skip to main content

hard drive - 0x00000e9 error on boot Windows 10

Recently when booting up my computer, the OS (Windows 10 Pro 64-bit) failed to load. When booting off of my primary drive, I received the following error:



0xc000000e A required device isn't connected or can't be accessed. You'll need to use recovery tools. If you don't have any installation media (like a disk or USB device), contact your PC administrator or PC/Device manufacturer



When booting off of the secondary, I receive a different error:



0x00000e9 An unexpected I/O error has occurred. This problem can happen when a removable storage is removed while it's in use or is failing. Properly connecting any removable storage and restarting your PC may fix this problem



I suspect that the primary drive is fine, and that the secondary drive is the problem. While the OS is installed to the primary drive, it used to be installed on the secondary drive before I did a clean install of Windows. I believe the MBR is still on the secondary drive, which would explain why the primary can't boot on its own. This is further reinforced by the secondary drive being the first in the load order between the two.


I installed Windows on a small (40 GB!) drive so I could boot into Windows and check on the status of the other two (Primary is 1 TB from 2012; Secondary is 0.5 TB from 2009). Pictured below is a screenshot from Disk Management run through the Windows I installed on the recovery drive. Disk 0 = recovery, Disk 1 = primary, and Disk 2 = Secondary:


enter image description here


All partitions (which aren't connected via RAID/etc) are showing up as healthy, and from Windows on the recovery drive I'm able to access the contents of the other drives no problem. Because the partitions are healthy, I'm unsure if this is an issue of wear and tear or the MBR somehow being damaged through other means. The PC was last rebooted by AMD's Radeon Crimson driver installer after it updated drivers, so it's not like it was abruptly shut down.


If possible, I would prefer to keep the contents of both drives, as well as the configurations to the Windows install. When I try to repair the OS install via USB, I'm told to boot from the damaged drive and repair from there, but this is impossible as booting from that drive immediately errors. How can I repair the drive(s) without losing my data, and potentially move the MBR to my primary drive? Should I look into replacing the secondary and/or primary drive as well?


Edit: Using the Windows installation USB, I opened the recovery command prompt and through using bootrec /scanos Windows was found on my primary drive. I then ran bootrec /fixmbr and bootrec /fixboot, and restarted the computer. It was to no avail though as I'm still receiving the same error.


Edit: I tried using bootrec /rebuildbcd and while booting from primary gives the same error, now I'm also getting the following error when I boot into repair from the recovery USB:



The boot configuration data for your PC is missing or contains errors. File:\EFI\Microsoft\Boot\BCD Error code: 0xc000000f



Edit: Fixed 0xc000000f error by re-creating the bootable USB. Concerning that it was damaged instead of my drive -- was /rebuild bcd targeting the USB instead of the drive?

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