Proxmox 4 shutdown/reboot

[ELS_sean]

Hi All,
First post, so please bear with me. I upgraded my proxmox server from 3.x to 4.x and everything behaves as it should with one import ant issue. I can not reboot the server from the web interface. If I try to reboot it from the web gui the machine shuts down but does not reboot. Push the power button and up comes the server no problem. Never saw this problem in the 3.x software. What additional info can I provide to help diagnose the issue?

Thanks,
Sean

 

[Oliver Polterauer]

is your server using Broadcom network cards? If so this might be your problem:

https://forum.proxmox.com/threads/no-reboot-with-4-4-pve-kernel.27908/

 

[ELS_sean]

No Broadcom. I just tried to issue the reboot command from the CLI and I got the same response. Shuts down but no reboot.

root@proxmox:~# lspci | grep Ethernet
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
root@proxmox:~#

Thanks,
Sean

 

[ELS_sean]

Anyplace else I can look? Remote reboots have become an issue for this machine obviously

 

[congo]

Hi,

I have the same problem, with a freshly installed PVE 4.3, which has been upgraded immediately to PVE 4.3-3.
The motherboard has an Intel Z97 chipset (Gigabyte GA-Z97-D3H). On-board NIC is disabled, only extra hardware is one additional NIC.

Ethernet controller: Intel Corporation 82541PI Gigabit Ethernet Controller (rev 05)

proxmox-ve: 4.3-66 (running kernel: 4.4.19-1-pve)
pve-manager: 4.3-3 (running version: 4.3-3/557191d3)
pve-kernel-4.4.19-1-pve: 4.4.19-66
lvm2: 2.02.116-pve3
corosync-pve: 2.4.0-1
libqb0: 1.0-1
pve-cluster: 4.0-46
qemu-server: 4.0-91
pve-firmware: 1.1-9
libpve-common-perl: 4.0-75
libpve-access-control: 4.0-19
libpve-storage-perl: 4.0-66
pve-libspice-server1: 0.12.8-1
vncterm: 1.2-1
pve-qemu-kvm: 2.6.2-2
pve-container: 1.0-78
pve-firewall: 2.0-31
pve-ha-manager: 1.0-35
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u2
lxc-pve: 2.0.5-1
lxcfs: 2.0.4-pve1
criu: 1.6.0-1
novnc-pve: 0.5-8
zfsutils: 0.6.5.7-pve10~bpo80

One extra bit of configuration is a data volume that is using md-raid. That one seems to get stopped correctly before the system hangs instead of rebooting. The root volume is zfs RAID 1.

Hope this helps.

 

[ELS_sean]

could this be related to a software raid I have on the box?

root@proxmox:~# cat /proc/mdstat
Personalities : [raid1]
md2 : active raid1 sdc1[0] sdd1[2]
1465134841 blocks super 1.2 [2/2] [UU]
unused devices: <none>
root@proxmox:~#

the root partition is a zfs pool
root@proxmox:~# zpool list
NAME SIZE ALLOC FREE EXPANDSZ FRAG CAP DEDUP HEALTH ALTROOT
rpool 464G 7.88G 456G - - 1% 1.00x ONLINE -
root@proxmox:~#
root@proxmox:~#
root@proxmox:~# df -h
Filesystem Size Used Avail Use% Mounted on
udev 10M 0 10M 0% /dev
tmpfs 6.3G 9.3M 6.3G 1% /run
rpool/ROOT/pve-1 417G 7.9G 409G 2% /
tmpfs 16G 40M 16G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 16G 0 16G 0% /sys/fs/cgroup
rpool 409G 128K 409G 1% /rpool
rpool/ROOT 409G 128K 409G 1% /rpool/ROOT
/dev/mapper/PVE1-vmdata 1.4T 621G 681G 48% /mnt/data
/dev/sde1 3.6T 471G 3.0T 14% /mnt/4TB_Backup
cgmfs 100K 0 100K 0% /run/cgmanager/fs
/dev/fuse 30M 16K 30M 1% /etc/pve
192.168.1.51:/mnt/ZFS1/NFS_ZFS1 6.0T 2.6T 3.5T 43% /mnt/pve/Freenas
tmpfs 3.2G 0 3.2G 0% /run/user/0
root@proxmox:~#


Any suggestions?

Thanks,
Sean