Download - Fujitsu
Transcript
TABLE A-4 Fixed Solaris OS Issues (Continued) CR Description Workaround 6589612 The raidctl -l command continuously outputs the following output: # raidctl -l Controller: 1 Volume:c1t0d0 Volume:c1t2d0 Disk: 0.0.0 Disk: 0.0.0 ... Note - Fixed in the Solaris 10 5/08 OS (and later) and in the Solaris 10 8/07 OS with patch ID 127127-11 or later installed. Use the Control-C keyboard sequence to stop the output. You can also upgrade the OS or install the patch to avoid encountering this issue. 6592238 You might not be able to remove a RAID 1 volume after RAID 1 and RAID 0 volumes are created. When two volumes are created through the onboard SAS controller (or any controller that uses the mpt driver), the raidctl utility is unable to delete one of the RAID volumes and cannot list the correct disk information. When this occurs, the following is the error message is displayed: # raidctl -l Device record is invalid. Note - Fixed in the Solaris 10 5/08 OS (and later) and in the Solaris 10 8/07 OS with patch ID 127127-11 or later installed. Update the OS to the latest version or install the mandatory patches to avoid encountering this issue in the future. 6594506 After certain hardware error events, it is possible that Solaris PSH events are no longer transported between the SP and the domain. For examples, see “PSH Events Are no Longer Transported (CR 6594506)” on page 124. Note - Fixed in the Solaris 10 5/08 OS (and later) and in the Solaris 10 8/07 OS with patch ID 127127-11 or later installed. See “PSH Events Are no Longer Transported (CR 6594506)” on page 124. You can also upgrade the OS or install the patch to avoid encountering this issue. 6596503 The output of the Solaris prtpicl -v command might show CPU cores or strands with an operational status of enabled when the cores or strands do not exist. Note - Fixed in System Firmware 7.1.6.d or later. Instead, use the output from the prtdiag or prtpicl -c cpu commands. You can also update the System Firmware to the latest version to avoid encountering this issue. Appendix A Fixed Issues 119