Search results

ok i resolved my problem with this procedure, this is for an OVH server with 2 disk SSD in soft RAID with LVM partition ! start your server in rescue mode (rescue64-pro) mount /dev/md126 /mnt mount -o bind /proc /mnt/proc mount -o bind /sys /mnt/sys mount -o bind /dev /mnt/dev mount...

no, this is after last apt upgrade (proxmox 7.3-4): Found linux image: /boot/vmlinuz-5.15.83-1-pve Found initrd image: /boot/initrd.img-5.15.83-1-pve Found linux image: /boot/vmlinuz-5.15.64-1-pve Found initrd image: /boot/initrd.img-5.15.64-1-pve Found linux image: /boot/vmlinuz-5.15.39-3-pve...

Hello, same problem after this, message after reboot : grub_disk_native_sectors not found

Hello, thanks, but i have this message when i start "upgrade-grub" Warning: os-prober will not be executed to detect other bootable partitions. Systems on them will not be added to the GRUB boot configuration. Check GRUB_DISABLE_OS_PROBER documentation entry. done

Hello I have a cluster of 3 Proxmox servers at OVH, on one of the servers I did an "apt upgrade" and I got this message during the upgrade: Warning: os-prober will not be executed to detect other bootable partitions. Systems on them will not be added to the GRUB boot configuration. Check...

great !!! it's ok thank you so much @wbumiller have a good day

i try but i have this error message when i want to add my key The clients relying party origin does not match our servers information Thanks

hi @t.lamprecht I had to set the "Require TFA" parameter in "Realms" to "none" and there I can choose between "totp" and "webauthn" when connecting. it works well ! :) With the "OATH/TOTP" parameter it does not work... On the other hand, on a cluster, the "Webauthn Settings" parameter...

Hi, So clearly webauthn is not working?

The solution is simple, remove these two parameters from "GRUB_CMDLINE_LINUX_DEFAULT" in "/etc/default/grub" biosdevname=0 net.ifnames=0 thhen run an "update_grub2" and edit the "/etc/network/interfaces" file to replace "ethX" with "enoX" I am closing this thread thank you

Hi @spirit I think I know where it came from, when updating from 6 to 7 I was asked if I wanted to replace the "/etc/default/grub" file with the new version or keep the current version, and like I had no info on the subject, I replaced the current version. It seems to me that in this file we...

Hello, Following the update from Proxmox 6 to 7, I followed a whole bunch of procedures and advice, but I can't get the network cards to work, I have error messages constantly scrolling (see all in down) and even by modifying the config of the interfaces to the bare minimum, like a first...

Hi I reboot the "secondary" host after apt upgrade and the "primary" host reboot too !! why ? (Quorum with 2 hosts only with drbd) look attach-file for proxmox version of "primary" host before apt upgrade, and "secondary" after apt upgrade. Thanks

Ok I found it! The update crashed the configuration of drbdmanage. replace: storage-plugin = drbdmanage.storage.lvm_thinlv.LvmThinLv by: storage-plugin = drbdmanage.storage.lvm.Lvm Modify config with Choose a storage plugin, and insert it in the config like

Hi, after upgrade proxmox with the latest 4.3, I have an error message when starting a new VM : (the VMs created before the update works fine) kvm: -drive file=/dev/drbd/by-res/vm-502-disk-1/0,if=none,id=drive-virtio0,cache=writethrough,format=raw,aio=threads,detect-zeroes=on: Could not open...

hi and what is your solution please ! :) Thanks

ok thank you @wosp i change the ip and now the corosync in second node start, but... :-) i have again this error in syslog: and the result of "pvecm status" : server 1: server 2 (new node): thank you for your help

and how to change the IP address to listen? Thank you

and since my backups on the first server crashes !! I confess that I am a little tired of proxmox 4, I only have problems with respect to the prior release! I find it extremely unstable !!!

I followed the procedure described here: on the first server that is in production for a while and that has never been a cluster, I launched this command: the result of "pvecm status" : on the new second server i launched this command: and I had the errors mentioned above. the content...