Forums

Choie
Choie
Offline
Resolved
0 votes
Our company is using clark connect community 5.0 it was working fine. then it happened, a power failure caused the clark connect server to shutdown improperly. then this error occured saying kernel was terminated.

cannot mount /dev/sda error.

it's hard bein newbie to linux and there was no proper endorsement by the previous MIS guys. I have installed CentOS 5.4 hoping to recover the files but it was unsuccessful. I tried to run the CC and rescue boot but the CC installer error message "cannot fine /dev/sda" thus it mean that the partition table had crashed?

can anyone please help me out.

thanks alot....
Wednesday, June 09 2010, 07:45 AM
Share this post:
Responses (6)
  • Accepted Answer

    Sunday, December 19 2010, 01:44 AM - #Permalink
    Resolved
    0 votes
    I know, but my harddisk has about 60% free before power lost, after this I get the "no space left " error
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, December 18 2010, 07:31 PM - #Permalink
    Resolved
    0 votes
    Sounds like your hard drive is full up! this will cause your system to stop functioning....the above procedure will not help as it fixes file system errors.

    I would have a look at the output of 'df -h' and then use the command prompt to try and regain some space. Remove some logs or other temp files. You can find which folder has the most data by using this command (note will take a while depending on the size)
    du / --max-depth=1 -h
    The reply is currently minimized Show
  • Accepted Answer

    Saturday, December 18 2010, 01:50 PM - #Permalink
    Resolved
    0 votes
    Hi there!

    I had a similar problem, but instead of mount error my proxy server did not start, and I get an out of space error...

    can I use the same procedure to fix it?

    I forgot to mention system log off me constantly and it´s very difficult to work in gui console.
    The reply is currently minimized Show
  • Accepted Answer

    Thursday, June 10 2010, 10:47 AM - #Permalink
    Resolved
    0 votes
    You can auto repair the file system by using
    fsck -p /dev/sda3

    Or more risky you can force yes to all questions by using
    fsck -y /dev/sda3


    Note this will recover as much as it can but you may lose some corrupt files in the process, it all depends on what your drive was reading / writing to at the time of the power cut - however it should get your system booting again

    If you have sensitive data (I hope you have a backup?) then boot up a Knoppix LiveCD or attach the drive to another machine and copy the data off it first, before attempting a recovery.

    UPS and RAID arrays are other means of protecting yourself against power cuts and drive failures.
    The reply is currently minimized Show
  • Accepted Answer

    Choie
    Choie
    Offline
    Thursday, June 10 2010, 09:15 AM - #Permalink
    Resolved
    0 votes
    Hi,

    I have followed your procedure but I have to pause it because I'm not sure if what I'm doing is right. this is the sequence of commands I did

    fdisk -l
    I saw that the hardrive is /dev/sda3
    fsck -C /dev/sda3

    after this there was a series of questions prompting:

    Inode 7504368, i_blocks is 16, should be 8. fix<y>?

    I clicked "y" for a couple of times thingking it will be atleast 10 questions but it goes continuesly for more than a hundred. so I need to ask is "what should I do?, do I need to press "y" till it finished?"
    I fear the unknown since this harddrive contains our company data that all files might be lose. I hope you can help me on this.

    Thanks alot...
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, June 09 2010, 09:16 AM - #Permalink
    Resolved
    0 votes
    It's possible your drive file system is damaged so that it can no longer be mounted

    You need to boot the ClearOS ISO CD, select rescue, it will ask to mount the old system under /mnt/sysimage but select no, this is required for the next step

    Then you need to use the 'fsck' command to check the disk and repair file system errors (much like checkdisk for windows). Manpage is here
    http://linux.die.net/man/8/fsck

    At the prompt type the following and note the partition list...first find the largest partition and double check that the partition number - usually sda3, we need that for the next step. Be careful here as you are booting from the CD so your hard drive may no longer be sda, but rather sdb. If your happy youve found your drive with it's partitions, carry on to step 2
    fdisk -l /dev/sd?

    To run the repair on say sda3
    fsck -C /dev/sda3

    where sda3 is the root partition probably causing you problems, identified above...yours might be something else.

    Hope that helps, if all is succesful you should be able to reboot (type 'shutdown -r now') and boot back into your system
    The reply is currently minimized Show
Your Reply