Link to home
Start Free TrialLog in
Avatar of compdigit44
compdigit44

asked on

ESXi 5.1 Core Dump Partition Missing

We are testing new Cisco UCS B200 blades which are setup to boot from SAN. Granted this is my first time boot from SAN so this whole process has been a great learning experience. Anyway We have a small 20GB boot lun which then has the remain portion as a local datastore (again just for testing). Once of our blades has a hardware failure so the boot profiles and was assigned to another host. The host boot without issue the both is when is came up it stated the core dump partition was not set. After searching on the internet I was able to reset and enable the core dump partition again.

Now I am trying to understand why this happened?
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Now I am trying to understand why this happened?


Are these CLONED LUNs ?
Avatar of compdigit44
compdigit44

ASKER

Yes , but the only thing that changed it that the "profile" was moved from on host to any other????

I have more experience with IBM blades that Cisco
Disk or Partition information for the core dump partition was different to what is was expecting.
Thank you for your reply...

This is the part the confuses me if in Cisco UCS when is all profile driven. You can move a profile from one physical blade to another with all the settings. So there should not be any difference
Since this is boot from San setup on the master image I used partedUtil to remove datastore1 since this would not detect on new host.. I am wondering if the core dump is stored on another partition other than VMFS which I deleted.. Then again if I it was created on another volume ... and I did remove if from the master image I would probably be in the same position an getting the core dump missing warning and need to recreate it anyway...

thoughts
Very interesting but here is my thought... Even if removed the proper partition using partedUtil when the boot image is cloned and present to a new host. I would still get the core dump is missing message. So in my mind there is really point of going back and removing the partiton since it will need to be recreated anyway correct. Would not doing this cause a problem later on
I would create on a per host basis.

it will not be an issue, core dump can be a partition or a file.
so leaving the master image as it and resting the diag partition would not be a problem then would not be a problem.  Am I correct that I would get the same warning message about the core dump missing even if I removed it from the master image... Still would need to recreate it. correct
ASKER CERTIFIED SOLUTION
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
thank!!!!!

Once again this grasshooper has learned something from the grand master..... LOL