-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
400 Bad Request on raspberry pi #40
Comments
Maybe some kind of file system problem. |
Filesystem is ext4, it's the internal SD card to try before using an additional SSD.
No there were no existing backups, it was newly initialized with 3.0.4. |
What version is your pve server? Does host or ct backups work? |
My pve server is 8.0.4.
Host backups do work, yes. I currently don't have any container to test with. |
This will not be easy to debug and I don't think that is a problem from this proxmox backup build. You can install auditd and create a rule for debugging: This will log all file accesses in your datastore directory to /var/log/audit/audit.log. You can than search for unsuccessful operations: This should show the failed operations to debug this further. |
The syslog shows nothing more than the output from proxmox backup server. The auditlog doesn't even show one file access in that directory at the time I try to create a backup. Trying with "touch /opt/fwpbs02/ns/fwpve01/vm/101/test" does log file access so it seems to work. Looks like proxmox backup server doesn't even want to try to write into it. :( |
That is strange. There are normally several filesystem operations between From the error |
I think xattr and acl is enabeld by default, at least I didn't modify anything like that.
It's really hard to debug, the only requirement I found is that the fs has to support hard links. |
I can't find anything problematic in the setup either. I would start again with debugging through auditd, maybe the rule was not insert correctly, because I haven't found a way to start the server in debug mode or increase the server logging. I can't reproduce this error on my system with this package build, so the best change to get help here is to ask in the official proxmox forum https://forum.proxmox.com/forums/proxmox-backup-installation-and-configuration.24/ or how you are planning to do it with an extra ssd. |
I think the rule is working, because I see log messages when I manually create files in that folder. I opened a thread over there, maybe it can be resolved with their help. Thanks a lot for your help and ideas! |
Have just come across the same issue. Also, an RPi5, though the dest is a zfs mirror, not an ext4 fs. Works fine for container backups, only VMs don't work. Let me know if/how I can help. |
I created a thread here: https://forum.proxmox.com/threads/400-bad-request-on-vm-backup.136824/ Unfortunately there are no replies, yet. I think they are not interested in solving the issue. |
Is this also a new install? |
The problem is that this seems to be a very specific problem with the Raspi 5. Proxmox itself does not offer arm64 packages and since it is not a general problem, help is difficult. Until someone can debug this problem on a Raspi 5 more accurately, no solution will be found. I use it myself on Armbian with a Helios64 and test it on a Raspi 4 and so far there are no problems. Maybe you can try different constellations (PBS versions, kernel, etc.) or try to find out with tools like audit or strace what exactly causes the "EINVAL: Invalid argument" error. You could also try to compile the packages with the script by yourself on the Raspi5, it might make a difference. |
Yeah I understand that they do not provide arm builds but with the rise of powerful arm VPS and the new raspberry pi 5 these builds are really cool. I just compiled them now but the issue is still present.
I even upgraded to the newest kernel:
Error:
|
Can you run following command during your attempt and look for the error there and post the corresponding lines or the complete output file. But be aware that some lines contains your pbs username and password!
|
So it seems Raspi 5 uses 16k pagesizes kernel. This can of course cause problems Pi5 16K PageSize Kernel Incompatible Software #107 |
From the docu (Raspberry Pi Documentation The config.txt file) the 6.1.0-rpi6-rpi-2712 is also a 16k kernel.
So you have to install a 4k kernel on the raspi 5 for proxmox backup server to work. |
Awesome, with kernel=kernel8.img in config.txt it now works!
Thanks a lot @wofferl 😀 |
Can confirm, adding this line works! Thanks |
Backups won't work on a new installation on raspberry pi 5.
Did I miss something? :)
The text was updated successfully, but these errors were encountered: