Search results

These 2 packages seam to be linked to my problem but I don't know what to do :( dpkg -C The following packages have been unpacked but not yet configured. They must be configured using dpkg --configure or the configure menu option in dselect for them to work: pve-kernel-5.13 Latest Proxmox...

So I have to admit up front.. I'm a newbie with linux... I tried to update my kernel with apt update && apt install pve-kernel-5.15 Everything went fine and I rebooted but now when I try to update I always get that issue : apt-get dist-upgrade Reading package lists... Done Building dependency...

I'm having the exact same results with apt dist-upgrade and apt full-upgrade

Please excuse my low level question but I'm still a newbie with linux... I've updated the kernel running :apt update && apt install pve-kernel-5.15 after a reboot I see that I'm running the correct kernel : pveversion pve-manager/7.1-10/6ddebafe (running kernel: 5.15.12-1-pve) But now I have...

Dunno if you guys can help me but it seems like I have a similar issue.. I’m not super qualified with linux and I hope someone here can help me since my system randomly reboot from time to time (ie every 3-4 days) and I’m clueless… I had Kdump installed in order to try to understand what is...

So I got my first reboot/crash since I installed kdump. I can see the dmesg log and the dumpfile I don't know how to read the dump itself... I was wondering if someone here could help troubleshoot based on these files content ? /var/crash/202112250917/dmesg.202112250917 in attachment

If I may ask, where did you changed the crashkernel to 512M ? Is it like this : /etc/kernel/cmdline: root=ZFS=rpool/ROOT/pve-1 boot=zfs nmi_watchdog=1 crashkernel=384M-:512M EDIT1 : Or should it be like this to fit all ram possibilities ? root=ZFS=rpool/ROOT/pve-1 boot=zfs nmi_watchdog=1...

I'm glad that you catch it before I test :)

after adding KDUMP_INITRD=/var/lib/kdump/initrd.img and running kdump-config load I got : kdump-config load Creating symlink /var/lib/kdump/vmlinuz. kdump-tools: Generating /var/lib/kdump/initrd.img-5.13.19-1-pve mkinitramfs: failed to determine device for / mkinitramfs: workaround is...

kdump-config status Invalid symlink : /var/lib/kdump/initrd.img ... failed! current state : ready to kdump kdump-config load Cannot change symbolic links when kdump is loaded ... failed! kdump-config show DUMP_MODE: kdump USE_KDUMP: 1 KDUMP_COREDIR: /var/crash crashkernel addr...

If I try to enable : KDUMP_INITRD=/var/lib/kdump/initrd.img in the file /etc/default/kdump-tools I get this error after rebooting when running kdump-config status : Invalid symlink : /var/lib/kdump/initrd.img ... failed! current state : Not ready to kdump the file /var/lib/kdump/initrd.img...

I tried to edit as follow : /etc/kernel/cmdline: root=ZFS=rpool/ROOT/pve-1 boot=zfs nmi_watchdog=1 crashkernel=384M-:256M Then run pve-efiboot-tool refresh and reboot now kdump seems to run : root@pve:~# kdump-config show DUMP_MODE: kdump USE_KDUMP: 1 KDUMP_COREDIR: /var/crash...

you are right, I do run ZFS on the filesystem with UEFI. right now, the files contains : /etc/kernel/cmdline: root=ZFS=rpool/ROOT/pve-1 boot=zfs /etc/default/grub: GRUB_DEFAULT=0 GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR="Proxmox Virtual Environment" GRUB_CMDLINE_LINUX_DEFAULT="quiet crashkernel=128M"...

ok so I was able to reconfigure it but now it does not seem to be active : kdump-config status no crashkernel= parameter in the kernel cmdline ... failed! Invalid symlink : /var/lib/kdump/initrd.img ... failed! Invalid symlink : /var/lib/kdump/vmlinuz ... failed! current state : Not ready to...

I'm having an issue where proxmox will crash from time to time.. Not being a linux specialist anyhow, I came accross this post mentioning how to enable kdump: https://forum.proxmox.com/threads/random-proxmox-server-hang-no-vms-no-web-gui.58823/ # apt install kdump-tools Select no for kexec...

Nah... I don't think so... these are for performance mon aren't they ? Have you ever seen Esx alerts ?

Correct. But I really hope we could have a bit more control on the types of alerts, including global system status, temperature, cpus, vm reboots, etc... I'm just surprised that is not implemented out of the box like it is with Esx. Is this something Proxmox is working on ?

One of the reason why I still use TrueNas to manage my disks with a passthrough in Proxmox is because if there is a disk failure or anything, I can easily get an alert by email. I was wondering if there is any alternative directly in Proxmox in order to customize or at least define what kind of...

Blacklisting mpt3sas ended up working for me so far since my system didn't crash / reboot for the last 12 hours... Surprising I didn't had to do so with v6. echo 'blacklist mpt3sas' >> /etc/modprobe.d/mpt3sas.conf

I read somewhere that it might be related to iommu but I don't understand anything about or don't know what I could try but here is how iommu_groups are splitted : find /sys/kernel/iommu_groups/ -type l /sys/kernel/iommu_groups/17/devices/0000:05:00.0...