Search results

I suggest that option 2 is preferable, except it won't protect you in the case of fire or flood in the home, but I'm sure that you are aware of that.

I have QTY7 Proxmox nodes running on single SSD/NVMe drives in my Homelab, for approx. 4 years now. I do keep meticulous triple PBS backups of the guests, and figure that if the Proxmox host drive fails it's simple enough to rebuild, with the only issue being iGPU etc passthrough. I wouldn't...

Are you guys using the Realtek drivers for those USB NIC's? The Debian / Proxmox OS defaults to the cdc network drivers. It's been a while but I understand that the Realtek drivers can be in installed via DKMS package. I believe that the latest kernel 6.17 (can cause other issues) might even...

I suggest once again that people evaluate the Pulse monitoring app, which uses the Proxmox api to monitor not only the temps, but the CPU/RAM/Disk/Backups/hosts/docker apps etc. on a single pane of glass, right across your estate. They have made the app secure and really easy to install...

The helper scripts are great (I have approx. 20 running in my homlab), but they are susceptible to break on OS or the underlaying package updates. If you are going with OMV I would highly suggest running it in a VM with the drives passed through. It will be far more stable. To be frank, I went...

Just to add some input into the conversation, I use the 'Pulse' monitoring app to keep an eye on Proxmox, it plugs into the Proxmox api to provide all the info you need, works with clusters, docker, hosts, PBS, the works, complete with user defined notifications. The tool is very light on...

I use OMV (even though I have 2x TrueNAS installs) as it's light on resources and plays nicely with USB drives, they can be temperamental + I didn't want the overhead of the zfs file system. I would suggest that you ensure that you have a redundant file system AND Backups.!!! If the family...

Oh, I'm sorry, I'm sure I read that as 3.1. If you can connect to the web interface OK, are you able to perform the system updates? If not that might indicate an incorrect DNS setting, or the Repositories set incorrectly. I had pfSense running for a while inside a VM, I had to provide a...

In addition to the hookscript on Proxmox, you also need 'reset mod' inside the guest OS, that is the only way the the guest can reset the GPU prior to shutdown/reboot. You've not stated if the guest is Windows or Linux but I found the following guide helpful...

Not so confusing, your private subnet 192.18.1.0/24 addresses the IP range from 192.168.1.1 to 192.168.1.254, so if you fix the IP of the Proxmox node to 192.168.3.1 it is sitting outside of your IP range and thus unable to communicate with the Router or any other device on the network. You...

Sorry for the delay, I need to make some downtime available to get the information requested as the TrueNAS running on that node is critical to multiple applications in my lab.

There is nothing about the bare metal & 10TB until I asked. Therefore the post comes across as if you are trying to squeeze a Proxmox installation complete with VM stores, onto a single 60GB drive.!

That requirement is so very different from everything indicated in this threat. Why on earth are you trying to squeeze every MB out of a 60GB drive, if I were in your shoes I would only consider that drive for the root, and ignore whatever space is left over, as you have to make space for 1TB of...

You have to proved some space for the Proxmox OS itself, What VM are you trying to create which needs the full 60GB, perhaps there is an alternative way to achieve what you want to do. If you have 10TB in a networked share you can place VM's or anything else you want to there, all you need to...

Set the swap to 0 (as it will default to 8GB) Set the maxroot to 56GB (leave 4GB free), in case of drive full, you will appreciate having some free space which can be converted. However, I'm not sure why you are trying to do this, you can get away with 16GB (32GB if you also want to store the...

Use the advance disk settings during installation and there you can specify the size of the swap and root/boot drive, then the balanced will be assigned to local-lvm. There use can also set zfs, drive mirroring etc.

The node in question is AMD based, it does host a Windows 11 VM with the AMD iGPU passthrough, but that VM starts without issue. The VM which fails to boot is a TrueNAS VM, with NVMe's & SATA interface passthrough, details of the config: root@pve-5:~# cat /etc/pve/qemu-server/410.conf #TrueNAS...

I haven't done an install in a while, but I think you can ONLY set the root/boot disk size & swap, the system will use any remaining space for local-lvm. Proxmox is designed to run a separate drive for boot and another drive or RAID for the VM/CT store, so what you are trying to achieve is not...

From the graphical interface you can only set the swap and root/boot drive capacity, the remainder will be set to local-lvm, but you can manually resize and partition the local-lvm after installation.

Thanks for your reply complexplaster27, The device is available for me to furnish any diagnostics information which might be of use, just let me know what's required. Best regards DerekG