Proxmox rescue disk trouble

versus

Active Member
Jan 22, 2017
5
5
43
56
I installed a Proxmox 7.3 with a ZFS RAIDZ1 file system. After finishing the installation I upgraded to Proxmox 7.4 with apt dist-upgrade.
Now I am trying to boot with a rescue disk.
I try the proxmox 7.4 rescue disk and when I try to boot I get the error:

Code:
Error: Unsuported embedded BP (type=116)
ERROR: unable to find boot disk automatically
Press any key to continue

When try with Proxmox 7.3 rescue disk the error is different

Code:
Compression algorithm 111 not supported
 ERROR: unable to find boot disk automatically
Press any key to continue

Is this kind of error normal?
Is Rescue mode really useful for ZFS file type?
Which rescue Linux distribution do you recommend?
I have sometimes tried Ubuntu as a rescue disk but the ZFS it incorporates does not have all the necessary features and the pool is mounted in read-only mode.
 
I boot the latest PVE ISO, then start the PVE installer in debug mode and write "exit" to exit the installation. Then you got a linux shell you can yu to import and edit your ZFS pools.
 
  • Like
Reactions: JMTpaso and versus
Yes, work fine

Boot with Proxmox ISO
Advanced Options
Install Proxmox VE (Debug Mode)

In the console:

Code:
exit
/sbin/modprobe zfs
mkdir /mypool
zpool import -f -R  /mypool rpool

In the directory /mypool is the Proxmox pool for changing what needed

When terminate the operations to start again Proxmox:
Code:
cd /
zpool export rpool
reboot
 
Yes, work fine

Boot with Proxmox ISO
Advanced Options
Install Proxmox VE (Debug Mode)

In the console:

Code:
exit
/sbin/modprobe zfs
mkdir /mypool
zpool import -f -R  /mypool rpool

In the directory /mypool is the Proxmox pool for changing what needed

When terminate the operations to start again Proxmox:
Code:
cd /
zpool export rpool
reboot
I just made this account to thank you
i had a cache harddrive fail and when rebooting i could see the rpool but the tank/data pool was missing no matter what i did it said no pool was there followed your steps and it recovered it all

you saved me hours if not days of work Thank you
 
Hi, I also wanted to say thanks. I have been frequently adding and removing additional network cards, which results in Debian renaming the interfaces, which makes /etc/network/interfaces incorrect. I also passthrough my video card with output disabled. This results in an inaccessible system.

I'm not running ZFS on my system, so once I got into debug mode, I did this:

Code:
mkdir /mnt/proxmox-root
mount /dev/pve/root /mnt/proxmox-root
nano /mnt/proxmox-root/etc/network/interfaces

I then make my modifications, guessing at what the interface numbers Debian will assign, save, exit, and reboot.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!