OK, a maybe stupid question. Which bootloader is my machine using?
As i#m stiuck at GRUB RESCUE, i gues it's GRUB? But if i remeber well, i have installed via installer on a zfs-RAID10, so it should be systemd-boot?
i do not have proxmox-boot-tool in proxmox boot media rescue to check it. So...
That's not possible in that way. I the HP-Bios can only select the HD-controller to boot from and select the order in which devices are tried (Floppy, HD controller, Network, ..) but there is no way to select a single disk to boot from.
About the partitions, i need to power up the machine, but till then i have this screenshot from a Linux installer (did not knew any more what distribution this was) that shows "some" partition info.
And no, i cannot access the server physically today to detach the broken disk, i wanted...
we are using a old, mostly unused Proxmox server (HP ProLiant DL160 Gen8) as backup/fail-safe Hypervisor for our infrastructure production VMs.
I boot up that server ever week and clone the storage of those VMs via "zfs send" to it.
Now it seems that one disk is broken and it does not...
For all the people who need a solution for this problem. The solution is more or less straight forward, you just have to do it manuially, on OS level,, and not the GUI.
Steps to do:
1) Create a empty VM (the cloned one) by copying and editing the <VM-ID>.conf file of the parent VM...
I think that nothing will happen to that requests?
And not even a warning when using zfs volumes. It would be nice to knew that BEFORE you choose your storage system. So i#m now stuck with a lot of VMs where i#m only able to work with the last snapshot and not with any else. :-(
I now need to...
hm, that worked in my test before, but now that it's gettinmg serious, it doesn't.
Even the target VM has no snapshot attached, it says it has one
cannot receive new filesystem stream: destination has snapshots (eg. Storage10k/vm-200-disk-2@--head--)
must destroy them to overwrite it
OK, the solution is really simple. Even in the GUI it does not work, via "zfs send" it does. When target VM already exists as a copy of the source system, it's:
zfs send Storage10k/vm-100-disk-0@vorSAPDMZTest | zfs recv -F Storage10k/vm-101-disk-0
if target VM does not exist already, you had...
a second problem is that i do not have enough free space on that host. That's the reason for the question about "zfs send".
I used "zfs send <zfs volume>" to copy VMs over network on a different host. But in that case all snapshots got transmitted over.
This would be also a solution, but i would...
i use Proxmox on ZFS.
I have a VM with multiple snapshots. I would now create a copy of that VM based on a dedicated snapshot of that VM.
Is that possible? With "zfs send | ssh zfs revev " to another host?
How to do that?
Thanks a lot.