Search results

After a regular update of the node the pinning is working again

Since this host is a cephnode, I can't do that

Yeah, both boot drives have the same default value set

Did that, boots into the new kernel still not using efi root@proxmox3-ng:~# cat /mnt/boot/grub/grub.cfg | grep default # from /etc/grub.d and settings from /etc/default/grub set default="${next_entry}" set...

They seem correct to me root@proxmox3-ng:~# ls -lha /dev/disk/by-uuid lrwxrwxrwx 1 root root 10 Jun 4 15:52 3C18-FADA -> ../../sda2 lrwxrwxrwx 1 root root 10 Jun 4 15:52 3CD7-1A85 -> ../../sdb2 root@proxmox3-ng:~# proxmox-boot-tool status 3C18-FADA is configured with: grub (versions...

update-initramfs -u proxmox-boot-tool reinit proxmox-boot-tool refresh Still booting into the unpinned kernel :/

Sadly not. Also tried unpinning, rebooting and pinning again. That didn't work either.

Nothing out of the ordinary root@proxmox3-ng:~# proxmox-boot-tool status Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount namespace.. System currently booted with legacy bios 3C18-FADA is configured with: grub (versions: 6.5.13-5-pve, 6.8.4-2-pve) 3CD7-1A85 is configured with...

Booting manually into the older kernel with grub->advanced works, so it has to be a problem with the proxmox-boot-tool

I got one node which pinning has no effect on. Problem is that this node is affected by the 6.8 crashes. I already tried the steps outlined in https://forum.proxmox.com/threads/unable-to-pin-kernel.111785/ but even the reinit doesn't make a difference. root@proxmox3-ng:~# uname -a Linux...

Hey, I need to replace the boot disks from my node. I know of the normal way described here but since sgdisk -R simply copies the partitions the main partition size wouldn't match the new diskspace. Is there a recommended way of increasing the size afterwards? Best regatds Ray_

Adding my 2 cents; I had to come up with a solution yesterday for our UPS emergency shutdown logic. I am using 2 scripts, one shutdown & one startup Shutdown script (read the comments!): #!/bin/bash # This script is to be run only on one (main) node. #systemctl stop pve-ha-lrm pve-ha-crm ->...

Hey, since Win 2012 Servers, Microsoft supports creating clones from a Domain Controller. (New-ADDCCloneConfig) However I could only find information about this on Hyper-V and ESXi. Does Proxmox/KVM support this feature aswell? I only found this old thread which doesn't have an answer...

If anyone else has a similar problem: 1. Check if the MTU to your storage is correct. In my case, Proxmox used 1500 and the storage used 1300. I changed everything to Jumboframed (9000 mtu) 2. Cachemode of Virtual Disks. I had writeback active on most of my VMs and that caused high IO-Delay when...

On the host, that's why it's affecting all VMs. I just set up my second server and it has the same Problem. The difference here: no multipathing, only one regular iSCSI connection.

Hey, over the weekend I brought our 2nd server online to redo the first one. I moved all VMs/CTs to the 2nd server and deleted the first since everything seemed fine. However when even the slightest IO operation occurs (e.g. opening a browser on a server) the IO delay skyrockets up to 90+%...

Hey, I have a VM with 3 disks. The disks are distributed over 3 different storages. When I select "Restore" in the Backup tab, I can only restore to one storage. Is it possible to select where each disk is supposed to be restored? (Same with moving to another node) Sincerely Ray_

Hey, I have a cluster of 3 nodes. One is booting via iSCSI which is kind of unstable. That's why I want to move the whole boot partition to local disks formatted with ZFS. No VMs are directly on this partition, only isos. My current plan is to migrate all VMs/CTs to the other 2 nodes and...

The data center technician scanned the whole system including hard drives and found no faulty parts.

Since I host this instance in a datacenter, I contacted their support. Let's see what comes from this. I am currently running the 5.13 kernel. Do you think an update to 5.15 would help? Had to do this for my PVEs since 5.13 plays badly with iSCSI boot.