ERROR: Backup of VM 108 failed - job failed with err -61 - No data available

[777rky]

Hello, i have a strange problem, all my vm s (6 vm on node) are bk up ok, only one not working..
Configuration: Proxmox VE 7.2.4
Proxmox Backup Server 2.0




Log from Proxmox VE:

INFO: starting new backup job: vzdump 108 --node davias --notes-template '{{guestname}}, {{node}}, {{vmid}}' --storage PBS --remove 0 --mode snapshot
INFO: Starting Backup of VM 108 (qemu)
INFO: Backup started at 2022-06-06 08:19:45
INFO: status = running
INFO: VM Name: machine
INFO: include disk 'scsi0' 'local-lvm:vm-108-disk-0' 500G
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating Proxmox Backup Server archive 'vm/108/2022-06-06T05:19:45Z'
INFO: started backup task '8173bf14-74e4-4d32-a8fb-e79a33a85b63'
INFO: resuming VM again
INFO: scsi0: dirty-bitmap status: existing bitmap was invalid and has been cleared
INFO: 0% (228.0 MiB of 500.0 GiB) in 3s, read: 76.0 MiB/s, write: 66.7 MiB/s
INFO: 1% (5.0 GiB of 500.0 GiB) in 1m 27s, read: 58.6 MiB/s, write: 58.0 MiB/s
INFO: 2% (10.0 GiB of 500.0 GiB) in 3m 1s, read: 54.3 MiB/s, write: 53.8 MiB/s
INFO: 3% (15.0 GiB of 500.0 GiB) in 4m 41s, read: 51.2 MiB/s, write: 50.3 MiB/s
INFO: 4% (20.0 GiB of 500.0 GiB) in 6m 4s, read: 61.6 MiB/s, write: 61.0 MiB/s
INFO: 5% (25.0 GiB of 500.0 GiB) in 7m 19s, read: 68.4 MiB/s, write: 67.2 MiB/s
...........
INFO: 73% (367.6 GiB of 500.0 GiB) in 1h 41m, read: 67.7 MiB/s, write: 64.1 MiB/s
ERROR: job failed with err -61 - No data available
INFO: aborting backup job
INFO: resuming VM again
ERROR: Backup of VM 108 failed - job failed with err -61 - No data available
INFO: Failed at 2022-06-06 10:00:45
INFO: Backup job finished with errors
TASK ERROR: job errors


Log from Proxmox Backup Server:


2022-06-06T08:19:45+03:00: starting new backup on datastore 'PBS': "vm/108/2022-06-06T05:19:45Z"
2022-06-06T08:19:45+03:00: GET /previous: 400 Bad Request: no valid previous backup
2022-06-06T08:19:45+03:00: created new fixed index 1 ("vm/108/2022-06-06T05:19:45Z/drive-scsi0.img.fidx")
2022-06-06T08:19:45+03:00: add blob "/mnt/datastore/PBS/vm/108/2022-06-06T05:19:45Z/qemu-server.conf.blob" (351 bytes, comp: 351)
2022-06-06T10:00:44+03:00: backup failed: connection error: bytes remaining on stream
2022-06-06T10:00:44+03:00: removing failed backup
2022-06-06T10:00:44+03:00: POST /fixed_chunk: 400 Bad Request: error reading a body from connection: bytes remaining on stream
2022-06-06T10:00:44+03:00: TASK ERROR: connection error: bytes remaining on stream
2022-06-06T10:00:44+03:00: POST /fixed_chunk: 400 Bad Request: backup already marked as finished.

Other log from Proxmox Backup Server at second try to bk same vm:


2022-06-06T02:30:04+03:00: starting new backup on datastore 'PBS': "vm/108/2022-06-05T23:30:04Z"
2022-06-06T02:30:04+03:00: GET /previous: 400 Bad Request: no valid previous backup
2022-06-06T02:30:04+03:00: created new fixed index 1 ("vm/108/2022-06-05T23:30:04Z/drive-scsi0.img.fidx")
2022-06-06T02:30:04+03:00: add blob "/mnt/datastore/PBS/vm/108/2022-06-05T23:30:04Z/qemu-server.conf.blob" (351 bytes, comp: 351)
2022-06-06T04:10:24+03:00: backup ended and finish failed: backup ended but finished flag is not set.
2022-06-06T04:10:24+03:00: removing unfinished backup
2022-06-06T04:10:24+03:00: POST /fixed_chunk: 400 Bad Request: error reading a body from connection: broken pipe
2022-06-06T04:10:24+03:00: TASK ERROR: backup ended but finished flag is not set.


Thank you!

 

[777rky]

someone with this problem?

 

[dcsapak]

the 'no data available' error is most likely from the source, so check if your vm disk is ok, e.g. try to read the whole disk and check for errors

 

[777rky]

the 'no data available' error is most likely from the source, so check if your vm disk is ok, e.g. try to read the whole disk and check for errors

Thank you for answer, i will try to scan with gnome utility or badblocks... but the vm is up and running..

Can you recommend me a tool for scan the disk.. also to repair, thx again

 

[dcsapak]

i'd just try to read the whole disk (e.g. 'cat /dev/sda > /dev/null') since the backup just reads the disk anyway

to repair, this depends on what is wrong and what storage/fs/etc you have. but if the disk/storage is really broken, i'd rather restore from a known good backup

 

[777rky]

What can i do for this?

 

[777rky]

i'd just try to read the whole disk (e.g. 'cat /dev/sda > /dev/null') since the backup just reads the disk anyway

to repair, this depends on what is wrong and what storage/fs/etc you have. but if the disk/storage is really broken, i'd rather restore from a known good backup

The problem is.. i don t have any backup and i can't loose this i post a ss from badblocks

 

[777rky]

any suggestion?

 

[dcsapak]

is that error from the vm or from the host?

in any case, i'd try to make an image of the disk somewhere safe, then try to find out what is actually wrong, and if the disk/storage is broken, try to restore the important data from your image to a new known good storage disk

 

[777rky]

is that error from the vm or from the host?

in any case, i'd try to make an image of the disk somewhere safe, then try to find out what is actually wrong, and if the disk/storage is broken, try to restore the important data from your image to a new known good storage disk

the error is from vm and it runs ubuntu 18..
i have an opensource mail server that runs on that vm, I have also tried to backup from inside the mail server... error can t read disk, the vm is ok for send and receive mail, also for read old e-mails from two years ago...
what can i do to copy the disk, or make an img for this disk.. after that i will try to repair badblocks... but i need to know that the data is safe.

 

[Megaron]

@777rky: I have the same issue on one of my VM‘s. Do you solved your Problem?