Subject: Re: mpt(4) issues, was: Why not softdep per default?
To: Hauke Fath <hauke@Espresso.Rhein-Neckar.DE>
From: Manuel Bouyer <>
List: current-users
Date: 04/04/2005 21:37:00
On Sat, Apr 02, 2005 at 11:02:06PM +0200, Hauke Fath wrote:
> At 18:50 Uhr +0200 2.4.2005, Manuel Bouyer wrote:
> >I had a look at the driver.
> >These:
> >mpt0: Unknown async event: 0xb
> >mpt0: Unknown async event: 0xb
> >
> >are defined in the mpt_mpilib.h as "MPI_EVENT_INTEGRATED_RAID".
> >Does these board have RAID functionality ?
> Yes. They can mirror (RAID level 1) two drives - a poor man's RAID
> controller, so-to-say. We are running all four machines in that mode.

And does the problem happen when not in RAID mode ? I'm not sure the driver
supports this. At last in this mode the firmware emits some events that
are not properly handled by the driver.
Does the firmware do all the work, or do you also have a raidframe on the
2 devices ?

> >As you also see:
> >sd0(mpt0:0:0:0):  Check Condition on CDB: 0x2a 00 03 69 13 bf 00 00 10 00
> >    SENSE KEY:  Hardware Error
> >    ASC/ASCQ:  Internal Target Failure
> >
> >It's quite possible that this is a hardware issue, and the firmware reports
> >this event because the RAID functionality is not (or not completely)
> >disabled.
> It's not disabled - it had better not be, since I set up the machines that
> way.  ;)
> The thing is that I only get the above log message from high traffic
> (untaring NetBSD binary tarballs, or nightly find(1) runs).

But the sense key and ASC/ASQ reported are quite clear, it's a hardware
error, not even a protocol error on the SCSI bus (or these disks are
braindead). It could be a power issue (power supply not strong enouth,
for example). 

Manuel Bouyer <>
     NetBSD: 26 ans d'experience feront toujours la difference