[SOLVED] Kernel 3.10.x hangs on Boot with root on ZFS

bbaumer

Renowned Member
Dec 10, 2011
11
0
66
I evaluate Proxmox 3.4 with ZFS on KVM (Nested Virtualisation).
I installed Proxmox 3.4 on ZFS (RAID 0) with success.

To test Snapshot and Rollback on the ZFS Rootfs i installed Kernel 3.10.0-8-pve. With Kernel 3.10.0-8-pve and 3.10.0-7-pve boot hangs at accessing the zpool.
Kernel 2.6.32-37-pve works fine.

I tried rootdelay=30 without any change.

Has someone experienced similar problems?

Code:
root@pve34-zfs-1:~# parted /dev/sda print
Model: QEMU QEMU HARDDISK (scsi)
Disk /dev/sda: 8590MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name                  Flags
 1      1049kB  2097kB  1049kB               Grub-Boot-Partition   bios_grub
 2      2097kB  136MB   134MB   fat32        EFI-System-Partition  boot, esp
 3      136MB   8589MB  8453MB  zfs          PVE-ZFS-Partition

root@pve34-zfs-1:~# zpool list 
NAME    SIZE  ALLOC   FREE    CAP  DEDUP  HEALTH  ALTROOT
rpool  7.81G  2.00G  5.81G    25%  1.00x  ONLINE  -
root@pve34-zfs-1:~# zfs list -t all
NAME                                 USED  AVAIL  REFER  MOUNTPOINT
rpool                               2.93G  4.76G   152K  /rpool
rpool/ROOT                          1.22G  4.76G   144K  /rpool/ROOT
rpool/ROOT/pve-1                    1.22G  4.76G  1.13G  /
rpool/ROOT/pve-1@test2              17.1M      -   920M  -
rpool/ROOT/pve-1@rear-install       20.0M      -   927M  -
rpool/ROOT/pve-1@kernel-update1      232K      -   921M  -
rpool/ROOT/pve-1@kernel-update-3.1   248K      -   921M  -
rpool/cttest1                        797M  1.22G   797M  /rpool/cttest1
rpool/swap                           953M  5.69G   100K  -
rpool/vm-100-disk-2                   72K  4.76G    72K  -
root@pve34-zfs-1:~#

Proxmox34-3.10.0-8-pve-hang.png
 
Last edited:
I evaluate Proxmox 3.4 with ZFS on KVM (Nested Virtualisation).
I installed Proxmox 3.4 on ZFS (RAID 0) with success.
...

seems you use virtio virtual disk for your virtual Proxmox VE hosts?
if yes, the issue is known, just virtual SCSI disks (or IDE).
 
Just tested (again) in a VM, 3.10 boots. But I did not test Snapshot and Rollback, as I am not totally sure what you do exactly.
 
I changed the Diskbus from SCSI to IDE at the KVM from the Proxmox Host. Now Kernel 3.10.x is booting.

Thanks for the Confirmation.

I try to find advantages for ZFS as Proxmox RootFS over ext4. My Idea was to take a snapshot before each Update, to be able to rollback if something does not work as expected.