FedoraThis forum is for the discussion of the Fedora Project.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
......
powernow-k9: try again with latest BIOS
Cannot open font file True
_Fedora=17-x86_6: UNEXPECTED INCONSISTENCY: Run fsck manual.
(i.e. without -a or -p options)
dracut Warning: e2fsck returned with 4
dracut Warning: _Fedora-17-x86_6 contains a file system with errors, check forced.
dracut Warning: _Fedora-17-x86_6: Inodes that were part of a corrupted orphen linked list found.
dracut Warning: *** An error occurred during the file system check
dracut Warning: Dropping you to a shell; the system will try
dracut Warning: to mount the filesystem(s), when yu leave the shell
dracut Warning:
Dropping to debug shell
(Repair filesystem)/# fsck
fsck from util-linux 2.21.2
(Repair filesystem)# ls
bin dev etc init lib .........
I reported something similar a while back, i got told it was a hardware error....I am using the same hardware now running Mint and have been for over a month....not hardware then is it?
Sorry this didn't answer your question....but you are not alone.
Simon
I reported something similar a while back, i got told it was a hardware error....I am using the same hardware now running Mint and have been for over a month....not hardware then is it?
Sorry this didn't answer your question....but you are not alone.
Simon
Something looks strange to me.
Fedora is now working after reinstallation. I have another HD on this PC (not connected at the same time) with Fedora 17 and Ubuntu 12.04, both 64bit, installed (dual boot). It has been running for sometimes without problem.
I agree, mine worked too, for a while after reinstall, I'm not good enough to recover that, and frankly I don't have time to wade through the stuff people were saying to cure it, when half the time I couldn't even get to a command line, out of interest, were you running firefox?
I had this strange feeling that after installing firefox and installing some add ons, I had this ever so slight feeling that it might have been related to that, but never had the time to work out which one, reason being, I had a fresh install that seemed to work fine, all updated, fine, then I put in my add ons using the febe tool and within an hour a brand new install had died in the same way....as for mint....well it's still banging away, although I prefer Fedora a would like for someone to be able to explain to me the issue. Getting them to accept the issue....now there is another thing.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.