Search results

I decided to do a checkup to find out what is happening. I restarted pvestatd and my node started working again. Before that my node had a question mark and the container that was running also had a question mark. Pretty much everything inside the node had a question mark, meaning each container...

Hello Everybody. I'm thinking there is a setting I am missing. Initially this was from a physical Windows Server 2016 Physical Install which was converted to Proxmox through a VHD. The Bios is OVMF. It's been running for a couple years atleast. Until one latest update, the reboot got stuck on...

You are brilliant!!! Got it from not working to working. I can't thank you enough. I did have to create the directories first to get rid of that error. Thank you for taking your time to work with me on this. I got the datastores connected to the container and I'm able to connect to it from...

So I was able to attach to a test datastore I created so I don't lose anything too vital. The restore was successful when I connected another PVE to the PBS Container. This is the error I'm getting when I add the second mount entry. This is the result of pct conf pct conf 209 arch: amd64...

Thank you so so much! I think I may have got it working. Though I'm not sure how to add more than one lxc.mount.entry: How I managed to get proxmox backup working was starting with a fresh Debian12 container. I apt update and apt dist-upgrade -y then I applied the id mappings. restarted the...

Okay I sorted some issues. I applied the id mappings before installing PBS. I created a standard Debian 12 container, then installed PBS. Is that recommended? or using PBS Installation Media? Should I be install proxmox-back or proxmox-backup-server. Looks like server leaves out some things...

I really appreciate your help. I followed through on your advice. The container starts. Does it matter if I use the mp0: or lxc.mount.entry mappings? Somehow the container starts and I can access it through the shell. However, the gui is not accessible on the host:8007 The share is accessible...

Thank you @zodiac I really appreciate your help. Do you have references on how to use lxc.mount.entry. I’d be interested to move towards that but haven’t found more detailed documentation about it. Seen it mentioned here and there though. I’m newer to containers compared to VMs. Thank you again.

I followed the document exactly to add the storage. The previous drive was through USB, I added the hardware to the VM, then setup the pool through the VM. When trying to access it through the container, I imported the pool on the hose and tried to use bindmount mp0...

I will try it again. I think the id backup command was issued before the added the uid mapping and recursively changing ownership. You didn't need to do that? this is in the document: As a final step, remember to change to owner of the bind mount point directory on the host, to match the uid...

Any developments here? I'm facing something similar, except my drive is mounted on host with zpool import. I followed their guidelines here https://pve.proxmox.com/wiki/Unprivileged_LXC_containers but still getting an error when trying to boot it. If I don't follow the permissions I can access...

Went through the chown -R 1005:1005 /usbpool002/dataset021/store021 chown -R 1005:1005 /usbpool002/dataset021/store021 root@tks-pve-02:~# pct start 205 lxc_map_ids: 3701 newuidmap failed to write mapping "newuidmap: uid range [0-1005) -> [100000-101005) not allowed": newuidmap 2440002 0 100000...

Good morning @Chris I started a new thread instead of continuing on this one unless it's related. https://forum.proxmox.com/threads/running-a-lxc-container-with-pbs-inside-and-using-bindmounts-for-an-external-drive-with-zpool-from-host.135173/ I appreciate your help. Thank you

I tried to create a container instead and bindmount the zpool. It takes a lot less resources but messes with permissions. https://pve.proxmox.com/wiki/Unprivileged_LXC_containers I followed the instructions but it didn't work or I didn't wait fully for the chown -R 1005:1005...

@ I mess something up, I tried to create a container instead and bindmount the zpool. It takes a lot less resources but messes with permissions. https://pve.proxmox.com/wiki/Unprivileged_LXC_containers I followed that and now I'm having some issues again. I'm trying to convert everything back...

So I managed to use pct set 205 -mp0 /usbpool002/dataset021/store021,mp=/store021 or editing the 205.conf I managed to get it working, but now I have to figure out permissions on making the zpools accessible/writable with the PBS Container. Thank you, Is there an easier way? this is for the...

@Tony Wondering if you could provide more details on how you did this? bind mounting a zpool inside a PBS Container. I tried mounting the zpool on the pve host first, when I pct set 205 -mp0 /usbpool002/dataset021/store021,mp=/store021 The container fails to start.

I had run a VM previously and passed an external USB HDD with zpool on it. Was thinking of going lighter with a Container but can't figure out how to pass the zpool through and make it accessible on the container side. Please help.

Also this supports a good reason to keep boot on a different drive than VMs. Unless you create more pools on the same drive but could be a bit confusing. I might try it out on a larger drive single system in order to store other VMs and backups.

I solved the issue but probably not in The best way. I restored the VM from a back instead. Hopefully I don’t run into that issue again.