Error After Upgrade To 9.10 - "Mount of filesystem failed..."

[forbidenpasionfruit]

Hi everyone,

I turned my server computer on after a few weeks of not having time to get back to it (after freshly installing 9.04 and getting some great help on these forums!), and it told me that 9.10 was out, so I upgraded in through the update manager.

It restarted a few times, and then on what was to be the last restart, it came up with the following error message:

Mount of filesystem failed. a8d932-6c28-4c09-8b0e-23a20e8c5a9d
A maintenance shell will now be started.
CONTROL-D will terminate this shell and retry.
root@server-desktop:"#

So I did CONTROL-D and this is what came up on the screen aftewards:

root@server-desktop:"# exit
fsck from util-linux-ng 2.16
/dev/sda1: superblock last mount time (sat oct 31 20:09:47 2009,
now=fri oct 30 12:10:06 2009) is in the future

/dev/sda1:UNEXPECTED INCONSISTENCY; RUN FSCK MANUALLY.
(i.e., without -a or -p options) 
swapon: /dev/disk/by-uuid/d5c266b2-fdc9-4417-b537-b4f388cc15c3: swapon failed: Device or resource busy
mountall: swapon/dev/disk/by-uuid/d5c266b2-fdc9-4417-b537-b4f388cc15c3 [910] terminated with status 255
mountall: problem activating swap: /dev/disk/by-uuid/d5c266b2-fdc9-4417-b537-b4f388cc15c3
mountall start/running, process 904
mountall: fsck / [908] terminated with status 4
mountall: Filesystem has errors: /
init: mountall main process (904) teminated with status 3
Mount of filesystem failed.
A maintenance shell will now be started
CONTROL-D will terminate this shell and retry.
root@server-desktop:"#

Restarting doesn't help, and I really don't know where to go from here, and didn't see anything helpful in my searches of the forums before posting here.

Any advice would be great.

Thanks again,
Nicole

[ikt]

/dev/sda1:UNEXPECTED INCONSISTENCY; RUN FSCK MANUALLY.

in the terminal space below type

fsck

after it runs, ctrl+d, and you may have to do it again.

It should generally 'fix itself' after running fsck, as many people had this issue.

[ranch hand]

I have not seen that bug myself but there was quite a bit of it a couple weeks ago. I would;

ubuntu-bug mountall

and follow the directions as they come up.

This will end up with you on the launchpad page with the bug and there should be directions for fixing it.

[zeilant]

[userergel:] schrieb:
> falls es jemand interessiert.
>
> Ich hab am Ende meiner fstab folgende Zeile gefunden:
> /home /home dazukofs
>
> Keine Ahnung wie die dahin kam, hab sie gelöscht und nun gehts.

[forbidenpasionfruit]

Hi guys,

Thanks for the help.

To ikt - I only know a tiny bit about cmd prompt style things, so even though I saw that and it made sense I didn't want to touch it just in case it made a bigger mess!

And in regards to the suggestions, I haven't had to do any of them as today (about 24 hours since the problem) I switched the computer back on, and it just worked - gotta love computers!

Thanks again,
Nicole

[bezt.inc]

I have same problem, and now it's solved.
Thanks a lot you guys

[OldGamer]

Thanks for the excellent advise! I had this same problem, and after running fsck one time (from the maintenance prompt), my ubuntu boots again. As always, this forum is great!

[fooliot]

in the terminal space below type

fsck

after it runs, ctrl+d, and you may have to do it again.

It should generally 'fix itself' after running fsck, as many people had this issue.

where can i find the space mentioned here? sorry if i wasn't clear before.

[jakare]

Edit:
I had fixed this problem but it wasn't solved by typing fsck. So when I shut
my computer off the problem returned. I think I should have used the terminal and type
fsck when ubuntu worked. Is the only way to reach terminal by using ubuntu cd or is there
another way, because in this "mount of filesystem failed" page I cannot do
anything else than pressing control D. This seems to be a shell??

[Dougle]

in the terminal space below type

fsck

after it runs, ctrl+d, and you may have to do it again.

It should generally 'fix itself' after running fsck, as many people had this issue.

Thanks Ikt, i've just put my laptop back together after cleaning it and got this error, an fsck fixed it within 2 mins, cheers.