Can I get away with mirrored 32GB SATA DOMs for Proxmox 5.1 boot drives? All VM's will run off NVMe but wanted to know if I could use the two orange connectors for drives.
Unfortunatelly, this is not true for Proxmox. In standard configuration it writes to disk all the time. Not much, but there are small writes every 2-3 seconds, even when no VM is running. Those are killing consumer-SSDs very quickly...Yep, I agree with @PigLover . You shouldn't be writing much data, if any at all, to your root OS partition. PID files, etc, should be going into RAM disk and logs should be written to your bulk storage or sent to a syslog server.
Sure thing. That's good anecdotal evidence, and I'd probably have a similar experience. The reason it's a concern for me is that frequent writing to consumer-grade USB sticks is not what I would consider a best practice... especially if you're trying to use the hypervisor in an enterprise environment.I have been using proxmox on USB dom on production for more then 2 yrs with more 30+ node ... i use Sandisk ultrafit using mirror Disks
What is the risk of running Proxmox on USB drives? (barring @llbeking opinion) I am also thinking of using mirror USB drives. Is it worthwhile changing the USB drives after a fixed period of time regardless of whatever wear it has?I have been using proxmox on USB dom on production for more then 2 yrs with more 30+ node ... i use Sandisk ultrafit using mirror Disks
In other words, an "out of the box" Promox installation is insufficient for protection against wearing out the flash, and needs to be configured as above? Is this written anywhere in the Proxmox documentation? Can you please provode a link? Remember, even though I am highly experienced with Debian, I am a complete newbie to Proxmox.A good USB DOM can handle Proxmox VE Cluster as I stayed you need to move
- /var/log
- /var/cache
- /var/tmp
- /var/lib/docker (if you are also running docker)
- swap
I have one of these cheap USB DOMs but I haven't used it yet. I don't know if it's SLC (I would presume MLC due to the price). Have you got a link to yours please?There are reliable SLC chip USB DOM (cost USD 25)
I love these USB sticks and I often use them as my OS boot drive.and also my favor dual SanDisk Ultra Fit. easily found anywhere
This is new information to me as it is very useful. I didn't know about this at all.What I found most troubling issue with ANY USB DOM is its over power protection issue and never is the write wear-out failure
usb device descriptor read/64, error -32 typically caused by bad/incompatible USB 3.0 controller on the motherboard, so that's why test your USB DOM first.
But doesn't this contract what was stated above? In other words, see the following quote:if you run NETDATA or other monitoring app, you will find once Proxmox is booted, there is very very little io goes to the root fs and that is a fact. So why waste a sata port when a USB A connector on the motherboard can do the job.
@Rhinox is talking about "standard configuration", whereas I get the impression you are talking about a non-standard configuration as per your list of file systems and mount points above. Is this correct?In standard configuration it writes to disk all the time. Not much, but there are small writes every 2-3 seconds, even when no VM is running. Those are killing consumer-SSDs very quickly...
netdata provides very good monitoring of the systemIn other words, an "out of the box" Promox installation is insufficient for protection against wearing out the flash, and needs to be configured as above? Is this written anywhere in the Proxmox documentation? Can you please provode a link? Remember, even though I am highly experienced with Debian, I am a complete newbie to Proxmox.
if you google it, you find evtran store right away. https://www.aliexpress.com/store/2842018 now is @ usd 16 and I always take off its plastic overI have one of these cheap USB DOMs but I haven't used it yet. I don't know if it's SLC (I would presume MLC due to the price). Have you got a link to yours please?
In the screenshot you posted, what is "eVtran V03S SLC"?
What Rhinox saying are log info write to /var/log/corosync directory and that's why I said you need to move entire /var/log with PERMISSION intact to your hdd pool@Rhinox is talking about "standard configuration", whereas I get the impression you are talking about a non-standard configuration as per your list of file systems and mount points above. Is this correct?
Not exactly Debian, but ESOS does a good job running from USB, completely unmounts and only writes are when the current config is changed. (USB mounted, config written, unmount)We need a Debian distribution that does minimal writing when the OS is running on a flash device. I guess this could be achieved withj some combination of OverlayFS, tmpfs, SquashFS, JFFS2, and UBIFS. Does anybody know if such a project already exists? The closest I can think of, off the top of my head, is Tails. I understand that NanoBSD does something similar to this already.
Do you also move these out of the usb drives?Dual Sandisk Ultra Fit 32GB for me in ZFS mirror so if one does shit the bed I've got half a chance to swap it out.