Tomorrow I am going to a customer site in order to try to find out this:
They successfully install ESXI to a LUN. They then patch the ESXi server, but as soon as they reboot the blade, all patches are lost and it boots up from scratch. Apparently.
I will check out this guide:
But I may need som emore suggestions here.
Could it be that this behaviour happens if they are using the wrong ESXi custom boot image?
Is it possible that the boot order got switched and it booted from a different LUN?
I think I have got it. They proabably forget to remove the mapped ISO-image. So when they boot, it boots up from the ISO-image...Will see tomorrow.
ESXi unmounts itself (vmedia/physical) after installation. I would suspect the SCSI LunID that is masked does not match what is configured in the Service Profile.
When it boots, does it boot into the ESXi loader? I would expect that behaviour if you were booting into the ISO.
Just to be clear, are you doing PXE booting, or just boot from SAN?
This is a known bug in the esxi5.0 if you are using FCOE boot.
http://kb.vmware.com/kb/2031315 UCS Blade loses configuration after reboot in VMware ESXi 5.0.x .
This should be fixed in esx5.1 or you can use local boot disks as a workaround.