When executing the ilorest tool on an ESXi host, you may encounter the error OSError: [Errno 28] No space left on device.
Example of command execution:
# export TMP=/usr/local/tmpdir
# /opt/ilorest/bin/ilorest.sh --nologo
iLOrest > login
Discovering data...Done
ERROR : Exception occurred while executing command.
OSError: [Errno 28] No space left on device
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/opt/ilorest/bin/rdmc.py", line 715, in cmdloop
self.retcode = self._run_command(opts, nargv, help_disp=False)
File "/opt/ilorest/bin/rdmc.py", line 435, in _run_command
return cmd.run(args[1:], help_disp=help_disp) if len(args) > 1 else cmd.run([], help_disp=help_disp)
File "/opt/ilorest/bin/extensions/COMMANDS/LoginCommand.py", line 108, in run
self.loginfunction(line)
File "/opt/ilorest/bin/extensions/COMMANDS/LoginCommand.py", line 288, in loginfunction
self.perform_login(options, skipbuild, user_ca_cert_data, args, app_obj)
File "/opt/ilorest/bin/extensions/COMMANDS/LoginCommand.py", line 126, in perform_login
self.rdmc.app.login(
File "/opt/ilorest/bin/redfish/ris/rmc.py", line 307, in login
self.save()
File "/opt/ilorest/bin/redfish/ris/rmc.py", line 203, in save
self._cm.cache_rmc()
File "/opt/ilorest/bin/redfish/ris/rmc_helper.py", line 420, in cache_rmc
indexfh.close()
OSError: [Errno 28] No space left on device
Error accessing the file path. Verify the file path is correct and you have proper permissions.
iLOrest > exit
Logging session out.
ESXi 8.0
This error indicates insufficient disk space on a specific file system within the ESXi host.
To resolve this issue, please follow the steps below:
1. Check File System Usage: Run the df -h command or the esxcli system visorfs ramdisk list command to identify which file system or ramdisk is full.
2. Free Up Space: Identify and remove unnecessary files from the affected file system to reclaim space.
Note:
Since ilorest is a third-party tool developed by HPE, specific details regarding which directory or partition the tool was attempting to access during the operation must be confirmed with the vendor.
Contact the appropriate support channel for the ilorest tool to determine the exact cause of the file system overflow triggered by the tool.