ddski@mhgki.att.com (52111-dennis) (06/24/89)
How do I recover from a UNIX system crash on an AT&T PC6300+ ? Background: I have a pc6300+ with ROM BIOS Vers. 2.05, running UNIX System V Release 2.0 Ver. 2.5 and Simul-Task 3.2 Vers. 2.5 What happened: While the system was up and running, for some reason it went into a "restart" mode (due to low power supply voltage?). While the system was coming back up it displayed a message saying a cleanup of the root file system was taking place. Then, the system crashed (went into "restart") again! This time, when the system was coming up, I received the following message: INIT: Cannot open /etc/inittab. errno: 2 ENTER RUN LEVEL (0-6,s, or S): What do I do now? I tried the simple minded approach, turning the computer off and back on again, and of course got the same message. ( I can dream, can't I ?) Any suggestions will be greatfully accepted. I'm not looking forward to the many hours it would take me to re-install the entire operating system, not to mention the files I would lose. +--------------------------+------------------------------------------+ | The only perfect science | Don Dennis (home) (201) 398-2747 | | is hind-sight. | att!mhuhk!ddski (work) (201) 582-7035 | +--------------------------+ ddski@mhuhk.ATT.COM ---------------------+
cgh018@tijc02.UUCP (Calvin Hayden ) (06/27/89)
You write: . . > While the system was coming back up it displayed a message > saying a cleanup of the root file system was taking place. > Then, the system crashed (went into "restart") again! > This time, when the system was coming up, I received the > following message: > > INIT: Cannot open /etc/inittab. errno: 2 > ENTER RUN LEVEL (0-6,s, or S): > > What do I do now? Ok, I'm no wizard, and I can't assure you that this will work, but it's worth a shot. ( I'm on a Vax, so I'm not sure how the smaller machine handles things) When you get the message above, go into single user mode. While there, fsck your root file system - dont fsck the raw device - the manual should mention something about fscking the root file system via block device ( on my system, I fsck /dev/dsk/0s1 instead of /dev/rdsk/0s1). Let it fix any problems it may find, and reboot if you have to. Once root is fscked, check to see if the /etc/inittab file is still there -- if it's not, restore the file from backup if you can, if you cant, then it may have to be manually reconstructed. Then be sure to fsck all other file systems. Sounds like inittab may have been damaged, or that the system thinks it may have been damaged. Hope this helps some. Like I said, I'm no expert by a long shot. Calvin