ESX 3.5 reboot fails after upgrade from 3.2

[jalyn14]

After upgrading from 3.2 to 3.5 I am getting this error:

cpu2: 1035) Mod: 1413: Initialization for vmfs3 failed with -1

cpu2: 1035)Util: 874: Failed trying to get a valid VMKernel MAC address: Failure. Various vmkernel subsystems will provide a lower quality service

cpu2: 1035)Mod: 1413: Initialization for lvmdriver failed with -1.

Can someone help??

[Texiwill]

Hello,

Reboot under Debug mode and run 'esxcfg-boot -r' to recreate the initrd image for the host.

Best regards,
Edward L. Haletky
VMware Communities User Moderator, VMware vExpert 2009
====
Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.
Blue Gears and SearchVMware Pro Blogs -- Top Virtualization Security Links -- Virtualization Security Round Table Podcast