Recent content by mediaklan

  1. M

    syslog getting spammed with "notice: RRD update error"s

    Same here, but with the message being slightly different. Can you check if the error persists if you backup /var/lib/rrdcached/db/pve-vm-9.0/130 out of the way and restart rrdcached ? mv /var/lib/rrdcached/db/pve-vm-9.0/130{,.$(date +%Y%m%d)} In your case, it usually means your VM was slightly...
  2. M

    Opt-in Linux 6.8 Kernel for Proxmox VE 8 available on test & no-subscription

    My logs are spammed with this (kernel 6.8). I've stopped the service for now and see if Grafana will get angry with me.
  3. M

    restic as a proxmox disaster recovery tool ?

    Hi to you all ! I've tried restic before and didn't get very far with it, but now I want to try again because there was some points I've really liked about it (fast, reliable and relatively easy to manage). The issue is ... I'm not confident enough in my linux-fu skills to know exactly how I...
  4. M

    grub rescue : “error: symbol ‘grub_disk_native_sectors’ not found”

    In this order : - using ventoy to boot with proxmox latest ISO - choose "advanced mode" when asked then "rescue mode" - from there, the rescue mode boot into my proxmox server - update-grub - grub-install /dev/sda In my BIOS, I can choose and override the boot disk (not sure if I can call it...
  5. M

    grub rescue : “error: symbol ‘grub_disk_native_sectors’ not found”

    I had this feeling that I will not end up being the only one. Unbelievable how a tiny binary can f*ck a great running proxmox installation. Well, this is my fault, never had the motivation to learn more about grub/uefi/(etc) and have only a little knowledge about it all. Anyway, I got...
  6. M

    grub rescue : “error: symbol ‘grub_disk_native_sectors’ not found”

    A little update : this page from the wiki have been greatly helpful. Basically, I booted from the Proxmox 8.0.iso image and choose "rescue mode". There it magically ended up booting my proxmox machine without any kind of intervention from me (I have no idea how this works). Now I'm still not...
  7. M

    grub rescue : “error: symbol ‘grub_disk_native_sectors’ not found”

    Hello to you all, It seems I have messed up my proxmox machine with an apt update this morning. I think it was grub-pc or something like that, which asks during the update where grub was installed. Well, I think I didn't answered correctly. Anyway, here's where I am for now : - I end up in grub...
  8. M

    [SOLVED] Non-free firmware moved to its own component in the archive

    Indeed, the question was whether we would still be able to receive the non-free firmware updates without adding anything, which I also believe post #9 by @Philipp Hufnagl answered (I should also point out that I was a bit confused by the constant apt notification about the non-free split...
  9. M

    Provision VM from template using ansible.

    Thanks for sharing. This looks like a madness ... under control ^^.
  10. M

    Provision VM from template using ansible.

    I'm not using ansible for proxmox (yet) but while I was looking into it some time ago, I think I've seen what you're looking for in github.
  11. M

    [SOLVED] monitor enter suspend mode with kernel 6.2.16-4-pve

    Just when I was about to give up, it's solved. But I'm not too sure what was the effective solution. What I've done, in this order : # remove upower service (I think it's most likely the solution) apt remove upower # add this in my .bashrc (debian wiki : https://wiki.debian.org/Suspend) xset...
  12. M

    [SOLVED] monitor enter suspend mode with kernel 6.2.16-4-pve

    Hello everyone, I'm using proxmox as a workstation (xfce/openbox), so I have a display connected for various purposes. Since the latest kernel upgrade (6.2.16-4-pve), my monitor is entering suspend mode (after 10 min or so), and it's a behavior I would gladly prevent. What I tried so far ...
  13. M

    [SOLVED] Non-free firmware moved to its own component in the archive

    That is what I expected but I've checked my upgrade history again, and can't find where I was asked for sshd. I got the same files indicated by the proxmox doc like /etc/issue, lvm.conf plus : - /etc/logrotate.d/rsyslog - saslauthd # maybe this one could be related ? Still, that was...
  14. M

    [SOLVED] Non-free firmware moved to its own component in the archive

    Hi to you all ! Upgrade to proxmox 8 was successful, but i have some warnings I'm not sure to understand. This one from apt for example : I add this to my sources.list : but then apt complains like this : So I followed the debian doc, remove the line from my sources.list and created the file...
  15. M

    Proxmox Mystery Random Reboots

    @Nuke Bloodaxe Nope, I'm good with my rollback, thanks. That's 25 hours now running without a reboot. I (hopefully) think my case is closed. Maybe that will need to be adressed again when I switched back to the 6.2 kernel. Either way, thank you for the tip about the ram speed.