Latest activity
-
Pp-user replied to the thread Screwed up (mea culpa).Ok, I ran a garbage collection job on the daDup datastorage, and got 85 warnings (see logs). Now what do I do? Regards, Albert
-
JJohannes S replied to the thread OMV as LXC or VM.Die Helferskripte werden eben (wie ja auch aus den Forumthread hervorgeht) halt auch von niemanden unterstützt, außer den Autoren der Skripte. Ich würde davon die Finger lassen, solange man nicht versteht, was die machen. Die anderen haben ja...
-
JVermutlich hat @chris_lucio dabei auch eins nicht bedacht, nämlich das die Pentium N3700 CPU dann eben alle Aufgaben zusammen erledigen muss, die vorher eben zwei, drei oder x Raspi erledigt haben, oder ggf. erledigt hätten. :) Wenn man diese...
-
JAlso mit der Hardware ist eigentlich kein Blumentopf zu gewinnen. Technische Daten : http://downloads.dell.com/Manuals/all-products/esuprt_desktop/esuprt_inspiron_desktop/inspiron-3252-small-desktop_Reference%20Guide_de-de.pdf Es gibt nur einen...
-
JEigentlich ist hier ja so gut wie alles bereits gesagt worden, aber vielleicht doch noch eine Anmerkung: Willst Du die Kiste dann hinterher auch produktiv nutzen, oder jetzt einfach nur mal um damit und Proxmox herumzuspielen? Falls Du die...
-
BBu66as reacted to UnknownNPC's post in the thread Proxmox Freezes mit ZFS Kernel Panic bei Hetzner mit Kernel > 6.8.12 with
Like.
Danke für die schnelle Antwort. Im Journal ist leider nicht mehr der komplette Stacktrace da das FS scheinbar danach nichts mehr schreiben konnte. Ich werde jetzt erstmal die C-States wie von dir genannt einschränken und dann bezüglich des ZFS... -
Pp-user replied to the thread Screwed up (mea culpa).Ok, progress. Since the .chunks directory was empty (due to my own doing) I recreated the subdirectories in there: cd /mnt/datastore/cache/.chunks printf "%04x\n" {0..65535} | xargs mkdir -p chown -R backup:backup * chmod 750 * This will...
-
Aapollo13 replied to the thread Cephx Key Migration Procedure and Ceph 19.2 Squid Going EOL Soon.I stumbled over this thread and was wondering why I am not seeing this warning. Turns out the enterprise repo doesn't seem to have 19.2.5 -- is that on purpose? I understand that 19.2.6 isn't there yet, but 19.2.5 is already old? I have this in...
-
bbgeek17 replied to the thread Recent PVE Kernel 7.0.14-17-pve NVME drives is not availabe.@fabian, in case this turns out to be related to the PCIe link retraining regression from 7.0.14-7 (https://forum.proxmox.com/threads/7-0-14-7-kernel-breaks-pci-link-training.185549/), plain lspci -v won't show the link registers. lspci -vv as... -
VictorSTS replied to the thread Cephx Key Migration Procedure and Ceph 19.2 Squid Going EOL Soon.Yes. Your choice to keep your "franken-cluster" :) or go for a better manageable / supportable configuration. I would remove Ceph and use ZFS replication, but don't want to lecture anyone or take the thread off topic. I would add PVE to that PBS... -
UUnknownNPC reacted to Bu66as's post in the thread Proxmox Freezes mit ZFS Kernel Panic bei Hetzner mit Kernel > 6.8.12 with Like.
Die eine VERIFY-Zeile allein bringt leider wenig, bei den btree-Assertions steht die Info im Stacktrace direkt darunter (welcher Thread, txg_sync/zvol/metaslab...). Kannst du den kompletten Block aus dem Journal nachreichen, also alles ab PANIC...
-
UUnknownNPC replied to the thread Proxmox Freezes mit ZFS Kernel Panic bei Hetzner mit Kernel > 6.8.12.Danke für die schnelle Antwort. Im Journal ist leider nicht mehr der komplette Stacktrace da das FS scheinbar danach nichts mehr schreiben konnte. Ich werde jetzt erstmal die C-States wie von dir genannt einschränken und dann bezüglich des ZFS...
-
SStiefel46 replied to the thread [SOLVED] Problem backing up container.I'm getting the same error and found no files in the mountpoint directories neither in /mnt/vzsnap0 nor in /srv. Backing up the container in stop mode works without any problem. Any help is appreciated. Thank you in advance.
-
Ddick_fiddler69 replied to the thread Windows Server 2025 EventLog crashes with x86-64-v4 CPU after Windows Update — 0xC000001D illegal instruction.definately crahes here but only with v4. as per above. Yes, I saw that note, does not seem to be connected to VirtIO version 0.1.285. It's the update and v4.
-
j.theisen replied to the thread Windows Server 2025 EventLog crashes with x86-64-v4 CPU after Windows Update — 0xC000001D illegal instruction.Tested again on an Intel Xeon 6426Y system. Works without issue with x86_64_v4 on my end. So QEMU Guest Agent is running and Event Viewer is opening properly. Sidenote: There are known issues with VirtIO version 0.1.285 and Windows Server 2025... -
Ttschmidt replied to the thread Cephx Key Migration Procedure and Ceph 19.2 Squid Going EOL Soon.It's my PBS host and thus should be seperate from the cluster. It only acts as a fifth vote in ceph / corosync so I can lose 2 PVE nodes. And it hasn't got the RAM to act as a pve node anyway.
-
bbgeek17 replied to the thread Proxmox VE 9.2 – sporadic iSCSI NOP timeouts / DID_TRANSPORT_DISRUPTED with Dell PowerVault ME5 and Intel E810.Hi @huganega, Good news, this lines up with what we thought was going on. Let me pin one thing down, though. With net.ipv4.tcp_shrink_window=1 set, are the timeouts and transport disconnects actually gone, or just less frequent? I want to know...
-
Aakorn replied to the thread How to apply default lxc.cap.drop to all lxc by os.I think I found why capabilities are not dropped by default as they should be. I wrote a small script that follows lxc.includes in configfiles and inlines the included files until it obtains transitive closure, and the part pertaining to...
-
TTh.Naumann replied to the thread Cephx Key Migration Procedure and Ceph 19.2 Squid Going EOL Soon.Hi @all, very strange behaviour here in our 5 node proxmox-cluster (incl. latest updates) after ceph-update from 19.2.5 to 19.2.6 and successful cephx-key-migration (ceph-health status is "OK"): All new ceph-keys (type aes256k) are valid and...
-
Ddrom replied to the thread [SOLVED] The repository 'https://enterprise.proxmox.com/debian/pve bullseye InRelease' is not signed.Hello I have the same issue, with a single node on a licensed pve10/debian 13 cluster where all 4 others have no issue, and they are just configured the same. last week it was still operating flawlessly.