PVE 4.4 to 5.2 Upgrade failing to boot

[tsumaru720]

Hi guys

I've tonight attempted to upgrade one of my servers from Proxmox 4 to Proxmox 5 - I followed the guide on the wiki for upgrading and it all seemed to go well until I rebooted the box once done.

Trying to load the new kernel pve-kernel-4.15.17-3-pve I get what appear to be traces possibly relating to ZFS (The text size on the console means I cant read the full history and when I scroll, it jumps back to the bottom because of the start job)

I used the ZFS install option when I first set up this server a while back on proxmox 4 so the entire system sits under 1 zfs vol.

FWIW I also tried pve-kernel-4.13.16-2-pve from repo but that dropped me into a boot shell stating that the zfs pool couldnt be found

Booting pve-kernel-4.4.128-1-pve works fine but so far I'm not having much luck on the new kernel. Has anyone come across this during an upgrade?

Thanks

 

[tsumaru720]

So Further info - none of the kernels in 4.15 branch work at all. I tried the latest 4.13 and it seems it just cant find my zfs pool. Booting the old Proxmox 4 kernel (4.4-128) the server boots, I can see the pool and all subvols, but Proxmox doesnt find any disks for my KVM VMs. (LXC stuff work fine).

 

[tsumaru720]

OK - I've managed to get 4.13 kernel working by adding some delays as per https://forum.proxmox.com/threads/zfs-cannot-import-rpool-after-reboot.37611/

I am still struggling to get 4.15 working. Whenever it boots I get the attached (apologies for it being a photo, the IPMI for the server isnt working!)

(The firmware corrupt has always been there, FYI)

 

[sahostking]

I seem to have similar issue after it loads swap and then does LVM section - I however use LVM where it gets stuck.

Not sure if its a similar issue but I am having some major trouble with 5.2 aswell with booting. https://forum.proxmox.com/threads/thin-pool-target-support-missing-from-kernel.44625/

I am not rebooting any node going forward till I understand or get some more answers

 

[tsumaru720]

Does anyone have any thoughts on this? This is currently blocking me from updating this box to 4.15