Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Well i was in linux just typeing in kword then the power went out because of a storm that was near my area. I unplugged everything and waited for it to pass. Then when i turned it back on linux wasnt working. It said that it found bad blocks and errors then ran a scandisk deal i guess. then restart my machine then it said bad blocks and errors and locked up there. So does this mean my linux os is dead
Use your install CD for boot disk.
After you log in as root tying running:
If you have one harddrive and Linux is in the first partiton:
fsck -y /dev/hda1
If you have more than one partition run fack on them also
just to be safe?
Then reboot, and pray to the great penguin in the sky
OK your wrong
My experience on experience with RH7.2 (ext3) is fsck is still
required after a hard crash such as this.
My impression was that, it was to elimiate fsck as part of standard reboots? But it could depend on how you journialing set up? The best inusrance against what digital bots described is a decent UPS, and if you're really serious RAID.
Well Slack just made a fool out of me, I installed Slack-8.1
with ext3 files systems. And to test the ext3 fs, just power it off and on twice? Both times the systems came up clean, without doing an fsck
well it works. i used my install cd as a boot disk and ran the command and then it said it didnt know what fsck was. So i powered down, restart the pc then it came on with linux runing for some odd reason. Then it said "Would you like to repair your system?" So i said yes and did the repair mode deal did the command in that and it worked so thanks a bunch i am back in slack and happy to tell ya that everything works. O THANK THE GREAT PENGUIN IN THE SKY.
Grab Slack-8.1 and use ext3. It works.
One other thought, if you have a complete set of Slack CD, you could
use Disk2 "Ready-to-Boot Linux Disc", is the utlimate rescue disk and
get in or repar your system that way.
Redhat, if you have ext3, does NOT force you to do a FSCK if you had a harsh reboot. It gives you 3 to 5 seconds to press the "Y" key to say if you wanna have it...otherwise it will go in as usual. Your experience on the experience you have with redhat does seem a little odd.