Recent content by SamTzu

  1. no storage ID

    My guess is when you move drive from storage 2 storage it is registered somewhere (via storage) and that info is used when migrating the container. When the old drive is missing the migration is aborted.
  2. no storage ID

    I don't know where this came from subvol-174-disk-0' (via storage). The container only had disk-1 active (or visible anywhere.) So I just backed up the container and restored it on the new node. But now the container has this drive subvol-174-disk-2
  3. no storage ID

    I just created a new qemu "node" with vdd drive (zfs) that I created using Proxmox GUI. I had the "Add to Storage" marked when I created the ZFS drive. After that I joined the new node to cluster and tried to move LXC container to it. () 2022-03-04 17:22:18 starting migration of CT 174 to node...
  4. no storage ID

    But this is not the reason the first container migration failed because it never had more that 1 drive.
  5. no storage ID

    So. For some reason Proxmox tried to migrate the deleted disk-1 and when It did not find it's storage ID it fails the job even though the 2 other disks migrated fine.
  6. no storage ID

    root@kvm-p1:~# cat /etc/pve/lxc/601.conf arch: amd64 cores: 2 hostname: pk1.ic4.eu memory: 4096 mp1: vdd:subvol-601-disk-2,mp=/var/backup,size=20G nameserver: 1.1.1.1 8.8.8.8 net0...
  7. no storage ID

    Here is a peek in other failure for newer amd64 LXC container. 2022-03-03 00:34:05 successfully imported 'vdd:subvol-601-disk-2' 2022-03-03 00:34:05 delete previous replication snapshot '__replicate_601-0_1645925586__' on vdd:subvol-601-disk-0 2022-03-03 00:34:07 delete previous replication...
  8. no storage ID

    That GeoDNS server is OLLLDDD... But some other newer LXC containers also give same error. I'm thinking this has something to do with bug 3376.
  9. no storage ID

    root@vm2401:~# cat /etc/pve/storage.cfg dir: local disable path /var/lib/vz content backup,iso,vztmpl shared 0 zfspool: local-zfs disable pool rpool/data content images,rootdir sparse 1 zfspool: vdd pool vdd...
  10. no storage ID

    root@vm2401:~# cat /etc/pve/lxc/144.conf arch: i386 cores: 1 features: nesting=1 hostname: geodns1.ic4.eu memory: 512 nameserver: 1.1.1.1 8.8.8.8 net0: name=eth0,bridge=vmbr1,firewall=1,gw=79.134.108.129,hwaddr=7A:54:79:4A:4B:C4,ip=79.134.108.144/26,ip6=auto,rate=2,type=veth onboot: 1 ostype...
  11. no storage ID

    Maybe this message is talking about /etc/vzdump.conf Storage ID? Maybe this has nothing to do with ZFS?
  12. no storage ID

    The vdd on the new node seems to be scsi1.
  13. no storage ID

    I found this on the "old" node.
  14. no storage ID

    ERROR: migration aborted (duration 00:00:06): storage migration for 'vdd:subvol-601-disk-1' to storage '' failed - no storage ID specified TASK ERROR: migration aborted I tried to migrate 1 LXC container to another from one (nested) Qemu node to another and got this error. I remember when I...
  15. IPv6 and LXC with DHCP

    I couldn't get it to work. Let me know if you figure it out.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!