Linux Mint Forums

Posted: **Mon Apr 14, 2008 12:04 am**

It says this;

* Checking file systems...
fsck 1.40.2 (12-Jul-2007)
/home: clean, 23621/8176896 files, 1498433/16506779 blocks
fsck.ext3: Unable to resolve 'UUID=a67a30a7-d7f9-41cd-3f2ed4dff391'
fsck died with exit status 8
                                                     [fail]
* File system check failed
a log is being saved in /var/log/fsck/checkfs if that location is writable.
Please repair the file system manually.
* A maintenance shell will now be started.
CONTROL-D will terminate this shell and resume system boot.
bash: no job control in this shell
bash: groups: command not found
bash: lesspipe: command not found
bash: Command: command not found
bash: The: command not found
bash dircolors: command not found
bash: Command: command not found
bash: The: command not found
root@user-desktop:~#

If I type "exit" here it boots up the system fine. What do I do to fix whatever is wrong?

A bit more information;

1) I'm triple booting, Linux Mint should be on partition 5
2) The /home is a different partition, I think it's partition 6
3) Partition 1 is windows, 2 is swap, 3 is linux, 4 is "extended" (whatever that means)

Posted: **Mon Apr 14, 2008 12:14 am**

You are in UUID hell. More on that here:
http://www.linuxmint.com/wiki/index.php ... _a_problem

Here's my get out of jail card / how-to-note for this problem:
As stated, this is a UUID corruption problem that pops up at times when installing a different distro on a multi-boot computer. And the following is what can be done on a multi-boot to fix it. In a terminal:

Code: Select all

sudo vol_id /dev/sdbx -u

(where x is the location of the offending partition)--this will display the UUID you need to...change (note it's a good idea to run the id command for all the disk numbers to have them handy because you need to change those that are listed wrong in fstab - see following).

Type the following in terminal:

sudo gedit /etc/fstab

...and replace the UUID for the offending partition with the new one you got from vol_id.

Now that is what you do if you want to keep the UUIDs. However, I prefer to do as indicated in the Wiki; I prefer to use device names in fstab instead of UUIDs.

Example:

Code: Select all

sudo gedit /etc/fstab

opens fstab in a text editor. The following is an example of what your might end up with.
#
# /etc/fstab: static file system information.
#
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/sda1 / ext3 defaults,errors=remount-ro 0 1
/dev/sda5 /home ext3 defaults 0 2
/dev/sda3 /media/sda3 ext3 defaults 0 2
/dev/sda4 /media/sda4 ext3 defaults 0 2
/dev/sdb3 /media/sdb3 ext3 defaults 0 2
/dev/sdb5 /media/sdb5 ext3 defaults 0 2
/dev/sdb6 /media/sdb6 ext3 defaults 0 2
/dev/sda6 none swap sw 0 0
/dev/sdb7 swap sw 0 0
/dev/hdd /media/cdrom0 udf,iso9660 user,noauto,exec 0 0
/dev/hda /media/cdrom1 udf,iso9660 user,noauto,exec 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec 0 0

Hope this gets you back in the game.

Posted: **Mon Apr 14, 2008 8:47 am**

I'm pretty sure that fixed it (it's booting up quite fine without interruption now). Thanks!

Posted: **Mon Apr 14, 2008 8:51 am**

Glad it worked. Keep it in a Tomboy note or someplace handy. It will happen again...

Linux Mint Forums

Checking file systems error on boot?

Checking file systems error on boot?

Re: Checking file systems error on boot?

Re: Checking file systems error on boot?

Re: Checking file systems error on boot?