Link to home
Create AccountLog in
Avatar of Thyagaraj03
Thyagaraj03

asked on

File system maintenance error, press ctrl+d to continue

In my office I've Ubuntu 8.10 desktop installed and it's running for a long time. When ever the system is started, I'll get a file system maintenance error and something it's prompted for the root password or (press ctrl+d to continue). After pressing Ctrl+D the system normally boots up. I could not resolve this issue for a long time and I think something should be done in the fstab  file. I'm not sure to do anything and expecting the experts here to help to perfectly fix this. Any help is appreciated.
Avatar of carlosevp
carlosevp

Hi.
Maybe you have a problem on the filesystem, so its better run a fsck over it.
After this, you can disable the auto-test by editing /etc/fstab and setting the last numerical values to 0.
Good Luck!
Avatar of Thyagaraj03

ASKER

I think running fsck may corrupt, is there any precautions I've to take before running. And how to run fsck, just typing fsck or fsck with root partition.
its always important to backup your data, but if anything is corrupted fsck will try to fix it.
just run "fsck /" if the problem is in your root partition.
Good Luck!
Hi!

Did the fsck work? Have you plugged in another disk in your computer before you got this error?

Can you show the output of:

cat /etc/fstab
sudo fdisk -l
sudo blkid
ls /media

Open in new window


Regards, Tobias
@TobiasHolm: No I didn't plug in any device. I'm afraid to run fsck, sometime it may corrupt the file system I think


fstab:
---------------------------------
# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
# /dev/sda1
UUID=2380956e-8ac1-4860-8542-67e63759ec8a /               ext3    relatime,errors=remount-ro 0       1
# /dev/sda5
UUID=47669975-5f5e-4ebb-add6-01c584162780 /home           ext3    relatime        0       2
# /dev/sda6
UUID=59066004-323b-4e2d-bbb4-a72c92dc1b3d /mnt/part1          ext3    relatime        0       2
# /dev/sda7
UUID=a6af12aa-e2c9-4b81-94e2-d7db95627337 /mnt/part2          ext3    relatime        0       2
# /dev/sda8
UUID=9d5d5c14-d7de-48f4-94cc-1dc8a2a4b986 /mnt/part3          ext3    relatime        0       2
# /dev/sda9
UUID=aee456b0-c570-4e98-91e3-4f5de89dad59 none            swap    sw              0       0
/dev/scd0       /media/cdrom0   udf,iso9660 user,noauto,exec,utf8 0       0
-----------------------------------------------

fdisk -l:
------------------------------------------
Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0005d1e0

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        4868    39102178+  83  Linux
/dev/sda2            4869       30401   205093822+   5  Extended
/dev/sda5            4869        8637    30274461   83  Linux
/dev/sda6            8638       13621    40033948+  83  Linux
/dev/sda7           13622       18971    42973843+  83  Linux
/dev/sda8           18972       30036    88879581   83  Linux
/dev/sda9           30037       30401     2931831   82  Linux swap / Solaris
-------------------------------------------------------------------

blkid:
-----------------------------------
/dev/sda1: UUID="2380956e-8ac1-4860-8542-67e63759ec8a" TYPE="ext3"
/dev/sda5: UUID="47669975-5f5e-4ebb-add6-01c584162780" TYPE="ext3" SEC_TYPE="ext2"
/dev/sda6: UUID="59066004-323b-4e2d-bbb4-a72c92dc1b3d" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda7: UUID="a6af12aa-e2c9-4b81-94e2-d7db95627337" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda8: UUID="9d5d5c14-d7de-48f4-94cc-1dc8a2a4b986" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda9: TYPE="swap" UUID="aee456b0-c570-4e98-91e3-4f5de89dad59"
--------------------------------------------------

ls /media:
------------
cdrom cdrom0
----------------

ok. If you haven't changed the disk config before the CTRL+D message begun to show I think you should run a fsck. Maybe you can see the complete error and which disk that's affected with the dmesg command?

dmesg

Open in new window

ASKER CERTIFIED SOLUTION
Avatar of TobiasHolm
TobiasHolm
Flag of Sweden image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account