Question

Kernel Panic not syncing: VFS: Unable to mount root fs on unknown block(0,0)

  • 25 June 2020
  • 3 replies
  • 340 views

Has anyone else had an issue with installing the lated CE image on esxi7? It seems to shutdown after the hypervisor is created and begins the startup. After you reboot and attempt to run it in regular mode I get this message:

 

If I go into safe mode I get the login prompt with the host name configured:

 

I performed a “virsh list --all” in safe mode to get the following:

 

When is attempt to start the vm in safe mode, the host machine shuts down:

 

 

 

Any Ideas?


3 replies

Userlevel 4
Badge +3

Hey, @breakscience so generally this error can be due to some problems in the OS itself after a suspected kernel upgrade did not complete successfully on the CVM.

Also, what is the version of AOS,AHV running on the cluster?

Can you go and check the CVM logs on the ESXi host inside:

vmfs/volumes/<xxxxxxxx-xxxxxxx-c1d2-111122223333/<NTNX-CVM>/vmware.log

And go to the end of the log file and check for any relevant messages related to the issue and paste them here.

I didn’t see anything unusual in the logs. You can see the closing of the session, but nothing more (see bold info below).

2020-06-27T23:54:45.867Z| vcpu-0| I125: pciBridge7:7: ISA/VGA decoding enabled (ctrl 0004)sdf

2020-06-27T23:54:46.371Z| vcpu-0| I125: Ethernet0 MAC Address: 00:50:56:a2:cf:e5

2020-06-27T23:54:46.371Z| vcpu-0| I125: VMXNET3 user: Ethernet0 RSS fields requested by vmx: 3

2020-06-27T23:54:46.371Z| vcpu-0| I125: VMXNET3 user: Supported set 0x0000003f, configured set 0x00000002

2020-06-27T23:54:46.670Z| vcpu-0| I125: HBACommon: First write on scsi0:0.fileName='/vmfs/volumes/5ec3d6d4-12e4be65-d2ab-305a3a56355d/ntx-ce-v511/ntx-ce-v511.vmdk'

2020-06-27T23:54:46.671Z| vcpu-0| I125: DDB: "longContentID" = "4521a6a705e530a81442b72f8f10e652" (was "2de2fc2959fb63d9030e94d1405e9981")

2020-06-27T23:54:46.676Z| vcpu-0| I125: DISKLIB-CHAIN : DiskChainUpdateContentID: old=0x405e9981, new=0x8f10e652 (4521a6a705e530a81442b72f8f10e652)

2020-06-27T23:54:47.323Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 0 starting feature 0

2020-06-27T23:54:47.323Z| vcpu-0| I125: CDROM: Emulate GET CONFIGURATION RT 0 starting feature 0

2020-06-27T23:54:47.488Z| vcpu-0| I125: Guest MSR write (0x49: 0x1)

2020-06-27T23:54:52.085Z| vcpu-1| I125: VMXNET3 user: Ethernet0 Driver Info: version = 17040640 gosBits = 2 gosType = 1, gosVer = 0, gosMisc = 0

2020-06-27T23:54:52.085Z| vcpu-1| I125: VMXNET3 user: Activate request succeeds for device 0.

2020-06-27T23:55:18.301Z| mks| I125: SOCKET 10 (126) Received websocket close frame with empty status code

2020-06-27T23:55:18.301Z| mks| I125: SOCKET 10 (126) Sending websocket close frame, status code = 1000

2020-06-27T23:55:18.301Z| mks| I125: SOCKET 10 (126) VNC Remote Disconnect: socket closed.

2020-06-27T23:55:18.301Z| mks| I125: MKSControlMgr: Remove VNC connection 1

2020-06-27T23:55:18.301Z| mks| I125: MKSRemoteMgr: CleanupConnection (numConsoles=0)

2020-06-27T23:55:44.136Z| vmx| I125: MKSVMX: Vigor requested a screenshot

2020-06-27T23:55:44.141Z| svga| I125: MKSScreenShotMgr: Taking a screenshot

2020-06-27T23:56:44.139Z| vmx| I125: MKSVMX: Vigor requested a screenshot

2020-06-27T23:56:44.141Z| svga| I125: MKSScreenShotMgr: Taking a screenshot

the installer log only contained the following: 

 

Reply