<font size=2 face="sans-serif">Jared,</font>
<br>
<br><font size=2 face="sans-serif">if time permits i would open a PMR to
check what happened. as i stated in my first email it could be multiple
things, the GPT restore is only one possible of many explanations and some
more simple reasons could explain what you see as well. get somebody from
support check the state and then we know for sure. it would give you also
peace of mind that it doesn't happen again when you are in production.</font>
<br><font size=2 face="sans-serif">if you feel its not worth and you don't
wipe any important information start over again.</font>
<br>
<br><font size=2 face="sans-serif">btw. the newer BIOS versions of IBM
servers have a option from preventing the GPT issue from happening : </font>
<br>
<br><font size=2 face="sans-serif">[root@gss02n1 ~]# asu64 showvalues DiskGPTRecovery.DiskGPTRecovery</font>
<br><font size=2 face="sans-serif">IBM Advanced Settings Utility version
9.61.85B</font>
<br><font size=2 face="sans-serif">Licensed Materials - Property of IBM</font>
<br><font size=2 face="sans-serif">(C) Copyright IBM Corp. 2007-2014 All
Rights Reserved</font>
<br><font size=2 face="sans-serif">IMM LAN-over-USB device 0 enabled successfully.</font>
<br><font size=2 face="sans-serif">Successfully discovered the IMM via
SLP.</font>
<br><font size=2 face="sans-serif">Discovered IMM at IP address 169.254.95.118</font>
<br><font size=2 face="sans-serif">Connected to IMM at IP address 169.254.95.118</font>
<br><font size=2 face="sans-serif">DiskGPTRecovery.DiskGPTRecovery=<b><u>None</u></b>=<Automatic></font>
<br>
<br><font size=2 face="sans-serif">if you set it the GPT will never get
restored. you would have to set this on all the nodes that have access
to the disks.</font>
<br>
<br><font size=2 face="sans-serif">------------------------------------------<br>
Sven Oehme <br>
Scalable Storage Research <br>
email: oehmes@us.ibm.com <br>
Phone: +1 (408) 824-8904 <br>
IBM Almaden Research Lab <br>
------------------------------------------</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Jared David Baker <Jared.Baker@uwyo.edu></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">gpfsug main discussion
list <gpfsug-discuss@gpfsug.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">10/29/2014 10:30 AM</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [gpfsug-discuss]
Server lost NSD mappings</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">gpfsug-discuss-bounces@gpfsug.org</font>
<br>
<hr noshade>
<br>
<br>
<br><font size=2 color=#004080>Thanks for all the information. I’m not
exactly sure what happened during the firmware update of the HCAs (another
admin). But I do have all the stanza files that I used to create the NSDs.
Possible to utilize them to just regenerate the NSDs or is it consensus
that the FS is gone? As the system was not in production (yet) I’ve got
no problem delaying the release and running some tests to verify possible
fixes. The system was already unmounted, so it is a completely inactive
FS across the cluster.</font>
<br><font size=2 color=#004080> </font>
<br><font size=2 color=#004080>Thanks,</font>
<br><font size=2 color=#004080> </font>
<br><font size=2 color=#004080>Jared</font>
<br><font size=2 color=#004080> </font>
<br><font size=2 face="Tahoma"><b>From:</b> gpfsug-discuss-bounces@gpfsug.org
[</font><a href="mailto:gpfsug-discuss-bounces@gpfsug.org"><font size=2 face="Tahoma">mailto:gpfsug-discuss-bounces@gpfsug.org</font></a><font size=2 face="Tahoma">]
<b>On Behalf Of </b>Sven Oehme<b><br>
Sent:</b> Wednesday, October 29, 2014 11:23 AM<b><br>
To:</b> gpfsug main discussion list<b><br>
Subject:</b> Re: [gpfsug-discuss] Server lost NSD mappings</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=3 face="Times New Roman">if you still have a running system
you can extract the information and recreate the descriptors. </font>
<br><font size=3 face="Times New Roman">if your sytem is already down,
this is not possible any more. </font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=3 face="Times New Roman">which is why i suggested to open
a PMR as the Support team will be able to provide the right guidance and
help . </font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=3 face="Times New Roman">Sven</font>
<br><font size=3 face="Times New Roman"> </font>
<br><font size=3 face="Times New Roman">On Wed, Oct 29, 2014 at 10:19 AM,
Jonathan Buzzard <</font><a href=mailto:jonathan@buzzard.me.uk target=_blank><font size=3 color=blue face="Times New Roman"><u>jonathan@buzzard.me.uk</u></font></a><font size=3 face="Times New Roman">>
wrote:</font>
<br><font size=3 face="Times New Roman">On Wed, 2014-10-29 at 09:42 -0700,
Sven Oehme wrote:<br>
> Hello,<br>
><br>
><br>
> there are multiple reasons why the descriptors can not be found .<br>
><br>
><br>
> there was a recent change in firmware behaviors on multiple servers<br>
> that restore the GPT table from a disk if the disk was used as a OS<br>
> disk before used as GPFS disks. some infos<br>
> here : </font><a href="https://www.ibm.com/developerworks/community/forums/html/topic?id=27f98aab-aa41-41f4-b6b7-c87d3ce87b9e" target=_blank><font size=3 color=blue face="Times New Roman"><u>https://www.ibm.com/developerworks/community/forums/html/topic?id=27f98aab-aa41-41f4-b6b7-c87d3ce87b9e</u></font></a><font size=3 face="Times New Roman"><br>
><br>
><br>
> if thats the case there is a procedure to restore them.<br>
<br>
I have been categorically told by IBM in no uncertain terms if the NSD<br>
descriptors have *ALL* been wiped then it is game over for that file<br>
system; restore from backup is your only option.<br>
<br>
If the GPT table has been "restored" and overwritten the NSD
descriptors<br>
then you are hosed.<br>
<br>
JAB.<br>
<br>
--<br>
Jonathan A. Buzzard
Email: jonathan (at) </font><a href=http://buzzard.me.uk/ target=_blank><font size=3 color=blue face="Times New Roman"><u>buzzard.me.uk</u></font></a><font size=3 face="Times New Roman"><br>
Fife, United Kingdom.<br>
</font>
<br><font size=3 face="Times New Roman">_______________________________________________<br>
gpfsug-discuss mailing list<br>
gpfsug-discuss at </font><a href=http://gpfsug.org/ target=_blank><font size=3 color=blue face="Times New Roman"><u>gpfsug.org</u></font></a><font size=3 color=blue face="Times New Roman"><u><br>
</u></font><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss" target=_blank><font size=3 color=blue face="Times New Roman"><u>http://gpfsug.org/mailman/listinfo/gpfsug-discuss</u></font></a>
<br><font size=3 face="Times New Roman"> </font><tt><font size=2>_______________________________________________<br>
gpfsug-discuss mailing list<br>
gpfsug-discuss at gpfsug.org<br>
</font></tt><a href="http://gpfsug.org/mailman/listinfo/gpfsug-discuss"><tt><font size=2>http://gpfsug.org/mailman/listinfo/gpfsug-discuss</font></tt></a><tt><font size=2><br>
</font></tt>
<br>