https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IyNjg0IiwiaGFzaCI6IjYwZTkzMmJhLTg5MzUtNGMwYS1iN2NlLWZlOTc0NDFlOWRkNiJ9
1-800-691-1991 | 9am - 8pm ET
EN

Failed to mount backup

Challenge

Recovery from backup on a machine running Linux kernel of one of versions 4.0.0-4.1.33 typically fails with ‘FUSE mount is not supported on kernel versions 4.0.0-4.1.33. Upgrade the kernel and try again.’

Cause

FUSE mounts on mentioned kernels fail due to a known kernel bug which was fixed in later versions. General recommendation is to upgrade kernel to a more recent version. However some in distributions fix was backported to older kernels, so you might want to try the following solution first (applicable to Agent for Linux version 2.0 and later only).

Solution

  1. In global configuration file of Agent for Linux – /etc/veeam/veeam.ini – change value of ‘ignoreFuseBug’ parameter from ‘false’ to ‘true’ and uncomment respective line
  2. Restart veeamservice service to apply changes
  3. Retry recovery
KB ID:
2684
Product:
Veeam Agent for Linux
Version:
1.x, 2.0.0.400
Published:
2018-07-11
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later