i have those "spikes" for hours (it is not a spike anymore). i am running systemctl stop udisks2 via crontab every 10 minutes.
what is a real solution? why are udisks2 generating high cpu?
i am trying the same, and having the same issue. but i am using docker. docker itself is running on this lxc container, but not with minikube.
docker: Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused...
hey, thanks once again pve-efiboot-tool did it. works great.
now i have one small issue. during my tests with removing and exchanging drives i observed that the devices in the pool are used with sda / sdb3 / ... after failover and rebooting from the "2nd device" of a mirror-0-zpool. can this be...
using "bios" instead of uefi didn't change anything. proxmox installation iso fails during reboot in the same manner as described above. maybe a socket is defect? but than i should get errors during mem check, right?
thx a lot!
does that mean if i replace a drive with a new one i have to create the partitions manually and then run pve-efiboot-tool init, or simply run pve-efiboot-tool on the uninitialized disk?
it is a xeon e5 2430v2 and i'd expect that it fails before booting linux.
bios settings have been set to default as well several times.
however, the board has 6 slots with 3 channels (1cpu system). the rest should be possible:
The R320 supports a flexible memory configuration according to...
i have an issue with a dell r320 server. it works fine with proxmox, but as soon as i have more than 16gb of ram installed the system powers off during linux booting. doing a system check all memory checks are passed successfully.
this happens during booting proxmox installation-iso as well...
I have installed proxmox on a dell r320 with zfs raid-1.
this seems fine, and i am able to remove a drive and everything works fine. doing further tests it doesn't wo work to simply insert a blank drive and attach it to the zfs pool - boot partition is not synced in this case.
today i installed updates, and i guess that libz.so.1 caused trouble again:
libxcomp3:amd64 (2:220.127.116.11-3+deb10u2) wird eingerichtet ...
pve-kernel-helper (6.0-8) wird eingerichtet ...
tzdata (2019c-0+deb10u1) wird eingerichtet ...
Current default time zone: 'Europe/Berlin'
Local time is now...
I checked via lsof:
root@server:~# lsof /usr/local/lib/libz.so.1
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
sshd 1963 root mem REG 8,17 113264 2885827 /usr/local/lib/libz.so.1
sshd 19223 root mem REG 8,17 113264 2885827...