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.
I am using rh9 and running only a txt based system. Before I encountered problems, I activated fsck and the shutdown -h now command.
After that, error occured informing me that filesystem initialization failed: here are some lines of failed initialization:
loading default keymap(us):
/etc/rc.d/rc.sysinit: line 16222:/dev/null: read-only filesystem [failed]
setting hostname localhost.localdomain: dup2: bad file descriptor [failed]
/etc/rc.sysinit:line 173: /dev/null:read only filesystem
initializing USB controll(EHCCI-HCO) [failed]
awk: cmd.. line:2: fatal: cannot open file "/proc/mount for readn(no such file of directory)
checking root filesystem
dup2: bad file descriptor [failed]
*** dropping you to a shell
*** when you like tehe shell give root password of maintenance
(or type control-d to continue):
repair filesystem 1#:
i look for ways and found this command:
fsck -V -A
i tried the command but returned error msg:
couldn't open /proc/partitions:
no such file or directory
is /proc mounted?
so i mounted the /proc and execute the fsck.
then an infinite loop msg appears "ext3-fs error (device ide0(3,3));ext3_readdir: bad entry in directory # 32449: rec_len%4!=0-offset = 2984, inode = 1281453, rec_len= 36270, name_len = 19
here is the copy of my fstab file. maybe it could help solve the problem.
afaik, you're not supposed to run fsck on filesystems that are mounted. if you did that, you might be scr3wed. one of the gurus here might be able to help you fix the damage if it's fixable, but i wouldn't mess around with fsck anymore until you're sure you know what you are doing.