Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1399040.1
Update Date:2014-07-25
Keywords:

Solution Type  Technical Instruction Sure

Solution  1399040.1 :   Sun Storage 7000 Unified Storage System: Recovery of 7x10 Appliance from Installation of Unsupported BIOS Release 3.x  


Related Items
  • Sun Storage 7110 Unified Storage System
  •  
  • Sun Storage 7210 Unified Storage System
  •  
  • Sun Storage 7410 Unified Storage System
  •  
  • Sun Storage 7310 Unified Storage System
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>ZFS Storage>SN-DK: 7xxx NAS
  •  
  • _Old GCS Categories>Sun Microsystems>Storage - Disk>Unified Storage
  •  




In this Document
Goal
Solution
References


Oracle Confidential PARTNER - Available to partners (SUN).
Reason: Typically requires a 7000 trained field engineer

Applies to:

Sun Storage 7210 Unified Storage System - Version All Versions and later
Sun Storage 7110 Unified Storage System - Version All Versions and later
Sun Storage 7410 Unified Storage System - Version All Versions and later
Sun Storage 7310 Unified Storage System - Version All Versions and later
7000 Appliance OS (Fishworks)

Goal

How to recover an S7x10 series NAS appliance following installation of unsupported BIOS release 3.x

This Document does NOT apply to the 7x20 Series or later.

Solution

Occasionally (due to an unsupported procedure), the NAS 7x10 Series gets updated with a version of 3.x BIOS.  This version is currently not supported on these models.

Please review the Oracle document 1174698.1  How to check the SP BIOS revision level  to see if your 7x10 is affected.

Once the correct version has been confirmed for your 7[134]10 NAS and you need to re-install you can go to My Oracle Support and download it via the 'Patches & Updates' tab.

Once you have the correct package and have updated the BIOS to the correct 2.X version (see 1357354.1  How to update the BIOS for a 7x10 NAS appliance)

Caution! : If you see this message during the upgrade ;

Cannot restore /conf for this version
upgrade failed: The config matching this version cannot be restored


CR 7002718 describes this issue and the workaround is to uncheck "Preserve Configuration":

[ PLEASE NOTE: If "Preserve Configuration" is unchecked, then the Service Processor network configuration will be lost - not the appliance network configuration which will remain untouched.  The customer/user has then to be onsite for this, so that he re-configure the SP network settings via the serial port. ]

Details from the CR -

There is only one case that you can downgrade ILOM from 3.x to 2.x successfully with preserving configurations:

1. The original ILOM loaded in SP is ILOM 2.x.

2. Then the ILOM is upgraded to ILOM 3.x with preserving configurations.  (In this upgrade, old configurations in ILOM 2.x will be saved in "/persist/conf.v2.0.tgz")

3. Downgrade ILOM from ILOM 3.x to ILOM 2.x with preserving configurations.   (In this downgrade, ILOM will try to find the old configurations from "/persist/conf.v2.0.tgz")

The step 8 in "Load SP Firmware/BIOS":

    "Confirm that "Preserve existing configuration" is checked for the SP Firmware."   should be   "Confirm that "Preserve existing configuration" is not checked for the SP Firmware."


After applying the package you need to check the BIOS settings as follows:

Sun Storage 7310 example:

Disable PCIPnP Option-ROM scanning for all slots Disable I/O allocation Configure boot drives. Use the right arrow key to page over to "PCIPnP" menu. Use the down arrow to highlight:

Scanning OPROM on PCI-E Slot0 Enabled

Press return and select "Disabled", followed by return. This will now appear as:

Scanning OPROM on PCI-E Slot0 Disabled

Repeat this for slots 1-2. You should now have:

Scanning OPROM on PCI-E Slot0 Disabled
Scanning OPROM on PCI-E Slot1 Disabled
Scanning OPROM on PCI-E Slot2 Disabled

Just below these OPROM settings are a group of settings which allow IO allocation to be disabled per-slot. Disable PCI-E slots 1 and 2. Only slot 0 should be enabled. It should look like:

IO Allocation on PCI-E Slot0 Enabled
IO Allocation on PCI-E Slot1 Disabled
IO Allocation on PCI-E Slot2 Disabled

Next, Use the arrow keys to navigate to the Boot menu and select the last item: "Hard Disk Drives" and press return. The list should include only 2 drives (the 2 internal SATA drives) with labels like:

SATA:11M-<drive model>
SATA:12M-<drive model>

If this list includes anything else (such as Readzilla cache devices with a 'STEC MACH8' string, or JBOD attached drives) you will need to remove them from the list by selecting the boot position and setting it to 'Disabled' for each non-boot drive.

Exiting BIOS Setup

Once you've removed any Readzilla cache or JBOD drive entries from the "Hard Disk Drives" list, perform the following;

- Press ESC to exit the "Hard Disk Drives" menu, then arrow right to the "Exit" menu.
- Press for the default "Save Changes and Exit", and return again to confirm the action with the pop up.

On boot, you will see the following warning message from the BIOS:

Warning: IO resource not allocated

This is an expected message and does not indicate a failure.

 

References

<NOTE:1357354.1> - Sun Storage 7000 Unified Storage System: How to Update the BIOS for a 7x10 NAS Appliance
<NOTE:1174698.1> - Sun Storage 7000 Unified Storage System: How to check the SP BIOS revision level

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback