NEWS
Proxmox spinnt - brauche Hilfe - auch mit Unifi
-
@homoran
Teil 3:[Mon Apr 25 12:47:06 2022] cryptd: max_cpu_qlen set to 1000 [Mon Apr 25 12:47:06 2022] rc rc0: lirc_dev: driver ite-cir registered at minor = 0, raw IR receiver, raw IR transmitter [Mon Apr 25 12:47:06 2022] input: ITE8713 CIR transceiver as /devices/pnp0/00:02/rc/rc0/input3 [Mon Apr 25 12:47:06 2022] SSE version of gcm_enc/dec engaged. [Mon Apr 25 12:47:06 2022] pstore: Using crash dump compression: deflate [Mon Apr 25 12:47:06 2022] pstore: Registered efi as persistent store backend [Mon Apr 25 12:47:06 2022] cfg80211: Loading compiled-in X.509 certificates for regulatory database [Mon Apr 25 12:47:06 2022] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [Mon Apr 25 12:47:06 2022] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [Mon Apr 25 12:47:06 2022] cfg80211: failed to load regulatory.db [Mon Apr 25 12:47:06 2022] usbcore: registered new interface driver btusb [Mon Apr 25 12:47:06 2022] Bluetooth: hci0: read Intel version: 370810011003110e00 [Mon Apr 25 12:47:06 2022] bluetooth hci0: Direct firmware load for intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq failed with error -2 [Mon Apr 25 12:47:06 2022] Bluetooth: hci0: failed to open Intel firmware file: intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq (-2) [Mon Apr 25 12:47:06 2022] bluetooth hci0: Direct firmware load for intel/ibt-hw-37.8.bseq failed with error -2 [Mon Apr 25 12:47:06 2022] Bluetooth: hci0: failed to open default fw file: intel/ibt-hw-37.8.bseq [Mon Apr 25 12:47:06 2022] i915 0000:00:02.0: vgaarb: deactivate vga console [Mon Apr 25 12:47:06 2022] Intel(R) Wireless WiFi driver for Linux [Mon Apr 25 12:47:06 2022] iwlwifi 0000:02:00.0: enabling device (0000 -> 0002) [Mon Apr 25 12:47:06 2022] iwlwifi 0000:02:00.0: Found debug destination: EXTERNAL_DRAM [Mon Apr 25 12:47:06 2022] iwlwifi 0000:02:00.0: Found debug configuration: 0 [Mon Apr 25 12:47:06 2022] iwlwifi 0000:02:00.0: loaded firmware version 29.4063824552.0 7265D-29.ucode op_mode iwlmvm [Mon Apr 25 12:47:06 2022] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Mon Apr 25 12:47:06 2022] intel_rapl_common: Found RAPL domain package [Mon Apr 25 12:47:06 2022] intel_rapl_common: Found RAPL domain core [Mon Apr 25 12:47:06 2022] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band Wireless AC 3165, REV=0x210 [Mon Apr 25 12:47:06 2022] Adding 7340028k swap on /dev/mapper/pve-swap. Priority:-2 extents:1 across:7340028k SSFS [Mon Apr 25 12:47:06 2022] thermal thermal_zone1: failed to read out thermal zone (-61) [Mon Apr 25 12:47:06 2022] iwlwifi 0000:02:00.0: Applying debug destination EXTERNAL_DRAM [Mon Apr 25 12:47:06 2022] iwlwifi 0000:02:00.0: Allocated 0x00400000 bytes for firmware monitor. [Mon Apr 25 12:47:06 2022] iwlwifi 0000:02:00.0: base HW address: 98:54:1b:19:00:af [Mon Apr 25 12:47:06 2022] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs' [Mon Apr 25 12:47:06 2022] iwlwifi 0000:02:00.0 wlp2s0: renamed from wlan0 [Mon Apr 25 12:47:06 2022] [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0 [Mon Apr 25 12:47:06 2022] ACPI: video: Video Device [GFX0] (multi-head: yes rom: no post: no) [Mon Apr 25 12:47:06 2022] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input5 [Mon Apr 25 12:47:06 2022] snd_hda_intel 0000:00:1b.0: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) [Mon Apr 25 12:47:06 2022] i915 0000:00:02.0: [drm] Cannot find any crtc or sizes [Mon Apr 25 12:47:06 2022] i915 0000:00:02.0: [drm] Cannot find any crtc or sizes [Mon Apr 25 12:47:06 2022] i915 0000:00:02.0: [drm] Cannot find any crtc or sizes [Mon Apr 25 12:47:06 2022] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC283: line_outs=2 (0x1b/0x21/0x0/0x0/0x0) type:hp [Mon Apr 25 12:47:06 2022] snd_hda_codec_realtek hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [Mon Apr 25 12:47:06 2022] snd_hda_codec_realtek hdaudioC0D0: hp_outs=0 (0x0/0x0/0x0/0x0/0x0) [Mon Apr 25 12:47:06 2022] snd_hda_codec_realtek hdaudioC0D0: mono: mono_out=0x0 [Mon Apr 25 12:47:06 2022] snd_hda_codec_realtek hdaudioC0D0: dig-out=0x1e/0x0 [Mon Apr 25 12:47:06 2022] snd_hda_codec_realtek hdaudioC0D0: inputs: [Mon Apr 25 12:47:06 2022] snd_hda_codec_realtek hdaudioC0D0: Mic=0x19 [Mon Apr 25 12:47:07 2022] input: HDA Intel PCH Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input6 [Mon Apr 25 12:47:07 2022] input: HDA Intel PCH Headphone Front as /devices/pci0000:00/0000:00:1b.0/sound/card0/input7 [Mon Apr 25 12:47:07 2022] input: HDA Intel PCH Front Headphone Surround as /devices/pci0000:00/0000:00:1b.0/sound/card0/input8 [Mon Apr 25 12:47:07 2022] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9 [Mon Apr 25 12:47:07 2022] audit: type=1400 audit(1650883628.020:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/lxc-start" pid=576 comm="apparmor_parser" [Mon Apr 25 12:47:07 2022] audit: type=1400 audit(1650883628.024:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/chronyd" pid=573 comm="apparmor_parser" [Mon Apr 25 12:47:07 2022] audit: type=1400 audit(1650883628.028:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="tcpdump" pid=574 comm="apparmor_parser" [Mon Apr 25 12:47:07 2022] audit: type=1400 audit(1650883628.036:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=581 comm="apparmor_parser" [Mon Apr 25 12:47:07 2022] audit: type=1400 audit(1650883628.036:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=581 comm="apparmor_parser" [Mon Apr 25 12:47:07 2022] audit: type=1400 audit(1650883628.044:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=580 comm="apparmor_parser" [Mon Apr 25 12:47:07 2022] audit: type=1400 audit(1650883628.044:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=580 comm="apparmor_parser" [Mon Apr 25 12:47:07 2022] audit: type=1400 audit(1650883628.044:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=580 comm="apparmor_parser" [Mon Apr 25 12:47:07 2022] audit: type=1400 audit(1650883628.056:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lxc-container-default" pid=577 comm="apparmor_parser" [Mon Apr 25 12:47:07 2022] audit: type=1400 audit(1650883628.056:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lxc-container-default-cgns" pid=577 comm="apparmor_parser" [Mon Apr 25 12:47:07 2022] softdog: initialized. soft_noboot=0 soft_margin=60 sec soft_panic=0 (nowayout=0) [Mon Apr 25 12:47:07 2022] softdog: soft_reboot_cmd=<not set> soft_active_on_boot=0 [Mon Apr 25 12:47:08 2022] vmbr0: port 1(enp3s0) entered blocking state [Mon Apr 25 12:47:08 2022] vmbr0: port 1(enp3s0) entered disabled state [Mon Apr 25 12:47:08 2022] device enp3s0 entered promiscuous mode [Mon Apr 25 12:47:08 2022] Generic FE-GE Realtek PHY r8169-0-300:00: attached PHY driver (mii_bus:phy_addr=r8169-0-300:00, irq=MAC) [Mon Apr 25 12:47:08 2022] r8169 0000:03:00.0 enp3s0: Link is Down [Mon Apr 25 12:47:08 2022] vmbr0: port 1(enp3s0) entered blocking state [Mon Apr 25 12:47:08 2022] vmbr0: port 1(enp3s0) entered forwarding state [Mon Apr 25 12:47:09 2022] vmbr0: port 1(enp3s0) entered disabled state [Mon Apr 25 12:47:11 2022] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control rx/tx [Mon Apr 25 12:47:11 2022] vmbr0: port 1(enp3s0) entered blocking state [Mon Apr 25 12:47:11 2022] vmbr0: port 1(enp3s0) entered forwarding state [Mon Apr 25 12:47:11 2022] IPv6: ADDRCONF(NETDEV_CHANGE): vmbr0: link becomes ready [Mon Apr 25 12:47:12 2022] bpfilter: Loaded bpfilter_umh pid 906 [Mon Apr 25 12:47:12 2022] Started bpfilter [Mon Apr 25 12:47:27 2022] device tap100i0 entered promiscuous mode [Mon Apr 25 12:47:27 2022] fwbr100i0: port 1(fwln100i0) entered blocking state [Mon Apr 25 12:47:27 2022] fwbr100i0: port 1(fwln100i0) entered disabled state [Mon Apr 25 12:47:27 2022] device fwln100i0 entered promiscuous mode [Mon Apr 25 12:47:27 2022] fwbr100i0: port 1(fwln100i0) entered blocking state [Mon Apr 25 12:47:27 2022] fwbr100i0: port 1(fwln100i0) entered forwarding state [Mon Apr 25 12:47:27 2022] vmbr0: port 2(fwpr100p0) entered blocking state [Mon Apr 25 12:47:27 2022] vmbr0: port 2(fwpr100p0) entered disabled state [Mon Apr 25 12:47:27 2022] device fwpr100p0 entered promiscuous mode [Mon Apr 25 12:47:27 2022] vmbr0: port 2(fwpr100p0) entered blocking state [Mon Apr 25 12:47:27 2022] vmbr0: port 2(fwpr100p0) entered forwarding state [Mon Apr 25 12:47:27 2022] fwbr100i0: port 2(tap100i0) entered blocking state [Mon Apr 25 12:47:27 2022] fwbr100i0: port 2(tap100i0) entered disabled state [Mon Apr 25 12:47:27 2022] fwbr100i0: port 2(tap100i0) entered blocking state [Mon Apr 25 12:47:27 2022] fwbr100i0: port 2(tap100i0) entered forwarding state [Mon Apr 25 12:47:27 2022] ch341-uart ttyUSB0: ch341-uart converter now disconnected from ttyUSB0 [Mon Apr 25 12:47:27 2022] ch341 1-4:1.0: device disconnected [Mon Apr 25 12:47:33 2022] device tap101i0 entered promiscuous mode [Mon Apr 25 12:47:33 2022] fwbr101i0: port 1(fwln101i0) entered blocking state [Mon Apr 25 12:47:33 2022] fwbr101i0: port 1(fwln101i0) entered disabled state [Mon Apr 25 12:47:33 2022] device fwln101i0 entered promiscuous mode [Mon Apr 25 12:47:33 2022] fwbr101i0: port 1(fwln101i0) entered blocking state [Mon Apr 25 12:47:33 2022] fwbr101i0: port 1(fwln101i0) entered forwarding state [Mon Apr 25 12:47:33 2022] vmbr0: port 3(fwpr101p0) entered blocking state [Mon Apr 25 12:47:33 2022] vmbr0: port 3(fwpr101p0) entered disabled state [Mon Apr 25 12:47:33 2022] device fwpr101p0 entered promiscuous mode [Mon Apr 25 12:47:33 2022] vmbr0: port 3(fwpr101p0) entered blocking state [Mon Apr 25 12:47:33 2022] vmbr0: port 3(fwpr101p0) entered forwarding state [Mon Apr 25 12:47:33 2022] fwbr101i0: port 2(tap101i0) entered blocking state [Mon Apr 25 12:47:33 2022] fwbr101i0: port 2(tap101i0) entered disabled state [Mon Apr 25 12:47:33 2022] fwbr101i0: port 2(tap101i0) entered blocking state [Mon Apr 25 12:47:33 2022] fwbr101i0: port 2(tap101i0) entered forwarding state [Mon Apr 25 12:47:42 2022] usb 1-4: reset full-speed USB device number 2 using xhci_hcd [Mon Apr 25 12:47:49 2022] device-mapper: thin: 253:4: reached low water mark for data device: sending event. [Mon Apr 25 12:47:49 2022] device-mapper: thin: 253:4: switching pool to out-of-data-space (queue IO) mode [Mon Apr 25 12:48:50 2022] device-mapper: thin: 253:4: switching pool to out-of-data-space (error IO) mode
-
@homoran sagte in Proxmox spinnt - brauche Hilfe - auch mit Unifi:
Ich kann jetzt diese VM weder rebooten noch stoppen.
Per shell auch nicht?
qm unlock 123 qm stop 123
-
@homoran worauf laufen denn die beiden VMs? Also z.B LVM-Volumes, LVM-Thin etc? Nodeseitig evtl. Snapshots aktiv? Die Meldung "I/O-Error" innerhalb einer VM oder LXC kenne ich eigentlich nur vom Fall, dass z.B. ein LV bzw. Snapshot "vollgelaufen" ist... (zumindest wenn man defekte Platten ausschliessen kann)
-
@homoran sagte in Proxmox spinnt - brauche Hilfe - auch mit Unifi:
[Mon Apr 25 12:47:49 2022] device-mapper: thin: 253:4: reached low water mark for data device: sending event.
schau' mal, was
lsblk
sagt - da kannst du sehen, zu was "253:4" gehört...
-
-
@jleg wäre dann der Hinweis
Apr 25 12:47:49 2022] device-mapper: thin: 253:4: switching pool to out-of-data-space (queue IO) mode [Mon Apr 25 12:48:50 2022] device-mapper: thin: 253:4: switching pool to out-of-data-space (error IO) mode
-
@jleg sagte in Proxmox spinnt - brauche Hilfe - auch mit Unifi:
sagt - da kannst du sehen, zu was "253:4" gehört...
ich sicher nicht
root@pve-neu:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 223.6G 0 disk ├─sda1 8:1 0 1007K 0 part ├─sda2 8:2 0 512M 0 part /boot/efi └─sda3 8:3 0 223.1G 0 part ├─pve-swap 253:0 0 7G 0 lvm [SWAP] ├─pve-root 253:1 0 55.8G 0 lvm / ├─pve-data_tmeta 253:2 0 1.4G 0 lvm │ └─pve-data-tpool 253:4 0 141.4G 0 lvm │ ├─pve-data 253:5 0 141.4G 1 lvm │ ├─pve-vm--100--disk--0 253:6 0 140G 0 lvm │ └─pve-vm--101--disk--0 253:7 0 32G 0 lvm └─pve-data_tdata 253:3 0 141.4G 0 lvm └─pve-data-tpool 253:4 0 141.4G 0 lvm ├─pve-data 253:5 0 141.4G 1 lvm ├─pve-vm--100--disk--0 253:6 0 140G 0 lvm └─pve-vm--101--disk--0 253:7 0 32G 0 lvm
-
@homoran ja
-
@homoran jo, sind thin pools - und der 253:4 ist voll - was sagt denn
vgdisplay -v pve
-
@crunchip sieht nicht gut aus:
-
root@pve-neu:~# vgdisplay -v pve --- Volume group --- VG Name pve System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 15 VG Access read/write VG Status resizable MAX LV 0 Cur LV 5 Open LV 3 Max PV 0 Cur PV 1 Act PV 1 VG Size <223.07 GiB PE Size 4.00 MiB Total PE 57105 Alloc PE / Size 53010 / 207.07 GiB Free PE / Size 4095 / <16.00 GiB VG UUID QxE0vt-KnKS-Z92t-L53i-YOyT-4PEr-9THeBz --- Logical volume --- LV Path /dev/pve/swap LV Name swap VG Name pve LV UUID u0kopG-fi9N-sqEn-YgpO-u82L-mAQp-RHpd38 LV Write Access read/write LV Creation host, time proxmox, 2021-12-13 15:30:10 +0100 LV Status available # open 2 LV Size 7.00 GiB Current LE 1792 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:0 --- Logical volume --- LV Path /dev/pve/root LV Name root VG Name pve LV UUID k8bNxN-ss4P-V1vf-Zeqm-reIp-9cRj-B2AnfY LV Write Access read/write LV Creation host, time proxmox, 2021-12-13 15:30:10 +0100 LV Status available # open 1 LV Size 55.75 GiB Current LE 14272 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:1 --- Logical volume --- LV Name data VG Name pve LV UUID AP1yuy-r0H8-jsq0-rvy9-DBnu-K0TB-5Qkt0M LV Write Access read/write (activated read only) LV Creation host, time proxmox, 2021-12-13 15:30:15 +0100 LV Pool metadata data_tmeta LV Pool data data_tdata LV Status available # open 0 LV Size <141.43 GiB Allocated pool data 100.00% Allocated metadata 5.40% Current LE 36206 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:5 --- Logical volume --- LV Path /dev/pve/vm-100-disk-0 LV Name vm-100-disk-0 VG Name pve LV UUID yVqmMo-lQFx-zeIW-VpEB-aC52-FQR9-dbjNZI LV Write Access read/write LV Creation host, time pve-neu, 2021-12-13 17:44:06 +0100 LV Pool name data LV Status available # open 1 LV Size 140.00 GiB Mapped size 95.47% Current LE 35840 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:6 --- Logical volume --- LV Path /dev/pve/vm-101-disk-0 LV Name vm-101-disk-0 VG Name pve LV UUID RZsqpX-CwHp-Obe9-nQYE-78F3-Jva5-lYRlRY LV Write Access read/write LV Creation host, time pve-neu, 2021-12-13 18:05:41 +0100 LV Pool name data LV Status available # open 0 LV Size 32.00 GiB Mapped size 24.30% Current LE 8192 Segments 1 Allocation inherit Read ahead sectors auto - currently set to 256 Block device 253:7 --- Physical volumes --- PV Name /dev/sda3 PV UUID AY1yhR-LBud-ZdQO-hN5N-n05P-Yrhd-zjt1Ii PV Status allocatable Total PE / Free PE 57105 / 4095
-
@homoran ist doch gestoppt
-
@crunchip jepp gerade eben
und jetzt auch die ander
-
@crunchip jetzt habe ich auch beide wieder starten können....
101 hängt schon wieder -
@homoran tja, dein lvm-thin-metadata-Storage ist vollgelaufen. Gründe für sowas gibt's einige, wenn du keine Snapshots benutzt, sind's vielleicht zu kleine Chunk-Sizes (beim Einrichten gewählt) oder so...
Schnellste Abhilfe wäre, das tmeta-LV zu vergrössern - blöderweise ist deine Volumegroup (pve) aber auch schon bis fast zum Anschlag ausgereizt (ich würde da immer bissel Luft lassen), du hast nur noch 6GB zur Verfügung. Das könnte aber schonmal helfen, zumindest für ein paar Wochen oder so..
Hier steht der Aufruf zum Vergrössern: https://pve.proxmox.com/wiki/LVM2#Resize_metadata_pool -
@homoran mein handy hängt die ganze Zeit, kann nicht scrollen in dem Thread.
Aber wenn ich es richtig sehe ist deine VM 140Gb?
Und dein LVM ebenfalls -
Danke euch beiden - keine Panik - die habe ich.
@crunchip sagte in Proxmox spinnt - brauche Hilfe - auch mit Unifi:
Aber wenn ich es richtig sehe ist deine VM 140Gb?
Und dein LVM ebenfallspasst wahrscheinlich zu
@jleg sagte in Proxmox spinnt - brauche Hilfe - auch mit Unifi:
dein lvm-thin-metadata-Storage ist vollgelaufen.
und ich nutze keine Snapshots
Habe schon den nächsten NUC vorbereitet gehabt, der 5PPYH sollte nur den Neuaufbau des i3 überbrücken.
und wie das so ist dauert ein Provisorium zu lange -
@jleg sagte in Proxmox spinnt - brauche Hilfe - auch mit Unifi:
(ich würde da immer bissel Luft lassen), du hast nur noch 6GB zur Verfügung. Das könnte aber schonmal helfen, zumindest für ein paar Wochen oder so..
wenn ich wüsste wovon du redest würde ich das wohl auch
@jleg sagte in Proxmox spinnt - brauche Hilfe - auch mit Unifi:
du hast nur noch 6GB zur Verfügung. Das könnte aber schonmal helfen, zumindest für ein paar Wochen oder so..
reicht
@jleg sagte in Proxmox spinnt - brauche Hilfe - auch mit Unifi:
Hier steht der Aufruf zum Vergrössern: https://pve.proxmox.com/wiki/LVM2#Resize_metadata_pool
DANKE
sehe ich mir an -
@jleg sagte in Proxmox spinnt - brauche Hilfe - auch mit Unifi:
Hier steht der Aufruf zum Vergrössern
Könntest du so nett sein und das für mich übersetzen?
lvresize --poolmetadatasize +<size[M,G]> <VG>/<LVThin_pool>
-
@homoran müsste sowas wie hier sein:
lvresize --poolmetadatasize +5G pve/data