Recent content by arteck

little infor from here after change crucial CT240BX500SSD1 to WD blue is the problem DONE

the issue was with crucial CT240BX500SSD1 I have changed it to WD blue.. i'm watching

ohmmm...I know you don't want to hear it but this is a SSD drive. and befor 18.2.6 it works without issue and nope no SMR method.. i think its only for HDD

@g yesterday after restart it was no longer there.. now same issue

strange is under 18.2.x was no problem with same hardware constellation.. why now ?? my unifi network works since 8 years.. no issue here btw: the last reef version 18.2.6 has the same problem...

wait 2 days and you see the info again

i see the same message and i only have ssd's. the strange thing is that the message goes away after 4-6 days and comes back after 7 days. without rebooting or anything else my cluster includes 5 devices and the cluster is running since 5 yeras.. the last reef version had the problem but not all...

i have 5 nodes and one have a problem with HEALTH_WARN: 1 OSD(s) experiencing slow operations in BlueStore [global] auth_client_required = cephx auth_cluster_required = cephx auth_service_required = cephx cluster_network = 10.45.45.196/24 debug_filestore = 0...

my cluster have 5 pve's..one is a HP ProDesk 400 G5-Desktop-Mini with Realtek RTL8111HSH-CG-Gigabit and this is my worry child aufter upgrade to version 8 after some time i see in log a error r8169enp14s0: rtl_counters_cond == 1 (loop: 100, delay: 10) and the pve is offline.. with version 7...

edit your /etc/network/interfaces

das hoffe ich root@pve:~# pveversion -v proxmox-ve: 6.3-1 (running kernel: 5.4.78-2-pve) pve-manager: 6.3-3 (running version: 6.3-3/eee5f901) pve-kernel-5.4: 6.3-3 pve-kernel-helper: 6.3-3 pve-kernel-5.4.78-2-pve: 5.4.78-2 pve-kernel-5.4.78-1-pve: 5.4.78-1 pve-kernel-5.4.73-1-pve: 5.4.73-1...

ne nicht wirklich... so wirklich nix... pveproxy, pvedaemon, pve-cluster laufen alle komisch ist .. erstellen geht .. nur starten nicht und nur lxc und nur aus der gui.. in der console geht.. VM kann ich erstellen und starten in der gui.. also beschränkt es sich nur auf lxc und nur aus der gui

ich mach das was du willst mit glusterfs .. über 5 nodes..

ja ich weiss USV davor... egall jetzt ist es halt passiert nach restart werden alle mschienen egal ob vm oder lxc container neu gestartet die gui sehe ich auch und ich kann vm aus der gui anlgegen und starten lxc kann ich anlgegen aber nicht starten das kommt als Meldung.. aus der console...

bin dabei