Server esxi báo lỗi insufficient disk space insufficient disk space

Actually for snapshots to consolidate they will need some free space. If things are not running at the moment, you can sutdown another working VM that does not need snapshots consolidated - migrate it to another datastore and bring it back online, this will give you some space on the original datastore to allow the other VM to consolidate.

If its not a snapshot issue and its simply a full datastore, then you will have to juggle VM's around so that you can expand your datastores.

Was this post helpful? thumb_up thumb_down

During a conversion to a VMware Infrastructure/ESX 3 Server, the "Create Virtual Machine" step goes into a recoverable error with the following message:

The CreateVM_Task submitted to the VMware ESX server failed: Insufficient disk space on datastore

The CreateVM_Task submitted to the VMware ESX server failed: A general system error occurred: The file is too big for the filesystem

The above error will occur if any of the following is true:

1. There is not enough disk space on the target host to create the .vmdk file
2. The block size of the VMFS partition needs to be increased to support the desired size of the .vmdk

The default configuration of the VMFS File System on a VMware Infrastructre/ESX 3 Server uses a block-size of 1 MB - which limits any individual .vmdk file to a maximum size of 256 GB.

Resolution

In order to be able to create a virtual disk with a size greater than 256 GB, the VMFS File System must be configured to use a larger block-size such as 2 or 4 MB.

Please note that in order to apply the larger block size change, users will need to do one of the following:

1. Create a new VMFS partition with the larger block size
2. Re-format the existing VMFS partition to apply the large block size change

If you have any questions regarding this article, please contact PlateSpin Support at: [email protected]

Error 28 No space left on device ESXi can occur due to various factors that lead to storage constraints on the ESXi host. Here are the main causes:

• Insufficient Disk Space: The most common cause is inadequate available disk space on the ESXi host. As VMs, snapshots, logs, and other data accumulate, they consume valuable storage, leading to space constraints.
• VM Snapshot Accumulation: While snapshots are valuable for restoring VM states, they can consume significant disk space if not managed efficiently. Large or numerous snapshots can exhaust storage resources, so you could not power on virtual machine No space left on device.
• Improper Resource Allocation: Mismanagement of virtual machine resources, such as overprovisioning storage, can lead to space constraints on the ESXi host.
• Abandoned or Failed VM Deletion: Improperly deleted or failed VMs may leave remnants behind, further reducing available disk space.

How to troubleshoot ESXi No space left on device

While updating or removing ESXi host with command line, you may encounter No space left on device ESXi update while updating VMware ESXi servers by using the "esxcli software vib update" command. Sometimes, the issue persists despite the fact that the df -h command confirms that the discs are functioning properly and have sufficient free space.

See below for a screenshot of the output including the reported error:

In response, df -h output disputes this assertion, stating that there is sufficient space in these volumes.

✧ A lack of inodes file objects

The file system structures are called inodes, and a single VMFS volume can have up to 640 000 of them. How many files are retained in the file system at any given time determines how many inodes are being used.

1. Check the number of available inodes with stat -f / command:

2. Check the number of available inodes by executing the df -I command:

$ df –i

Filesystem Inodes IUsed IFree IUse% Mounted on

/dev/sda1 942080 507361 11 100% /

As you can see, it is extremely unlikely that you would exceed this number, but if you do, simply delete some files from the ESXi host.

✧ Excessive files on ESXi

ESXi may contain log files that are more than 50 MB in size as well as additional files that are not stored on VMFS volumes. The following command will help you locate these files while avoiding failing to expand VMFS datastore:

find / -path "/vmfs" -prune -o -type f -size +50000k -exec ls -l '{}' \;

Following the execution of the command, a list of local files, including ISO images, large log files, etc., will be generated. If you no longer require any of that information, you can delete it or send it to storage for future reference.

✧ A lack of RAM on ESXi host

In essence, the host is unable to allocate adequate RAM for upgrading. Enabling the ESXi system swap on a different datastore, where RAM will be flashed during updates if the problem arises, will fix this issue.

1. Navigate to Manage >> Settings >> System Swap to turn on the ESXi system swap. Then click Edit.

2. Specify the datastore and click OK. In Edit Host Profiles, you can additionally specify the datastore for memory paging:

3. After choosing the datastore for the system swap, update and restart the ESXi host.

Batch backup ESXi VMs for data protection

To ensure the protection and recovery of your ESXi virtual machines and data, it is essential to perform batch backups regularly. AOMEI Cyber Backup is a powerful VMware backup software that can help you manage your ESXi virtual machines and data seamlessly.

To perform batch backups, you can use AOMEI Cyber Backup to create backup tasks for multiple VMs simultaneously. This feature is particularly useful for businesses with a large number of virtual machines to manage. Of course, it also offers some other benefits as follows:

◈ Agentless Backup: Create complete and independent image-level backup for VMware ESXi VMs. ◈ Schedule Backup: Auto backup virtual machines on regular basis to protect VMware workloads continuously. ◈ Instant Recovery: Once the VMware crashes, quickly restore VMware to normal state and reduce business-critical downtime. ◈ Role Assignment: Allows one administrator to create sub-accounts with limited privileges.

Please get and set up the agentless backup program - AOMEI Cyber Backup and you can use the following free trial for 30 days:

*You can choose to install this VM backup software on either Windows or Linux system.

Simple steps to backup multiple VMware ESXi VMs

1. Access to AOMEI Cyber Backup web client, and add vCenter or Standalone ESXi hosts as the source device. Then click Backup Task >> Create New Task.

2. In the task wizard, enter a name and select the virtual machines for backup.

3. After that, set the Task Name, Device, Target, Schedule and Cleanup according to your need.

• Schedule (optional): Choose to perform full, differential or incremental backup, and automate execution daily, weekly or monthly according to the frequency you specified.

• Cleanup (optional): Configure a retention policy to auto delete old backup files and save storage space.

4. Click Start Backup and choose Add the schedule and start backup now or Add the schedule only.

5. Once the backup is complete, the restore process is also very simple. Navigate to Start Restore, you can change restore location here to create a new VM or another datastore/host.

Conclusion

In conclusion, maintaining sufficient storage virtualization space and regularly performing backups are critical measures for protecting data and ensuring the stability of your ESXi host. The ESXi No space left on device error highlights the importance of monitoring disk space and taking proactive steps to prevent data loss.

Additionally, securing data through measures like encryption and access controls can further protect against data breaches and other security threats. By implementing these best practices, you can safeguard your valuable data and maintain the integrity and reliability of your ESXi host.