Welcome to the most active Linux Forum on the web.
Go Back > Forums > Linux Forums > Linux - Desktop
User Name
Linux - Desktop This forum is for the discussion of all Linux Software used in a desktop context.


  Search this Thread
Old 05-29-2012, 02:15 AM   #1
Registered: Jul 2011
Distribution: ubuntu 10.10
Posts: 42

Rep: Reputation: Disabled
Boot failure upon updating e2fsprogs in ubuntu 10.10

I just installed the latest e2fsprogs from source (sudo make install) to update the existing version on ubuntu 10.10. However, upon restarting the computer it produces errors which can be seen in the picture attached, and mentions fsck. The boot process appears to stop there. Of course, the system loaded enough code from the hard drive to print those messages so it must be able to access the file systems, which are fine, as I can browse them using a live cd. So I'm not clear as to what those messages really indicate.

My update of e2fsprogs is likely the problem, but I don't know for sure. How do I fix this?

Perhaps it can be fixed by uninstalling the new e2fsprogs. I would cd to their directory and run make uninstall. However I don't know how to do that without having the system boot. Maybe by using a live cd and chroot but I'm not sure about the exact steps. I extracted e2fsprogs to a dir in my home folder, which is on a separate partition (sda2) from the main installation (sda3). I did
chroot /mnt/sda2
but I don't know how to mount sda3 to /home.
mount -t ext4 /mnt/sda3 /home
and variations on that command using --bind result in "device doesn't exist" errors. /mnt/sda3 would now be an invalid pointer, but I tried /dev/sda3 and that doesn't work also. I tried running the commands with sda3 both mounted and unmounted (to /mnt using puppy gui) but it doesn't work in both cases. Copying from urxvt doesn't work for some reason (using puppy live cd) so didn't paste the whole command log.

Please answer as soon as possible.
Attached Thumbnails
Click image for larger version

Name:	fsck 001.jpg
Views:	11
Size:	270.4 KB
ID:	9776  

Last edited by Xl1NntniNH7F; 05-29-2012 at 10:15 AM.
Old 05-29-2012, 10:27 PM   #2
LQ Veteran
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 15,987

Rep: Reputation: 2217Reputation: 2217Reputation: 2217Reputation: 2217Reputation: 2217Reputation: 2217Reputation: 2217Reputation: 2217Reputation: 2217Reputation: 2217Reputation: 2217
fsck is telling you the devices don't exist - do they ?. You can certainly check the UUIDs from the liveCD.
Why are fsck's being forced on those filesystems - do you have that set in fstab or the f/s itself ?.

What convinced you to upgrade the tools ?.
Old 06-01-2012, 04:48 AM   #3
Registered: Jul 2011
Distribution: ubuntu 10.10
Posts: 42

Original Poster
Rep: Reputation: Disabled
The UUID's seem to be correct:
# blkid /dev/sda1
/dev/sda1: LABEL="boot" UUID="adef9a8b-8e42-4eb9-b4ec-3d2f452c0edf" TYPE="ext4"
# blkid /dev/sda2
/dev/sda2: LABEL="ubuntu" UUID="c586946d-5781-478d-bef6-f08b997d281f" TYPE="ext4"
# blkid /dev/sda3
/dev/sda3: LABEL="h" UUID="20750408-b2e2-4299-9562-97c4fd53cd6e" TYPE="ext4"
# blkid /dev/sda4
/dev/sda4: LABEL="files" UUID="7039a01e-e4a2-40ee-8934-257b1cabeb0f" TYPE="ext4"

I don't why they're being checked. Here is fstab (relevant section):
UUID=c586946d-5781-478d-bef6-f08b997d281f / ext4 relatime,errors=remount-ro 0 1
UUID=20750408-b2e2-4299-9562-97c4fd53cd6e /home ext4 nodev,nosuid 0 2
UUID=adef9a8b-8e42-4eb9-b4ec-3d2f452c0edf /boot ext4 defaults,exec 0 1
UUID="7039a01e-e4a2-40ee-8934-257b1cabeb0f" /media/files ext4 defaults 0 2
/mnt/1024Mb.swap none swap sw 0 0

I upgraded e2fsprogs because it says on their website that they fixed important bugs.

Last edited by Xl1NntniNH7F; 06-01-2012 at 04:53 AM.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Cannot continue to boot Ubuntu 64 bit Linux due to FSCK error in superblock albertwt Linux - Newbie 5 01-08-2011 07:14 AM
Removing external drive causes boot failure: fsck.ext3: unable to resolve... David Marks Linux - Hardware 6 06-23-2009 11:14 AM
ubuntu 8.04, inodes-orphan relationships cause boot to fail until fsck done mokrunka Ubuntu 2 10-02-2008 10:03 PM
fsck failure at boot time - hda mounted twice Steve2001 Linux - General 1 07-30-2005 11:45 AM
fsck failure Zorck Linux - Newbie 2 04-01-2002 08:19 AM > Forums > Linux Forums > Linux - Desktop

All times are GMT -5. The time now is 10:38 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration