Du meinst also ein ZFS RAID 1 aus den beiden 256GB Disks, da drauf dann proxmox installieren und auch die VM's und aus den beiden 1TB ein ZPOOL als Datenspeicher?
Hallo zusammen,
ich habe seit ca. 2 Jahren einen Proxmox Setup laufen das ich damals komplett unwissend aufgesetzt habe.
Jetzt will ich einen neuen Server aufsetzen und dachte mir ich frage mal nach Ratschlägen zur Aufteilung der Disks.
Der Server besteht aus:
Core i7 CPU
Fujitsu Mainboard...
I tried the manual way, still the same result:
1. removed EFI disk
2. created a new one on local-lvm
3. used dd to copy data over to new EFI disk
root@server:/# find -name vm-200-disk-1
./dev/zvol/zfs-pool/vm-200-disk-1
./dev/zfs-pool/vm-200-disk-1
./dev/pve/vm-200-disk-1
root@server:/# dd...
Just tried two methods:
Shutdown VM, wait 10 Minutes, move EFI disk -> no luck
Shutdown VM, use sync command on command line, move EFI disk -> no luck
The move task output is:
create full clone of drive efidisk0 (zfs-pool:vm-200-disk-1)
Using default stripesize 64.00 KiB.
Rounding up size...
Hi,
thanks for the reply, I'll try you suggested method of waiting longer before starting the move task.
I'll let you know if I have success.
P.S. Yes I've managed to use the old EFI image from the ZFS pool, everything is up and running at the moment.
I do the following procedure:
Turn off the VM
Move the system disk to the other storage
Boot up again (that works fine)
Turn off again
Move the EFI disk to the other storage
Boot up again
Then it fails with above screen
What I can see is that the EFI image on the ZFS pool has just 128K...
Hi,
I try to move the EFI disk image from one storage to another, but if I do so using the GUI "move" option, the installed Windows 10 Guest doesn't boot and I get some sort of EFI Shell.
Can anybody point out if there is a way to move said EFI disk?
I use Proxmox 5.1 on a system with 3...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.