Specifications

Chapter 6 Troubleshooting Common Problems 6-17
6.11 Disconcerting Error Messages
During ufsdump operations, the following errno 5 message may appear:
This message can be ignored if the error only occurs when ufsdump is running.
Otherwise the error needs to be further evaluated. See bug 4234852 and bug
4289725 and the related escalations. This message is not encountered when using
RAID Manager 6.22x. The root cause is ufsdump reading past the end of the
partition or reading 192 bytes which is not a proper "block read".
Make sure that the file system being dumped is not mounted and make sure it is
clean, run fsck.
The error message ASC/Q 0C/00 sense key 4,(6) indicates write failure when
its only a battery warning which may cause disabling caching or mirroring.
Sometimes after power up, it takes a while for the battery to recharge. See
raidcode.txt for the list of possibilities. Also see bug 4124793.
Another harmless message is:
Upgrading to RM 6.22.1 will reduce the occurrence of this message. This message
can be safely ignored. See bug 4671354 for details.
6.12 Troubleshooting Controller Failures
Refer to the information listed under Technical Information at:
http://webhome.sfbay/A3x00
Apr 10 22:29:40 abc unix: WARNING: The Array driver is returning an
Errored I/O, with errno 5, on Module 1, Lun 1, sector 43261180
unix: WARNING: kstat rcnt == 0 when exiting rung, please check