Closed boospy closed 5 years ago
Thanks for reporting, will try this and see if i can reproduce and fix!
Hm, i'm unable to reproduce:
/tmp/pve-iso-2-pxe# ./pve-iso-2-pxe.sh /tmp/pve-iso/
#########################################################################################################
# Create PXE bootable Proxmox image including ISO #
# #
# Author: mrballcb @ Proxmox Forum (06-12-2012) #
# Thread: http://forum.proxmox.com/threads/8484-Proxmox-installation-via-PXE-solution?p=55985#post55985 #
# Modified: morph027 @ Proxmox Forum (23-02-2015) to work with 3.4 #
#########################################################################################################
Using 5.4.iso...
Mounting iso image...
copying kernel...
copying initrd...
Unmounted iso, extracting contents of initrd...
Added iso, creating and compressing the new initrd...
/tmp/pve-iso/pxeboot /tmp/pve-iso /tmp/pve-iso-2-pxe
Cleaning up temp files...
Done! Look in /tmp/pve-iso/pxeboot for pxeboot files.
/tmp/pve-iso /tmp/pve-iso-2-pxe
/tmp/pve-iso-2-pxe
Thanks for testing, you are right. There was ein automtic ACLtool that blocks that process on ZFS Filesystem. :+1:
Hello,
yesterday i tested the new PVE 5.4 ISO. The script seems to be working, but if you boot, you came to a kernelpanic. Here is the output.
This is the content of the folder pxeboot:
Thanks :+1: