No longer able to boot - failure with /boot

I recently, due to a hard drive change, rebuilt my desktop. Every now and again, since then, it hasn't booted. I just logged into root and rebooted; figuring I'd sort it out at some point.
Only, now it won't boot at all. When I go through journalctl -xb I get the following errors (the ellipsis, in case it isn't clear, indicate an number of lines with no error in between the error messages):
Job dev-sda2.device/start timed out.
Timed out waiting for device dev-sda2.device.
Dependency failed for /boot.
Dependency failed for Local File Systems.
Triggering OnFailure= dependencies of local-fs.target.
Dependency failed for File System Check on /dev/sda2
and also, much later in the logs:
Failed at step EXEC spawning /bin/plymouth: No such file or directory
My initial assumption would have been that the relevant drive is failing, but I only recently ran a check on the drives (a few days ago and since the rebuild) and all was fine and dandy - but I had already been seeing these errors on a periodic basis. Only now, as I said, they happen at every boot and I never get as far as login.
Thanks in advance for any help.

I ran the extended smartmontools test on the disk today and it returned with no errors. However, the error log for the disk did contain the following:
Complete error log:
SMART Error Log Version: 1
Warning: ATA error count 21 inconsistent with error log pointer 5
ATA Error Count: 21 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 21 occurred at disk power-on lifetime: 10341 hours (430 days + 21 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
c8 00 08 00 00 00 e0 08 01:12:12.224 READ DMA
27 00 00 00 00 00 e0 08 01:12:12.224 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 0a 01:12:12.224 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 0a 01:12:12.224 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 08 01:12:12.224 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 20 occurred at disk power-on lifetime: 10341 hours (430 days + 21 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
c8 00 08 00 00 00 e0 08 01:11:26.048 READ DMA
27 00 00 00 00 00 e0 08 01:11:26.048 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 0a 01:11:26.048 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 0a 01:11:26.048 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 08 01:11:26.048 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 19 occurred at disk power-on lifetime: 10341 hours (430 days + 21 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
c8 00 08 00 00 00 e0 08 01:10:16.816 READ DMA
27 00 00 00 00 00 e0 08 01:08:51.584 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 0a 01:08:51.584 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 0a 01:08:51.584 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 08 01:08:51.568 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 18 occurred at disk power-on lifetime: 10340 hours (430 days + 20 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
25 00 01 00 00 00 e0 08 00:04:28.384 READ DMA EXT
c6 00 10 00 00 00 e0 08 00:04:28.384 SET MULTIPLE MODE
91 00 3f 00 00 00 a0 08 00:04:28.384 INITIALIZE DEVICE PARAMETERS [OBS-6]
10 00 00 00 00 00 a0 08 00:04:28.352 RECALIBRATE [OBS-4]
25 00 01 00 00 00 e0 04 00:04:28.352 READ DMA EXT
Error 17 occurred at disk power-on lifetime: 10340 hours (430 days + 20 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
25 00 01 00 00 00 e0 08 00:04:28.288 READ DMA EXT
c6 00 10 00 00 00 e0 08 00:04:28.288 SET MULTIPLE MODE
91 00 3f 00 00 00 a0 08 00:04:28.288 INITIALIZE DEVICE PARAMETERS [OBS-6]
10 00 00 00 00 00 a0 08 00:04:28.272 RECALIBRATE [OBS-4]
25 00 01 00 00 00 e0 04 00:04:28.272 READ DMA EXT
Does this mean my disk is dying? That would be very annoying after just rebuilding from another failed disk!

Similar Messages

Windows XP system boot failure with \Boot\BCD status 0xc000000f

I have a ThinkCenter M52 purchased secondhand from my employer. It was originally loaded with Vista but was upgraded to Windows XP before I got it. (The recovery partition on the HDD is still Vista.) For the 15 months since I bought I have had no problems. I had to reboot earlier this week because of a software upgrade and now I get:
File: \Boot\BCD
Status 0xc000000f
An error occurred while attempting to read the boot configuration data
From Google searches this is a Vista error, somehow the XP configuration has been lost. I have tried using a partition manager, BOOTCFG from an XP install disc, BartPE. I have run out of ideas, how do I fix this?

Did you check your HDD for errors?Try using Lenovo's hard drive quick test
http://www-307.ibm.com/pc/support/site.wss/MIGr-70578.html#boot
Cheers and regards,
• » νιנαｿѕαяα∂нι ѕαмανє∂αм ™ « •
●๋•کáŕádhí'ک díáŕý ツ
I am a volunteer here. I don't work for Lenovo

Boot failure with AMD core unlock *solved*

Before you criticize me for buying a triple core instead of a quad core, I want you to know that my situation seems to only conflict with Arch.
I have an AMD Athlon II x3. If I unlock the 4th core, Linux live CDs boot up just fine, Windows XP boots fine, Windows 7 boots fine, and as long as any OS completely boots up it runs flawlessly for hours with constant load. However, Arch will fail to boot IMMEDIATELY after unlocking cores. IIRC, the Arch setup CD also fails to boot. I have a small feeling that GRUB has something to do with it, but whenever I attempt to install GRUB2 I'm never able to boot again.
As another note, I can't seem to get IOMMU to work with Arch. With Debian based distros it works immediately, but I can't find anything on how to enable it with Arch. I get this impression that there's a lot of missing Kernel entries in Arch which are causing these CPU problems, and possibly others.
Last edited by schmidtbag (2011-09-27 16:16:30)

schmidtbag wrote:
R00KIE wrote:Not much of an idea then, get /proc/config.gz from the distros that work and the one from arch, compare them and see if you can spot what might be causing the problem. No other ideas here.
debian doesn't have that file, did you mistake it for something different?
I know some distros don't have it but I wasn't aware debian is one of them (I use arch everyday and I try to manage a few centos boxes and that's all), that is an option can be enabled/disabled when building the kernel and it can be quite useful when trying to figure out why something doesn't work (such as seeing which drivers were built and which option was selected when there are multiple choices), however I guess it might have security implications since anyone can find out which options were selected when building the running kernel and some combinations may have yet uncovered/unpublished/undisclosed security exploits.

Msi Z87-GD65 Booting Failure With eSATA Drives

Hi Folks,
Before I go down the (probably ill-fated) Customer Service path I thought I'd address the forum here on a little problem I'm having with my Z87-GD65.
IN essence, if I have a hard drive connected to my eSATA port the PC won't boot. I'm using an ICYDOCK 4 bay external enclosure (MB561US-4SB if interested). If the drive itself is on but the HD trays are ejected then it boots. If any of the drives are secured then it'll hang at a post-BIOS/pre-Windows screen where all I get is a blinking cursor for about 30 seconds and then it disappears to a plain black screen. If the device is powered off then it boots.
I've checked the BIOS with one of the HDs running and it doesn't appear within my boot list - in fact, except for one selection in the bios allowing me to disable eSATA there really isn't much I can do there.
I've upgraded my BIOS to 1.30 from 1.00 and the process seems to move a bit further - now I get the oh-so-pretty ugly Windows logo and that's all.
When I do actually boot the PC with the ICYDOCK off then I'm able to get into Windows normally, and turn on the ICYDOCK. After a few seconds all 4 hard drives report in and everything's fine.
I've been using this ICYDOCK for about a year and a half, with 2 other motherboards (neither were an MSI) and i7 cores, and neither of them caused me any issues. I remember that neither of those boards had the port multiplier eSATA capability so I had to buy a controller card with that capability. I could probably dig that up and see if the problem remains.
In case you're wondering, if it helps, I built a Msi Z87-GD65/4770 i7 - based PC with 2 internal 2TB Hard Drives, and 16gb RAM. I already mentioned the ICYDOCK. I used LiveUpdate to install all the latest drivers & BIOS before uninstalling it.
I build & repair PCs for a living so I'm pretty familiar with what's going on with the system. I figure that there must be something happening between the BIOS and Windows "handoff" of the ICYDOCK, but I'm damned if I can figure out just what.

More information please. PSU, OS being used, etc..
Live Update is best uninstalled. Flash UEFI/BIOS the safer way;
https://forum-en.msi.com/index.php?topic=169827.0
Recommend to download drivers and utilities from the MSI Websites and install manually.
>> Posting Guide <<

Boot Failure with HP HDD

I have an old Vectra VL420 mini tower which I've used to install 3 different operating systems on 5 different IDE Ultra ATA hard drives from different manufacturers. The drives range in size from 40G to 200G.
I have a second, socket 370, system which I built myself using an ASUS TUV4X motherboard. I have used this system to install two different operating systems, each on its own drive.
Both systems run without issue, but here's the rub:
1) I can boot my Vectra with the drives from my home-built system, but...
2) I cannot boot the home-built system with any one of the Windows (Win 2k Pro and XP home) drives from the Vectra, nor can I slave any one of the Vectra's Windows drives to it.
3) I have one drive with an old Red Hat OS that will boot either system.
4) The home-built will not boot if I swap its optical drive with one from the Vectra.
When I try to boot the home-built with the Vectra loaded Windows drives the sequence of events is always the same:
1) Power on...
2) Fans come on and drives start to spin up. This last for about 2 or 3 seconds before...
3) The system shuts itself off (power off). It doesn't even stay up long enough for a BIOS screen to appear.
This also happens when I swap the optical drive with the Vectra's.
I get the impression that the motherboard takes one quick look at the hardware, doesn't like what it sees, and shuts down.
I've spent a lot of time with the TUV4X owner's manual trying to see if there was some parameter in the BIOS or some switch/jumper on the motherboard that would solve this issue. I'm reasonably certain this is a dead end.
I'm beginning to think that there's something peculiar about the way HP formats drives. Perhaps it even modifies the firmware on them.
Any ideas?
Thanks in advance,
Pat

Hi dragnoak,
I'm talking about the USB cable that came with my Navigon 72 Plus. I bought this GPS navigator 2 years ago, which means that I used the cable 8 times (I update the maps 4 times/year), always on my X220t.
I plugged it into the A520's USB 3 port for the first time last week. You know what happened.
I said that the cable has been "destroyed" because I don't know the right English word, but you should understand what that means: the cable stopped working during the first half hour. After that I tried to connect my GPS to the X220t, but to no avail.
Same thing happened to my "pass-through" e-cigarette (it is equipped with a micro-USB port at the bottom). After a few hours the red LED next to the port turned off and the battery stopped charging. I had to order a new cable.
Neither the GPS nor the e-cigarette were damaged, only the cables. Strange things happen sometimes...
I have no doubt that your USB 3 ports work like a charm. Mine don't, since day 1. My external USB 3 compatible HDD is plugged into a USB 2 port, otherwise I can't save anything onto it (just read). In short, I have two useless USB 3 ports. I am not complaining, just talking about a fact.
@TLC2013,
I apologize for using your topic to report my own issues...
X220t | i7 | 320GB HDD | 8GB RAM | WIN7 PRO
IdeaCenter A520 | i5 | 1 TB HDD | 6GB RAM | WIN8.1

W530 Boot Failure with out any BSOD

I bought my thinkpad w530 in Oct. 2012. It works perfect until recent month.
At the beginning, it can't wake up in the sleep mode. If I connect the AC power, it reset the BIOS time.
And nowadays, when i power off this laptop, it can't boot. And I remove and setup the battery, It restored. But if I first connect the ac power/dock, and remove-setup the battery, the BIOS time is reseted.
I updated all my drivers. The failure is still here. I wonder if oneday it died forever?
Thinkpad W530 2lu, 32G DDR 3 Kinston, 500G HDD. K2000m

Can you try resetting your BIOS settings to defaults?
It's also possible that your CMOS battery is depleted, in which case you would have to replace it.
W520: i7-2720QM, Q2000M at 1080/688/1376, 21GB RAM, 500GB + 750GB HDD, FHD screen
X61T: L7500, 3GB RAM, 500GB HDD, XGA screen, Ultrabase
Y3P: 5Y70, 8GB RAM, 256GB SSD, QHD+ screen

Boot failure, endless boot loop

About a week ago I was using my iMac as usual, gaming, when the colors all went wonky, extremely basic colors, and the comp froze. Upon reboot, when the gray screen came up there were vertical artifact lines running down my screen, and after the Apple came up, the wheel would spin for about 10 seconds, then more artifacts would come up, distort the screen, and the computer would lock up.
I attempted to boot into safe mode, but the artifact stripes were still there, and the comp would still freeze.
I booted into single-user mode and ran fsck -fy, it fixed something once, the next time it ran fine, but upon normal reboot the problem persisted.
I put in my install CD and attempted to boot from the CD, same problem.
I booted into hardware check mode, and the scan came up clean, but the stripes were still there, and every time I moved the mouse, the stripes would flicker. Anytime the screen updated, the flicker occurred.
I reset the pram and the SMC, no luck.
I could boot from target disk mode, and I was able to get my pictures onto my laptop thank God, so the hard disk appears to be intact. Every time the firewire logo moved, the flicker appeared and the stripes were there too.
This morning, while in target disk mode, the iMac suddenly reboot itself, and continues to do so forever. The screen turns on but displays nothing, just chimes and chimes. I reset the SMC once and got the gray screen to come up but no Apple, and it just went right back to rebooting itself.
I'm guessing I'm pretty much hosed at this point, but, what the heck happened? I've searched around a bunch and can't find anything exactly like what's going on with mine, but several similar ones. What are my options at this point?
Thanks a ton.

My 24"IMac (Dec 2007) started to automatically reboot 2 days ago. Didn't matter whether I was running any particular application or browsing the net, it would auto reboot, sometimes make it to the logon screen, sometimes not, just an endless loop of rebooting. I tried the SMC reset and the PRAM reset multiple times. A few times I was able to logon to the desktop but even without touching a thing the system would reboot within a few minutes. It finally got to the point of not being able to boot up at all. I could barely hear the fan running and occasional hard drive sounds as the system kept attempting to boot. Tried multiple different outlets, plugging the power cord directly into the wall. Nothing worked.
Fortunately, I had the 3 yr protection plan so dropped it off with the local Apple store yesterday. Picked it up today. Turns out it was a bad power supply. They replaced it with a new one and so far things seem to be working normally. I hope that was the only problem. I know many other IMac owners have had problems with auto rebooting so thought I would post what the fix was for mine. At least Apple didn't have to wipe my hard drive like I've read others have had to do with a similar problem.

Recovery Disk Install will not boot ends with \Boot|BCD error

Hi
I have a Compaq Presario CQ56-219WM with Win7 64bit
The OS needed to be reloaded but the F11 recovery option was not working so I purchased the Factory Recovery DVD's from HP.
When I go through the install procedure with the factory DVD's the sytem is disk is reformatted and programs loaded but the system refuses to boot... it always ends with an error message say that it can not read \BOOT\BCD
I found a genuine Win7 pro DVD from another system and tried to run the repair options but that did not change the error
It seems that the factory recovery disk really don't work in all cases. Can anyone help with this?
Thank you

Boot from the Win 7 disc and try the suggestion here:
http://www.sevenforums.com/hardware-devices/82226-boot-bcd-0xc000000d-unreadable-boot-configuration-...
******Clicking the Thumbs-Up button is a way to say -Thanks!.******
**Click Accept as Solution on a Reply that solves your issue to help others**

No longer able to control iTunes with my razer tarantula keyboard since i updated to v10.4

I have been using Razer Tarantula keyboard for close to 3 years. It worked well with iTunes all the time, i am able to control stop, play, next on my keyboard's built-in keys without the need to Alt+Tab to iTunes. Since i update iTunes 10.4, these keys no longer work.
Am i the only one with this problem? Are there any solutions to it?

FYI - I just fixed the "problem" and still havent quite figured it out other duplicating her settings then pwr off/on bingo
Interesting to say the least. Had everything to do with the speaker setting within System Preferences.... you tell me? lol Later

NO LONGER ABLE TO USE FIREWALL WITH 10.5.5

IT took me a while to figure out it was my firewall preventing me from connecting to the internet, Since I've had no problems before, Until I updated to 10.5.5(The only major change since problem started). Now my firewall setting is "Allow all incoming connections". I would like to have it set at "Set access for specific services and applications". Any suggestions. TIA

Hiya,
that's odd. When you go to system preferences/security and select the firewall tab, you should be able to set to "set access for specific services and applications" with no problems at all (your administrator password may be required).
And whilst not the best, the firewall does work. So most odd, if it should "fail" after the 10.5.5 update. if you cannot find the radio button for the specific access, then try the 10.5.5 combo update http://www.apple.com/downloads/macosx/apple/macosx_updates/macosx1055comboupdate .html,
but do not install until you have repaired disk permissions (which you should do prior to any software update)?

ITunes 11 No Longer Able to Sync Contacts with Google?

Hello,
I sincerely apologize if I am posting a redundant topic here; however, I was unable to find any other posted solutions.
After upgrading to iTunes 11, I noticed that there is no longer an option to sync the contacts on my iPhone to my Google Contacts.
Is this a feature that has been removed? Or is there something that I am missing with the new interface?
Any assistance that you can provide is greatly appreciated, thank you!

I am so beyond fed up with this and with Apple. THANK GOD I just switched to a Galaxy S3. The whole reason I did it is because iOS 6 crossed the line, especially with the removal of the native Google apps, only to replace Maps with the biggest joke of a maps app I have ever seen in my life. Within 5 minutes of turning on my new Android phone, literally every single feature, down to the most minor detail, was better than iPhone. Every iPhone user that has checked out my new phone says the same thing. I cannot find ONE thing that is better on the iPhone. Not ONE thing.
Before activating my new awesome phone, I wanted to sync my busted old piece of junk iPhone with Google contacts so I can seamlessly transfer them to the new phone, and lo & behold, I encounter even more of Apple's BS with regard to Google.
Apple, I can promise you this... by taking this stance against Google & making things SO much harder for your users, you are driving them away from Apple in DROVES, and straight into Googles open arms. Prepare to circle the drain. Switching to Android is the best decision I've made all year. I LOVE MY NEW PHONE!

No longer able to send fax with Brother MFC-8820D

I used to be able to send a fax by going to the Print... dialog box and selecting "Send Fax..." from the dropdown menu. Unfortunately, "Send Fax..." isn't there anymore. I've installed the latest Brother drivers. I'm not sure, but this may have started a couple versions of Leopard ago.
Any ideas?

According to the Brother website, the Printer driver for my MFC is bundled with OS X 10.5. Furthermore, it states: "The Bundled Drivers support the PC-FAX Send and the Status Monitor features." Scanner driver can be downloaded separately, but there's nowhere else to get the fax driver. So I'm still stuck.

TCCService diagnostic crash event after a mini boot time with boot Apple's logo

iOS 7.1 Crashing and showing the Apple's boot logo. However this Apple's boot logo is showed only for few seconds. So, the device shows the "unlock screen". In the iPhone's diagnoses datas there are a new item event "TCCService" . After all, it is a hardware problem or software? If it is a iOS bug can I do something to fix it?

You can go to the feedback page www.apple.com/feedback and click on the link for a bug report. I believe you can copy and paste the information into the comments section. They do not respond to individual feedback, but they do take your email address and can contact you. I have seen it before.

Dropbox - no longer able to open/save with 6.1.3

I recently updated my iPad software to iOS 6.1.3, and I can no longer "Open In" Dropbox. I can still open in all other apps such as Kindle, Evernote, etc. Does anyone have a fix for this? I have uninstalled and reinstalled twice. In fact, Dropbox is no longer in the list of apps in settings? This is odd.. Could Apple have restricted this app?
Thanks!

The App is not restricted. It works fine for me on iOS 6.1.3.
Have you tried restarting or resetting your iPad?
Restart: Press On/Off button until the Slide to Power Off slider appears, select Slide to Power Off and, after the iPad shuts down, then press the On/Off button until the Apple logo appears.
Reset: Press the Home and On/Off buttons at the same time and hold them until the Apple logo appears (about 10 seconds).

IPhoto 09 8.1.1 update: no longer able to sync photos with AppleTV

I have Itunes 9.0.2 (25) and just updated iPhoto 8.1.1 (419) and when I try to synch with my AppleTv 3.0.1 I get an error -50 trying to sync the photos. If I unselect photo sync it will work sync just fine. Also I am now unable to select individual events or photos. That option is now grayed out in ITunes. Did this new update change the iPhoto library format so it is not recognized by iTunes?
I have tried reinstalling both iTunes and iPhoto no help. I also rebuilt the iPhoto library
Help!

I found the problem. This is a new bug introduced in 8.1 of iPhoto.
According to iPhotoManager:
Another recently introduced problem, which appears to only happen with iPhoto 8.1, has to do with music that you've assigned to a custom slideshow. If you have created a slideshow in iPhoto, and using the "Settings" button, have assigned a song from your iTunes library to be played with that slideshow, then if that song has an ampersand (&) character anywhere in the path to the music file (this can include the name of the artist, the album, or the song itself), iPhoto does not write it out correctly to the XML file and you get an error. If you do have a music file assigned to a slideshow, you will either need to assign a different song, or remove any ampersands in the path to the song and re-select the same song in iPhoto to update it to the new location. (make sure to click "Apply" in the settings window to make your change "stick").
This was my problem. I had a song from Simon & Garfunkel in a slideshow and the Path to the song had the & that was malformed.
I removed the slideshow and I am now working.
Apple please fix this bug. I wasted over 5 hours until I went and purchased iPhoto Library Manager and it immediately pointed out the problem.

No longer able to boot - failure with /boot

Similar Messages

Maybe you are looking for