Fujitsu M10 Product Notes page 116

Table 3-11 Problems resolved in XCP 2220 (continued)
SPARC M10-
RTI No. 1 4 4S
RTIF2- x x x
140507-001
RTIF2- x
140507-002
Fujitsu M10/SPARC M10 Systems Product Notes for XCP Version 2240 ･ March 2015
102
Description
In a SPARC M10 system with XCP 2043
or newer, when a disk failure occurs due
to its removal from a hardware RAID
(RAID1 or RAID1E), if the state of the
Open Boot PROM is transitioned due to
the execution of input power off/on,
rebooting of Oracle Solaris or the
execution of the "shutdown -i0"
command, even after the restoration of
the disk, it is not placed in the original
RAID volume but in another RAID
volume. Moreover, the original RAID
volume stays in the degraded state.
If the system board is deleted by dynamic
reconfiguration of physical partitions,
Oracle Solaris on the domain may panic,
or Hypervisor may abort.
Workaround
Execute any of the following procedures
according to the encountered circumstances.
- If the disk, which is a part of the RAID
volume, fails while the system is
running, do not restart Oracle Solaris
and replace the disk while the system is
running.
- If the disk, which is a part of the RAID
volume, is removed while the system is
running, do not restart Oracle Solaris
and remount the removed disk while
the system is running.
- If the disk, which is a part of the RAID
volume, is removed while the PPAR is
powered off, remount the removed
disk while the PPAR is in the powered
off state.
[How to Restore]
Perform the following procedure if this
symptom occurs:
1. Remove the newly created RAID
volume.
2. Set up the target disk as "hot spare".
When the "hot spare" feature is
enabled, the disk will be automatically
placed in the original RAID volume.
Meanwhile, refer to "F.4 Creating Hot
Spare of Hardware RAID Volume" or
"F.5 Deleting Hot Spare of Hardware
RAID Volume" of Fujitsu M10/SPARC
M10 Systems System Operation and
Administration Guide for the procedures
of removing a volume or setting up a hot
spare.
There is no effective workaround.