Recent content by Jarvar

I have some weird issues. I'm trying to restore to a PBS inside Proxmox 7. It's taking a long time, my suspicion has led me to think it's a slower network speed inside Proxmox. However, I have a Windows VM running on the PVE, when I run a speedtest from speedtest.net from a browser or using...

Hmm it's possible, and this was probably the first time I rebooted the system fully since the beginning of December. I guess that's why it's good to plan for when not everything needs to be running. Luckily I was able to build another container quickly and point it to the data in a pinch. Thank...

Any idea how that might have changed? Maybe when I edited the bind mounts somewhere along the line? I know previously we have a zpool called just storage, but since then we reinstalled from scratch PVE 7 to PVE8. Well I really appreciate your help so efficiently and in depth.

This may be a easy question, but is it okay to edit the storage.cfg while the system is running? I have a vm using the same storage, but it looks like mountpoint generally affects the containers. Thanks

Silly me. I think you wrote that, but I didn't register in my head I kept thinking 205.conf This is what shows in the storage.cfg file zfspool: storage01 pool storage01 content rootdir,images mountpoint /storage sparse 1 The mointpoint doesn't look right, is it...

cat /etc/pve/lxc/205.conf arch: amd64 cores: 2 features: nesting=1 hostname: deb-pbs-005 lock: mounted memory: 2048 net0: name=eth0,bridge=vmbr0,firewall=1,gw=10.4.0.1,hwaddr=BC:24:11:D4:6E:F5,ip=10.4.0.235/24,type=veth ostype: debian parent: snap1 rootfs: storage01:subvol-205-disk-0,size=8G...

Thank you @Chris I added the snapshot to the config output above. Yes there's a a mount lxc.mount.entry: /storage01/dataset001 mnt/storage01/dataset001 none rbind.create=dir which was connected before, this was part of a dataset on the zpool storage01 which was working before reboot. I wasn't...

arch: amd64 cores: 2 features: nesting=1 hostname: deb-pbs-005 memory: 2048 net0: name=eth0,bridge=vmbr0,firewall=1,gw=10.4.0.1,hwaddr=BC:24:11:D4:6E:F5,ip=10.4.0.235/24,type=veth ostype: debian parent: snap1 rootfs: storage01:subvol-205-disk-0,size=8G swap: 2048 unprivileged: 1 lxc.idmap: u 0...

I get an error when trying to start my lxc container I bypassed it by creating a new lxc but using the local-zfs as rootfs instead of storage01 This is the error I get. run_buffer: 322 Script exited with status 2 lxc_init: 844 Failed to run lxc.hook.pre-start for container "205" __lxc_start...

@nqservices Could you just mkfs.xfs or mkfs.ext4 /dev/sda3 then Install your datastore on that partition?

You're a genius @leesteken Thank you! Okay I added the bindmount mp0: /mnt/usbpool004,mp=/mnt/usbpool004 and inside the lxc if I type df -h it will show the correct size and mountpoint. then I'll check permissions ls -l /mnt/usbpool004/ total 0 drwxr-xr-x 2 nobody nogroup 6 Jan 19 03:43...

Hello everyone, I had previously connected a USB HDD setup as a zpool and used lxc.mount.entry inside an LXC setup with Debian and Proxmox Backup Server. I got it working but one of my other drives is a single drive and the ZFS was causing errors. I followed some recommendations to try out XFS...

Thank you so much. Root seems to have space left. Only 17% used. Can I see a list of running services through command line?

I did. I tried both PAM and PBS. Weird. It used to work. Would datastores that are no longer connected or available cause issues?

I wanted to work on some NFS shares inside my PBS VM. I can access the console, but the WEB GUI won't accept the root user and password. Any thoughts on how I can diagnose this and fix it? Thank you.