The Wiki gives you keys heh, use a debian live CD or a rescue shell.. you can try efibootmgr -n 0000 to avoid the 0003 entry that is probably unhappy. If that works, well, set the boot order to start with the proxmox entry.
If it fails, mount...
you can logrotate / delete it, but you'll lose track of people trying to get to your server.. however, I'm guessing this is urgent, but maybe try to back it up before deleting it.
I'd suggest setting up a firewall to restrict who can connect...
Well, unless you actually restore a backup, it won't leave the cluster, that's quite a given. But a NIC can easily be replugged to another bridge.. I guess if it's more of a marker, and if you make sure you don't reconfigure the NIC it's fine...
Not that I know of, maybe room for a contribution here.. However, technically, the MAC is linked to the VM/CT, not to the network it's hooked on, so that may not be a reasonable feature. Imagine a NIC whose MAC would change depending on the...
hmm, just set the policy to DROP maybe? and disallow everything.. but at that point, why even connect the NIC?
EDIT: Ah, because you want IPv4 only heh. Well, I'm not sure you need ipv6-icmp if you block ipv6, it's enough for me (and do not...
You could use it as outgoing filter for your typo3 instance, I'd say this is a reasonnable usecase for PMG, heh!
You'd need to setup 587 port either using the firewall, or by tweaking postfix conf (setting up "submission" protocol the same way...
Hi Gilou,
The 1001 user is on the SMB/CIFS files to this folder. So I guess that the log files and the dump files are generated by different user ID's
However, Good News!
On the NAS:
I created a new NFS pool "ProxmoxBackup" on the NAS and...
Yeah, it's a bit weird, I wonder what the 1001 user is about on some files..
What ! would do is set up a user/group on the NAS, give it permissions on the dir to be exported still on the NAS, and mapall (root included) to that user. then...
Well, if they are not detected physically, you won't see options at all here (no boot from nic, no option to set them up..).. Did lshw / dmidecode yield anything interesting?
Check in the BIOS setup that your hardware is detected there maybe? Usually you can setup PXE or some options (like.. disabling them) in the setup..
If you don't see anything in dmesg, linux probably doesn't see it at all anyway. You can still...
Success! These are the steps:
umount /boot/efi
proxmox-boot-tool init /dev/disk/by-uuid/AED9-4562 grub
proxmox-boot-tool refresh
mount -a
reboot
After that the system rebooted with the updates showing kernel: Linux 6.17.4-2-pve .
Thanks for...
And also, but I don't suggest doing that.. since you only have one ESP, that you don't boot on ZFS nor use secure boot, I'd just bypass proxmox-boot-tool, and use grub directly.. but well, it's there :P
The upgrade path was not too smooth there.. If you need details about all this, you can check https://pve.proxmox.com/wiki/Host_Bootloader on the wiki, btw.
well, proxmox-boot-tool here thinks it's driving systemd-boot, and so does the UEFI setup. You could re-enable it (install the tooling, then make sure it boots the proper kernel). But I'd suggest going back with GRUB if you don't need...