Ubuntu

unable to run fsck

Asked by Rebecca Hixon

I have never used Linux and I have a problem with a VM running Ubuntu 8.04.3 (64-bit).
I received the following error after the system was shutdown improperly.

fsck 1.40.8 (13-Mar-2008)
root: clean, 7288/489600 files, 112768/1953905 blocks
    ...done.
*Checking file systems:
fsck 1.40.8 )13*Mar-2008)
boot: clean, 38/122880 files, 63033/489948 blocks
home: clean, 5641/236640 files, 180855/945826 blocks
opt: clean, 8277/61200 files, 359471/2441880 blocks
tmp contains a file system with errors, check forced.
tmp:
Indoes that were part of a corrupted orphan linked list found.
tmp: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
    (i.e., without -a or -o options)
usr: clean, 61234/612000 files, 348032/2441872 blocks
var: clean, 3302/417792 files, 211594/1668751 blocks
fsck died with exit status 4
...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.
Give root password for maintenance (or type Control-D to continue)

I do not know what commands to type to run the fsck and as far as I know we do not have the cd.
Any help would be greatly appreciated.

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
peter b (b1pete) said : 		#1

Rebecca, pls run

fsck --help

first, that will display a list of options/switches available in that fsck version (1.40.8) that you're having. for sure there will be a switch available to allow a fs automatic repair, it may be something like

fsck -p

as it is in the latest lucid release or something else/different. pls use caution. there will be for sure displayed quite a few other switches; if in doubt pls ask.

Revision history for this message
Antonio Litterio (antonio-litterio-gmail) said : 		#2

Dear Rebecca
your problem is caused to some errors in filesystem. To repair this problem simply you must launch command fsck.
Do after those error lines appear the command line?
Then put your password to enter in shell like a root. If you are root you'll see "#" at the end of name shell with something like this "myname@laptop:~#"

Then launch command fsck "myname@laptop:~#fsck" and put 'y' when it asks you some questions.

Sorry for my English....

Regards
Antonio

Revision history for this message
Vishal Telangre (vishaltelangre) said : 		#3

fsck is the FileSystem ChecKer, which runs automatically when you boot if you didn't shutdown cleanly. Type "man fsck" for information on running it manually. The command "sudo shutdown -F -r now" will force a reboot and a filesystem check; "sudo touch /fastboot" will skip a filesystem check at next reboot

Can you help with this problem?

Provide an answer of your own, or ask Rebecca Hixon for more information if necessary.

To post a message you must log in.