Recent content by PigLover

It definitely not an enterprise class device, but the NUC 12 PCIe card is no slouch either. I9-12900. 3x m.2 slots (PCIe gen4 slots), 10gbe+2.5gbe LAN. 2x Thunderbolt 4. If I was building a business I'd probably use traditional servers. But you could build one heck of a cluster out of these...

In order to remain HA Ceph requires you to supply enough “spare” resource to absorb a failure. You need to have enough disk space free on each host in order to absorb the loss of your largest OSD on that host. Further, in a cluster with replica 3, you really should have at least 4 hosts in...

If your up for a BYO project - take a look at the Akasa Euler series of heatsink chassis. They have a good choice of compatible miniITX motherboards and you can build performance to match your price target...

+1. The single most annoying thing about Proxmox.

There is a better resolution discussed here (post in the thread #6): https://forum.proxmox.com/threads/hdd-never-spin-down.53522/#post-322522

You might want to install the drivers using the dkms method (from the .deb file) rather than using the direct installer (its described on Odroid's wiki). If you install it directly with the driver compile script then you'll lose the driver and have to re-install any time you do an update that...

If your primary issue is Plex transcoding then the dual 2670s might not be the best choice. It will be a world better than you got on the Synology, but transcoding really works best on a GPU. Either (a) add a good Nvidia GPU to this project and pass it through to the Plex VM for transcoding...

GigE ports running at 100Mbps is often a symptom of a cable with one or more bad pairs or a bad connector on the NIC or Switch. Have you tested/swapped them?

But why do you care? You stated your belief that Proxmox is just an " an expensive packaging of KVM and a couple of open-source tools". You've trashed on their choice to make it Debian based (despite your denials - yes, you came here to trash talk them). Its clear you have no desire to use...

Nobody at Proxmox "forces others to use their distro". They provide a comprehensive package for a purpose. Lots of people seem to like it. It happens to be built on Debian. If you don't want to use it you are free not to do so. You said: - "I use as I please": good. An expression of...

You should double check that assumption. Assuming you are buying new, current prices for 25GB NICs/Switches are only a small margin higher than 10gb. Of course this changes if you have significant installed base to leverage (existing switches or 10GB NIC inventory). But check current pricing...

Odd. Last suggestion is to reboot the Proxmox host now that they are wiped and see if it clears anything that is still stuck. After that I'm at a loss.

Try doing a "vgscan" to re-scan the LVM cache. They originally had LVM data on them (lsblk in post #3) and it may still be registered in the LVM cache.

You shouldn't need to wipe the disks using dd - just clean out the MBR & GPT tables, all of the backup GPT copies and any LVM data. "sgdisk --zap-all <device>" should do it. After you've done that - or if you used the "dd" wipe - you have to get the system to re-trigger the device info for the...

Possibly this: https://tracker.ceph.com/issues/42026 I was seeing this same fault periodically on a non-Proxmox (K8s/rook) install of Ceph. Its fixed in Octopus (Ceph 15.x).