0

Laptop battery of my Lenovo Ideapad S205 ran out of power while upgrading to 14.10. I connected it and powered it up as usual, but forgot about resuming the upgrade. Then I put it to hibernate, and since then it's stuck in a boot loop whenever I turn it on.

The BIOS screen will load and the fan go on, but then it will turn black and the fan goes off. Then it does the same again, on and on.

I can boot from live USB fine. I have chrooted and resumed the upgrade from here (dpkg --configure -a, then apt-get upgrade again) and configured Grub to show the boot menu (edited /etc/default/grub, then update-grub && grub-install /dev/sda). But the boot loop remains. I guess it never gets to the point where Grub takes over.

Could it be that the hibernated session is broken and is preventing the boot procedure? Can I "clear" it? Edit: I tried to clear it with mkwap as suggested, but had no success. Btw the root and swap partitions are LVM, but the /boot partition is ext2.

What else could cause this behaviour?

Arild
  • 455

3 Answers3

1

You can clear the hibernated session by cleaning the swap partition (if isn't cleaned)

you can know what is your swap partition by running:

lsblk -f | grep swap
├─sda5 swap         81ede0e2-2b07-4986-9a98-cea7a5b22556 [SWAP]

Then, you can clear it:

mkswap /dev/YOUR-SWAP-PARTITION
Abdelhak Bougouffa
  • 76
0

May be your grub installation is corrupted. I would try to reinstall grub2: 

apt-get --reinstall install grub2

If I can add, would not rule it took to check the integrity of fs in the partition in question.

fsck /dev/sdaX

Edit: Did you fsck /boot partition? In this case (separate /boot partition) the correct grub-install command is grub-install --boot-directory=<mnt>/boot /dev/sda , where <mnt> is the mount point of your previously mounted /boot partition.

bolichep
  • 418
0

I gave up, so I made a backup of my home directory using a LiveUSB and chroot, and then I reinstalled Ubuntu 14.04.

After that I upgraded the system again, only to find that it was actually the 14.10 upgrade that broke the system. I suspect that this bug might be the culprit, but I'm not sure, as I couldn't really reproduce the efibootmgr steps (/sys/firmware/efi did not exist).

In the end I reinstalled the system again, and will simply avoid upgrading.

Arild
  • 455