teqqy
Enthusiast
Betreibt jemand sein Proxmox Server schon über einen längeren Zeitraum (1 Jahr und länger) auf einem USB-Stick oder SATA DOM? Wenn ja auf welchem?
Follow along with the video below to see how to install our site as a web app on your home screen.
Anmerkung: this_feature_currently_requires_accessing_site_using_safari
arch: amd64
cores: 1
hostname: openhab2
memory: 786
net0: name=eth0,bridge=vmbr0,hwaddr=1A:E3:4E:A1:E4:67,ip=dhcp,type=veth
ostype: debian
rootfs: LVM-thin:vm-102-disk-1,size=3G
swap: 256
Mar 27 09:15:23 proxmox systemd[1]: Starting PVE LXC Container: 102...
Mar 27 09:16:53 proxmox systemd[1]: pve-container@102.service: Start operation timed out. Terminating.
Mar 27 09:16:53 proxmox systemd[1]: Failed to start PVE LXC Container: 102.
Mar 27 09:16:53 proxmox systemd[1]: pve-container@102.service: Unit entered failed state.
Mar 27 09:16:53 proxmox systemd[1]: pve-container@102.service: Failed with result 'timeout'.
Mar 27 09:16:53 proxmox pve-guests[5045]: command 'systemctl start pve-container@102' failed: exit code 1
Mar 27 09:16:54 proxmox pvesh[2494]: Starting CT 102 failed: command 'systemctl start pve-container@102' failed: exit code 1
Mar 27 09:17:39 proxmox systemd-udevd[7782]: Could not generate persistent MAC address for veth102i0: No such file or directory
Mar 27 09:17:39 proxmox ovs-vsctl: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port veth102i0
Mar 27 09:17:40 proxmox ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named veth102i0
Mar 27 09:17:40 proxmox ovs-vsctl: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port fwln102i0
Mar 27 09:17:40 proxmox ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named fwln102i0
Mar 27 09:17:40 proxmox pvestatd[2374]: unable to get PID for CT 102 (not running?)
Mar 27 09:17:41 proxmox ovs-vsctl: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port fwln102i0
Mar 27 09:17:41 proxmox ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named fwln102i0
Mar 27 09:17:41 proxmox ovs-vsctl: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port veth102i0
Mar 27 09:17:41 proxmox ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named veth102i0
Mar 29 18:56:08 proxmox pvesh[2558]: Starting CT 104
Mar 29 18:56:08 proxmox pve-guests[2572]: <root@pam> starting task UPID:proxmox:0000114D:00003CA8:5ABD1AA8:vzstart:104:root@pam:
Mar 29 18:56:08 proxmox pve-guests[4429]: starting CT 104: UPID:proxmox:0000114D:00003CA8:5ABD1AA8:vzstart:104:root@pam:
Mar 29 18:56:08 proxmox systemd[1]: Starting PVE LXC Container: 104...
Mar 29 18:56:08 proxmox ovs-vsctl: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port veth108i0
Mar 29 18:56:08 proxmox ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named veth108i0
Mar 29 18:56:08 proxmox ovs-vsctl: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port fwln108i0
Mar 29 18:56:08 proxmox ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named fwln108i0
Mar 29 18:56:08 proxmox kernel: [ 155.349538] eth0: renamed from vethJ0BWK1
Mar 29 18:56:09 proxmox pvestatd[2449]: unable to get PID for CT 108 (not running?)
Mar 29 18:56:09 proxmox pvestatd[2449]: status update time (92.127 seconds)
Mar 29 18:56:10 proxmox ovs-vsctl: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port fwln108i0
Mar 29 18:56:10 proxmox ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named fwln108i0
Mar 29 18:56:10 proxmox ovs-vsctl: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port veth108i0
Mar 29 18:56:10 proxmox ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named veth108i0
Mar 29 18:57:38 proxmox systemd[1]: pve-container@104.service: Start operation timed out. Terminating.
Mar 29 18:57:38 proxmox systemd[1]: Failed to start PVE LXC Container: 104.
Mar 29 18:57:38 proxmox systemd[1]: pve-container@104.service: Unit entered failed state.
Mar 29 18:57:38 proxmox systemd[1]: pve-container@104.service: Failed with result 'timeout'.
Mar 29 18:57:38 proxmox pve-guests[4429]: command 'systemctl start pve-container@104' failed: exit code 1
Mar 29 18:57:39 proxmox pvesh[2558]: Starting CT 104 failed: command 'systemctl start pve-container@104' failed: exit code 1
Mar 29 18:57:39 proxmox pvesh[2558]: Starting CT 101
Mar 29 18:57:39 proxmox pve-guests[4871]: starting CT 101: UPID:proxmox:00001307:0000603C:5ABD1B03:vzstart:101:root@pam:
Mar 29 18:57:39 proxmox pve-guests[2572]: <root@pam> starting task UPID:proxmox:00001307:0000603C:5ABD1B03:vzstart:101:root@pam:
Mar 29 18:57:39 proxmox systemd[1]: Starting PVE LXC Container: 101...
Mar 29 18:58:25 proxmox systemd-udevd[4927]: Could not generate persistent MAC address for veth104i0: No such file or directory
Mar 29 18:58:25 proxmox systemd-udevd[4926]: Could not generate persistent MAC address for veth074IYP: No such file or directory
Mar 29 18:58:25 proxmox systemd-udevd[4950]: Could not generate persistent MAC address for vethWG2C73: No such file or directory
Mar 29 18:58:26 proxmox ovs-vsctl: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port veth104i0
Mar 29 18:58:26 proxmox ovs-vsctl: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port veth101i0
Mar 29 18:58:26 proxmox ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named veth104i0
Mar 29 18:58:26 proxmox ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named veth101i0
Mar 29 18:58:26 proxmox ovs-vsctl: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port fwln104i0
Mar 29 18:58:26 proxmox ovs-vsctl: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl del-port fwln101i0
Mar 29 18:58:26 proxmox ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named fwln104i0
Mar 29 18:58:26 proxmox ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named fwln101i0
Mar 29 18:58:26 proxmox kernel: [ 292.471258] vmbr0: port 3(veth104i0) entered blocking state
Mar 29 18:58:26 proxmox kernel: [ 292.471262] vmbr0: port 3(veth104i0) entered disabled state
Mar 29 18:58:26 proxmox kernel: [ 292.471357] device veth104i0 entered promiscuous mode
Mar 29 18:58:26 proxmox kernel: [ 292.473542] vmbr0: port 4(veth101i0) entered blocking state
Mar 29 18:58:26 proxmox kernel: [ 292.473546] vmbr0: port 4(veth101i0) entered disabled state
Mar 29 18:58:26 proxmox kernel: [ 292.473632] device veth101i0 entered promiscuous mode
Mar 29 18:58:26 proxmox kernel: [ 292.473693] vmbr0: port 4(veth101i0) entered blocking state
Mar 29 18:58:26 proxmox kernel: [ 292.473696] vmbr0: port 4(veth101i0) entered forwarding state
Mar 29 18:58:26 proxmox kernel: [ 292.611183] eth0: renamed from vethWG2C73
Mar 29 18:58:27 proxmox systemd[1]: Started PVE LXC Container: 101.
Mar 29 18:58:27 proxmox pvestatd[2449]: unable to get PID for CT 104 (not running?)
PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU COMMAND
11 root 155 ki31 0K 32K RUN 0 56.1H 76.95% [idle{idle: cpu0}]
11 root 155 ki31 0K 32K CPU1 1 56.1H 73.00% [idle{idle: cpu1}]
12 root -92 - 0K 352K WAIT 1 15:28 25.98% [intr{irq258: virtio_pci1}]
12 root -92 - 0K 352K WAIT 0 11:20 18.99% [intr{irq261: virtio_pci2}]
Zur Info: der Bug in zfs 0.7.7 wurde bei Proxmox schon vor Release ausgemerzt.
Der -a muss aber vermutlich neu installiert werden, weil auf dem SAS-Controller die falsche Firmware ist (IR statt IT).
Kommt darauf an, ob ihr RAID-Funktionalitäten der IR-Firmware nutzt. Wenn nicht, sollte nach der Firmware-Anpassung alles wie gehabt funktionieren. Ich habe kürzlich auch die Firmware meines LSI SAS3008 von IR zu IT geflasht. An dem Controller wird ein RAID-Z2 (ZFS 8x4TB) betrieben. Nach der Änderung der Firmware lief alles wie vorher, da ich die RAID-Funktionen der IR-Firmware für mein ZFS vorher auch schon nicht genutzt habe (macht ja auch keinen Sinn).
Gruß Hoppel
ein OMV Update ganz gerne mal den ZFS Treiber zerschießt. OMV mag ja auch Bind-Mounts nicht (wird in KVM ja so oder so nicht unterstützt - oder?) und Docker (für Plex bspw.) würde ich auf der KVM auch gerne laufen lassen. Die (meiner Meinung nach) beste Möglichkeit wäre:
Hat FreeNAS unter Proxmox nicht massive Performanceprobleme? Sie waren zumindest vor einem Jahr noch sehr akut. Ich weiß nicht ob das gelöst wurde.