[SOLVED] 400 Bad Request on VM Backup

Finn0811

New Member
Nov 20, 2023
2
0
1
Hi,

first of all, I know running proxmox backup server on arm64 is not supported at all but maybe someone can help me debugging this issue.

I already posted this issue at the GitHub project providing arm64 builds: https://github.com/wofferl/proxmox-backup-arm64/issues/40

The problem is that VM backups are not working while host backups using proxmox-backup-client are working fine.

Code:
2023-11-19T21:11:58.634070+01:00 raspberrypi proxmox-backup-proxy[916]: GET /previous: 400 Bad Request: no valid previous backup
2023-11-19T21:11:58.657460+01:00 raspberrypi proxmox-backup-proxy[916]: POST /fixed_index: 400 Bad Request: EINVAL: Invalid argument
2023-11-19T21:11:58.680567+01:00 raspberrypi proxmox-backup-proxy[916]: backup ended and finish failed: backup ended but finished flag is not set.
2023-11-19T21:11:58.680626+01:00 raspberrypi proxmox-backup-proxy[916]: removing unfinished backup
2023-11-19T21:11:58.680712+01:00 raspberrypi raspberrypi proxmox-backup-proxy[916]: removing backup snapshot "/opt/fwpbs02/ns/fwpve01/vm/101/2023-11-19T20:11:58Z"
2023-11-19T21:11:58.681001+01:00 raspberrypi proxmox-backup-proxy[916]: TASK ERROR: backup ended but finished flag is not set.

Code:
root@raspberrypi:~# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/`

Code:
root@raspberrypi:~# cat /etc/proxmox-backup/datastore.cfg
datastore: fwpbs02
        comment
        gc-schedule daily
        path /opt/fwpbs02/
        prune-schedule daily

Code:
root@raspberrypi:~# ls -la /opt/fwpbs02/
total 1052
drwxr-xr-x 4 backup backup    4096 Nov 19 13:15 .
drwxr-xr-x 6 root   root      4096 Nov 19 13:14 ..
drwxr-x--- 1 backup backup 1060864 Nov 19 13:15 .chunks
-rw-r--r-- 1 backup backup       0 Nov 19 13:14 .lock
drwxr-xr-x 5 backup backup    4096 Nov 19 13:16 ns

Code:
root@raspberrypi:~# dpkg -l | grep proxmox
ii  libproxmox-acme-plugins              1.4.6                               all          Proxmox acme.sh wrapper for DNS API plugins
ii  proxmox-backup-client                3.0.4-1                             arm64        Proxmox Backup Client tools
ii  proxmox-backup-client-dbgsym         3.0.4-1                             arm64        debug symbols for proxmox-backup-client
ii  proxmox-backup-docs                  3.0.4-1                             all          Proxmox Backup Documentation
ii  proxmox-backup-file-restore          3.0.4-1                             arm64        Proxmox Backup single file restore tools for pxar and block device backups
ii  proxmox-backup-file-restore-dbgsym   3.0.4-1                             arm64        debug symbols for proxmox-backup-file-restore
ii  proxmox-backup-server                3.0.4-1                             arm64        Proxmox Backup Server daemon with tools and GUI
ii  proxmox-backup-server-dbgsym         3.0.4-1                             arm64        debug symbols for proxmox-backup-server
ii  proxmox-mini-journalreader           1.4.0                               arm64        Minimal systemd Journal Reader
ii  proxmox-widget-toolkit               4.0.9                               all          Core Widgets and ExtJS Helper Classes for Proxmox Web UIs

Code:
root@raspberrypi:~# cat /etc/fstab
proc            /proc           proc    defaults          0       0
PARTUUID=b2a89280-01  /boot/firmware  vfat    defaults          0       2
PARTUUID=b2a89280-02  /               ext4    defaults,noatime  0       1
# a swapfile is not a swap partition, no line here
#   use  dphys-swapfile swap[on|off]  for that

Code:
root@raspberrypi:~# tune2fs -l /dev/disk/by-partuuid/b2a89280-02
tune2fs 1.47.0 (5-Feb-2023)
Filesystem volume name:   rootfs
Last mounted on:          /
Filesystem UUID:          cb6f0e18-5add-4177-ab98-e9f0235e06b3
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype needs_recovery extent 64bit flex_bg sparse_super large_file dir_nlink extra_isize metadata_csum
Filesystem flags:         unsigned_directory_hash
Default mount options:    user_xattr acl
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              7622368
Block count:              31085056
Reserved block count:     1554233
Free blocks:              27278133
Free inodes:              7352328
First block:              0
Block size:               4096
Fragment size:            4096
Group descriptor size:    64
Reserved GDT blocks:      299
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8032
Inode blocks per group:   502
Flex block group size:    16
Filesystem created:       Tue Oct 10 06:04:14 2023
Last mount time:          Wed Sep 20 14:15:15 2023
Last write time:          Thu Jan  1 01:00:09 1970
Mount count:              2
Maximum mount count:      -1
Last checked:             Mon Nov 20 22:50:54 2023
Check interval:           0 (<none>)
Lifetime writes:          22 GB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               256
Required extra isize:     32
Desired extra isize:      32
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      aeb82a13-d56b-4342-809f-47e69117f8e4
Journal backup:           inode blocks
Checksum type:            crc32c
Checksum:                 0x5274fcfb

How can I try to resolve this issue?
 
To explain what the problem here is, now that it has been found (400 Bad Request on raspberry pi). The raspi 5 has by default a kernel with 16k pagesize, this probably leads to a problem when writing or creating the fixed index, which leads to this error.

If you switch to a kernel with 4k (Raspberry Pi Documentation The config.txt file), the unofficial packages for arm64 will also work here.

Whether this is due to hard coded pagesize or a problem with the build process itself is not yet clear.
 
  • Like
Reactions: Finn0811

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!