Ask Ubuntu is a question and answer site for Ubuntu users and developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've installed Ubuntu on an ASUS S200E, but after the installation I'm no longer able to run either Ubuntu or Windows 8. This is the boot-repair log I've got, here you can find all the info:

After using boot-repair, this is the new bootinfo summary:

Now, I can boot the system, but I can't login ("invalid password" error). Maybe boot-repair deleted some system files?

SOLVED: Thank you, the problem was that Ubuntu wasn't correctly installed. The installation procedure didn't create the user! I've reinstalled Ubuntu, re-did the boot-repair procedure, and now everything works.

share|improve this question

According to , Boot-Repair has successfully setup your boot in UEFI mode.

Boot-Repair never (cannot) touches files related to login, so the "invalid password" error is due to something else. Eg, if your password contains numbers or special character, try to type it with CapsLock enabled/disabled.

share|improve this answer

It's not clear precisely what your symptoms are. If I'm reading correctly, you were initially unable to boot either OS, but after running a boot repair utility, you're now able to boot, but not log in, to at least one OS. Which OS(es) are bootable is unclear to me. I'm guessing you can boot but not log into Linux and are unable to boot Windows. I have some observations:

  • Windows 8 includes a "fast boot" feature that involves leaving disks in an unclean state on shutdown. This may work fine on a Windows-only computer, but on a dual-boot system, it's a problem waiting to happen. I recommend you disable it by typing powercfg /h off in a Windows Administrator command prompt. With any luck that action will clean up the errors associated with /dev/sda5 in your Boot Info Script output.
  • Your disk (/dev/sda; it looks like /dev/sdb is a USB flash drive) is set up with a GUID Partition Table (GPT), and if Windows ever booted from this disk that means that Windows was booting in EFI mode.
  • Your disk (again, /dev/sda) has GRUB BIOS-mode boot code in the MBR. If your computer is booting in EFI mode, this is unnecessary at best. On some systems, it can cause boot problems because some EFI implementations look at the MBR and decide which boot mode to use based on the presence or absence of BIOS boot code in the MBR. That said, if you're successfully booting Ubuntu in EFI mode, you should probably leave this alone.
  • Your grub.cfg file lacks an entry for Windows, but you've got two such entries in /etc/grub.d/25_custom. You might be able to incorporate them into your GRUB menu by typing sudo grub-mkconfig -o /boot/grub/grub.cfg. Alternatively, you could try another boot manager, such as rEFInd or gummiboot. In fact, these can both boot Linux kernels directly, bypassing GRUB, but you'll need to do some extra configuration to get this to work. For rEFInd, once it's set up you won't need to do any more changes in the future; but for gummiboot, you'll need to edit your boot configuration manually whenever you update your kernel.

As LovinBuntu says, a boot repair utility shouldn't have touched your password. If you're desperate enough, you can boot with an emergency disc and edit /etc/shadow on your main installation directly with a text editor. Back up the original file before proceeding, in case you make a mistake. The second colon-delimited field (right after username:, where username is your username) holds the password. It's hashed, so it will be unintelligible and quite long. Delete the password only (up to the next colon on that line) and when you reboot your account will have no password. Log in and change it immediately. Of course, it's best to check the simple obvious-in-hindsight possibilities like the stuck Caps Lock key that LovinBuntu suggested first!

share|improve this answer
Thank you, the problem was that Ubuntu wasn't correctly installed. The installation procedure didn't create the user! I've reinstalled Ubuntu, re-did the boot-repair procedure, and now everything works. – Abral Nov 22 '12 at 18:39

Check out the links below. They have helped me. Can help you as well.

Win7 installed first and Win7 still controlling startup after Linux installation ( )


Windows 7 installed first and Ubuntu's GRUB2 on Windows partition controlling startup


share|improve this answer
Welcome to Ask Ubuntu! Whilst this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the link for reference. – fossfreedom Nov 24 '12 at 21:21

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.