Scratch partition settings not being saved upon reboot running on ESXi 6.7 U2 with Qlogic driver
book
Article ID: 317630
calendar_today
Updated On:
Products
VMware vSphere ESXi
Issue/Introduction
To avoid the scratch partition from reverting to default.
Symptoms:
Scratch partition settings not being saved upon reboot.
ESXi host log show similar to below
syslog.log 2019-08-28T11:55:13Z nativeExecutor[2098830]: mount point '/vmfs/volumes/56f5361d-6590e921-a756-90e2ba1dc0d4/Scratch/fs8-n14.test.com' not restored, waiting 64 seconds 2019-08-28T11:56:17Z nativeExecutor[2098830]: mount point '/vmfs/volumes/56f5361d-6590e921-a756-90e2ba1dc0d4/Scratch/fs8-n14.test.com' not restored before timeout, giving up
In vmkernel.log 2019-08-28T11:53:50.605Z cpu27:2097951)Loading module qlnativefc ... 2019-08-28T11:53:50.609Z cpu27:2097951)Elf: 2101: module qlnativefc has license BSD 2019-08-28T11:53:50.622Z cpu27:2097951)QLogic Fibre Channel HBA Driver: 3.1.8.0-debug 2019-08-28T11:53:50.622Z cpu27:2097951)Device: 192: Registered driver 'qlnativefc' from 20 2019-08-28T11:53:50.622Z cpu27:2097951)Mod: 4962: Initialization of qlnativefc succeeded with module ID 20. 2019-08-28T11:53:50.622Z cpu27:2097951)qlnativefc loaded successfully 2019-08-28T11:54:11.561Z cpu28:2097857)Activating Jumpstart plugin configure-locker. 2019-08-28T11:54:12.852Z cpu28:2097953)qlnativefc: vmhba1(b:0.0): GFO failed, completion status (6). 2019-08-28T11:54:13.025Z cpu49:2098838)qlnativefc: vmhba1(b:0.0): Entering qlnativefcDoSinglethreadWork 2019-08-28T11:54:13.025Z cpu28:2097953)qlnativefc: vmhba1(b:0.0): device wrap (ba0c40)
Note:The preceding log excerpts are only examples.Date,time and environmental variables may vary depending on your environment. Disclaimer:VMware is not responsible for the reliability of any data,opinions,advice or statements made on third-party websites.Inclusion of such links does not imply that VMware endorses,recommends or accepts any responsibility for the content of such sites
Cause
This is a known issue with the Qlogic driver related to GFO(Get Fabric Object) failure particularly with version 3.1.8.
Resolution
To resolve this issue, upgrade to a newer version of Qlogic Driver. To download go to Customer Connect
Workaround: To workaround this issue disable QoS using command and reboot. esxcfg-module -s "ql2xfabricpriorityqos=0" qlnativefc