Search results

The cursor is down a few lines from the top because I have hit enter a few times.

Yes sir. Sometimes it opens the console prompt quickly. Other times it just hangs and doesn't come up. Seems something to do with VLAN tagging and I am on a complete Unifi ecosystem so setup is very straightforward.

I can't get a console after creating a container with a tagged VLAN. Console is just a black pane. Ubuntu or Debian, both same result.

ok, after waiting about 10 minutes, the login prompt came up. hrm... I wonder if this error has something to do with it? systemctl * networking.service loaded failed failed Raise network interface

the console will not show the login prompt. when I remove the VLAN tag, console works. when I add the VLAN tag, console wont work. ping tests to container when using VLAN = OK.

I see. Thanks

Because I am trying the simplest method to simply pass data from one conatiner to the next. Using the ZFS mounts isn't working because each container is just creating separate subvols when I mount the same ZFS storage. I can find many posts online with people experiencing similar issues, but...

But I cannot mount the directory even in a single container? What sort of filesystem does the mount dir function require? Its not clear on this page: https://pve.proxmox.com/wiki/Storage:_Directory

im sure this is a stupid question, but... I keep getting this error: command 'mkfs.ext4 -O mmp -E 'root_owner=0:0' /zvol/henry/tmp/images/123/vm-123-disk-1.raw' failed: exit code 144 (500) and all I am trying to do is add this directory to a couple of containers to transfer some data.

Yup this is the solution. Thanks!

Thank you sir for your help! I haven't been able to test your solution just yet but I will in the next day and report my findings. | Cheers, Henry

I deleted the ZFS storage first from the datacenter, and now there's an entry in the resources tab of my container for an "unused disk" that I cannot rid myself of. I already destroyed the ZFS filesystem so not sure what to do now...

Well, I guess ill answer my own silly question in case any other noobs come around. For whatever reason, SDB wasn't initialized while the other disks were. Clicking on: "Initialize Disk with GPT" solved the issue.

Hi there, I have abandoned FreeNAS as I found the bhyve VM support for windows machines (on an AMD chip) dreadful. I am excited to be migrating to proxmox as it looks very powerful. I have a mirrored zpool named "zvol", which is functioning without error on FreeNAS. after running: #...