[Users] Kernel Panic 2.6.32-042stab090.3

[Rene C.]

Actually I think the problem is related to a faulty disk controller or
loose cable connection. I'm having the datacenter look into that.

In the meantime, I have a related problem of a container that's gone
read-only.  I'm trying to stop the container but get this error:

[root at server18 ~]# vzctl stop 1703
Unable to create lock file /vz/lock/1703.lckzFIthv, use --skiplock
option: Read-only file system
Unable to lock container
[root at server18 ~]# vzctl stop 1703 --fast
Unable to create lock file /vz/lock/1703.lcka6nW5r, use --skiplock
option: Read-only file system
Unable to lock container
[root at server18 ~]# vzctl stop 1703 --skiplock
vzctl: unrecognized option '--skiplock'

Just seems whatever I do openvz won't stop this container.  How can I stop it?


On Mon, Jun 30, 2014 at 2:10 PM, Pavel Odintsov
<pavel.odintsov at gmail.com> wrote:
> Maybe you upgraded from centos5? It's CentOS 6?
>
> On Mon, Jun 30, 2014 at 10:37 AM, Vasily Averin <vvs at parallels.com> wrote:
>> It is initrd-related problem,
>> kernel did recognized hardware/filesystem and do not know where is root partition to mount it.
>> So I belive it is some local problem on this particular node.
>>
>> On 06/29/2014 11:33 PM, Rene C. wrote:
>>> Screenshot attached, hope it's useful.
>>> _______________________________________________
>>> Users mailing list
>>> Users at openvz.org
>>> https://lists.openvz.org/mailman/listinfo/users
>>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at openvz.org
>> https://lists.openvz.org/mailman/listinfo/users
>
>
>
> --
> Sincerely yours, Pavel Odintsov
> _______________________________________________
> Users mailing list
> Users at openvz.org
> https://lists.openvz.org/mailman/listinfo/users