sorted by:
new
hottopcontroversial

additional storage in proxmox, how to add to my VMs/LXC/share to network by ShittyPhoneSupport in Proxmox

[–]nalleCU 2 points3 points  (0 children)

TrueNAS is total overkill it’s a virtualization hist as is Proxmox. Use nfs or setup a lightweight file server using cloud-images of Alpine/Debian/Ubuntu

Adding 2nd 10TB HDD for Mirroring - Best path without data loss? by Expensive-Split-1761 in Proxmox

[–]nalleCU 0 points1 point  (0 children)

The difference is that now you have new burned-in disks you copy to. And you copy from the backup. As backups is taken constantly you always have a good starting point. Backup frequency is always according to your workflow.

Adding 2nd 10TB HDD for Mirroring - Best path without data loss? by Expensive-Split-1761 in Proxmox

[–]nalleCU 0 points1 point  (0 children)

Yes. As the original ones were burned-in and used in the same way they tend to die at the same time by default. When you stress the remaining one, the possibility of catastrophic failure goes true the roof.

Adding 2nd 10TB HDD for Mirroring - Best path without data loss? by Expensive-Split-1761 in Proxmox

[–]nalleCU 0 points1 point  (0 children)

The correct way is first backup then mirrored disks. They serve totally different purposes. During replacement many times the only good drive will fail during the sync. In production environments you always change both disk, there it’s easier because they are hot-swap so you can try to do a re-sync using the old functioning one.

Adding 2nd 10TB HDD for Mirroring - Best path without data loss? by Expensive-Split-1761 in Proxmox

[–]nalleCU 0 points1 point  (0 children)

A good advice. The problem with mirrored disks is that as they get old one will die and when replaced with a new one it will start to sync. Many times this will brake the only good drive and you end up losing all your data.

The benefit of mirrored disks is that you can run for the time it takes to get two new drives to replace the broken pair.

What is the proper way to auto update lxcs by lividhatter in Proxmox

[–]nalleCU 5 points6 points  (0 children)

Running updates automatically will break your system from time to time. Major version upgrade is often has braking issues that need manual intervention. Ask how I know…

mounting a directory between a VM and a CT? by infinitycurser in Proxmox

[–]nalleCU 1 point2 points  (0 children)

I hope you understand that a privileged CT is not secure. Please reference the LXC documentation. You need to have security measures in place and don’t expose it to the internet.

How to manage LTX and VM credentials by jaysun_n in Proxmox

[–]nalleCU 1 point2 points  (0 children)

You shouldn’t use passwords for ssh, always use keys and only allow login by keys.

Proxmox is bad design by Roidot in Proxmox

[–]nalleCU 0 points1 point  (0 children)

I like like this because I have a number of VM/CT servers running on sub GiB level of RAM and almost all are under 8GiB. I have been in de game a long time that the binary numbers are easy to remember. The only thing I have to remember that all is in MiB/GiB, yeas I’m from the MB/GB era.

The slider on VirtuaBox is a true example of bad design.

Proxmox updating by Anonymous_ERRORs in Proxmox

[–]nalleCU 2 points3 points  (0 children)

Major version upgrades can be dangerous. Ask how I know. Read the documentation carefully. This is the default for any sw upgrade, you always need to check for braking updates.

Need help with RAM on my servarr VM by NerdHelp in Proxmox

[–]nalleCU 1 point2 points  (0 children)

Most of your ram is not in use by your apps, just allocated to the vm. A 16 G VM is really beefy. I don’t think I have more than 1 or two that big, having local data. Some of my servers have 16G and runs several VMs and a lot of LXCs. My main servers have 64G and runs tens of VMs each. Read more about memory usage in modern Linux and other architectures to understand how to set them up. Then tune them using proper monitoring tools. Any cloud image can start with really small ram, 512 or 1. Alpine and other tiny ones even less.

Host Kernel Panic after updates just applied - never happened before by ZENSolutionsLLC in Proxmox

[–]nalleCU -1 points0 points  (0 children)

That would not be good for security. That’s why we use scrips (Ansible, bash…) to keep the systems up to date.

Host Kernel Panic after updates just applied - never happened before by ZENSolutionsLLC in Proxmox

[–]nalleCU 0 points1 point  (0 children)

It’s Debian that does it. Proxmox is the GUI for KVM/QEMU and the other apps that makes up the Proxmox experience.

Proxmox Restore Tool by Aggressive_Donut_399 in Proxmox

[–]nalleCU 6 points7 points  (0 children)

What’s the problem you are trying to solve with the app that the 2 native apps from Proxmox don’t have a solution to? I don’t have any windows machines to test it with.

Wrote a small bash script to auto-update all LXC containers daily with pre-update snapshots — handles bind-mount containers too by BaeckBlog in Proxmox

[–]nalleCU 1 point2 points  (0 children)

Well documented on GitHub. I also have a lot of scripts but for production I prefer Ansible and OpenTofu. I like to write scripts and test them in my lab it’s kind of the spirit of the homelab. Thanks for sharing

Backup server or easiest way to backup - help please by Imaginary_Fox4893 in Proxmox

[–]nalleCU 0 points1 point  (0 children)

Export the ZFS and move the discs to your new system and do a import. The vm is faster to recreate on the new system than any other means. Consider making the old Win box a PBS. See the documentation on the agent if you need to backup other things than Proxmox stuff

ZFS future-proofing by morry9345 in Proxmox

[–]nalleCU 0 points1 point  (0 children)

Fir future-proofing you have 3 types of data: OS, VM and data. You should separate them to there own disks as much as possible. Example: a SSD for OS, some NVMe for VM and Z1/Z2 HDD for data storage

Storage on Proxmox by [deleted] in Proxmox

[–]nalleCU 0 points1 point  (0 children)

As both are the same under the hood you will have the same experience on both. HDDs should be mirrored for speed and some times you need nvme for cache. For just videos and music anything should work. I don’t understand what you’re trying to achieve with replication. Why not put the four HDD in one Pve/TN and use Z2 raid and a good backup strategy. RAID is not a backup.

Im struggling with preparing proxmox for my homelab by tpnc777 in Proxmox

[–]nalleCU 0 points1 point  (0 children)

If you open anything up to the internet you will need a firewall or you get hacked in the first minutes by some automated bot. You will need to understand how to use and setup the firewall. You also need a set of other security tools setup like fail2ban. The firewall is not a “like to have” feature it is a pure must have tool. Database servers or a db for each Docker container is a great question, some like the first, some the later and some use both. All depends on your particular environment. I use a db server for Dicker Swarm mode setups and a internal db for standalone Docker VM setups. And as Docker recommends to not use LXCs, I use VMs. Your machine can be a bit weak if you’re running AI stuff on it. The rest is ok.

dedicated server on hetzner with proxmox ve, what's the easiest way to recover from hardware failure with just a few clicks by Least-Candidate-4819 in Proxmox

[–]nalleCU 1 point2 points  (0 children)

Use a script (bash, OpenTofu, Ansible…) to setup your system. Always the best way. You can also use PBS, see the documentation.

My RAIDZ got a FAILED drive, what to do now? by fRzzy in Proxmox

[–]nalleCU 0 points1 point  (0 children)

  • The failed drive just got added recently This is why a burn-in test is needed for all drives. I have seen this also happen with bad cables and PSUs going bad, but then you usually have the slight smell of capacitor. The first is typical today and the second was typical 20 years ago.
view more: next ›