Host can't reboot / shutdown

stephane_c

New Member
Sep 18, 2015
8
3
1
Hello,

I have a problem with my proxmox server when I want to reboot or shutdown.
The server shutdown correctly all VMs/containers, but can't shutdown itself (I think I have a kernel panic).

Hardware :
  • CPU: Intel(R) Core(TM) i7-7700K CPU
  • MB : MSI Product Name: Z270 GAMING PRO (MS-7A59)
  • 2x SSD (RAID 1) NVME for system
  • 3x HD (RAID 5) for vm/containers
I checked log files, but don't see useful information about this.

Screen when shutdown: ( I can't get more information :()
497386IMG20170509091039.jpg



Any way to find more logs / information about this ?
 
+1 for taking an appropriate screenshot

it looks to me like a disk device was missing at the time of the unmount step of the shutdown
did you unplug a USB key without unmounting properly ?
also does the problem happen on each shutdown ?
 
Hello,
I don't have usb key, and yes problem happen on each shutdown.

I take an other screen :
584170Capture.png


in my fstab :
(RPOOL = 2xSSD RAID 1 xfs, md0 => 3xHDD RAID 5)
Code:
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/zvol/rpool/swap none swap sw 0 0
proc /proc proc defaults 0 0
/dev/md0        /disks/ ext4    defaults        0       0

Code:
root@server:~# zpool list
NAME    SIZE  ALLOC   FREE  EXPANDSZ   FRAG    CAP  DEDUP  HEALTH  ALTROOT
rpool   232G  1.27G   231G         -     0%     0%  1.00x  ONLINE  -
Code:
root@server:~# zpool status
  pool: rpool
 state: ONLINE
  scan: none requested
config:

        NAME           STATE     READ WRITE CKSUM
        rpool          ONLINE       0     0     0
          mirror-0     ONLINE       0     0     0
            nvme0n1p2  ONLINE       0     0     0
            nvme1n1p2  ONLINE       0     0     0

errors: No known data errors



Shutdown problem was appeared just after proxmox installation (I was never can reboot server without force hardware)
 
PVE does not support mdraid. The kernel stack trace indicate that it tried to write out an unmapped buffer. The only references I could find to similar issues are a bug in fallocate/truncate, and interactions with already closed nbd connections. Maybe mdraid has a similar problem?
 

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!