Search results

Hi, I have multiple CT using ZFS and for only one of them, taking a snapshots fail. The tasks never ends and I've to reboot the server to have the GUI working after. I can also add that doing the zfs snapshot command manually is well working. Task status is : stopped / unable to read tail. Here...

Hi, I have twice the same issue updating the kernel with 25 july release. I need to rewrite the grub each time I update the pve-kernel version. Am I the only to have this ?

Hi, I just wanted to repopen this thread. Today I performed an apt-get update && apt-get dist-upgrade During the process, everything went well and the kernel was updated from 4.15.17-13 to 4.15.17-14 . But after a reboot, I got the following issue with grub error compression algorithm inherit...

Thanks, this solved the issue Now the question, I never add one, just modified the first one, I have no idea why 3 threaa value has been updated during the apt-get dist-upgrade

Is it not this boot variable causing the issue? ENV not showing it

For increasing delay, what line should be changed from # If you change this file, run 'update-grub' afterwards to update # /boot/grub/grub.cfg. # For full documentation of the options in this file, see: # info -f grub -n 'Simple configuration' GRUB_DEFAULT=0 GRUB_TIMEOUT=5...

Ok, this is exactly what I used to generate the boot loader zpool import -R /mnt rpool mount -t proc /proc /mnt/proc mount --rbind /dev /mnt/dev mount --rbind /sys /mnt/sys # Enter chroot chroot /mnt /bin/bash source /etc/profile # Reinstall package dpkg --configure -a apt-get update &&...

Hi, Thanks but it doesnt change something, still the same error after a reboot. Is it the first time you listen of this?

Hi No this is hdd drive

Hi, 2 days ago, I perform an apt-get dist-upgrade to update to latest PVE kernel (4.15.17.13) and since I am not able to reboot the machine anymore I have the follozing error apparing in grub ---------- error: attempt to read or write outside of disk "hd1" loading initial amdisk error: you need...

I think I've found the issue. Can anyone from proxmox can confirm me this cannot work like this: cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network...

See here https://forum.proxmox.com/threads/port-forwarding-on-5-2-2-does-not-work-as-5-1-36.44535 Ps another note about OVH and Proxmox. Proxmox over zfs use 0.7 version. In case of failure, OVH give you the ability to restart on a rewcue that has a 0.6 of zfs. The issue is if you enabled of...

Ps maybe I just wrote on bad thread on this forum

Ive found the issue. OVH customized the installation and they put a /etc/systemd/network/50-* files that mount the main ip on the eth0. This is conflicting with the vmbr0 and this is why the routing table get strange. Removing this file seems to be ok. Also in /etc/udev/rules.d/70-per, they...

Hi have the same issue https://forum.proxmox.com/threads/proxmox-5-2-and-host-ping-connection-lost.44473/ On my case the 2 interface etho0 and vmbr0 get the ip mounted, and for so the route table looks like this. And same thing, if a remove all eth0 route line, I have the network without issue

HI I have the same issue with a PVE 5.2 Fresh install. How this was solved in your case ? Thanks

Hi I have the exact same issue, could you le me know has this has been resolved ? Thanks

With debian 9, I have an issue where eth0 (or other) and vmbr0 get the IP assigned. This is what is troubling the routing table 2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master vmbr0 state UP group default qlen 1000 link/ether 08:60:6e:e5:c0:47 brd...

Jun 14 16:02:24 proxmox systemd[1]: Starting Raise network interfaces... Jun 14 16:02:25 proxmox ifup[1926]: interface dummy0 does not exist! Jun 14 16:02:25 proxmox ifup[1926]: Waiting for vmbr1 to get ready (MAXWAIT is 2 seconds). Jun 14 16:02:25 proxmox ifup[1926]: Waiting for vmbr0 to get...

root@proxmox:~# pveversion -v proxmox-ve: 5.2-2 (running kernel: 4.15.17-3-pve) pve-manager: 5.2-2 (running version: 5.2-2/b1d1c7f4) pve-kernel-4.15: 5.2-3 pve-kernel-4.15.17-3-pve: 4.15.17-12 corosync: 2.4.2-pve5 criu: 2.11.1-1~bpo90 glusterfs-client: 3.8.8-1 ksm-control-daemon: 1.2-2...