Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


Unable to boot up.

  • Please log in to reply
2 replies to this topic

#1 RythTheYoshi


  • Members
  • 10 posts
  • Local time:06:05 AM

Posted 29 July 2013 - 06:12 PM

Every time I try to run my computer, it will boot up as normal. However, it will stick to the splash screen, then freeze. If I press F1, I can see lines of text stating:

Mountall: Plymouth command failed
Mountall: Disconnected from Plymouth
*Setting sensors limits. [OK]
Starting avgd (recovering).
*Speech-dispatcher configured for user sessions
*Starting VirtualBox kernel module
* done.
*starting the winbind daemon winbind. [OK]
*PulseAudio configured for per-user sessions
* Enabling additional executable binary formats binfmt-support. [OK]
* Starting Adaptive read ahead daemon preload. [OK]
*Checking battery state... [OK]

The format is as close as I could make it, I'm typing this off my iPad. The desktop was a Linux Mint 9, but I did run an update to upgrade to Linux Mint 14, I believe, from the terminal, not through an iso or USB.

Nevertheless, the boot stops here and doesn't progress. Any help would be thanked!

BC AdBot (Login to Remove)


#2 stiltskin


  • Members
  • 238 posts
  • Gender:Male
  • Location:Western MO
  • Local time:08:05 AM

Posted 29 July 2013 - 07:43 PM

Just a guess here. If you went straight from 9 to 14, you most likely munged a lot of libraries and other things up. In other words, there's a good chance all is lost.


Well, not ALL lost. You can still rescue /home. Particularly if you have it as a separate partition. If not, you can still boot from a live CD/DVD/thumbdrive, copy everything there to some other place, and save it that way. But if /home is on a separate partition, you can reinstall (almost certainly needed) without losing anything there. Just tell the new installer to use that same partition as /home.


If you didn't set a separate partition, now would be a great time to create one to save everything for the future. On my desktop machine I still have almost exactly the same /home I had several years ago. I added things to it. I had to move it to other drives. I even put a copy of the identical partition on a netbook. But there's stuff there that was created in the early-to-mid part of the last decade.


I once did an Ubuntu upgrade on a Mac that went from one version to another 3-5 releases later. But I did that by upgrading one release at a time. If I had done 2, I might have lost stuff. If I'd done 3, I definitely would have had problems like you're seeing.

#3 RythTheYoshi

  • Topic Starter

  • Members
  • 10 posts
  • Local time:06:05 AM

Posted 29 July 2013 - 07:47 PM

I'm not entirely sure if it was 9 to 14, but it was a jump. Odd thing was that it has worked after the update. I was out when I was told of this problem, and I just now got to it and learned that this started ever since a power outage. Maybe it shorted the battery out, saying that it stops at checking the battery state?

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users