Search results

  1. U

    negative SSD "Wearout -140%"

    One of our servers uses two Crucial MX500 SSDs in a ZFS RAID1 setup as boot drives. By chance, I checked the servers' SMART values in the UI and it shows a whopping negative -140% wearout. Not sure what to make of this? In the shell, smartctl -a doesn't show anything extraordinary except the...
  2. U

    [SOLVED] increasing the size of a legacy /boot partition

    One of my PVE nodes has been installed some years ago and even though it has always upgraded it to the newest PVE version (currently 8.4.3), one thing has been bothering me for a while. When the node was installed, it was done by using ext4 & mdstat, ending in a partition layout like this: $...
  3. U

    PVE 8.3 node with btrfs booting into grub command line after hard reset

    Hi, for my home lab, I wanted to give btrfs a try and since PVE supports btrfs+RAID on root, I decided to give it a try and added a PVE 8.3 node with exactly that into my little 2 node home lab. Things went smoothly so far, but after a recent hard reboot, the node doesn't boot anymore, but...
  4. U

    "invalid: subscription information too old" and "Connection error 596: Broken pipe"

    Hi, one of our nodes feels unhappy about its subscription state and displays "invalid: subscription information too old" in the node's subscription page: When I click "Check", a popup opens and displays "Connection error 596: Broken pipe". Nothing conclusive in the logs, maybe anyone else...
  5. U

    migration path from ZFS via iSCSI to ceph?

    When it comes to storage, we have been using ZFS over iSCSI in our clusters for years. Now for a couple of new projects, we require S3 compatible storage and I am unsure about the best way to handle this situation. I am tempted to use MinIO, but I've read mixed reviews about it and Ceph seems...
  6. U

    [SOLVED] unable to access API using PVEAPIToken

    I am trying to use the terraform<->proxmox plugin and for that purpose, I have created a dedicated terraform provisioning user like this: pveum role add TerraformProv -privs "VM.Allocate VM.Clone VM.Config.CDROM VM.Config.CPU VM.Config.Cloudinit VM.Config.Disk VM.Config.HWType VM.Config.Memory...
  7. U

    cloudinit: how to get nameservers and other networking settings via DHCP

    I'm in the process of migrating our infrastructure to a more declarative, GitOps/terraform style. As a part of this, a lot of VMs will be created using customized cloud-init images (debian, fwiw). Now the only thing missing for my little puzzle is to get networking right. When creating VMs...
  8. U

    correct way to pause ZFS over iSCSI connections

    HI, I need to replace a switch in one of our datacenters, that is used by a couple of PVE nodes for almost anything (corosync, ZFS over iSCSI, node to node traffic for VMs etc.). The replacement shouldn't take long, but still it may take a minute or so. For all the traffic except ZFS over...
  9. U

    linux guest: weird NIC names "rename10", "rename11" ...

    I've recently upgraded one of our installations from 6.x to the latest 7.x. Because of that I have been monitoring the VMs a little bit more closely, which is why I noticed one linux VM behaving strangely. This is a debian 10 VM with more than 10 NICs and after closer inspection, I saw that a...
  10. U

    clusterwide startup order

    I'm trying to figure out how to have a cluster wide startup order. Initially I thought, the "Start and Shutdown Order" mentioned in "11.3.6. Automatic Start and Shutdown of Containers" of the PVE Admin guide was the way to go, but it turned out that this "Startup Order" is only taken into...
  11. U

    [SOLVED] random reboots

    I only learned today that my home proxmox server reboots frequently. Sometimes it's sufficient to just start it to have the proxmox server go down an reboot. Unfortunately, I only activated the journal today, so I can't say how long this has been happening. After activating persistent logging...
  12. U

    implications of qemu "cache=unsafe"

    Like the title says, I am trying to understand the implications of using cache=unsafe for some VMs. Don't you worry, I did my homework and I am well aware about what the PVE documentation says about it (ie https://pve.proxmox.com/wiki/Performance_Tweaks), as well as numerous other sources (eg...
  13. U

    LSI SAS2308 SCSI controller: Unsupported SA: 0x12

    We're using one of our proxmox nodes as an iSCSI target. The node is equiped with an HP H220/LSI SAS2308 SCSI controller with a number of disks attached to it. During high load (particularly when cloning or when the backups run), the kernel ring buffer get's spammed with tons of "Unsupported...
  14. U

    after upgrading from 5.x to 6.x, iSCSI VMs can only be started via commandline

    Hi, I've upgraded one of our clusters from 5.4 to 6.2 only yesterday and unfortunately cannot start VMs using iSCSI storage using the UI. The logs don't show much, all I see there is Error: start failed: QEMU exited with code -1 Researching the forum I read that errors like these are likely...
  15. U

    [SOLVED] Windows 10 (1809): nested virtualization does not work

    In order to run Docker for Windows, I'm trying to setup nested virtualization for a Windows 10 guest on our up to date 5.3-11 installation. I've followed the wiki describing the required steps https://pve.proxmox.com/wiki/Nested_Virtualization and I've searched both the net and the forum, but...
  16. U

    ZFS via iSCSI using LIO/targetcli

    Hi, If I see it right, proxmox currently (5.1) does not really support ZFS via iSCSI on up to date versions of Linux. "Linux" support for ZFS over iSCSI found in proxmox today means "IET", which has been deprecated for quite a while unfortunately. I've looked into how IET support has been...
  17. U

    unable to install: "no cdrom found"

    Hi, I'm trying to get my feet wet with proxmox, but so far fail even with the very first step of installing it from an USB stick, using the lastest ISO available (proxmox-ve_5.1-3.iso). No matter what I do, the installation process ends pretty early, just after the kernel has been booted...