ESXi Host boot process stuck on "swapobj loaded successfully"
search cancel

ESXi Host boot process stuck on "swapobj loaded successfully"

book

Article ID: 375782

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

The ESXi host boot process hangs after displaying the message "swapobj loaded successfully", leading to boot times that take up to 30 minutes or greater for the ESXi host. 

Environment

ESXi 6.X
ESXi 7.X

Cause

Failed connectivity to NFS storage during the boot process.
Once the boot process completes, the following can be found within the relevant logs. 

- Within /var/log/boot, the plugin "mount-disk-fs" starts after the "swapobj" plugin completes. 

2024-08-26T19:25:57.257Z cpu14:2097685)swapobj loaded successfully.
2024-08-26T19:25:57.258Z cpu47:2097796)Jumpstart plugin tag-boot-bank activated.
2024-08-26T19:25:57.314Z cpu57:2097739)Jumpstart plugin vsan activated.
2024-08-26T19:25:57.318Z cpu58:2097808)Activating Jumpstart plugin vmkapps.
2024-08-26T19:25:57.318Z cpu45:2097711)Activating Jumpstart plugin mount-disk-fs.

- Following the start of the plugin, logs similar to the following, indicating an inability of the ESXi host to connect to the NFS storage

2024-08-26T19:26:27.471Z cpu15:2097685)NFS: 172: NFS mount XXX.XXX.XXX.XXX:/ESXi_Logs failed: Unable to connect to NFS server.
2024-08-26T19:26:27.477Z cpu15:2097685)NFS: 161: Command: (remount) Server: (XXX.XXX.XXX.XXX) IP: (XXX.XXX.XXX.XXX) Path: (/Dir1/Dir2/Dir3) Label: (PROD) Options: (None)
2024-08-26T19:26:27.477Z cpu15:2097685)StorageApdHandler: 966: APD Handle XXXXXXXX-XXXXXXXX Created with lock[StorageApd-0x############]
2024-08-26T19:26:38.471Z cpu0:2098789)SunRPC: 3291: Synchronous RPC cancel for client 0x############ IP XXX.XXX.XXX.XXX proc 3 xid 0x######## attempt 1 of 3
2024-08-26T19:26:38.471Z cpu15:2097685)SunRPC: 3291: Synchronous RPC cancel for client 0x############ IP XXX.XXX.XXX.XXX proc 3 xid 0x######## attempt 1 of 3
2024-08-26T19:26:48.471Z cpu3:2097685)SunRPC: 3291: Synchronous RPC cancel for client 0x############ IP XXX.XXX.XXX.XXX proc 3 xid 0x######## attempt 2 of 3
2024-08-26T19:26:48.471Z cpu4:2098789)SunRPC: 3291: Synchronous RPC cancel for client 0x############ IP XXX.XXX.XXX.XXX proc 3 xid 0x######## attempt 2 of 3
2024-08-26T19:26:58.471Z cpu4:2098789)SunRPC: 3291: Synchronous RPC cancel for client 0x############ IP XXX.XXX.XXX.XXX proc 3 xid 0x######## attempt 3 of 3
2024-08-26T19:26:58.471Z cpu3:2097685)SunRPC: 3291: Synchronous RPC cancel for client 0x############ IP XXX.XXX.XXX.XXX proc 3 xid 0x######## attempt 3 of 3
2024-08-26T19:26:58.471Z cpu3:2097685)SunRPC: 1092: Destroying world 0x######
2024-08-26T19:26:58.471Z cpu4:2098789)SunRPC: 1092: Destroying world 0x######

-Eventually, the following log entry indicating the failure of the plugin to start

2024-08-26T21:01:49.484Z cpu15:2097787)Jumpstart plugin restore-nfs-volumes activation failed: restore-nfs-volumes->start() failed: error while executing the cli

- Within /var/log/jumpstart-stdout.log, a simplified view of the information above

2024-08-26T19:25:57.318Z executing start plugin: mount-disk-fs
2024-08-26T19:25:57.345Z executing start plugin: restore-nfs-volumes
2024-08-26T21:01:49.475Z Executor failed executing esxcli command: boot storage restore --nfs-volumes
2024-08-26T21:01:49.484Z Method invocation failed: restore-nfs-volumes->start() failed: error while executing the cli

Resolution

Investigate the network connectivity between your ESXi host and the NFS storage.