8/9/2023 0 Comments Freenas zvol![]() ![]() ![]() All other functions where ProxMox integrates with FreeNAS work correctly - I can create snapshots, clone VMs, make new VMs, make new disks in VMs, etc. ![]() I followed the remaining instructions in the README. I then patched the files again without any errors. I then re-installed the pve-manager, libpve-storage-perl, and pve-docs packages using 'apt-get -reinstall install'. I got error messages that the files had already been patched, but attempted to patch anyway. I then followed the instruction in the README. To try and fix this, I have made sure to update ProxMox, FreeNAS, and done a 'git pull' for the freenas-proxmox git repo. IE If I delete vm 140 from ProxMox, manually delete the extents and zvols for the vm 140 disks (eg disk 0 and disk 1), when I create a new vm 140, the first disk is vm-140-disk-2. This has caused a side issue of ProxMox being unaware of the deleted disks. When I have to do any of the above things, I have to perform the action in the ProxMox WebGUI and then complete the action by manually deleting the extents and zvols in the FreeNAS WebGUI. ProxMox-VMs/vm-140-state-snap1 at /usr/share/perl5/PVE/Storage/LunCmd/FreeNAS.pm line 212. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |