Hello dear all, I use a Slackware 12.2 associated with a database in MYSql, by innatention a collegue abruptly shut down the inverter, which caused the untimely shutdown of the server that we use since 2009 without problem. After restoring the current, we have this error message:
INIT: version 2.86 booting
INIT: No inittab file found
Enter runlevel:
But the machine crashes no keyboard key runs
All suggestions are welcome. Thank you

Welcome to LQ

I'd use a Slackware install DVD or CD1 to boot, then mount the root Slackware 12.2 partition as /mnt, see what is damaged and repair. If really there is no /mnt/etc/inittab or it is damaged, just replace it. Oh and as Slackware 12.2 is no more maintained since December 9, 2013 I advise you to upgrade.

Additionally, so that your post be seen by more people running Slackware, I suggest that you hit "Report" on your own post and request a moderator to move this thread to the Slackware forum.

Try this: Boot to a Live CD of something (the Slackware install disk might work for this, as this is command line), mount your root directory, then, as root, issue these commands:

If inittab is present but malformed, you might be able to repair it.

I have not tested this.

1 members found this post helpful.

Thanks for your help, but when I try to type: # updatedb
I have: -sh:updatedb :not found

Thank you Mr Didier, but the problem is about commands: after to boot with DVD Slackware I have this
Root@Slackware :/# when I try to mount any command be abble

Hi, I had just changed my hard drives in another computer, now I can have the ability to type the execution level but only when I have entered the levels from 0 to 6, the following message tells me there are No process in this level
And I do not know what to do
When I boot with my Slackware DVD, after mounting the root
Root @ slackware: / # here I can not execute any command unless I try to edit / etc / inittab
With the code: vi / etc / inittab
It shows me a series of 39 action that execute.
If you can help me with some codes to solve this problem.
cordially.

save your data and data base configuration to another drive
it sounds like your slack 12.2 is so messed up the easiest way to fix it would be to reinstall
when you get it back up start looking for a way to import you data to a newer version of your database
2009 to 2017 is way tooooo long to go without updating your O/S
you can still use it the software will not wear out but you may be close to not being able to export your data

I just looked at the slackware 14.2 ISO
inittab is in the sysvinit-scripts-2.0-noarch-33.txz package
witch in in the slackware/a directory
in your case look for sysvinit-scripts-?.?-noarch-??.tgz
good luck

@OP, if you "reinstall" without formatting the drive, everything should be as normal (assuming your harddrive isn't toast). When you reinstall without formatting, it will just restore all the stock packages without touching your 3rd-party packages. So the only thing you might lose is any customization you did with the official packages.

This might be the best quick-n-dirty solution to get your system back up and running. But as others have mentioned, 12.2 is EOL and you won't be seeing any further updates to the packages, so you probably already are vulnerable to various bugs that are present but haven't been patched. I'd highly recommend you taking this issue and using it to push yourself to a newer, fully supported Slackware. Ideally 14.2, as this would bring you the possibility of the longest supported version of Slackware currently available.