vzctl start xxx failed : exit code 47

[samontetro]

Hi,

this is my first big problem with proxmox. Last week we had a big power failure. To reboot the server I had to run an xfs_repair on the /var/lib/vz partition and some files have been removed. Now, my last 2 virtual servers (linux) do not restart and I get this error code 47.
Of course, these are the last two installed server and I've no backup for these one as they were in prod for only some weeks...

Any suggestion ?

I'm runing proxmox V2.1-1

Thanks

Patrick

 

[tom]

xfs for OpenVZ is not (and was never) supported for container. use ext3 (default) of ext4.
and 2.1 is very outdated, you should always run latest version ONLY.

I know that this does not help to bring your data back but I just want to point that out.

 

[mir]

Anything relevant from the log files?

What output do you get if you try starting the CT from the command line?

 

[samontetro]

xfs for OpenVZ is not (and was never) supported for container. use ext3 (default) of ext4.
and 2.1 is very outdated, you should always run latest version ONLY.

I know that this does not help to bring your data back but I just want to point that out.

May be I've missed that xfs was not supported in the documentation. I can backup this partition and restore on an ext4 filesystem this afternoon.

version 2.1 was the latest available at install time and since it was working fine.... "when all is working do not touch anything"
Can I safely move to 3.2 ?

 

[samontetro]

In the log file I have only these lines :

2014-07-16T10:18:21+0200 vzctl : CT 106 : Container is not running
2014-07-16T10:18:28+0200 vzctl : CT 106 : Starting container ...
2014-07-16T10:18:28+0200 vzctl : CT 106 : Container is mounted
2014-07-16T10:18:28+0200 vzctl : CT 106 : Setting CPU units: 1000
2014-07-16T10:18:28+0200 vzctl : CT 106 : Setting CPUs: 1
2014-07-16T10:18:28+0200 vzctl : CT 106 : Configure veth devices: veth106.0
2014-07-16T10:18:28+0200 vzctl : CT 106 : Unable to start init, probably incorrect template
2014-07-16T10:18:28+0200 vzctl : CT 106 : Container start failed
2014-07-16T10:18:28+0200 vzctl : CT 106 : Stopping container ...
2014-07-16T10:18:29+0200 vzctl : CT 106 : Container was stopped
2014-07-16T10:18:29+0200 vzctl : CT 106 : Can't umount /var/lib/vz/root/106: Device or resource busy
2014-07-16T10:18:29+0200 vzctl : CT 106 : Container is unmounted

I've seen that the 47 code means a problem with init or sh and I've check they exist in /var/lib/vz/private/106/... (I have also running containers on this host, only 2 not runing)

 

[mir]

What output do you get when doing this from the command line:
vzctl start 106

 

[samontetro]

What output do you get when doing this from the command line:
vzctl start 106

Hi Mir, i'm back. I'v spent some time moving /var/lib/vz on a new ext4 filesystem.
Using "vzctl start 106" give the same information:

# vzctl start 106
Starting container ...
Container is mounted
Setting CPU units: 1000
Setting CPUs: 1
Configure veth devices: veth106.0
Adding interface veth106.0 to bridge vmbr1 on CT0 for CT106
Unable to start init, probably incorrect template
Container start failed
Stopping container ...
Container was stopped
Can't umount /var/lib/vz/root/106: Device or resource busy

 

[mir]

What is the content of /etc/inittab ?

 

[samontetro]

Only one line in /var/lib/vz/private/106/etc/inittab:
id:3:initdefault:

Patrick

 

[mir]

It seems the CT is severely broken. Could you not pull out the customized peaces from /etc and then make a new CT copying in the peaces from the old CT

 

[samontetro]

It seems the CT is severely broken. Could you not pull out the customized peaces from /etc and then make a new CT copying in the peaces from the old CT

This CT was hosting an indefero server. I must check all that should be saved (mysql, git reposits etc....).
I start running this procedure now. Thanks.

Patrick

 

[samontetro]

Thanks Mir, it was the right procedure:
- I've re-installed a new container (107) with the same linux flavor
- installed and configured Mysql
- installed but not configured indefero
- stopped this container
- copied all etc home/git usr/share/indefero var/lib/mysql trees from /var/lib/vz/private/106 to /var/lib/vz/private/107
- restarted VM 107
- dump VM 107 !!

All seems to work properly.

Thanks again for hour help

Patrick