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-79-1628947.1
Update Date:2018-03-26
Keywords:

Solution Type  Predictive Self-Healing Sure

Solution  1628947.1 :   Sun Fire X2270 M2 Server Symptoms and Solutions  


Related Items
  • Sun Fire X2270 M2 Server
  •  
Related Categories
  • PLA-Support>Sun Systems>x86>Server>SN-x64: SERVER 64bit
  •  




In this Document
Purpose
Details


Applies to:

Sun Fire X2270 M2 Server
Information in this document applies to any platform.

Purpose

This document outlines the top non-hardware issues our customers encounter on the Sun Fire X2270 M2 Server, with the firmware version which fixes that issue or the workaround


These issues are outlined in more detail on the internal Sun Fire X2270 M2 Current Product Issues <Document: 1353759.1>

Details

Documentation Sun Fire X2270 M2 Server - Patches & Firmware Sun Fire X2270 M2 Server - My Oracle Support Community (MOSC) Sun x86 Systems - Oracle System Handbook Sun Fire X2270 M2 Server 

 

SymptomDetailsResolution/Workaround
SUSE Linux Enterprise Server 10 SP3 won't boot on 2TB harddisk

SLES 10 SP3 will create a GPT partition(about 7.84MB) in 2TB HDD by default partitioning.But the BIOS on Wasp is still the legacy BIOS which doesn't support the GPT partition. This issue only happens with SLES10 SP3. It does not happen with SLES11,SLES11 SP1 or newer

Workaround: Create a explicit(seperate) partition "/boot" and put it ahead of the root partition. It is a grub limitation.

 

 ACPI warning messages:"\_SB_:_OSC invalid UUID"

ACPI warning logged in dmesg:

[    2.701764] ACPI: EC: Look up EC in DSDT
[    2.712788] \_SB_:_OSC invalid UUID
[    2.712793] _OSC request data:1 7
[    2.713675] ACPI: Executed 1 blocks of module-level executable AML code

This happens on SUSE Linux Enterprise Server 11 SP1

Solution: Issue fixed in ILOM 3.0.9.20.c r65614 BIOS vers. 2.07 or later
 ILOM rescan/reset periodically all 19 to 21 days The ILOM performs an ILOM resets/rescan every 19 to 21 days. This may cause the installed OS to crash.  Solution: Issue fixed in ILOM 3.0.9.20.c r65614 BIOS vers. 2.07 or later

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