So I did finally get everything fixed!

The key was the command:
mount -n -s -t ext3 -o remount,rw / /

This allowed me to fix the bad /dev/null
With /dev/null fixed, I could run fsck

All is now fixed with my system.

Well where do i start. My Linux admin guy volted. With no documentation and very little Unix experience I have ran into a reboot error.
. I have done the following:

1. the Unix box froze and I had to restart alt ctrl del to restart
2. machine restarted and i received the following options

Well where do i start. My Linux admin guy volted. With no documentation and very little Unix experience I have ran into a reboot error.
. I have done the following:

1. the Unix box froze and I had to restart alt ctrl del to restart
2. machine restarted and i received the following options

Gentoo GNU/Linux 2.6.11 - gentoo -r5
Gentoo GNU/Linux 2.6.11 - gentoo -r5 second partition

hit either then i get this

booting 'Gentoo gnu/linux 2.6.11-gentoo-r5
root (hd0,1)
filesystem type unkonwn, partition type 0x82
kernel /bzimage -2.6.11-gentoo-r5 root=/dev/sda3/i8042.reset

any suggetions would be greatly appreciated

thanks

Charlie

when I wrtie this command " /sbin/fsck /dev/hdb7" in my fedora 4 machine i get the following message
"fsck 1.37 (21-Mar-2005)
e2fsck 1.37 (21-Mar-2005)
/dev/hdb7 is mounted.

WARNING!!! Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.

Do you really want to continue (y/n)?"

I am afriad to unmount my file system because of bad experiences connected with it which led losing all my informations in my filesystem.

I would be glad if you give me some direction in order to repair my file system which was damaged due to a power failure.
thanks,

I have a similar problem in FC7. After making some changes to the fstab file (I wanted to mount two directories at 90.0.0106), I received the following message on boot:

fsck.ext3: No such file or directory while trying to open 90.0.0.106/FDS
fsck.ext3: No such file or directory while trying to open 90.0.0.106/FDS2
[Failed]
*** An error occured 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 startup):

I provide the root pwd and get to the shell. I can navigate to the fstab file, however, I cannot edit out what I believe are the bad entries causing the problem due to the fact that the file is read only.

Loosing my hair fast. Please help.

HELP! Like the previous posts, I made changes in the fstab file (I was trying to add mount point /dev/sdd2) and received the following message after reboot:

Checking filesystems:
fsck.ext3: No such file or directory while trying to open /dev/sdd2
[Failed]
*** An 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 startup):

I can access to the fstab file, and tried to comment out the line; however, I cannot write/save the file because it is read only. I've tried accessing other kernels and no luck.

Try
If it objects, usually you'd boot off the install media or a rescue disk and mount the '/' partition read/write and fix it from there.
Can i suggest that you always backup key files like fstab before editing them. Note also that after you've edited fstab, try
which will try all the mounts in fstab, so you can fix them without rebooting.