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.
Let me kick this off with "i'm a newbie" ok now thats clear ..heres the problem.
I am running SME server v 6.0 on a 120GB HDD. Its been running well for about 5 months, I leave it running for periods of "weeks" without issues. Yesterday however we had a series of power failures, thankfully I have a UPS and managed to shutdown safely, however the power failures continues to plague the day. In the end my server failed to boot up.
During the typical system check on startup I recieved the following:
the numbers (xxxxxxx) ascending as the error message would repeat for serveral minutes finally concluding with:
Couldn't find matching filesystem: LABEL=/
*** and error occurred during the file system check
***dropping you to a shell; the system will reboot
***when you leave the shell
Give root password for maintenance
(or type Control-D for normal start up):
once i have type the root password i recieve:
(Repair file system) 1 #
At this point i have tried the following commands
fsck / -v-y
fsck /dev/hda1 -v-y
fsck /dev/hda2 -v-y
e2fsck -cc -C -f -v /dev/hda1
as adviced on other similar forum ...ultimately the results the same. I would recieve I recieve:
bash: fsck : No such file or directory
(Repair filesystem) 2 #
and so it goes on....what am i supposed to do, continue typing in commands....I have tried just typing y through to (Repair filesystem) 800 #
I need help.
(remember the first line..Im a newbie...so anyone kind enough to offer advice please keep instructions clear and basic)
I've been thinking about installing SME Server myself so I'm glad to hear that it run so well for that length of time.
I use Mandrake and it has a repair facility that you can stick in the CD at boot-up and repair various bits and pieces, I've done it to repair Lilo.
Does SME have something similar ?
Umm do you have backups of your critical data ? because this doesnt sound good.
What happens when you Control-D
My Smoothwall will occasionally do this and I just let it reboot and whatever the problem was gets fixed during the next file check
( now obviously your problem is more serious than mine )
after a serious power failure I had to let the system reboot 3 or 4 times, each time it fixed a different problem before it finally decided that it had righted itself