Videos
Hi!
Looking to buy a pair of 1tb SSDs for proxmox for a RAID 1 setup. What are some good entry level enterprise grade SSDs that I can expect a few years of worry free use on? I dont know much about the differences between enterprise & consumer SSDs, but I've read enough to know that I should care to use the better disks for the long term.
Hello!
I'm going to be running my first virtualization server using Proxmox 7, and I'd like to keep the OS on a pair of 2.5" SATA SSDs in ZFS RAID 1 configuration.
I've got a pair of Lexar NS100 512GB SSDs I was going to use to get started, but I've run into a problem with TRIM. The hardware apparently supports it, according to `smartctl` and `hdparm`, but `fstrim` says they don't support the `discard` command.
I could very easily see Lexar putting out an SSD at the low end that supports TRIM when the Windows utility is installed, but doesn't support it under Linux using standard tools.
So, I need to pick up a pair of high-endurance, low capacity 2.5" SATA SSDs that will work for this purpose. My size options (thickness) are "7mm to 9.5mm."
I'd prefer to buy used enterprise SSDs, as so far that's gotten me higher endurance at lower prices.
Any suggestions?
Thanks!
I've been looking at various NVMe SSDs and I can't fully get a picture of what's worth purchasing. I have brought a 2TB Crucial P5 Plus, but looking at storagereviews (linked below) isn't not looking the best, when you look at the SQL test. Since I'm using the disk to run multiple VMs.
Would I be better exchanging it for another NVMe drive, or am I worrying about nothing here? I would buy a DC grade NVMe but those are very expensive in the 2TB capacity mark.
I was looking at exchanging it for a Samsung 970 Evo Plus, but I've read there maybe hardware issue with cache design on that model, people seem to get varying results.
I'm using the NVMe disk in a PCI3.0 slot, so 4.0 isn't required, only got the Crucial P5 Plus because it was a good price.
https://www.storagereview.com/review/crucial-p5-plus-ssd-review
Hello all,
I've ordered a couple of mini PCs to add to my existing Proxmox setup to play with HA configuration.
These mini PCs only have 1x m.2 NVMe slot (2280) and 1x SATA 2.5in slot.
My question: From a purely VM performance perspective, would it be preferable to go with a large consumer NVMe drive for VM storage, or a large (used) enterprise SATA 2.5in SSD instead? The entirety of the Proxmox forums is "consumer SSD = crap," but the official benchmarks I've been able to find are just vs. the consumer SATA SSDs - I've not been able to find any real comparisons with consumer NVMe drives. In those benchmarks, though, the consumer drives lagged waaaayy behind, presumably due to them not performing as well under a Proxmox / VM workload. Because of this, I'd initially been planning on getting a used 1.92TB PM863 for each of them for VM storage, but have been re-thinking that.
Yes, there will be backups.
Thank you
My Proxmox installation and containers are currently on a 250 GB NVME. I want to add a 2.5" SSD (2TB capacity) to my machine and keep 1 TB reserved for taking backups of different containers on a periodic basis and reserve the other 1TB as data storage for quick sharing of files over the network using samba. What would be the best way to set this up?
If its possible you may consider using seperate 1TB ssds so if one fails you don't lose everything. Also you'll make it easier to allocate on the host. Just my opinion
As mentioned you should backup to a different drive (and location, if you can). But this isn't really a backup strategy question, so I'll stop there.
As for your setup, I would create a zpool for that drive alone. Then I would create two separate zfs file systems, one for backups and one for file sharing. You can put file system quota on each to limit the size to 1tb if you want.
For file sharing I would just build a CT (I use debian 11) and install samba there. Then you bind mount the associated file system directory(ies) to the VM and share them as needed. Simple and elegant. Bonus: encrypt the entire file system and use a startup script to unlock it and start the CT either on boot or with a password. Then it's locked down if someone steals the drive or server.
To do backups, I would create a CT with PBS and bind mount that file system to it as a storage repo and do all of my backups to it. That way on a NAS you can just sync it with that repo. I like this method because your server does all the work and your network just has to transfer what's required to sync the backups.