Recent content by tjh

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

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

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

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

My three containers are all Debian 9.6

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!

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

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.

@UHL-Services It's free software. If you don't like the support you're getting, for free, running free software, go elsewhere. This is community support, if you want official support, pay for it. I don't even know why I am bothering to answer your question, but I will anyway. You don't use...

You probably need to turn off hardware offload or similar on your VM's NICs. You don't give any deatils though so it's impossible to guess :)