#1 Global Leader in Data Protection & Ransomware Recovery

Backup fails with "Invalid argument Asynchronous request operation has failed. Failed to open storage for read/write access"

KB ID: 4586
Product: Veeam Backup & Replication | 12 | 12.1
Published: 2024-05-31
Last Modified: 2024-05-31
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Challenge

When attempting to write a restore point (VBK or VIB) to a Linux repository with a 4k logical block size, the task fails with the error:

Invalid argument Asynchronous request operation has failed. Failed to open storage for read/write access

Cause

This error occurs when the storage device is formatted with a 4k logical block size and the Veeam Data Mover Service does not have sufficient permissions to determine the logical block size.

On a Linux repository, the Veeam Data Mover Service must have read access to the following file for each device where a restore point would be written:

/sys/dev/block/{id}/queue/logical_block_size

If the Veeam Data Mover Service cannot access this file to determine the device's logical block size, the service will use the default file system block size of 512 bytes. However, if the block size is actually 4096 bytes, this usage of 512 bytes will cause the operation to fail.

Solution

To prevent this issue, ensure that the user account used to install the Veeam Data Mover service is able to read the logical block size of each device (/sys/dev/block/{id}/queue/logical_block_size).

 

Check Permissions

On the Linux repository, check the current permissions using the following command:

 ls -lah /sys/dev/block/*/queue/logical_block_size
[backupsvc@rhel9 ~]$ ls -lah /sys/dev/block/*/queue/logical_block_size
-r--r--r--. 1 root root 4.0K May 29 16:37 /sys/dev/block/11:0/queue/logical_block_size
-r--r--r--. 1 root root 4.0K May 29 16:38 /sys/dev/block/253:0/queue/logical_block_size
-r--r--r--. 1 root root 4.0K May 29 16:38 /sys/dev/block/253:1/queue/logical_block_size
-r--r--r--. 1 root root 4.0K May 29 16:38 /sys/dev/block/8:0/queue/logical_block_size

In this example, the permissions for all block devices are as required.

 

Set Permissions

If any entry did not have -r--r--r--r (444) permissions, update and run the following command to assign it those permissions.

sudo chmod 444 /sys/dev/block/x:y/queue/logical_block_size 

More Information

For other requirements and limitations affecting services installed on managed Linux servers, see Veeam Data Mover Service and Linux Server
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.