How to fix a Fedora crash mentioned “RUN fsck MANUALLY” nice and easy.

Today I found I couldn’t upload file to our Linux server using SSH file transfer. I haven’t calculated anything on the server since last week and no one was touching it. I am confused. Anyway, after I reboot the machine, more serious problem occurred, at least looks very serious for a Linux newbie like me.

So I Googled what’s on the screen, and found a webpage I can’t open seems describing the very same problem. However the cache is still usable, so I followed the simple steps easily fixed the problem. That actually reminds me of my early life of problem fixing on windows, I searched the internet using a 5 kbps modem, followed the instructions given by some nice people whom fixed the same problem and share the solution. ( I also did :p). That restored my faith in humanity every time.  So I decide to copy all that stuff down to preserve this knowledge and also the kindness.

Following is the post all credit to Yodiaditya, a kind newbie friendly software engineer, thank you dude.

 

Solve Fedora 17 boot problem repair filesystem fsck

It’s weird when my Fedora suddenly crash and it’s give this error message when boot-up and asking for “repair filesystem”:

Loading initial ramdisk… _Fedora-16-Beta-: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. (i.e., without -a or -p options) dracut Warning: e2fsck returned with 4 dracut Warning:_Fedora-17-contains a file system with errors, check forced. dracut Warning:_Fedora-17: Inodes that were part of a corrupted orphan linked list found. dracut Warning: * An error occured during the file system check. dracut Warning: * Dropping you to a shell; the system will try dracut Warning: * to mount the filesystem(s), when you leave the shell. dracut Warning: Dropping to debug shell. sh: can’t access tty; job control turned off (Repair filesystem):/#

The solution for this cases is easy: 1. Get your root partition :

blkid

For instance, I have fedora installed in “/dev/sda6″

/dev/sda1: SEC_TYPE=”msdos” LABEL=”DELLUTILITY” UUID=”3030-3030″ TYPE=”vfat” /dev/sda2: LABEL=”Recovery” UUID=”CC70378A703779F2″ TYPE=”ntfs” /dev/sda3: LABEL=”OS” UUID=”AC7C4EC27C4E86D4″ TYPE=”ntfs” /dev/sda5: LABEL=”DATA” UUID=”2E24594324590EE9″ TYPE=”ntfs” /dev/sda6: LABEL=”_Fedora-17-x86_6″ UUID=”861accd0-45a3-4129-a477-f931e5dc9816″ TYPE=”ext4″ /dev/sda7: UUID=”87c4e897-c3b7-467e-b275-2838e50cc1a5″ TYPE=”swap”

2. Repair

fsck /dev/sda6 -vY

Do hard reboot and you will get your Fedora back! Remember to have backup of your HDD

Sina WeiboShare

Leave a Reply

Your email address will not be published. Required fields are marked *

*


*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>