Re: [vserver] Kernel panic - not syncing

On 08/24/2013 09:00 AM, Herbert Poetzl wrote:
> On Fri, Aug 23, 2013 at 03:33:15PM -0700, Roderick A. Anderson wrote:
>> I am trying to build a new CentOS 6.4 64bit host.
>
>> Started with a Minimal Desktop, followed the instruction on the
>> wiki, but when I reboot I get:
>
>> kernel panic - not syncing. No init found.
>> Try passing init= option
>> Pid: 1. comm: init Not tainted
>> 2.6.32-358.14.1.el6.vs2.3.0.36.29.6.31.x86_64
>
> sounds like the rootfs cannot be properly mounted and
> thus the designated init cannot be found/executed.

I'm getting that feeling myself.

>
>> There are Call Trace: lines but I only have them as a image
>> with my phone. If they will help I'll transpose them to text.
>
> still no serial (or other remote) console on a server?

Yup! Not my servers or NOC so I have to deal with what they provide me.

>> This kernel is from Daniel's repo.
>
>> 2.6.32-358.14.1.el6.vs2.3.0.36.29.6.31.x86_64
>
>> The CentOS kernel is (which boots just fine):
>
>> 2.6.32-358.14.1.el6.x86_64
>
>> Any suggestions on how to get this working?
>
> well, if you provide the boot log, it's probably simple
> to diagnose where it goes wrong, possible reasons include
> but are not limited to:

It looks like Redhat/CentOS have decided to over-write the boot.log file
When I revert to using the CentOS kernel that kernel is all that is in
the file.

> - bad initramfs (old initrd tools)

Seems to be the latest (CentOS) version of dracut that was used when I
installed the Linux-Vserver kernel from the repo. More research to do
on this.

> - driver for rootdev/rootfs missing

Yeah I have got to figure out if they were included (properly) when the
initfs was created.

> - device names changed (hda -> sda)
> - incompatible hardware
>
>> Additionally: I'm about 35 miles from the server, no IPMI
>> (yet), so I have to travel for each reboot/test attempt.
>
> you must really like travelling then :)

Not really! But I appear to be the only Linux-Vserver person in the
area. I have been trying to get someone else to take over the support
since I'm mostly retired.

Thanks for the pointers and help. I'll keep at it and see how things go.

Rod

-- 
>
> best,
> Herbert
>
>> TIA,
>> Rod
>> --