Version is 7.0.2.00200
When I run "/bin/firmwareConfig.py --backup /tmp", below error was shown.
Saving current state in /tmp/firmware-backup.$$
Clock updated.
Time: 08:35:15 Date: 01/18/2022 UTC
Traceback (most recent call last):
File "./firmwareConfig.py", line 324, in <module>
sys.exit(main(sys.argv[1:]))
File "./firmwareConfig.py", line 307, in main
configBundle = backupConfig(options.backup)
File "./firmwareConfig.py", line 138, in backupConfig
bootCfg = BootCfg(BOOT_CFG_PATH)
File "/lib64/python3.8/site-packages/vmware/esximage/Utils/BootCfg.py", line 89, in __init__
self.parse(f)
File "/lib64/python3.8/site-packages/vmware/esximage/Utils/BootCfg.py", line 126, in parse
fobj = open(f, "rb")
FileNotFoundError: [Errno 2] No such file or directory: '/bootbank/boot.cfg'
Then I found that the symbolic link of "bootbank" in "/" is pointed to a non-exist folder.
lrwxrwxrwx 1 root root 49 Nov 18 11:21 bootbank -> /vmfs/volumes/7e6f30d7-8f4165e4-e287-5145a583d99b
[root@Host1:/vmfs/volumes] ls
5d1ab746-6464d39a-ba1f-08f1eaeae522 5d1dae96-6d936c7e-6f4d-08f1eaeae732 ESXLOG
5d1ab75b-9be46932-41d7-08f1eaeae522 Data01 Heartbeat
[root@Host1:/vmfs/volumes]
That's weird. It was a newly installed ESXi in June last year, it wasn't upgraded from older version. How on earth it created symbolic link that are linked to nowhere.
