A mount of filesystem failed

bacy · 11-07-2009, 06:13 AM

hi to everybody, I have a problem that I don't succeed in resolving...
I passed from 9.4 to ubuntu 9.10 to the beginning been all right everything, but when I restart the pc i found this:
mount of filesystem failed
4c291a-bc0f-49ab-8936-a6e222d5065
A MAITENANCE SHELL WILL NOW BE STARTED
CONTROL-D will terminate this shell and re-try
root@foura-laptop:

what can I do? please, I am writing the thesis and I need the computer.
Thanks
bacy

camorri · 11-07-2009, 06:40 AM

You have something wrong in your /etc/fstab file for the partition that did not mount. Open an editor, copy and paste the contents of the /etc/fstab file here.

When you upgraded, did you format any partitions beisdes the '/' ( root partition )? Just a guess, 9.10 is using ext4 by default. So this may not match the fstype of the partiton(s) not mounting.

eth1 · 11-07-2009, 06:50 AM

This problem is because the /(root) file system has file system corruption errors.

Identify the root file system device name using,

Quote:

fdisk -l

Depending on the output you get run a file system check on the partition. If it's a ext4 file system,

Quote:

fsck.ext4 /dev/sdaX

where /dev/sdaX is the / partition. If it's a ext3 file system then you need to run fsck.ext3 /dev/sdaX

bacy · 11-07-2009, 07:31 AM

Quote:

Originally Posted by eth1

This problem is because the /(root) file system has file system corruption errors.

Identify the root file system device name using,

Depending on the output you get run a file system check on the partition. If it's a ext4 file system,

where /dev/sdaX is the / partition. If it's a ext3 file system then you need to run fsck.ext3 /dev/sdaX

what means of this: "Identify the root file system device name using"
you must think that I am ignorant in this field...I don't understand anything!

bacy · 11-07-2009, 07:36 AM

you must think that I am ignorant in this field, I don't understand anything!
you explain to a child as to resolve her problem...
thanks of your patience
:-(

camorri · 11-07-2009, 10:11 AM

bacy,

Here is what you were asked to do. I did it on my system, and am posting the results to show you how.

Open a konsole, and use the 'su' command to get root privileges.

Quote:

[cliff@Duelie:~]$ su
Password:
[root@Duelie cliff]# fdisk -l

Disk /dev/sda: 160.0 GB, 160040803840 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x16001600

Device Boot Start End Blocks Id System
/dev/sda1 * 1 1784 14329948+ 83 Linux
/dev/sda2 1785 19457 141958372+ 5 Extended
/dev/sda5 1785 2038 2040223+ 82 Linux swap / Solaris
/dev/sda6 2039 19457 139918086 83 Linux

You need the root password, you would set that up at install time. Then run the command 'fdisk -l' ( without the quotes ).

The ID field identifies the file system type. 83 is ext3. 82 is swap file system.

Once you know what partition number, and the file system, you run the command 'fsck.ext4 /dev/sdaX' This would be for ext4, the default for Ubuntu 9.10. You need to use the correct partition number, my system has sda1 and sda6. Yours will have possibly the same, or different depending on the types of harddrives, and the partitioning scheme you have.

Hope this makes it easier to follow.

clayb226 · 11-07-2009, 10:13 AM

Use the fdisk -l command to find out which partition has the / mount point, and then run the fsck command on that partition.

kihitara · 11-12-2009, 01:47 PM

I get this message, too, after rebooting.

I did fdisk -l

Mine shows that Linus is on dev/sda1 (boot) and dev/sda5

I typed fsck.ext4/dev/sda1
and got bash: fsck.ext4/dev/sda1: No such file or directory

I get the same when I try sda5

kasunbg · 11-12-2009, 05:14 PM

Quote:

Originally Posted by kihitara

I typed fsck.ext4/dev/sda1
and got bash: fsck.ext4/dev/sda1: No such file or directory

You have to put a space after fsck.ext4 . That means in your case, the command would be,

Code:

fsck.ext4 /dev/sda1

hth

kihitara · 11-12-2009, 06:59 PM

Ahhhh thank you. Well, I have reinstalled the whole system and it seems to be working so far (this is about install 10... so I'm not holding my breath). If it happens again, I will definitely do that. Thanks.