Hi all. I wanted to make some testings placing a CT inside a NFS share from the OVH's NAS service.
I added a new storage ponting to that NAS, it worked right and I made som backup tests, eveything went fine.
Then I tried to move a CT to the NAS storage, but couldn't start ir properly, so went back.
I wanted to make a clean test. I created a new CT directly in the NAS storage (remmember, nfs)
Creation of the container had no problems (a bit slower uncompressing, of course)
Then I started this CT and had exactly the same problem as before.
CT is started and mounted, but it looks like it's not booting.
CT is 99% CPU, I can connect to console but it seems hanged on boot.
It won't listen for a local "init 0" (not found) and took a very long time (10 mins) and 3 attempts to stop it using vzctl
The only log I see is about the NAS server (ip 11.22.33.44):
When CT is stopped, those messages disapear from syslog (debian server)
I don't understand why the machine is not booting?
Anyone can help me? Thanks.
I added a new storage ponting to that NAS, it worked right and I made som backup tests, eveything went fine.
Then I tried to move a CT to the NAS storage, but couldn't start ir properly, so went back.
I wanted to make a clean test. I created a new CT directly in the NAS storage (remmember, nfs)
Creation of the container had no problems (a bit slower uncompressing, of course)
Then I started this CT and had exactly the same problem as before.
CT is started and mounted, but it looks like it's not booting.
CT is 99% CPU, I can connect to console but it seems hanged on boot.
It won't listen for a local "init 0" (not found) and took a very long time (10 mins) and 3 attempts to stop it using vzctl
The only log I see is about the NAS server (ip 11.22.33.44):
Code:
kernel: ct0 lockd: server 11.22.33.44 not responding, still trying
kernel: ct0 lockd: server 11.22.33.44 OK
When CT is stopped, those messages disapear from syslog (debian server)
I don't understand why the machine is not booting?
Anyone can help me? Thanks.