Recent content by Dunuin

There are cheap N100 MiniPCs that support 32 GB of RAM and Ryzen Mobile MiniPCs that support 96GB.

Not only log. Logs, metrics of all the graphs and also constant writes to the config DB. And yes, there are hacks to reduce the writes...but not recommended if you care about stability. Power outage or kernel crash and all that then volatile data will be lost. Maybe not that problematic to lose...

You can't do that using the GUI. Like most advanced stuff with PVE, you will have to do that via CLI. Create a mountpoint using mkdir /mnt/someMountpoint, then use the mount -t xfs /dev/disk/by-id/yourdisk-partX /mnt/someMountpoint command to mount it temporarily or edit your fstab if you want...

Jdownloader: 3 vCPUs and 4GB RAM (otherwise browsing will be terrible and extracting eats CPU and RAM) Nextcloud: 2 vCPUs and 4GB RAM (maybe more in case you want apps like clamav and office) OMV: 2 vCPUs and 4GB RAM (probably less RAM will work but caching is nice for performance...especially...

One option would be to restore that VM 123 using another VMID like 1000. Then, depending on the storage that is used, rename the virtual disk according to naming scheme. So for example from vm-1000-disk-1 to vm-456-disk-1. Then do a qm rescan and destroy VM 1000. The disk should now appear as an...

If you are not working with namespaces, this is fine. Yes, see notifications: https://pbs.proxmox.com/docs/maintenance.html#notifications You might need the latest PBS3.2 in case you don't want to set up a mailserver like postfix yourself on that PBS.

Combine those two examples: https://pve.proxmox.com/wiki/Network_Configuration#sysadmin_network_vlan https://pve.proxmox.com/wiki/Network_Configuration#sysadmin_network_bond So for example: auto lo iface lo inet loopback iface eno1 inet manual iface eno2 inet manual auto bond0 iface bond0...

PVE isn't supporting mdadm raid (but its working fine with some special case exceptions where it might break your array). Both should work. But keep in mind that a VM won't directly access the real physical disks but is still working with virtual dual disks if you don't passthrough the entire...

See "Changing a failed bootable device": https://pve.proxmox.com/wiki/ZFS_on_Linux#_zfs_administration But instead of the "zpool replace" you add the first new disk via "zpool attach". Once that is done and your mirror is working you could do the same again but this time using "zpool replace"...

Do you actually mean VZDump backups or that your PBS VM got its datastore on an external storage? In the latter case you should backup your PBS VM via VZDump to be able to restore it on the new cluster.

I store all important stuff on the TrueNAS because otherwise my Windows machines would need to use NTFS and I trust ZFS way more with its data integrity features that all Windows filesystems (except for ReFS that that my Win10/11 Pros don't support) are lacking. You don't passthrough the real...

PVE only runs on top of Debian 12, not Ubuntu. I don't think the PVE ISO installer will support dual-boot. So you would probably need to switch to Debian 12 or at least install a Debian dualboot with Ubuntu and then PVE8 on top of Debian 12 with mod-probe enabled for both linuxes.

Depends on how much you harden security of PVE/PBS and how much you optimize them. If you do that there is a lot more to do. - installing additional packages - editing lots of configs of debian packages that are not in /etc/pve - setting up users/groups/privileges - changing the owner of every...

You shouldn't run PVE on thumb drives or SD cards. Its writing a lot and will kill them quite fast because of cheap NAND and missing wear leveling. USB SSDs or USB HDDs would be fine.

I also observed this. Editing the network config of the LXC via webUI isn't always updating the config files of the Debian 12 LXC. Not even after stopping and starting the LXC. I then had to edit the LXCs /etc/network/interfaces, /etc/resolv.conf and /etc/hosts to match the changes done in the...