If it's just one out of three you might have a bad patch cable. Did you also try another patch cable?
Also, Minisforum boxes are known to thermal issues. Maybe this particular system gets hotter than the other two?
Topic says it all. But first let me introduce the topology:
PVE Host connected via LACP (bond0) to a core switch pair (QSW-M7308R-4X) MLAG trunk port. Trunk port has PVID 1 and IDs 1600 and 1702 configured. This configuration is known to work as...
Hello everyone I deleted an old VM from PBS with id 100. The new VM always with id 100, from error in the backup.
I solved the problem because inside the datastore there was the same id 100 but with the notes inside the folder. So I delete the...
In your first screenshot there is "Prunes 0". Is this still the case?
You may trigger pruning manually via "Run now" - and watch the log live.
Are namespaces involved? The "Edit: Prune Job" has a "Max. Depth" setting. If this is set to low it...
To be on the same page, none of this is PVE specific. You are dealing with basic Linux network management.
At one point in the thread you mentioned that there is a "direct" connectivity between the clients, is there an actual direct cable?
Your...
When logged in, try reset. (If this sounds risky: read man reset.)
I have no idea what triggered that behavior, but "reset" should re-initialize the terminal with sane values.
Disclaimer: I do not use containers...
this is a kernel regression affecting these devices with some firmware versions:
https://bugzilla.kernel.org/show_bug.cgi?id=220693
https://lore.kernel.org/all/176467086520.364377.182740446463637461.b4-ty@kernel.org/
the fix should come in via...
Could be kernel bug - https://bugzilla.kernel.org/show_bug.cgi?id=220693. I ran into it with S4600 drives, regression to kernel 6.14 fixed the issue so far.
@fabian - a kernel patch for the issue has appeared - details here:
https://github.com/tailscale/tailscale/issues/19777#issuecomment-4559535237
(sorry, wrong link initially)
Is this the sort of thing you bring forward to the current kernel...
Yes, you typically do not recover a node partially. What you did is effectively replace the node but put old hard drives in and now you’re trying to recover those in a clustered file system. At this point, the data on the ‘dead’ OSD is out of...
Yes, you typically do not recover a node partially. What you did is effectively replace the node but put old hard drives in and now you’re trying to recover those in a clustered file system. At this point, the data on the ‘dead’ OSD is out of...
i would stongly advice. as you wrote yourself - you fugg around since days with it.
i had exactly the same experience. i played around 3 days. nothing worked. finally i reinstalled proxmomx completely - my cluster wasnt productive yet and, as i...
So, should I just wipe the OSDs on that node then and re-add them? I just want to clarify before attempting that. I am in a 2/3 for that setup, and CephFS did come back up, and I am able to access everything, those 15 OSDs are still down though...
Stefan & daanw, thank you for responding. syslog.txt attached from a boot into kernel-6.17.13-6-pve. (I cannot ssh in to capture output when booting into kernel-7*, but can capture terminal screenshots via iDRAC if needed.)
Attached is an...
the issue, as i see, the osd service doesnt start. you need reset the counter
systemctl reset-failed "servicename"
systemctl start service
i had the same issue last weak, the result from some network changes. never got it fully up again...