Search results

That worked, thank you!

Hi, I've created a brand new Debian 12 LXC from the official template on my Proxmox 8 server. I've installed logcheck on the LXC as I usually do. Thanks to that I've noticed that APT "cron" tasks are having some problem with systemd-networkd-wait-online. I've quoted "cron" because I think those...

It might be related to IPv6 DHCP. Check if your network is compatible with that, and either disable DHCPv6 or switch to SLAAC.

I had the same problem and the culprit was the DHCP for IPv6. Although I have IPv6 at home it seems my router is not running a DHCPv6, but addresses are handed out using SLAAC. If I were you I would try either disabled IPv6 or switching to SLAAC if you actually have IPv6 in your network.

I'm in, using a simple password I managed to login with the console. Indeed, the image doesn't include a SSH server.

I've been using Proxmox for a while with both VMs and containers. I wanted to test Alpine linux in a container but it seems to me the template is broken or it works quite differently than the Debian or Ubuntu images. The problem is a cannot login into it. Do they start a SSH server? I usually...

Yes, the storage is on configured on PVE. I will disable it in order to change it. About using the partition links instead of the whole disk... which partition? When I created the pool I used whole disks. Actually I think I used the GUI, but anyway it showed as full disk (aka sda, sdb...). Now...

I've already tried (without the /dev/disk/by-id prefix, just ata- .... I've just now tried again with the prefix. It's not working. By the way, there's a mechanism to auto-import pools somehow? If I export it it kind of imports itself after some seconds. Look at this. root@pve-shark2:~# zpool...

So I did some replacement and upgrades of drives on a PVE node using ZFS and some hot swap enclosures. Everything went fine until the next reboot. Suddendly the zfs pool was degraded. The problem was some drives changing names in the form /dev/sda and so on. That's because I left a "hole" and I...

Seems that the latest kernel fixes it: 5.0.21-2-pve At least since its installation two days ago no more reboots.

Right, sorry. I don't think so but I'm not completely sure when exactly it started happening because both VMs are running services that start automatically so a restart is not always detected right away.

Hosts? What do you mean? The host is PVE latest version.

I have a couple Windows 10 VMs on my host with very different configurations. Both see frequent (as in daily, twice a day) reboots. The event log shows this: > The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x00000000c0000005, 0xfffff8000a8c4ce3, 0xffff848f31524a40...

Same issue here. Is this really the recommended solution? It seems like just a workaround.

Solved. Just had to delete the partition /dev/sda1 , that's what "usage: partitions" mean I guess.

Hi, I have a Proxmox 5.4 installation consisting on a single node. The node has two physical drives: one NVMe drive and one SATA drive. The NVMe drive is the system one so everything is configured by default. The SATA drive was not configured during setup. After installation I configured as a...