-   Linux - Software (
-   -   help, terrable problems about read-only mounting when starting my system (

Snerkel 01-20-2005 01:06 PM

help, terrable problems about read-only mounting when starting my system
Hi, i have been getting errors for a few days now when i logged into my server, something about "/dev/null". i just rebooted my server and it wont even boot! it says that its mounting read only so i cant even edit anything! it stops booting 1/2 way through and says "press ctrl + D to boot normally or enter root password to enter the system now" if i enter root password i cant do anything because its all read only, and if i boot into the system i cant even log in.

im running a hardened gentoo system.

i really dont know what to do!, can anyone PLEASE help me?

Thank you so much, Ben.

320mb 01-20-2005 01:52 PM

yea, you need to boot into it using a "Live-Cd" like knoppix........
and do whatever permission changes to /ect/fstab.......and/or
filesystem directories.........

Snerkel 01-20-2005 09:16 PM

i dont have the first clue whats wrong or what i need to change :(

wpn146 01-21-2005 01:25 PM

I hope you have a backup because your file system could be toasted.

Too bad you didn't provide the exact error messages. That could have helped, but here are a few guesses.

Try booting from a rescue disk and try mounting the root partition at a mount point. Look around for obvious things, like directories it won't let you into or ls displays strange results. Check the files grub.conf (or lilo.conf if you use lilo), your /etc/fstab, inittab, etc.

So far, none of these checks will harm anything. If it appears that the file system is badly damaged, then unmount it and run fsck on it. This WILL write to the disk!!! (You might try it with the "-N" parameter first and it will do a read-only scan.) Fortunately, fsck is very smart and is your friend. After it gets done, you MIGHT be missing a lot of files it couldn't recover. Some of these MIGHT be critical for booting and you will be left with a trashed system. Remember, the damage was probably already done before fsck ran.

A lot of this snooping around could have been done while you were logged in with a read-only file system, but you would be using tools -- including "cd" and "ls"-- that could themselves be corrupt.

Good luck!

One more thing... If somebody tries to tell you that "/dev/null" is full and has to be emptied out, they are trying to pull your leg. /dev/null is the bit bucket.

All times are GMT -5. The time now is 09:49 AM.