Search results

Cool, thx, worked :-) thx

bridge_hw option got ignored... even after reboot, got a random mac on the brige...

Got a remote IP KVM, host booted fine, but do not have network. NIC still named enp3s0 removed the bridge and gave enp3s0 my first IP, worked... Guess it's related tho the mac address thing. Need to read a little bit more doku

Anyone got this working with 7.0 ? Just reinstalled it, it's also booting fine in the rescue QUEMU, but its not reachable after reboot, cant even ping it. 6.4 with the same network settings worked fine.

Ok fogett it :) IP-Forwarding was not enabled (I thought it was enabled by default in proxmox ;-) ) an simple: sysctl -w net.ipv4.ip_forward=1 solved it

Hi, Since my new ISP dose not support yet IPv6, I need to setup my Hetzner Proxmox server with an IPv4. I followed the Proxmox wiki and the Hetzner wiki (https://wiki.hetzner.de/index.php/Proxmox_VE) but I'm not able to ping the vm or the outside world from the Internet. Ping from the host to...

what is not working? I just installed the host right now, no problems so far.

actually I like the new formart :-) first time I heared from this, but the pro arguments are mutch bigger than the cons^^ Admins need to be forced some times ;-)

Just a quick note: After I installed 5.0 ISO, I noticed, that the naming for networkadapters changed to "Predictable Interface Names" I dont know if this is normal for the latest ISO but if your interface is named like mine: "enp2s0" root@hostname:/etc/apt# ip link show 1: lo...

It's now working even with 5.0. I used that flag before but didn't worked. Properly they fixed it now

Anyone tried to install 5.0 with this? I'm running into an issue: command 'chroot /rpool/ROOT/pve-1 dpkg --force-confold --configure -a' failed with exit code 1 at /usr/bin/proxmoxinstall line 385 Edit: installing 4.4 on the same machine and upgrading to 5.0 afterwards, works with no...

Thats normal. iptabels rules are lost every reboot by default. If you want to keep it: https://www.thomas-krenn.com/en/wiki/Saving_Iptables_Firewall_Rules_Permanently

Very useful, I have a spare EX41 and Installed it like this 5 min ago, THX :-)

Iptabels should work at any time. Im using this with 4 different hosts and its working even with 5.0 Beta

For those who are interested: I got finally the root cause! My Adaptec 72405 (24 port SAS controller), which I got used from Ebay, was set manually to: SGPIO backplane mode. I switched it to "Automatic" mode (Default) and now the backplane runs with the IBPI protocol. Now my pools are healthy...

Same problem here. A LARA is the best solution, its free for 3 hours (additional 3 hours cost only 10€) you just need to provide them an FTP or HTTP link to the Proxmox .iso and they will burn it to a CD / USB drive. If they want to charge you (they told me it will cost 59€) show them this...

But do you know why ZFS blocked the I/O while the drive was healthy and recognized by the OS? I/O errors are bad enough, but when you can't clear them, because ZFS is blocking the drive, its double bad... I didn't do anything else than a long SMART test and it worked...

Ok thats random... After an long SMART test: where no errors are found, I'm able to clear the errors with: after that ZFS starts to scrub the pool and found 2 errors on metadata (and repaired them) Now everything looks healthy and I can boot my VM again. Very random... If anyone knows...

so everything looks normal, except that ZFS is blocking my pool. And as I said, all other file systems are working normally. without any I/O errors or data lose