pbs.sh script

[mcooperRPI]

Please verify that you have read and understood the guidelines.

yes

A clear and concise description of the issue.

Hey there guys,

I tried the Proxmox Backup Script on my Orange Pi 5 Proxmox/PiMOX Cluster. I did have to dl the tar.xz file and rename it I got it from here: https://images.linuxcontainers.org/images/debian/bookworm/arm64/default/20240624_05%3A24/

The rootfs.tar.xz to debian-bookworm-rootfs.tar.xz then I uploaded it to the cluster/iso storage and tried to install.

Please let me know what else you need.

1. Each node has Orange Pi 1.1.8 Bookworm with Linux 5.10.160-rockchip-rk3588
2. Proxmox VE Environment 8.2.4
3. Orange Pi 5 (8 cores-16 gb of ram)
4. I ran this in the shell on the host

pbs.sh script on a PiMOX/Proxmox SBC Cluster with Proxmox v8.2.4

I got the follwoing error in the shell after this script completed it's run. I am not sure if it is something I did or if it's in the script.

What settings are you currently utilizing?

Advanced Settings

Which Linux distribution are you employing?

Debian 12

If relevant, including screenshots or a code block can be helpful in clarifying the issue.

---

/ ___ __ __ _ / ) __/ / __ / _/ __ __ _ / // / / _ | |// __ \/ __ \| |/_/ / __ / __/ / /// / / / \ _ \/ \/ / | / / \/ _/ / __/ / / // /> </ / / / / / // /> < / // / // / /_/ ,< / // / // / / / / / | |/ / / / // // _//|// // //_//|| //_,/_//||_,/ ._/ /__/_/_/ |/\// // Using Advanced Settings Using Distribution: debian Using debian Version: 12 Using Container Type: 1 Using Root Password: **** Container ID: 201 Using Hostname: pbs Using Disk Size: 20 Allocated Cores: 2 Allocated RAM: 2048 Using Bridge: vmbr0 Using IP Address: 192.168.2.81/24 Using Gateway IP Address: 192.168.2.254 Using APT-Cacher IP Address: Default Disable IPv6: no Using Interface MTU Size: Default Using DNS Search Domain: Host Using DNS Server IP Address: Host Using Vlan: Default Enable Root SSH Access: yes Enable Verbose Mode: yes Creating a PBS LXC using the above advanced settings ✓ Using ARM_ISOs for Template Storage. ✓ Using local for Container Storage. |unable to create CT 201 - error in setup task PVE::LXC::Setup::post_create_hook /bash: line 218: exit: A problem occured while trying to create container.: numeric argument required

Please provide detailed steps to reproduce the issue.

I created a new VM on my OPi5 Cluster,

1 - Create VM
2 - VM ID: Unique ID is best mine is 201
3 - Name your vm ex: pve-plex-vm-01 <click next>
4 - Do not use any media - THIS IS A MUST!
5 - Type should be: Linux 6.x <click next>
6 - Bios should be OVMF (UEFI) & Choose the EFI Storage I always use local
7 - Select Qemu Agent - check box. everything shoudl be default. <click next>
8 - Start out with local, Select disk size; I will show you later how to move it to Shared Storage.
9 - I use SSD Emulation and Discard but that's me. <click next>
10 - Select your cores: depending on usage select how many you want. 
Type should be host. Everything else default <click next>
11 - Memory: Your shoice here I use a minimum of 2048 and uncheck balooning. <click next>
12 - Usually the default nic is a good choice. <click next>
13 - Now make sure everything is correct then <click finish> if it is correct.
14 - highlight the vm in the left menu in the menu to the right select Options
15 - Select hardware > CD/DVD Drive > Remove button at top > Then Add button > CD/DVD Drive > 
Bus/Device: scsi then id > select the next available ID number > storage (Should be where ISOs are stored)
ISO image: the one you want to use goes here. > click add button.
16 - Options > Select Boot Order > then the Edit button at the top > uncheck net0
 (Unless you are using PXE Boot)
17 - Highlight the VM > right click > then start
18 - ssh <user>@server_ip
19 - sudo nano -c /etc/hosts
20 - sudo nmtui - set the static ip
21 - sudo reboot now

Then I went in to the shell and ran chmod +x pbs.sh Then I ran ./pbs.sh in the shell & got the above error - I am pretty sure this error is due to not having an ARM version of PBS. Please let me know what else you need.

[mcooperRPI]

Just an FYI, I got the same error with dockge.sh install script:

unable to create CT 201 - error in setup task PVE::LXC::Setup::post_create_hook
 -bash: line 218: exit: A problem occured while trying to create container.: numeric argument required

Just let me know where it is; it could be my setup is not working correctly. Thanks for your hard work.

[tteck]

Run the script within the Proxmox shell.

[mcooperRPI]

I did run in the proxmox shell:

[image: image.png]

Thanks for helping. Michael Cooper Linux Certified Professional Kubernetes/Docker Trained RPi Hobby Blog http://www.rpihobby.org/

On Mon, Jun 24, 2024 at 7:12 AM tteckster @.***> wrote:

Run the script within the Proxmox shell.

— Reply to this email directly, view it on GitHub https://github.com/asylumexp/Proxmox/issues/46#issuecomment-2186320935, or unsubscribe https://github.com/notifications/unsubscribe-auth/A65HAYFJQ5JW5QK3M3TIYITZI75KFAVCNFSM6AAAAABJZSPWZCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBWGMZDAOJTGU . You are receiving this because you authored the thread.Message ID: @.***>

[tteck]

Your "Please provide detailed steps to reproduce the issue." suggests not. It looks like you created a VM, and tried to run the script within it.

[tteck]

copy the script (link), paste it within the Proxmox shell, hit enter. That's all that is required.

[tteck]

you are using the website to obtain the link to paste in the Proxmox shell, correct?

https://pimox-scripts.com/scripts?id=Proxmox+Backup+Server

[asylumexp]

The Debian rootfs tar from linux containers doesn't work because newer images use some other networking package that i cant remember rather than ifupdown2, if you delete or rename that tar then rerun the script itll download a rootfs tar made using the build script found here, the only differences between this image and the one from linuxcontainers is that this image includes ifupdown2 for networking and netcat for apt cacher.

[asylumexp]

Forgot to mention that ifupdown2 is required is because Proxmox expects that for Debian LXCs (didn't have any issues creating Ubuntu LXCs which don't use ifupdown2).

[mcooperRPI]

Yes sir I am thank you Michael Cooper Linux Certified Professional Kubernetes/Docker Trained RPi Hobby Blog http://www.rpihobby.org/

On Mon, Jun 24, 2024 at 8:08 AM tteckster @.***> wrote:

you are using the website to obtain the link to paste in the Proxmox shell, correct?

https://pimox-scripts.com/scripts?id=Proxmox+Backup+Server

— Reply to this email directly, view it on GitHub https://github.com/asylumexp/Proxmox/issues/46#issuecomment-2186425381, or unsubscribe https://github.com/notifications/unsubscribe-auth/A65HAYAUXW4Z2GAWS3JILRLZJAD4JAVCNFSM6AAAAABJZSPWZCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBWGQZDKMZYGE . You are receiving this because you authored the thread.Message ID: @.***>

[mcooperRPI]

Ah okay that would make sense. Let try it with the ones you suggested thank you very much, Michael Cooper Linux Certified Professional Kubernetes/Docker Trained RPi Hobby Blog http://www.rpihobby.org/

On Mon, Jun 24, 2024 at 8:34 AM Sam Heinz @.***> wrote:

The Debian rootfs tar from linux containers doesn't work because newer images use some other networking package that i cant remember rather than ifupdown2, if you delete or rename that tar then rerun the script itll download a rootfs tar made using the build script found here https://github.com/asylumexp/debian-ifupdown2-lxc, the only differences between this image and the one from linuxcontainers is that this image includes ifupdown2 for networking and netcat for apt cacher.

— Reply to this email directly, view it on GitHub https://github.com/asylumexp/Proxmox/issues/46#issuecomment-2186475453, or unsubscribe https://github.com/notifications/unsubscribe-auth/A65HAYCLSKFI3PK46S4RJPLZJAG45AVCNFSM6AAAAABJZSPWZCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBWGQ3TKNBVGM . You are receiving this because you authored the thread.Message ID: @.***>

[mcooperRPI]

Thank you Sam, It is much appreciated ......................... Michael Cooper Linux Certified Professional Kubernetes/Docker Trained RPi Hobby Blog http://www.rpihobby.org/

On Mon, Jun 24, 2024 at 8:34 AM Sam Heinz @.***> wrote:

Closed #46 https://github.com/asylumexp/Proxmox/issues/46 as completed.

— Reply to this email directly, view it on GitHub https://github.com/asylumexp/Proxmox/issues/46#event-13265724644, or unsubscribe https://github.com/notifications/unsubscribe-auth/A65HAYAQAZPFY4Y6AHQRBULZJAG4ZAVCNFSM6AAAAABJZSPWZCVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJTGI3DKNZSGQ3DINA . You are receiving this because you authored the thread.Message ID: @.***>

[mcooperRPI]

That makes perfect sense, Thank you. Michael Cooper Linux Certified Professional Kubernetes/Docker Trained RPi Hobby Blog http://www.rpihobby.org/

On Mon, Jun 24, 2024 at 8:34 AM Sam Heinz @.***> wrote:

The Debian rootfs tar from linux containers doesn't work because newer images use some other networking package that i cant remember rather than ifupdown2, if you delete or rename that tar then rerun the script itll download a rootfs tar made using the build script found here https://github.com/asylumexp/debian-ifupdown2-lxc, the only differences between this image and the one from linuxcontainers is that this image includes ifupdown2 for networking and netcat for apt cacher.

— Reply to this email directly, view it on GitHub https://github.com/asylumexp/Proxmox/issues/46#issuecomment-2186475453, or unsubscribe https://github.com/notifications/unsubscribe-auth/A65HAYCLSKFI3PK46S4RJPLZJAG45AVCNFSM6AAAAABJZSPWZCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBWGQ3TKNBVGM . You are receiving this because you authored the thread.Message ID: @.***>

[mcooperRPI]

Thank you Sam, now that I know what I needed everything is working, I didn't realize it was the images but they are working perfectly. Again thank you very much.

Michael Cooper Linux Certified Professional Kubernetes/Docker Trained RPi Hobby Blog http://www.rpihobby.org/

On Mon, Jun 24, 2024 at 8:34 AM Sam Heinz @.***> wrote:

The Debian rootfs tar from linux containers doesn't work because newer images use some other networking package that i cant remember rather than ifupdown2, if you delete or rename that tar then rerun the script itll download a rootfs tar made using the build script found here https://github.com/asylumexp/debian-ifupdown2-lxc, the only differences between this image and the one from linuxcontainers is that this image includes ifupdown2 for networking and netcat for apt cacher.

— Reply to this email directly, view it on GitHub https://github.com/asylumexp/Proxmox/issues/46#issuecomment-2186475453, or unsubscribe https://github.com/notifications/unsubscribe-auth/A65HAYCLSKFI3PK46S4RJPLZJAG45AVCNFSM6AAAAABJZSPWZCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBWGQ3TKNBVGM . You are receiving this because you authored the thread.Message ID: @.***>