Arch Linux

Vlavv

Member

Registered: 2012-04-09

Posts: 9

Cannot boot after a migration to systemd in OpenVZ

EDIT: I "solved" my problem, and I doubt this thread will ever help anybody. You're warned.

Hello,

Earlier today, my Arch install that was still running with initscripts (and without the last filesystem/bash upgrade) suddently rebooted, and that broke a certain number of things (services weren't starting anymore, etc.). I figured I had waited too long before migrating to systemd for good, and therefore I followed the migration guide on the Wiki, added the "init=/usr/lib/systemd/systemd" kernel parameter and rebooted again.

Sadly, ps -p 1 was still showing init instead of systemd. After a few more tries, I installed systemd-sysvcompat (thus replacing the sysvinit package), and rebooted again. That last reboot failed. Now OpenVZ stops suddently with the following messages:

[root@ks /]# vzctl start 106
Starting container ...
vzquota : (warning) Quota is running for id 106 already
Container is mounted
Adding IP address(es): ***
Setting CPU units: 1000
Setting CPUs: 2
/bin/bash: line 72: /bin/cp: No such file or directory
 ERROR: Can't copy file /etc/rc.conf
Unable to start init, probably incorrect template
Container start failed
Stopping container ...
Container was stopped
vzquota : (error) Quota off syscall for id 106: Device or resource busy
vzquota off failed [3]

I tried to chroot in the VM folder and reinstall sysvinit, but that was too late:

pacman -U /var/cache/pacman/pkg/sysvinit-2.88-9-x86_64.pkg.tar.xz
(...)
error: could not open file: /etc/mtab: No such file or directory
error: could not determine filesystem mount points
error: failed to commit transaction (unexpected error)
Errors occurred, no packages were upgraded.

It looks like I can't use pacman in a chroot. The host OS is not running Arch so I cannot use pacman with the --root flag.

I'm running out of ideas. Any help would be really appreciated...

Thank you.

Last edited by Vlavv (2013-06-27 00:26:12)

Scimmia

Fellow

Registered: 2012-09-01

Posts: 13,727

Re: Cannot boot after a migration to systemd in OpenVZ

Read the wiki about chrooting, you need to mount the kernel filesystems to make things work.

As for openvz, I have no idea.

Vlavv

Member

Registered: 2012-04-09

Posts: 9

Re: Cannot boot after a migration to systemd in OpenVZ

The problem with the chroot options is that I don't have the root privileges on the host machine. I was only able to access that chroot thanks to a kind administrator, but I couldn't ask too much either.

OK, so I've done some Ugly Things, messed with the contents of the sysvinit package archive manually to get the right files at the right places, and eventually managed to boot my VM and get all the stuff working. I'm certainly not proud of myself, but at least things are working again for now. I'll do a clean reinstall later. Thank you for the suggestion, and sorry for the noise.

Cheers.