RC sysinit error

C

ChrisHDtoSA

Guest
Hello, y'all. A server at my work went down, and I'm trying to help get it back up, if possible. I'm afraid I don't know what distro this is from, but I'm guessing either Red Hat or Fedora. I'm only a help desk analyst. Anybody know how to fix this error/problem? See below:

"/etc/rc.d/rc.sysinit: /dev/null: read-only file system
Dup2: Bad file descriptor
An error occurred during file system check
Give root password for maintenance
Control-D to continue
Reboot and replay the movie over and over."

It refuses to boot back up and after MANY reboots, it just does not want to come to life.

If I'm not mistaken, the rc.sysinit script file is practically what starts it up. I'm guessing something within the script is corrupt. Is it possible to remount the disk as RW, delete the /dev/null folder and recreate it, and create an inode? Or maybe the rc.sysinit file in the path /etc/rc.d/rc.sysinit: is corrupted?

Please help, so I can impress the senior guys.
 


rc.sysinit is from the Red Hat family, so I'd wager your server is Red Hat or CentOS.

You need to give the root password when prompted (not Ctrl-D) so you can run a filesystem check by hand and correct any errors (be prepared to discover your disk is hosed though). At the prompt that appears, try:

Code:
fsck -Asr

Follow the prompts, and take good notice when it says things are dangerous. Reboot when prompted, and see what happens.

Now is a good time to talk backups. What's your strategy, and when was it last tested?

The Tigers
 
rc.sysinit is from the Red Hat family, so I'd wager your server is Red Hat or CentOS.

You need to give the root password when prompted (not Ctrl-D) so you can run a filesystem check by hand and correct any errors (be prepared to discover your disk is hosed though). At the prompt that appears, try:

Code:
fsck -Asr

Follow the prompts, and take good notice when it says things are dangerous. Reboot when prompted, and see what happens.

Now is a good time to talk backups. What's your strategy, and when was it last tested?

The Tigers

One of the senior guys said that he reactivated the VM, and restored the current. He also said it might be hardware related. So, he will check it the morning. I believe this is our backup. As for when it was last tested, that's a question for the seniors. I figured they knew how to fix it, but I wanted to impress them by suggesting procedures that could resolve this issue - almost as if they were testing me. Which is ok by me, as long as I was doing well enough. I'm sure I got more and more to learn.
 

Members online


Top