Recent content by astrakid

oh man... i guess it was a reboot that i missed after changing ipv4_forward in sysctl.conf to 1 - or just do a sysctl -p... however it works now

14 minutes ago hi, after a total outage of my server i recovered mostly everything. one step is missing, and i am sure it is the configuration on my hypervisor. i am running a single server system with proxmox. in a virtual machine pfsense is doing all the stuff (simple firewalling, dhcp, dns...

ah cool. first question after a quick look: i am running on ext4. would that work, too (clearly i wouldn't perform the zfs steps)?

hi, i have a proxmox server installed years ago and upgraded from 4.x up to 7.3 currently. the server was installed in legacy bios mode. firmware upgrades are not supported in this mode, so i would like to migrate to uefi. it is a single node installation (home server) with a couple of VMs on...

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? regards, andre

you have to clear cache or reload page with strg+f5 (chrome and firefox). then it should work again.

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. error message: stderr: docker: Error response from daemon: OCI runtime create failed: container_linux.go:349: starting container process caused...

and thanks once again! set ZPOOL_IMPORT_PATH in /etc/default/zfs to /dev/disk/by.id and it works as i like!

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...

nevertheless thx a lot for all your effort.

Windows crashes as well...

yes, good hint. i have the latest win10 iso downloaded some days ago. so i will check that.

hi, 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?

interesting, didn't find something like that. will check running bios only. btw: using the "faulty ram" is working without any issue, as long as there are only 16GB in total in use.

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? regards, andre