Kernel panic on boot, when importing zfs pool

ZZZXXXTTT

Member
Sep 12, 2022
5
1
8
Hi, as mentioned in the title, I am running in issue when there is something wrong with my vm-storage zfs pool

I just decided to move the pool from an NFS share on truenas (virtualized) to native proxmox zfs, but yesterday when I was trying to move the VM disks from the original source to the new zpool, I believe I accidentally let it run despite of the storage capacity limitation. (in other words, I saw the capacity of the pool being full, transfer hang, and system not responsive when I woke up)

Now, my proxmox instance refuses to boot as it prints out:

panic adding existence segment to range tree

Please forgive me as I do not have a way to get any console outputs easily.

What I have tried was trying to prevent the zfs pool from being imported on boot, but the only way I could get into any interface that I can interact was through PVE's recovery mode, but when doing so I cannot import or destroy anything or copy any data to a different drive

Since it was just all my VM's storage and I already have 2/3 of the most important disks backed up (container storage and GitLab), I could just ignore it and destroy the dataset/entire pool, but the problem is that I am stuck with the panic and exceeding 120 seconds message on my screen and couldn't do anything

Sorry for the rather confusing lines in the post, I will try providing any details I can.

Thank you everyone for your patience and help
 
It would be nice if I could import the pool on read-only and get other VM disks out, as it would save me hours of configuration, but if not, as the first post described, I can also live with re-installing the runner and Linux GUI instance