Search results

  1. T

    Scheduled Backups Didn't Run (After 8.2.5 upgrade)

    Hi @jshuf Thanks for the hint - I was going to recreate my job myself as it didn't run again last night (to be clear, I didn't expect it would) I have recreated it and restarted the scheduler. Thanks for your post.
  2. T

    USB Drive mount a very rare issue

    What does dmesg say when you connect them to your device?
  3. T

    One on One help needed

    Hi Saxophone. If you are not even sure how to setup a ceph storage cluster and it's causing you confusion, I really would not recommend using ceph for storage of your personal stuff just yet. It's wonderful, it really is, but if you're not careful with it you'll put your lifes work on it...
  4. T

    Scheduled Backups Didn't Run (After 8.2.5 upgrade)

    Thanks MrJosh appreciate you commenting - good to know it's not happening to just me. Hopefully a small error that can be fixed quickly. Cheers!
  5. T

    Scheduled Backups Didn't Run (After 8.2.5 upgrade)

    Replying to myself, but I have just found this in syslog. Sadly I don't really know what it means nor how to fix it. 2024-09-20T01:00:06.896391+12:00 max pvescheduler[3248904]: 400 Parameter verification failed.#012job-id: invalid format - invalid configuration ID '5e8548a1be291e6b716...
  6. T

    Scheduled Backups Didn't Run (After 8.2.5 upgrade)

    Platform: Standalone Proxmox 8.2.5 using only the community (Free) repo: root@max:/var/log# pveversion pve-manager/8.2.5/12c0a59769080547 (running kernel: 6.8.12-1-pve) I got an alert this morning that my backups of my Proxmox guests were older than 24 hours. Given that I have a job that runs...
  7. T

    Upgrading PVE Tries to Remove proxmox-ve package

    Interesting. I just apt-get update && apt-get dist-ugprade my Proxmox 7.2 install and on reboot had exactly the same issue.
  8. T

    Sudden Grub Error on update-grub

    Thank you so much for your followup. It puts my mind at ease that I've done the right thing and, while I don't plan to update to 8.0 just yet, when I get around to it it's good to know the bug is fixed there. Really appreciate your detailed answer with pointers - thank you. Tim
  9. T

    Sudden Grub Error on update-grub

    hmm ok I seem to have fixed this by the "update something on the lvm" thing, so I just created a new VM with a 1G disk attached to that LVM and it seems to have fixed it.
  10. T

    Sudden Grub Error on update-grub

    Hi, I'm still runing Proxmox 7.4 - I haven't bitten the bullet for an 8 upgrade yet. This morning I did an apt-get update / dist-upgrade (I am using the free repo) and I got a new kernel version: Log started: 2023-07-31 10:45:04 (Reading database ... ^M(Reading database ... 5%^M(Reading...
  11. T

    Proxmox VE 7.1 released!

    This appears related to all the problems people are seeing. It's not the kernel it's the qemu version (6.1)
  12. T

    Do I need lynx installed?

    Yes I'm familar with it (though I prefer links) I just wondered if my hypervisor needed it :) Which it doesn't. Thanks very much for the replies! Tim
  13. T

    Do I need lynx installed?

    A few years ago I installed Proxmox from an ISO, I think back at version 5. I'm currently running version 6 and I see lynx (and lynx-common) want an update. I've just apt purge'd them - I can't see why my Hypervisor needs lynx. I'm just posting this to ask if that's OK - There's not some...
  14. T

    Upgrade to kernel 4.15.18-12-pve goes BOOM!

    Sorry @TheGrandWazoo looks like I might be totally wrong here: root@orbit:~# apt-cache depends insserv insserv Depends: libc6 Breaks: sysv-rc Suggests: bootchart2 root@orbit:~# dpkg -l | grep sysv-rc root@orbit:~# Pretty sure that's saying the only thing that depends on it is sysv-rc...
  15. T

    Upgrade to kernel 4.15.18-12-pve goes BOOM!

    This was what apt did today, for anyone with clue following along: Start-Date: 2019-03-19 10:31:42 Commandline: apt-get dist-upgrade Install: pve-kernel-4.15.18-12-pve:amd64 (4.15.18-35, automatic) Upgrade: zfs-initramfs:amd64 (0.7.12-pve1~bpo1, 0.7.13-pve1~bpo1), zfsutils-linux:amd64...
  16. T

    Upgrade to kernel 4.15.18-12-pve goes BOOM!

    I noticed my "apt-get dist-upgrade" today removed insserv, which I did wonder if it was a bad thing or not. I haven't rebooted yet though, now reading this post I'm too scared too. root@orbit:~# dpkg -l | grep inss rc insserv 1.14.0-5.4+b1 amd64...
  17. T

    Containers not starting.

    My three containers are all Debian 9.6
  18. T

    Containers not starting.

    I've just hit this problem. At least, I haven't rebooted in a while, but after a recent apt-get dist-upgrade I can no longer get a console on my Containers using the WebGUI. Using pct enter works just fine though. I'm a tad scared to reboot now too!
  19. T

    Sudden PowerOutage fail proof?

    Power is always a cause of issues! You can have disks that haven't been properly written to, causing failures of either the host or guest(s). If you want a reliable server you can trust, reliable power you can trust is a must. Most people would install a UPS and then run some sort of UPS...
  20. T

    clean old kernels

    No, this is community support. If you're a paying customer, you'd use the ticket system. I'm sorry you think I'm a bug. Good luck with being shouty.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!