So, I've just done a regular arch linux system update. Of course without kernel updates because of issues/14622.
After rebooting, there was nothing left. I still got an ZFSBootMenu entry somewhere in the efibootmgr but that's it.
After using my archzfs usb iso, I went to software/arch-linux-configuration/scripts/zfs/recover and started 01-mount.sh. What I got in return was a no pool available.
I've used them all, parted, gdisk, testdisk and fdisk but they all have told me the same "shiny new ssd you got there". By the way, the ssd is a nvme-one from Samsung.
I've fired up the lenovo internal system check tools but all they say is "super fine disk you got there, almost totally new".
What I did at the end was rebuilding my partition table using sgdisk. After that, I've also mkfs.vfat the efi boot partition and recreated the zfsbootmenu as well as the efibootmg entries. Important not, you have to update your /etc/fstab for the boot efi partition after doing that.
Nice to know, after creating the zfs partition via sgdisk, I was able to fully import my encrypted zfs pool.
This is a pretty strange error and I hope I don't have to fix this again in the near future. It leaves a strange feeling in your stomach
Today, I had the "joy" to work on a linux machine and edit a lot of files. The problem is, I had to use a Windows 10 as host OS.
Furthermore, the remote machine was available only via a bastion host/jump host. So it took me some time to make this possible.
I was not able to make sshfs-win working. WinSCP is a fallback option but this would result in edit a file -> save a file -> upload a file. I wanted to avoid the step upload a file.
What comes after this line is a snapshot of my created howto. I hope it will save you some time. It took me a lot to figure it out.
Given is, that you need to mount a filesystem via sshfs.
Following up, I will provide a guide how to do this by using a Windows 10 machine.
Bonus task, we are using a jumphost.
Steps
1.) Ensure you are running wsl2
wsl1 does not have a working fuse
Open a powershell and run wsl --list --verbose
If the VERSION says something bigger 1, you are fine