[SOLVED] Stuck to get into Debug Boot

[Astralix]

Hi!

My root zfs is on consumer SSDs and these are only good to produce massive IO backdraws. So, I am going to switch them out with server rated Intel drives.
These two new SSDs are a bit smaller then the original three ones, so I have to replace them manually.

Unfortunately I cannot get the Proxmox ISO image to boot into a terminal for the final few commands. I am using an older ASUS Z10PA-UE mainboard that initially already boots through all controllers and PXE and whatever and I can't get it to boot faster, however, when it boots the USB stick and shows the Install Proxmox boot menu, I only have two or three keyboard clicks, then it completely freezes.
Especially trying to move the selector over the Terminal + Serial option just freezes the whole system. Only using Page Down gets me to Advanced and then I have to wait another 30s to see the Advance Menu. But that is all. No way to select "Terminal UI + Debug Mode".

I booted a Debian Image, unfortunately that doesn't come with ZFS.

So, instead of following THIS post and copying over 500MB of VM and being back online, I am now trying to get into a Proxmox Console for 4h (after searching for additional SATA cables for another 2h)

Any ideas?

 

[Astralix]

Okay, I half-way solved it.
I could use PgDn to jump to Advanced and then slowly press ENTER two times what brings me into the Debug screen of the graphical installer. Using Ctrl-D and another Ctrl-D I can get into the installer and then I can press ALT-A to abort. Other than the normal installers, this get you into the command line.

As that way you also have network access, you can install packages like fdisk and parted.

Even all that solved my initial question, the whole description I tried to follow from the post listed above didn't work out for me.
Everything goes well until I try to run grub-install.real /dev/sda inside the chroot. I always gives me an error: file-system not found.
Probably the reason is that the Intel drives like to be partitioned on 4096 bytes per sector borders while the blog writers and my old crucial drives are on 512 bytes per sector.
SO I have to find another route to follow.