Mint17-64 Boot fail after updates interrupted

Questions about Grub, UEFI,the liveCD and the installer
Forum rules
Before you post please read how to get help
Post Reply
jotrago
Level 1
Level 1
Posts: 12
Joined: Thu Dec 19, 2013 12:52 pm
Location: Cape Town
Contact:

Mint17-64 Boot fail after updates interrupted

Post by jotrago » Tue May 19, 2015 11:01 am

Cannot boot Mint 17 (64) after updates interrupted.

Mint 17.1 Cinnamon 64 bit on Dell Vostro 3500 i5 8Gig Ram 500G Drive
Mint Only no windows or dual boot
Boot, Root, & Home Partitions

I was running updates (unattended) when the machine powered off during a power cut.

On boot up I now get "udevadm settle is not permitted while udev is unconfigured", and a couple of variants
Also "mdadm Create Group Disk is not found" errors repeatedly at the cli screen, it never gets to the gui.

AFAIK there is no raid on the system. it's a laptop with a single drive so I am puzzled as to why mdadm is involved.
Mint may have enabled volume manager during install if that is the default.

Grub Boot page shows only the latest Kernel & it's recovery option. No "Previous" versions.
Neither the main version or the recovery version boot, both give the same errors as above.

I found various references to updating initramfs using update-initramfs when running from a live CD.
http://ubuntuforums.org/showthread.php?t=1567147
&
http://georgia.ubuntuforums.org/showthr ... ?p=9798322

I tried with the Parted Magic CD but that does not have the update-initramfs command. (it appears to be unique to ubuntu)
I then booted off my original Mint 17.1 Install usb drive.
I was able to boot up, mount my boot partition, I could see the various Kernel 3.13.0-37-generic modules including the initrd.img-3.13.0-37-generic archive.

I could not get chroot to work. It gave "chroot: failed to run command '/bin/bash': no such file or directory.

This appears to be because chroot expects to find a whole /bin folder structure in the folder to be chrooted, which of course my boot partition does not have.
I tried creating a /bin folder and copied the bash file there, but to no avail.

Other solutions I have been able to find all involve booting into recovery mode, which is not working for me, nor are any previous versions dispalyed in Grub

I am beginning to think that maybe I can re-install the whole boot partition without overwriting the root & home partitions, but have no idea how to do that.

Can any one point me in the right direction here.
Mint 17.3 (64) Cinnamon
Dell Vostro 3500 i5 8G Ram 500G Seagate Hybrid Drive with 4G SSD
Virtual Box 5 with Mint 17 (64); Win XP; Win7; Win2008; Dos6.2; Virtual Machines
Synology DS212 Nas
Draytek Vigor 2860VN+ Router

jotrago
Level 1
Level 1
Posts: 12
Joined: Thu Dec 19, 2013 12:52 pm
Location: Cape Town
Contact:

<SOLVED> Mint17-64 Boot fail after updates interrupted

Post by jotrago » Tue May 19, 2015 3:26 pm

SOLVED

Further research found this old bug on Ubuntu Launchpad
https://bugs.launchpad.net/ubuntu/+sour ... bug/358654

The solution is to use a live-CD to mount the system (or boot from a completely separate installation), mount the failed OS partition(s), and complete the update process:
e.g.
sudo -i
# create a target mount point
mkdir tmproot
# mount root
mount /dev/sda2 /home/mint/tmproot
# mount boot into the boot folder in root
mount /dev/sda1 /home/mint/tmproot/boot
# into Rebecca
chroot /home/mint/tmproot


NB the devices and paths were specific to my installation, adjust as necessary for your own

Now I understand the issue with chroot
First we need to mount the root folder in the mount target (which includes the full bin folder structure, including bash.
THEN we mount the boot partition in the BOOT Folder in root.
NOW when we run chroot there IS a /bin/bash and all is good

# update
dpkg --configure -a


Accept the defaults for modified config files
Noticed a section setting up UDEV
Noticed update-initramfs, generating a new initrd.img-3.13.0-37-generic
Noticed a warning “no support for locale: en_ZA.utf8 (remember seeing a post regarding this, will fix later)
https://codeghar.wordpress.com/2014/09/ ... initramfs/
Finally some errors regarding openjdk-7 and icedtea-7 (probably I can just update these later)

# done
exit
#unmount
umount /home/mint/tmproot/boot
umount /home/mint/tmproot/


Rebooted and Mint came up successfully (Phew!!)

For the sake of completeness I then ran update manager to update all to latest.
This whole issue started when previously I tried Update Manager and it would not run
Then in running updates manually from the CLI we had the power failure.

Now Update Manager runs to completion and I get the Green Tick

All is wonderful.

In the process of all this I discovered the Ubuntu "Boot-Info" and "Boot-Repair" utilities (Google "ubuntu boot-repair)
which are very useful. Boot-Info collects boot info and posts it to pastebin to facilitate support and form assistance.

For Reference this is the the boot-info output for my recovery setup, booted off a Mint 17.1 USB (/dev/sdb) mounting /dev/sda with my original Root (/sda2) & Boot (/sda1) Partitions.
http://paste2.org/WzEOvDx5

And this is is the Boot Info from my recovered original configuration. All partitions on /dev/sda
http://paste2.org/CZYmxpzk
Mint 17.3 (64) Cinnamon
Dell Vostro 3500 i5 8G Ram 500G Seagate Hybrid Drive with 4G SSD
Virtual Box 5 with Mint 17 (64); Win XP; Win7; Win2008; Dos6.2; Virtual Machines
Synology DS212 Nas
Draytek Vigor 2860VN+ Router

Post Reply

Return to “Installation & Boot”