Need help?

Our experts have had an average response time of 13.52 minutes in October 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

Openvz “Failed to mount image” – How to fix

by | Jun 5, 2021

Wondering how to fix Openvz “Failed to mount image” error? We can help you.

At times while trying to start Container we may end up with a “Failed to mount image” error.

Here at Bobcares, we often handle requests from our customers to fix similar errors as a part of our Server Management Services. Today we will see how our support engineers fix this for our customers.

What causes Openvz “Failed to mount image” error

Before going into the steps for fixing this error we will see what causes this error.

A typical error may look like the one given below:

Openvz Failed to mount image

The container’s mount fails due to file system errors inside the ploop virtual disk.

Steps to fix Openvz “Failed to mount image” error

Firstly, we must run the check disk.

Then to run fsck, follow the following steps:

1. Ensure that the container is stopped by using the following commands:

~# vzctl stop 101
~# vzlist 101
101 - stopped fsck.test

Note: Do not perform fsck when the container is running or mounted.

2. Mount the container’s ploop image. This allocates a ploop device on the host:

~# ploop mount /vz/private/101/root.hdd/DiskDescriptor.xml
add delta dev=/dev/ploop12345 img=/vz/private/101/root.hdd/root.hds (rw)

3. Run fdisk -l for the /dev/ploopX device reported by the previous command.
We will need to let the system fetch a list of partitions on /dev/ploopX:

~# fdisk -l /dev/ploop12345
WARNING: GPT (GUID Partition Table) detected on '/dev/ploop12345'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/ploop12345: 10.7 GB, 10737418240 bytes
255 heads, 63 sectors/track, 1305 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot      Start         End      Blocks   Id  System
/dev/ploop12345p1               1        1306    10485759+  ee  GPT

4. After that we will perform a file system check for the partition reported in the previous command’s output (note p1 at the end):

 ~# e2fsck /dev/ploop12345p1
e2fsck 1.41.12 (17-May-2010)
/dev/ploop12345p1: clean, 22404/655360 files, 238012/2620923 blocks

Note: We can add more options to e2fsck, check the manual pages if needed.

5. Now we can unmount the ploop image with the following commands:

~# ploop umount -d /dev/ploop12345
Unmounting device /dev/ploop12345

6. Finally, we can start the container using the following:

~# vzctl start 101

[Need assistance? We can help you]


In short, we saw how our Support Techs fix Openvz “Failed to mount image”  error for our customers.



Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.


var google_conversion_label = "owonCMyG5nEQ0aD71QM";


Submit a Comment

Your email address will not be published. Required fields are marked *


Privacy Preference Center


Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]


Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid


Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie


These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.