Results 1 to 6 of 6

Thread: embarassing fsck problem

  1. #1
    Join Date
    Feb 2007
    Beans
    303
    Distro
    Ubuntu 9.04 Jaunty Jackalope

    Red face embarassing fsck problem

    Hi,
    Ive been telling my friends how great linux is and one of them is interested in giving it a try. So I was gonna let her try it out on my computer, but when I turned it on it came up with an error (I was so embarrased, especially since I kept claiming linux to be rock solid ).

    I have no idea what could possibly have caused this since the last time I used the computer I didnt do anything that could have broken it, nor do I remember installing updates.

    Anyway here's what I get at startup:

    activating swap...
    checking root file system...
    fsck 1.41.3 (12-oct-2008 )
    /dev/sda3 contains a file system with errors, check forced.
    /dev/sda3:
    Inode 1163301 has illegal block(s).

    /dev/sda3: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
    (i.e., without -a or -p option)
    fsck died with exit status 4
    [FAIL]
    *An automatic file system check (fsck) of the root filesystem failed.
    A manual fsck must be performed, then the system restarted.
    The fsck must be performed in maintanence mode with the root filesystem mounted in read-only mode.

    *The root filesystem is currently mounted in read-only mode.
    A maintanence shell will now be started.
    After performing system maintanence, press CONTROL-D
    to terminate the maintanence shell and restart the system.
    bash: no job control in this shell
    root@ed-desktop:~#



    So I tried typing 'fsck' and i get this next:

    fsck 1.41.3 (12-Oct-2008 )
    e2fsck 1.41.3 (12-Oct-2008 )
    /dev/sda3 contains a file system with errors, check forced.
    Pass 1: Checking inodes, blocks, and sizes
    Inode 1163301 has illegal block(s). Clear <y>?


    I'm a but unsure what to say since I dont even understand what the problem is, nor what's going on.

    Please guys, I'm hoping some of you can help me with this issue and hopefully help me re-convince my friend linux really is more stable. Of all the times to happen it had to occur when she's around lol.

    Thanks in advance.

  2. #2
    Join Date
    Mar 2009
    Beans
    3

    Re: embarassing fsck problem

    I am also a new ubuntu user, so take this with a grain of salt. Hit the "y" button to say yes, and continue to do so until it prompts you to reboot. On reboot it should start correctly.

  3. #3
    Join Date
    Feb 2007
    Beans
    303
    Distro
    Ubuntu 9.04 Jaunty Jackalope

    Re: embarassing fsck problem

    well I wasnt sure what it was deleting (read some posts where some guy lost the use of apt because of something similar) thats why I wanted to double check first. But since posting I did say yes (since I had no other option).
    Had to say yes to a whole load of stuff and even after that it didnt work.
    Some error about X.

    Still no luck I guess

  4. #4
    Join Date
    Feb 2007
    Beans
    303
    Distro
    Ubuntu 9.04 Jaunty Jackalope

    Re: embarassing fsck problem

    ok tried rebooting a second time and it works now! so glad.
    The problem is now solved, but I would still like to know why this happened in the first place?

    Also how do i mark this thread as solved?

  5. #5
    Join Date
    Jun 2008
    Location
    Tennessee
    Beans
    3,421

    Re: embarassing fsck problem

    Sounds like the hard drive may be going bad. I would boot up the live CD and run the following from a terminal:

    Code:
    badblocks -v /dev/sda
    If that starts spitting out a list of numbers, those are bad blocks. That means the disk is physically going bad.

  6. #6
    Join Date
    Feb 2007
    Beans
    303
    Distro
    Ubuntu 9.04 Jaunty Jackalope

    Re: embarassing fsck problem

    Quote Originally Posted by lykwydchykyn View Post
    Sounds like the hard drive may be going bad. I would boot up the live CD and run the following from a terminal:

    Code:
    badblocks -v /dev/sda
    If that starts spitting out a list of numbers, those are bad blocks. That means the disk is physically going bad.
    oh really?

    Ok I'll try that, thanks.

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •