Kernel panic - not syncing attempted to kill init. What to do?

Question

linux

The server worked more or less stably for several years until the hoster overloaded it tonight. Since then it has refused to start. When I try to run it, it gives the following error:

OS version - Ubuntu 12.04 (64)
I tried to follow the advice from the forums, but so far everything is deaf.
1) SELinux. The /etc/selinux directory, where the config should be located, simply does not exist. I did not find anything similar in the settings of the rough search. Therefore, the advice did not fit - stackoverflow.com/questions/12867591/how-to-solve-...
2) Initramfs. I booted into recovery mode from LiveCD and ran "update-initramfs -u" - the problem persisted.

Answer 1

To everyone who replied, thank you. Yesterday I couldn’t cope with the problem on my own and I had to connect a specialist from a system administrator company.
He confirmed my concerns about our #$%^#[email protected] software raid and helped clear up the aftermath. In the process, the kernel was updated and the most terrible manifestations of dependency hell were destroyed.
This is just one of those cases where error messages are not a direct indication of a problem, but only hints in the direction of searches.

Answer 2

Which selinux, which initramfs? It says in black and white to you: /init: .: line 69: can't open '/scripts/functions'.
Look at your /init, line 69. Why does it need /scripts/functions? Where could he go? Maybe he is no longer needed? Maybe it was accidentally deleted, but you still have a backup copy?

Answer 3

Wasn't there an hour on this server for updating bubunts without rebooting?
Let's say, there was an old bubunt, on which there was sysvinit, and then suddenly it was updated to a new one, in which sysvinit was cut out, and instead of it was pottero slag.
If it was, then the reason is obvious: an incorrect update (i.e. the system was updated, but all the settings and init scripts remained old).
Another option besides jcmvbkbc suggested : there was a kernel update that went wrong (let's say you have an initramfs, but the update didn't).
The system boots with init=/bin/bash? If yes, then, taking into account the changes that caused this problem, correct the errors.

Answer 4

Let me guess - when you do update-initramfs, it gives you these errors, but you ignore them:

find: invalid predicate `-regextype'
find: warning: unrecognized format directive `%Y'

Here is an interesting link, which, however, does not explain the reason for getting into such a situation: askubuntu.com/questions/15296/kernel-panic-line-61...