Search results

Yes, but they had nothing except networking connected. I have had a HDMI monitor that would kill anything you plugged it into because it would connect a number of the pins to 340V (i.e. rectified mains). I didn't know that is what it was doing till I poked the plug and found out for myself. I...

Indeed. But they usually stay in that PC and don't transfer to the next one! I have another that is slightly different, older model and most importantly not bought at the same time. I installed pve on that, same settings, pulled the VM's from a one of the very few backups that didn't fail...

I said that I still had issues, running apt install. Independent of the VM. It also borked when running backup - in fact that is where it most often happens. I have installed different hardware as of yesterday evening and I am running the same potentially problematic VM so we will see if that...

I thought it was that VM because that VM would trip up, then in the logs you'll see a load of KVM exceptions followed by some seg faults and then a bunch of memory page issues - I think its simply because more was happening in that VM such that it was more likely. However, as noted when I ran...

I can't really believe it but I have 3 of these and they are all unstable. It must have been a bad batch but good enough to pass power on or self testing.

This is what it is. Its reporting eth0. Its part if how that container does its work.

https://github.com/aceberg/WatchYourLAN/issues/56 I think this is the culprit and probably expected...

I just remembered I have watchmylan community script container running in there as well, I will turn that off for 20 mins and see if that clears it.

can a guest VM do that? In Hyper-V you can but not without configuration.

Jul 14 10:46:19 pve1 kernel: eth0: entered promiscuous mode Jul 14 10:46:21 pve1 kernel: eth0: left promiscuous mode Jul 14 10:48:22 pve1 kernel: eth0: entered promiscuous mode Jul 14 10:48:24 pve1 kernel: eth0: left promiscuous mode Jul 14 10:50:26 pve1 kernel: eth0: entered promiscuous mode...

Recently I have had many issues from corrupt SSD to regular crashing. And more recently when running things like apt upgrade it seems to find checksum errors in the files downloaded. So you might think - that sounds like dodgy RAM? I ran memtest all day and no issues. Same thing. I then...

I have not seen a problem with guests that are at least kernel 3.2. Prior to that there looks like some kind of bug where the disk never recovers. It behaves exactly like the old days when you got the CHS wrong on a disk and you could read some things but others were corrupt or you got IO...

All, over the last week there have been a few reports in the media of embarrassments caused by certificate expiries that apparently nobody was on top of. Chromecast is one of the high profile issues and it made things extremely hard to fix due to the nature of certificates and the fact that it...

Yes, there were no interface problems - occasionally when its gone bonkers, you can see the interface go down and up, in this case all interfaces never changed. Again, the physcial network isn't to blame, rather something on proxmox network stack itself because nothing was changed, in fact not...

I have had a look. I did see one or two Mar 09 07:15:09 proxmoxmon3 sshd[2062129]: fatal: ssh_packet_send_debug: send DEBUG: Connection reset by peer Mar 10 08:30:13 proxmoxmon3 sshd[335445]: fatal: ssh_packet_send_debug: send DEBUG: Connection reset by peer Mar 11 21:45:06 proxmoxmon3...

Restarted two nodes that seemed to be having issues the most, whilst upgrading to 8.3.5, issue hasn't resurfaced yet. Will report back in a few days. This means, don't really have an answer for the caused.

I have slowly been seeing more and more replication job failed errors. By the time I get to them, the problem has gone and I cannot find a sensible log to work out what the problem is. I would suggest the configuration isn't wrong per-se otherwise it wouldn't work most of the time. I get a...

TLDR it failed to boot. Then I upgraded proxmox for some other reason and when it rebooted my upgraded container sprang into life. So the questions is - is this something to do with the kernel being upgraded? I'd just like to understand that a bit better. I had upgraded containers before and...

So attempting to fix it myself.... root@proxmoxmon4:/# zfs destroy rpool/data/subvol-119-disk-0@__migration__ root@proxmoxmon4:/# zfs list -t snapshot rpool/data/subvol-119-disk-0 NAME USED AVAIL REFER MOUNTPOINT rpool/data/subvol-119-disk-0@cleardown...

Snapshots should be a safety feature meaning that the user can use them to try something safe in the knowledge that they can revert back. In my case there always seems to be a reason why this doesn't work as it should. Here's an example: I had created a more recent snapshot but it can't roll...