[SOLVED] Errors updating Proxmox

isolis

Active Member
Apr 16, 2015
2
0
41
Hello, i'm trying to update our proxmox installation and i have these errors anyone know why?

Thanks in advance!

root@pve1.xxx.xxx:/lib# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
6 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]? y
Setting up ntp (1:4.2.6.p5+dfsg-2+deb7u4) ...
insserv: Service zfs-mount has to be enabled to start service ntp
insserv: exiting now!
update-rc.d: error: insserv rejected the script header
dpkg: error processing ntp (--configure):
subprocess installed post-installation script returned error exit status 1
Setting up pve-firewall (1.0-21) ...
insserv: Service zfs-mount has to be enabled to start service pvefw-logger
insserv: exiting now!
update-rc.d: error: insserv rejected the script header
dpkg: error processing pve-firewall (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of qemu-server:
qemu-server depends on pve-firewall; however:
Package pve-firewall is not configured yet.

dpkg: error processing qemu-server (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of pve-manager:
pve-manager depends on qemu-server (>= 1.1-1); however:
Package qemu-server is not configured yet.
pve-manager depends on pve-firewall; however:
Package pve-firewall is not configured yet.

dpkg: error processing pve-manager (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-ve-2.6.32:
proxmox-ve-2.6.32 depends on pve-manager; however:
Package pve-manager is not configured yet.
proxmox-ve-2.6.32 depends on qemu-server; however:
Package qemu-server is not configured yet.

dpkg: error processing proxmox-ve-2.6.32 (--configure):
dependency problems - leaving unconfigured
Setting up zfsutils (0.6.3-3~wheezy) ...
update-rc.d: warning: default start runlevel arguments (2 3 4 5) do not match zfs-mount Default-Start values (S)
insserv: warning: current start runlevel(s) (2 3 4 5 S) of script `zfs-mount' overrides LSB defaults (S).
insserv: warning: current start runlevel(s) (2 3 4 5 S) of script `zfs-mount' overrides LSB defaults (S).
insserv: Service zfs-mount has to be enabled to start service shareiscsi
insserv: exiting now!
update-rc.d: error: insserv rejected the script header
dpkg: error processing zfsutils (--configure):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
ntp
pve-firewall
qemu-server
pve-manager
proxmox-ve-2.6.32
zfsutils
E: Sub-process /usr/bin/dpkg returned an error code (1)
 
Last edited:
Hi,

Finally i found the problem.

I installed the server from scratch many times to find the point where the problem appears and I found it when I added that:


  • edit /etc/insserv.conf,
and at the end of the $local_fs line,
add zfs-mount (without a plus).
#
# All local file-systems are mounted (done during boot phase)
#
$local_fs +mountall +mountall-bootclean +mountoverflowtmp +umountfs

I have a zpool added like directory in storage and the pool wasn't mounted after a reboot.
So if I don't put at the end of the line zfs-mount without a plus, everything it's ok.

Thank you!

Israel Solis
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!