HP A3550A User Manual - A3661-90001 - Page 307
Troubleshooting, Value, Description
View all HP A3550A manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 307 highlights
Table 6-14 Most Common Microcode Panic Codes (Continued) Value Description 0x00240010 SCSI protocol problems. The microcode panics 0x00A000B0, 0x00240010, and 0x00220050 occurred in SCSI environments that have severe SCSI protocol problems due to improperly working initiators or noisy conditions. Fixed in microcode revisions 8.27, 8.58, and 9.04. 0x0024001A 0x0026000E 0x0026000F Front end SCSI reset. Caused by a front end SCSI bus reset during a SCSI write buffer mode 1 command. Fixed in microcode revision 7.61. A SCSI bus reset on the front end while a mode select is in progress might intermittently cause the microcode to panic. Fixed in microcode revision 8.20. PROM erase failed. An attempt to erase a FlashROM failed. PROM program failed. An attempt to program a FlashROM failed. 0x00260022 Grid Manager failure. If a change configuration type request was issued during extremely heavy I/O, Grid Manager failed to read the request from the pipe. Fixed in microcode revision 8.20. 0x00280002 0x0028000F 0x00280010 0x00300000 0x0040300E Bad unit type detected. Executing a SCSI Verify or Write Same commands to a Fast RAID-3 LUN would result in 0x00280002 or 0x00220055 panics. Fixed in microcode revision 9.09. Heavy I/O with unusual stripe size. Occurred while executing heavy I/O to a RAID-5 LUN with an unusual stripe size setting such as 99. Fixed in microcode revision 9.09. Binding a RAID-5 LUN containing something other than five disks and a nonstandard stripe size could cause this when the host writes to the LUN. Fixed in microcode revision 7.63. RAID-3 bound with an illegal stripe size. Microcode revision 7.16 allowed the SCSI bind command to bind a RAID-3 LUN with an illegal stripe-size. This caused the microcode to panic when the host issued an I/O command to that LUN. Microcode revision 7.53 fixed this problem by allowing only valid stripe sizes when using the SCSI bind command. Fixed in microcode revision 7.61. Invalid memory sizes. Invalid memory sizes specified in mode page 0x2A could result in a panic instead of rejecting the request. Inaccessible LUN. A power failure, trespass, or SP fault with a high SP cache dirty page count under a heavy I/O load might cause one or more LUNs to become inaccessible. Cycling power did not clear this state. A limited number of data sectors could be unrecoverable. Fixed in microcode revision 7.16. 0x00501001 Parity error (Firmware revision greater than 9.44.00). A SCSI controller chip detected a parity error during a transfer from data RAM. (Reference the 0x00000012 code.) Troubleshooting Unsolicited Event Log 6-59