Search results

I changed the mount point again. mp1 this time pct set 101 --mp1 /dev/disk/by-id/ata-ST400DM000-1F2168_Z30091R1-part1,mp=/mnt/extHDD,backup=0,ro=0 Still ... unable to reboot I can confirm my command changed 101.conf I can confirm host see's the disk as well

Hello again. I've made some changes / upgrades, and i'm running into an issue. I upgraded to ProxMox Virtual Environment 6.1-7 I tore apart my odroid H2 build and added two new platter drives and increased RAM. I decided to rebuild my File Server container still 101 but i've added a larger root...

Thank you Thomas. This did the trick for me. Is there perhaps something I did incorrectly during initial setup that would prevent my disks from showing up in the Add drop down in the image above? I think I can do this again via CLI for some other disks and containers. I'm just thinking...

Thank you root@xkey:~# pct set 101 delete --mp0 Option mp0 requires an argument 400 unable to parse option pct set <vmid> [OPTIONS] root@xkey:~# pct set 101 delete --mp0 /dev/disk/by-id/ata-ST400DM000-1F2168_Z30091R1,mp=/mnt/HDD,backup=0 400 too many arguments pct set <vmid> [OPTIONS]...

Interesting... This was the first command I tried before searching forum posts. I wasn't able to get this command to work initially and I can't recall why at this moment. I went back and removed the previous lines from my 101.conf stopped the container and then.. pct set 101 --mp0...

hello, thank you for the links. and suggestions. I can't say this left me feeling confident. The first link was difficult to follow so I attempted the second link first. However, even with clear instructions. this did not work for me either Just as the post suggested I stopped my LXC file...

EDIT 1: It seems CLI is the only option for passing block storage to my container. Follow the example provided; pct set <VMID> --mp<#> /dev/disk/by-id/<your disk ID + partition #>mp=<path to mount> EDIT 2: this method worked for me, until I tried removing the 101 file server container and...