Last edited:
# create chroot dir
mkdir /target
# import, but not mount rpool, with all mountpoints prefixed with /target
zpool import -N -R /target /target
# mount root dataset to /target (you need to add your dataset here - you can find it with "zfs list")
mount -t zfs rpool/... /target
# mount special FS
mount -t proc proc /target/proc
mount -t sysfs sys /target/sysfs
mount -o bind /dev /target/dev
mount -o bind /run /target/run
# chroot into chroot dir
chroot /target
zpool import -N -R /target /target
zpool import -N -R /target rpool
last access by Proxmox hostid=xxxxxxxx at yyyyy
The pool can be imported, use 'zpool import -f' to import the pool.
zpool import
zpool import -N -R /target rpool -f
. Sorry for so many questions but I want to be extra careful with chroot as I don't want to perform the wrong steps for a disastrous consequences.zfs list
:mount -t zfs rpool/ROOT /target
and it says,rpool/ROOT
to /target/rpool/ROOT
already. If that's the case, is that good enough?rpool
to /target
, do I still run the following:mount -t proc proc /target/proc
mount -t sysfs sys /target/sysfs
mount -o bind /dev /target/dev
mount -o bind /run /target/run
chroot
, is still still chroot /target
? Or is it chroot /target/rpool/ROOT
?journalctl -b-1
but it is very long (as expected). How can I go about exporting it to a USB stick.journalctl -b-1 > bootlog.txt
. However, how do I go about copying that to a USB stick since I am chroot'ed?chroot /target
immediately after zpool import -N -R /target rpool -f
and zfs mount rpool/ROOT/pve-1
. It seemed to work for me (at least I was able to run journalctl -b-1
.mount -t proc proc /target/proc
mount -t sysfs sys /target/sysfs
mount -o bind /dev /target/dev
mount -o bind /run /target/run
journalctl -b-1
for your review. I hope there is a fix for this.\etc\network\interfaces
to remove all MTU related settings, reboot the system and no luck. I also reboot using USB and tried Rescue Boot
and still no luck. It says it cannot find rpool
. So it looks like the underlying issue is still related to rpool
not being recognized.initrd=\EFI\proxmox\6.8.12-11-pve\initrd.img-6.8.12-11-pve root=ZFS=rpool/ROOT/pve-1 boot=zfs quiet intel_iommu=on iommu=pt nvme_core.default_ps_max_latency_us=0 pcie_acs_override=downstream,multifunction initcall_blacklist=sysfb_init video=simplefb:off video=vesafb:off video=efifb:off video=vesa:off disable_vga=1 vfio_iommu_type1.allow_unsafe_interrupts=1 kvm.ignore_msrs=1
nomodeset
by following your instructions:initrd=\EFI\proxmox\6.8.12-11-pve\initrd.img-6.8.12-11-pve root=ZFS=rpool/ROOT/pve-1 boot=zfs quiet intel_iommu=on iommu=pt nvme_core.default_ps_max_latency_us=0 nomodeset
pool import rpool -f
and then exit
as suggested. That fixed my system and it booted up normally. I was able to then login via the web interfaces, ran updates and everything seems to be working. Thank you. proxmox-boot-tool refresh
, correct (no need to run update-grub
since the system is running zfs)?We use essential cookies to make this site work, and optional cookies to enhance your experience.