Search results

Context matters. What are you trying to keep alive?

Since in a pve environment any node can serve as api head, the simplest approach is to use a reverse proxy, typically run on your router but you can use a vm for this too. ngnix or haproxy work fine for this, you can use any of the million tutorials available.

There is no rational reason to run a cluster with different version nodes. There is RARELY a reason to run a cluster without being fully updated- and even then, fully updated with an older kernel pinned.

this is fairly straightforward. step 1: ensure autoexpand is enabled: zpool set autoexpand=on rpool step 2: use the instructions here to replace the first disk: https://pve.proxmox.com/wiki/ZFS_on_Linux#_zfs_administration step 3: either wait for rebuild to complete, OR follow the instructions...

Yes. Stop doing that. Neither the storage nor your hypervisor are designed for use with constantly changing disk presentation, so there is no tooling for it. If you REALLY want to do this you'll need to develop your own tooling.

Ah understood. So as @bbgeek17 mentioned this functionality is not present in PVE (at least not yet.) HOWEVER since PVE sits atop of debian its possible to home cook solutions for this using the API; there are a number of projects and discussions on the forum on user's solutions- example...

WD_480 is of type lvm. as mentioned above, qcow is only an option for fileshare types. see https://pve.proxmox.com/wiki/Storage for more information.

I see this constantly. "speed" is NOT the only metric by which a storage solution is measured. In truth, you RARELY use whatever "speed" a subsystem is capable of, but you depend on features regularly. If you can get by without integrated filesystem level checksum, PVE intefrated snapshots...

Why in god's name are you allowing multipathd trap your SATA DISKS? dont do that. there's literally zero benefit and added failure domain.

the "format" your vm's will be written as is a consequence of the store type. Post the content of /etc/pve/storage.cfg to get specific feedback.

You have two options. option 1: https://wiki.debian.org/NetworkConfiguration option 2: reinstall and this time DONT do whatever you did before that lead to your network configuration.

I have no idea what I'm looking at- and even with that I can search for eno3 or 7df06 and get no hits.

unless your interfaces changed names, they would be brought up during boot. check your interface names and look through your dmesg/journal to see whats going on.

Thats not particularly actionable ;) smarctl --test=long /dev/sdc

It could be, especially if is a vanilla esxi play. You would need to evaluate your usecase in its totality (distributed switches, storage technology, vrops, DRS, etc) PVE's scope is quite a subset of the entirety of the Vsphere stack. You'd need to be more specific. in what context? I guess...

post the content of /etc/network/interfaces

lsscsi --verbose you're looking for bus id 6.00 but with only 4 drives just run a full smart test on ALL of them.

Its not. if you really insist on using this hardware- make all disks passthrough (or single drive raid0, although that can still have issues when mapped as OSDs) and connect each storage device DIRECTLY to a SINGLE HOST. there's no point or benefit in multipathing for your usecase.

hmm. I'm due for a Eurotrip. maybe I can swing it if they'll still let me in with an American passport ;)

umm... I dont understand your network. why do you need cascading routers? EITHER your WRT or Opnsense can and should manage your entire network. It could work, but this describes a proxmox cluster which I thought you wanted to avoid. Seriously, why are you looking for so much convolution? just...