New Install of Proxmox 5.1 ZFS Mirror enters Busybox on first boot

A

am45931472

Member
Feb 10, 2018
4
0
21
45
Just trying to do a basic zfs mirror install of my proxmox 5.1 OS but every time after initial install I get forced into busy box with no rpool found error. I've tried zpool import but no luck.

I know this is a common problem, I know it has to do with how device names are assigned from the system in proxmox 5 which has changed from how it was before PVE 5.

Hardware is Supermicro x9srl-f motherboard and multiple LSI 9207-i8 HBAs.

I've got multiple HBA's in this system, running legacy bios. the USB stick that I use to do the install also gets a Device sdX name which of course gets removed from the system after install thus reordering device names. When i remove all the HBA's from my system and just do the zfs mirror install using only 2 disk attached to the motherboard sata ports it enters proxmox just fine. but once i reinstall the HBA's it reorders everything.
 
Thought I should Add some more information into this posting as this problem is driving me crazy and I just cant spend so much time on this getting no where.

Hardware is a Supermicro X9srl-F motherboard with a Xeon 2650. 32GB Ram.
I have multiple LSI 9207-i8 HBA's, 1 GPU, USB card and 2 Intel NIC's

Proxmox 5.1, also experiences this with Proxmox 5.0

just trying to do a clean install of proxmox onto a ZFS mirror using 2 SSDs.

install from usb stick

after going through the install when proxmox is loading I'm hit with the error

cannot import 'rpool': no such pool avalible

Failed to import pool 'rpool'
Manually import the pool and exit

I am then able to manually do zpool import and use its long number identifier to import the pool and the system will successfully boot.

I am able to do edit ZFS_INITRD_PRE_MOUNTROOT_SLEEP as suggested in the Proxmox ZFS Tips and Tricks page however I still see that I'm getting a ZFS error on loading

Failed to start Mount ZFS filesystems
see 'systemctl status zfs-mount.service' for details


Just trying to find a way forward. I plan on passthrough the GPU and HBA's in this system to VMs and would like to try and prevent future problems when i do that as I suspect this all is caused by proxmox device naming scheme.

I'll also be creating some other ZFS pools to store VMs on.
 
You must log in or register to reply here.
Top Bottom