Windows Inaccessible Boot Device Error

I recently upgraded to a K8N Neo 2 Platinum with an Athlon 65 3500. I used my WD Caviar IDE 40 GB drive (boot drive) from my old computer. There are no detection problems and the POST proceeds normally. As Windows is loading up I get a blue screen error that says INACCESSIBLE_BOOT_DEVICE. It tells me to run CHKDSK. I have done this, and tested the drive with the WD diagnostic tools. The test report says there are no errors. I even tried restoring an older boot track. Still nothing. Any ideas?

if it has no slave use it jumperless stand alone master
or cable select
but not master
on the end of an 80 wire ide with blue end in the board

Similar Messages

"Inaccessible boot device" error message when I try to boot up.

Greetings, I recently upgraded to Windows 10, and I wanted to do a factory reset yesterday. I did this, and when it tried to boot up after it was finished I got the error message "Inaccessible boot device", and then my computer kept on restarting itself over and over, and never getting into the OS properly. I am using a Portege R705-P35. I tried searching for the device drivers to install on a USB and booting from this, but my computer could not boot from this properly. So i believe my problem is related to the device driver. What is the exact driver I need to boot up? I checked the Toshiba site and there was a list of about 25 drivers for my PC, and I'm not sure which would work. All help is greatly appreciated on this

I have excatly the same issue on my WT8-A. I have been running Windows 10 as an Insider for months on the device, and after RTM decided to do a full reset. I now get the same message as the OP saying "INACCESSIBLE BOOT DEVICE" I now have an unusabe device. Please help.

Fresh install of Server 2012 R2 causes inaccessible boot device on first Reboot

Hello Everyone,
Doing a fresh install of Windows Server 2012 R2 on a SuperMicro X9DRT-HF+ motherboard based server. The server is using iSCSI boot, setup detects the iSCSI disk and copies its files, finishes the "Getting files ready for installation" "Installing
Updates" phase, reboots, takes a while and eventually gives a Blue screen with Inaccessible Boot Device error. I have tried some changing options in the BIOS, I've had Nimble (storage array) support on the phone and they confirmed the setup is correct
but for some reason after the first reboot Windows can no longer find its install files and gives a BSOD.
Additional Information:
Server: SuperMicro X9DRT-HF+ (no internal disk)
Storage: iSCSI disk provided from Nimble CS220 Array
Windows 2008 R2 Server installation will proceed without any problems.
I checked the \Windows\Panther\Setupact.log / CBS.log file and there doesn't seem to be anything indicating a problem.
I have googled a number of times to find solutions but most articles reference a similar problem after installing a particular KB (which shouldn't be the case here). Need some help :)

Hey Tim,
Thanks for your reply, since the start of this post I have also installed MDT to try a different approach to installing the OS. Using MDT I have injected the Intel I350 driver into the installation so it should be restarting with the driver loaded.
The odd thing is that when the server reboots the Windows startup screen loads for about 4 minutes before it gives the INACCESSIBLE_BOOT_DEVICE error. This would indicate to me that it sees the disk and tries to boot from it but then something goes wrong.
Other than the \Windows\Panther location is there another place I should be looking for log files during this part of the Windows install? I have reviewed all the locations listed under the TechNet library article "hh824819" (I can't post
a link to the article but a google search brings it up) but I can't seem to find a log of when the server crashes what it is doing at that point.

Inaccessible boot device win 8 install U410

Hello,
I've bought an upgrade for Win 8 pro. Since then i get an inaccessible boot device error when i try to install. I've read the forum to devide the SSD and the regular harddrive but the Rapid drive program won't install. Please come with a solution, Because it's a bad case. Lenovo says you can upgrade to win 8. But a lot of people need help, And a lot of noliage of windows. A amateur like me, it is not possible to get windows 8 running on my U410.

And what about the small onekry button. Same condition. The button is on the side.
Ishaan Ideapad Y560(i3 330m), Hp Elitebook 8460p!(i5-2520M) Hp Pavilion n208tx(i5-4200u)
If you think a post helped you, then you can give Kudos to the post by pressing the Star on the left of the post. If you think a post solved your problem, then mark it as a solution so that others having the same problem can refer to it.

ZCM 11.3.1 and BSOD (7B Inaccessible boot device)

Hi all,
We have been struggling with seemingly random BSOD for many months across our laptop and desktop fleet. Different vendors, model, different model hard drives.
Today we have finally been able to do something that has been reproducible, for probably the first time.
(Thanks to Donald Jones, Great Basin College for the push in the right direction)
Environment:
Windows 7Pro SP1 (x86-64)
Novell Client 2SP3IR8
ZCM 11.3.1
(Also, Mcafee Virusscan 8.8)
1.
On a clean HDD, we physically image (drive replicator) with our SOE (Sysprepped image, none of the above software pre-installed)
At Windows "First Boot, OOBE", we install :
-Machine specific drivers
-Novell Client 2SP3IR8
-iPrint 5.98
-ZCM 11.3.1
-Mcafee Virusscan 8.8
as part of the OOBE.
2.
Machine completes build fine. We have had a few machines BSOD within hours. Others may take months of use.
3.
When a machine fails, it seems to be after a clean shutdown, at the next startup.
At boot, the Windows Startup screen appears, but within a second or two we see a BSOD, with a 7B (Inaccessible boot device) error.
BSOD Error details:
0x0000007B
(0xFFFFF880009A97E8, 0xFFFFFFFFC0000034, 0x0000000000000000, 0x0000000000000000)
4.
If we load the SYSTEM registry hive of the device, and edit this key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\{4d36e967-e325-11ce-bfc1-08002be10318}
Before: Lowerfilters: = zesdac
After: Lowerfilters: =
The machine will now boot OK.
5.
We then shutdown the device, and load the SYSTEM hive to check the key and it has been repopulated (self healed?) with:
Lowerfilters: = zesdac
However, we can now boot cycle the machine numerous times, and the machine boots fine, as normal.
The c:\windows\system32\zesdac.sys file has these properties:
File Description: Novell ZESM Device Access Control Driver
Type: System File
File Version: 11.3.1.214
Product Name: Novell ZENWorks Endpoint Security
Product Version: 11.3.1.214
Copyright: Copyright (c) 2003-2013 Novell Inc
Size: 31.2 KB
Date Modified: 24/06/2014 12:58pm
Language: English (United States)
Original Filename: ZESDAC.SYS
These TIDs don't relate to the 11.3.1 version we use, but started me looking..
https://www.novell.com/support/kb/doc.php?id=7011969
https://www.novell.com/support/kb/doc.php?id=7008599
We have also checked things like 'force run bundles' that may push changes to the device, and have disabled the 'automatic install/launch' relationships.
We will continue to investigate, but if anyone has any further ideas, I'd love to hear them.

We're seeing the exact same stop message, but only on a two specific model laptops from the same vendor and not our other devices (different models from same vendor and different vendors).
It has been ongoing since March/April. It seemingly happens (BSODs) after Windows Updates have been applied and upon the next boot. It has happened to about 15 devices so far. There are about that many more that are of the same hardware/model that have not had the issue all during the same period. These devices do have SSD drives of varying vendors.
We finally got Microsoft to investigate the issue and were able to get the machine to boot after messing with the registry hives. When they looked into the differences between the "corrupted" hives and the now working ones, they pointed to the same zesdac registry key/area as mentioned in the first post.
"As per our discussion, after comparing your System hive. I got the conclusion that your System was in No boot situation due to the absence of following registry Key :
HKLM\System\CCS\Services\zesdac
And on the other hand, following filters were present on the registry location:
HKLM\test\ControlSet001\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318}
UpperFilters:
PartMgr
LowerFilters:
zesdac
Our database contains 30 different files for filename zesdac.sys . This files most often belongs to product Novell ZENworks Endpoint Security. and were most often developed by company Novell, Inc. This files most often have description Novell ZESM Device Access Control Driver. This file contains driver. You can find it in the Drivers section of the System Explorer. you can find detailed information about the file itself, download information, its demographics distribution, security rating given by users, antivirus reports from AV applications, user's reviews and comments for the file and much more, which can help you to decide if the file can be safe or threat for your computer.
Since, its lower filter was present and in services zesdac was not present. Which was ultimately leading to no boot situation."
We're running ZEN 11.2.4 and our devices are all Win7SP1x64.
While Microsoft was able to get the machine to boot, we're unable to install any applications (MSI/EXE), windows updates, etc... since they were able to get the machine to boot.
So with them pointing us to ZENworks as the culprit, we're still no closer to finding a prevention or a real working fix as of yet other than re-imaging the device.
Any thoughts?
Thanks,
LK

Inaccessible boot device Windows 8

Hi!
My laptop was supposed to restart after windows updating. Instead of that bluescreen appears and says 'inaccessible boot device'. I've changed SATA Controller Mode Option to Compatibility and it still doesn't work. I also cannot open safe mode. Tried pressing F8, shift+F8, Fn+F8. Nothing works.
Please help me.
Thank you!

hi jumanjirose,
It's possible that one of those Windows Updates corrupted some of the Windows system files, causing the BSOD error. If you didn't create a recovery drive using this method, try one of the following:
Option 1:
Enter Push-Button Reset (PBR) mode - this is like a recovery environment to restore the pc from a previous working state. To do this, hold the power button while Windows 8 is loading up - the one where you see the white dots goes in circles (you need to do this twice). If successful, Windows will run startup repair. If it can't repair the error, you'll see this screen:
From here, click Advanced Options > Troubleshoot and you can:
a. Boot from the Last Known Good Configuration
b Boot into Safe Mode
c. Do a System Restore to restore Windows from a working state
d Refresh your Windows 8 PC or Reset windows 8 (note that this will wipe the computer clean)
Option 2:
If Push Button Reset doesn't work, follow this guide on how to enable legacy Safe Mode. When done, you should be able to access Safe Mode / Last Known Good Configuration by pressing F8 on startup or perform the PBR options above.
Regards
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter!

Inaccessible boot device after splitting windows 8 partition

Originally my Lenovo IdeaPad Flex 14 came with windows 8 64bit, I upgraded it to windows 8.1. Later I decided I wanted to do a dual boot. The windows8OS partition was about 400GB so I split it using AOMEI Partition Assistant Pro Edition 5.1. The process didnt work, now I keep getting a BSOD "inaccessible boot device" and keeps restarting. All it accomplishes is restarting. How do I fix this problem?
Solved!
Go to Solution.

Welcome to the forum!
Generally failures during a partition resizing are not fixable. The easiest repair would be to just re-install the operating system and resize the partition during the process or just restore the hard drive back to its original condition from a recovery disk or image file. Hopefully you have such options available.
If by chance you were successful in resizing the partition and the machine won't boot correctly then try using the Boot Corrector or MBR Repair feature of your partitioning software. After a successful resizing, the Master Boot Record (MBR) sometimes needs to be updated or repaired in order for the computer to boot successfully.
In addition, when setting up a computer for dual or triple booting Windows operating systems you generally install the older version of Windows first then the newer version. Here is link to a Microsoft article on the topic that you may find informative.........
http://windows.microsoft.com/en-us/windows/install-multiple-operating-system-multiboot#1TC=windows-7
Owner & Operator of the following:
● Lenovo Ideapad Z570 w/ Win 7 & Win 8.1 Dual Boot ● Lenovo Yoga 3 Pro w/ Windows 8.1 ● Toshiba A75-S206 w/ Win 7
● IBM Thinkpad T-23 w/ Win XP ● IBM Thinkpad T-22 w/ Win XP • As well as multiple desktops dual/triple booting XP, Vista and Win 7.
★ Find a post helpful? Thank that member by clicking on the ☆Star☆ to the left awarding them a Kudo.
★ Posting a problem and a reply is helpful and it answers your question, please mark it as an "Accepted Solution"
★ I'm not a Lenovo employee, just a volunteer geek who likes to help folks. Enjoy your time here, pay it forward by helping others !
★ Sorry, I don't answer questions via Private Messages. Posting in the appropriate forum is the best way to get assistance.

Lenovo G510 Inaccessible Boot Device and Internal Empty Port 5

Hi! I´ve got a lenovo G510 Laptop and I´ve been having several issues lately with it. First, it sometimes does not boot (a blue screen saying Inaccessible Boot Device appears on the screen). On the other hand, there are moments when the DVD recorder is not recognized either on windows or BIOS. (On Intel Rapid Storage there´s a SATA disk for the OS and instead of recognizing the DVD recorder it says Internal empty port 5); but this is not always, just sometimes. Is it possible for the two problems to be conected?Best,

To me that sounds like a harddrive is getting ready to, or has, totally failed. If this is a new laptop or the warranty is still good, I would contact customer support and see if you can get it fixed.
Hoov
Microsoft MVP - Consumer Security
SpywareHammer.com

G965M-F W2k inaccessible boot device during install

I'm having problems with install of W2k on G965M. I've used the F6 option to install the drivers from the CD using floppy. I've tried ICH8R (iastor), JMicron(jraid), and I've upgraded bios to v 1.4. When W2k completes loading files and 'Setup is starting windows 2000' I get the STOP 0x07b inaccessible boot device screen. I've downloaded latest drives from MSI with same results. POST shows IDE CDROM as USB device 01 and WD SATA as 3rd Master.
I am able to install windows XP without any additional drivers specified with this same configuration. Anyone know what I'm doing wrong. Thanks..

Problem solved. MSI tech support responded (quickly!) to my problem. I needed to integrate SP4 with the W2K install CD. Worked perfect.

[SOLVED] external USB HDD fails to install arch w/boot device ERROR

I've been working on installing arch linux via an external USB harddrive (specifically seagate free agent go 320GB) for 1 week now, and everytime I failed - until TODAY! thankfully I found this post, where user Dieter@be references this link, which displays BUG ID#17231 at the top titled "Can't boot LiveCDs 2009.08 (/dev/archiso doesn't show up)". the bug report states ::
I can't boot the LiveCDs 2009.08, neither netinstall nor core.
When it tries to access /dev/archiso it shows these messages:
:: Waiting for boot device ...
Waiting 30 seconds for device /dev/archiso ...
ERROR: boot device didn't show up after 30 seconds ...
Falling back to interactive prompt
You can try to fix the problem manually, logout when you are finished
ramfs$
reading further thru this bug report, I found a very insightful post by Heiko Baums (cyberpatrol) where he says the following, and I quote ::
Problem found. The link /dev/archiso wasn't created.
After
ramfs$ cd /dev
ramfs$ ln -s sr0 archiso
ramfs$ exit
it continued booting correctly.
And sg was also loaded after this. ;-)
as you see, the bug report was for the CD version, not the USB version - yet, my issue with the USB bootdisk was the same, (no matter which boot disk I tried = netinstall, core, .img, .iso, etc) meaning I got the EXACT same error = "ERROR: boot device didn't show up after 30 seconds ..." ! well, I figured that I'd try one of the new fancy ISOs found @ http://build.archlinux.org/isos/ - specifically I use/used archlinux-2010.03.04-netinstall-x86_64.iso.
upon running Unetbootin from windows 7, and choose to install the ISO archlinux-2010.03.04-netinstall-x86_64.iso to my first partition on my USB harddrive (that first partition being FAT32, and had already been set as bootable previously), that completed successfully. I rebooted, and choose to boot from USB drive, the ISOlinux bootloader came up as normal, I choose DEFAULT and off it went.... sure enough, it errored out at the same place as listed in the bug report ::
:: Waiting for boot device ...
Waiting 30 seconds for device /dev/archiso ...
ERROR: boot device didn't show up after 30 seconds ...
Falling back to interactive prompt
You can try to fix the problem manually, logout when you are finished
ramfs$
this time though, I issued the following 2 commands ::
ln -s /dev/sdb1 /dev/archiso
exit
from there, EVERYTHING worked as it should!
to recap: the solution for me was create a symbolic link pointing /dev/archiso => to my partition which held the archlinux netinstall (which is where I told Unetbootin to install it to)! done and done. I felt this needed to be posted here, as I could not find this solution after MANY google searches, archlinux wiki searches, forum searches, etc. honestly, I think it would be prudent to have this tidbit of information added to the Install from USB stick archwiki page as a side note to those that may run into this issue.
this is not the FIRST time I have run into this problem with a USB install of archlinux, but this is the FIRST time I found a fix! thanks to all the great posts I reference here, without this information I dont think I would have been able to install archlinux on my new alienware m11x laptop.
-peace-
PS: no amount of rootdelay=XX nor pmedia=usb nor usbdelay=XX would work in my above attempts either.
Last edited by fnord0 (2010-03-12 04:54:26)

FAT16 here. Parted Magic sees my USB drive as sdd. I tried your way and surprise, surprise, it didn't work.
ln -sf /dev/sdd /dev/archiso
mount -t vfat /dev/archiso /bootmnt
mount : Invalid argument
I thought maybe you meant mount -f vfat /dev/archiso /bootmnt instead. I tried it too, it resulted in a kernel panic.
What else can I try besides installing from a IDE/SATA CD drive ? Because this issue is NOT solved. At least not for me. Wonder if "archlinux-2010.04.05-netinstall-i686.iso" from the here will solve it (really hope so).
SOLVED IT HERE (with yet another image): http://bbs.archlinux.org/viewtopic.php?id=93645
Last edited by DSpider (2010-04-17 14:21:27)

Boot Device Error

Hi, can anyone help, I started up my sun sparc statioon5 thismorning, and i have this error popping up, it goes like this. Boot device: /iommu/sbus/espdma@5, 84000000/esp@5, 88000000/sd@3, 0 File and args: the file just loaded does not appear to be executable.
Do I have to re-install solaris? or is it something more..... any help is appreciated

There are 2 options, 1 I have done and the other is still untried.
1. Get the install CD and perform an upgrade to the drive to reload the system specific files.
2. There are reports of being able to boot to the cdrom and just reload the boot files form the /platform directory.
Hope this helps.
Lane

Inaccessible boot device

I have a Mac Prod (mid 2006) and OS X 10.7.5 installed. I had a Win7 bootcamp install that I upgraded to Win 8. Windows did boot up the first time around, but since then I have been getting INACCESSIBLE_BOOT_DEVICE when windows tries to star. I can run the same windows image out of VMWare without any issues.
Also, if I shut down my computer, restart into Mac, it takes forever to get to the OS startup - seems like it OS X does some repair (grey background with progress bar) before the OSX boot screen (grey with apple logo) shows up.
I have reFit installed.
How can I fix my boot record or whatever is wrong with the machine?
The disks are the right format because everything was working in boot camp mode with windows 7 x64
thanks

What you are asking for doesn't exist, the IDE controller on that board is about 5 years old and is only ATA33.
You can try removing the IDE controllers from the device manager and then installing the intel inf befor swaping the boards (don't restart after the inf, shut down and power back up on the new board).

Compaq presario cq61-411wm no booting device error/"hard disk not exist" help!!

screen is cracked so hooked up a external monitor. no bootable device error in white on black screen. did tests all passes except hard disk. this one gives " hard disk not exist" error..trying to save all my pix of my sons on computer.someone please help!! thanks in advance!! =D

Did you drop the laptop? If the computer is not "seeing" the hard drive your only hope is that the hard drive got knocked loose and is still good, just not connected. Otherwise a drop that can crack a screen may well have also killed the hard drive.

ASR 1002-x "Unnsupported boot device" error

I have not been able to get the ASR to accept/use the new IOS. Not sure what is wrong. Please review and advise.
ASR1002x#dir
Directory of bootflash:/
   11 drwx       16384 Jun 27 2014 04:33:23 +00:00 lost+found
32769 drwx        4096 Jul 22 2014 11:27:38 +00:00 .prst_sync
   12 -rw-   393060852 Jun 27 2014 04:35:01 +00:00 asr1002x-universal.03.08.00.S.153-1.S.SPA.bin
114689 drwx        4096 Jun 27 2014 04:34:48 +00:00 .installer
688129 drwx        4096 Jun 27 2014 04:45:46 +00:00 core
704513 drwx        4096 Jun 27 2014 04:46:06 +00:00 .rollback_timer
802817 drwx       16384 Jul 22 2014 11:28:15 +00:00 tracelogs
   14 -rw-   411494592 Jul 22 2014 08:30:17 +00:00 asr1002x-universalk9.03.12.01.S.154-2.S1-std.SPA.bin
   13 -rw-     3832112 Jul 22 2014 08:55:24 +00:00 asr1000-rommon.154-2r.S.pkg
ASR1002x#sh ver
Cisco IOS Software, IOS-XE Software (X86_64_LINUX_IOSD-UNIVERSAL-M), Version 15.3(1)S, RELEASE SOFTWARE (fc4)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2012 by Cisco Systems, Inc.
Compiled Tue 27-Nov-12 11:17 by mcpre
IOS XE Version: 03.08.00.S
Cisco IOS-XE software, Copyright (c) 2005-2012 by cisco Systems, Inc.
All rights reserved. Certain components of Cisco IOS-XE software are
licensed under the GNU General Public License ("GPL") Version 2.0. The
software code licensed under GPL Version 2.0 is free software that comes
with ABSOLUTELY NO WARRANTY. You can redistribute and/or modify such
GPL code under the terms of GPL Version 2.0. For more details, see the
documentation or "License Notice" file accompanying the IOS-XE software,
or the applicable URL provided on the flyer accompanying the IOS-XE
software.
ROM: IOS-XE ROMMON
MMC-ASR1002x uptime is 2 minutes
Uptime for this control processor is 4 minutes
System returned to ROM by reload
System image file is "bootflash:/asr1002x-universal.03.08.00.S.153-1.S.SPA.bin"
Last reload reason: Reload Command
ASR1002x#sh bootvar
BOOT variable = asr1002x-universalk9.03.12.01.S.154-2.S1-std.SPA.bin,1;
CONFIG_FILE variable does not exist
BOOTLDR variable does not exist
Configuration register is 0x2102
Standby not ready to show bootvar
boot-start-marker
boot bootstrap tftp asr1000-rommon.154-2r.S.pkg 255.255.255.255
boot system flash asr1002x-universalk9.03.12.01.S.154-2.S1-std.SPA.bin
boot-end-marker
ASR1002-X platform with 4194304 Kbytes of main memory
boot: unsupported boot device "asr1002x-universalk9.03.12.01.S.154-2.S1-std.SPA.bin"
autoboot: boot failed, restarting...
Initializing Hardware ...
System integrity status: 00000610
System Bootstrap, Version 15.4(2r)S, RELEASE SOFTWARE (fc1)
Copyright (c) 1994-2014 by cisco Systems, Inc.
Current image running: Boot ROM1
Last reset cause: LocalSoft
SPI Flash 4KB Descriptor Area Checksum = 0x6f5a0db2
ASR1002-X platform with 4194304 Kbytes of main memory
no valid BOOT image found
Final autoboot attempt from default boot device...

boot bootstrap tftp asr1000-rommon.154-2r.S.pkg 255.255.255.255
Get rid of this line and save the config. This is NOT the way to upgrade the bootstrap.
To upgrade the bootstrap, use the command "upgrade rom file bootflash:asr1000-rommon.154-2r.S.pkg all".

Proper BOOT device error

Hello. I restored my com to out-of box setting. Now, when my com starts it indicates "Check cable connection!, Reboot and select proper boot device." I do not have the CD. Is there anyway I can add/change the settings via F2 , ?, etc. in order to get my laptop working. I have a SATELLITE L855D-S5200. Thank you

Hi ! If you are wanting to change boot order, try this. You may also want to set BIOS back to default.
http://pcsupport.about.com/od/fixtheproblem/ss/bootorderchange_2.htm
I Love my Satellite L775D-S7222 Laptop. Some days you're the windshield, Some days you're the bug. The Computer world is crazy. If you have answers to computer problems, pass them forward.

Windows Inaccessible Boot Device Error

Similar Messages

Maybe you are looking for