I need help!

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.

LABEL = / ext33 defaults 1 1
none /dev/pts devpts gid = 5 mode = 620 0 0
none /proc proc defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/hda4 swap swap defaults 0 0
/dev/cdrom /mnt/cdrom/ udf, iso96600 noauto, owner, kudzu, ro 00
/dev/fd0 /mnt/floppy auto noauto, owner kudzu 00


I was challenged to learn how to repair such problems and also learn to analyze and interpret error messages as possible.

I am hoping for tips, suggestions whatsoever regarding this matter.

thank you very much!


CatLinuz

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.

Thank you for the tip SYNAPTICAL! Kindly inform our friends here, maybe they could help me about it. BTW, how will i know if the damage is fixable or not?

unmount the filesytem then run fsck?