Recent content by tjh

I would suggest you have an underlying hardware issue there. Did you try a different USB stick? If not, that's what I'd be suspecting is the issue, otherwise I wouldn't currently be trusting your server hardware.

Are you sure you're not running out of disk space or something? I just downloaded the 9 ISO today and installed a PVE9 system with no issues. What's the full error you're getting?

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.

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

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...

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!

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...

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...

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

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

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.

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...

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

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

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...