yes. as Peter suggested.
I've personally found similar issues with two Proxmox node having a single m.2 as Os/boot drive.
- In the process I cloned the m.2 to a ssd. And the instance ran fine... without this error.
- Pushed fresh backups, reinstalled, rejoin cluster, import backups. Less than...
Yes... PBS discord dark (which I reffered to as discord dark in the previous post)...
Works very well... But i'd never use this on a production server, neither will I use ''Dark reader'' in any production environment.
-
But yeah, these guys pulled it off, makes you wonder what Proxmox is...
Touching the OSD?... With my hands? I'm letting you a 5 minutes headstart before I call the police sir! ROFL
I'm currently using the discord dark theme onto the ''entry point'' node of my personal cluster, I let all the nodes from work vanilla, this way I will not mistakenly reboot a node at...
It's an m.2, i don't get any relevant information out of any smartctl.
It all started when the GRUB refused to find the lvm:
1. Cloned the m.2 to another storage, Grub still needed to be repaired
2. done the grub repair procedure with the ''nudge'' operation to repair this newly cloned image...
Instead if playing with lvexpand, you can nudge the lvs another way:
Did a vgrename to pve (like pvee)
Revert back to pve,
did the grub-update, and it worked
(Note: It took a while, probably because it's changing sub reps names for all my 52 lvs)
*Warning, In another occurrence, I tried...
HI,
I got this exact problem but..
I got no room to lvextend root partition.
Lv reduce seems to corrupt the install. Good thing I'm testing everything on a clone.
Still. it repairs grub anyway so I was able to confirm, booting off two drives, that my proxmox is still alive but locked under the...
I don't trust plugins for this, that's why I'm using PVEDiscord DARK on the least ''important'' node of my cluster to benefit from the dark mode, but still, it's not ideal, I wouldn't dare to install this on any node on the cluster at work.
Let me even extend this post to a new request.
Dark...
Still doing experiments and the more I play with it, the more I begin to suspect Proxmox has simply a problem dealing with a second Bridge.
Why can't it be set on two gateways?
The only way I sucessfully was able to experience a truly working bond was when I set the bond as the ONLY connection...
Thanks for your kind reply. I tried second example and I simply don't get any net access to the server VIA bond0 anymore.
Is there a line missing?
Just to be clear.
vmbr0 is fine (vlan aware, running on base lan)
vmbr1 needs to be:
from the bond0
vlan aware
running on vlan 66
I'm sorry if...
Some progress here...
Was able to effectively run a second NIC on a VLAN, passing through other VLANS. Now. I'm LAGG doesn't work properly. here is the current config.
auto lo
iface lo inet loopback
iface enp3s0 inet manual
auto enp9s0f0
iface enp9s0f0 inet manual
auto enp9s0f1
iface...
Hi everyone,
I'm running a particular scenario here
I'm using three nics in total.
enp9s0f0
enp9s0f1
Are bond to LACP, slaves to Vmbr1, vlan aware
Should run on a 66 Vlan
enp3s0
slave to vmbr0, vlan aware
should run on primairy gateway
---
The reason for this setup is to, mainly run on...
I understand how complex/impossible to take into account All bios behaviors accross space and time,
The way I read you, there are no way to determine which Serial number was associated to a particular IOMMU group and remap the newly numbered group to the VM(s) it was associated to.
Also I...
Hi all,
Very sorry if the topic is already adressed (pun intended)
I read the documentation of Iommu and this behaviour doesn't seems to be covered (or incompatible jargon)
Is there a way to ensure that IOMMU device adress shifts along with hardware changes?
IOMMU id's seems to be arbitrairy...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.