REAL bad, need help, system won't boot due to errors
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
REAL bad, need help, system won't boot due to errors
Ok yesterday I left the computer on and linux was running, while I was eating my sister didn't know how to shut down linux and open windows so she manually reset it.
Today I tried to load up linux and it says
Quote:
/dev/hda5 (my linux hd) contains a file system with errors, check forced...
and during the check it had loads of inode errors where it says something like
Quote:
inode ... was 64 should be 8 - FIXED
and it had like 10-15 of them come up. Then once the forced check was complete it says there are too many errors or something and then says:
Quote:
Press control+D to reboot and startup as normal or login as root to fix the problem
But it won't let me type anything and whenever I press control+D it reboots and then just says exactly the same thing.
Does this mean I have to re-install slackware everytime my computer gets manually shut down?!
Ok yesterday I left the computer on and linux was running, while I was eating my sister didn't know how to shut down linux and open windows so she manually reset it.
Today I tried to load up linux and it says
and during the check it had loads of inode errors where it says something like
and it had like 10-15 of them come up. Then once the forced check was complete it says there are too many errors or something and then says:
But it won't let me type anything and whenever I press control+D it reboots and then just says exactly the same thing.
Does this mean I have to re-install slackware everytime my computer gets manually shut down?!
Too many errors or something?? Could you get the exact error message for this thread please.
What filesystem are you using?
And no, you should not have to re-install slackware because it got manually shutdown. Your system should have found the errors if any fixed them and continued to boot.
Try booting in single user mode:
Suppose the label that you normally type in the LILO screen to boot your kernel is "linux", you must now start your computer and at the LILO prompt, type linux 1 (the word 'linux' with the number "one" added at the end).
This will boot slackware into single user mode, and hopefully it will let you run
Code:
fsck -fy /dev/hda5
This will usually be able to repair your filesystem.
If your computer will not even let you get to the point where you can run that command, try to boot from your Slackware setup CD, and instead of starting the setup procedure, you run
What file system were you running that it got nuked by a single hard reboot?
Bet it wasn't ext3 and friends. My system hits the dirt quite
often but always comes back (knock on wood). Hope I haven't
jinxed myself. Even given that I keep backups on DVD of the
file systems. Helps to reduce pain and suffering when the
inevitable happens.
Bet it wasn't ext3 and friends. My system hits the dirt quite
often but always comes back (knock on wood). Hope I haven't
jinxed myself. Even given that I keep backups on DVD of the
file systems. Helps to reduce pain and suffering when the
inevitable happens.
I once had this with an ext2 filesystem. Guess it doesn't happen that often, but if the stars are in the right position, it can happen to all of us.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.