Yes hardware. 

Try running a hard drive sector test utility from the vendor.

Might want to fail this component out of your RAIDFrame.

And of course, make sure your backups are running properly >:}

~BAS


On Tue, 2006-09-26 at 00:04, Louis Guillaume wrote:
> Hi!
> 
> On NetBSD-3...
> 
> $ uname -a
> NetBSD thoth.zabrico.com 3.0_STABLE NetBSD 3.0_STABLE (GENERIC.MP) #2:
> Fri May 19 20:53:19 EDT 2006
> louis@shodo.berklee.net:/usr/obj/sys/arch/i386/compile/GENERIC.MP i386
> 
> 
> ... (no changes were made to GENERIC.MP) or the source tree at all...
> 
> I've recently been getting these errors...
> 
> $ dmesg |grep esiop
> esiop0 at pci1 dev 6 function 0: Symbios Logic 53c1010-66 (ultra3-wide scsi)
> esiop0: using on-board RAM
> esiop0: interrupting at ioapic1 pin 13 (irq 7)
> scsibus0 at esiop0: 16 targets, 8 luns per target
> esiop1 at pci1 dev 6 function 1: Symbios Logic 53c1010-66 (ultra3-wide scsi)
> esiop1: using on-board RAM
> esiop1: interrupting at ioapic1 pin 12 (irq 10)
> scsibus1 at esiop1: 16 targets, 8 luns per target
> sd0(esiop0:0:0:0): command timeout, CDB: 0x2a 00 00 41 07 9f 00 00 60 00
> esiop0: scsi bus reset
> sd0(esiop0:0:0:0): command with tag id 2 reset
> sd0(esiop0:0:0:0): command with tag id 6 reset
> sd0(esiop0:0:0:0): command with tag id 7 reset
> sd0(esiop0:0:0:0): command timeout, CDB: 0x2a 00 00 41 07 9f 00 00 60 00
> esiop0: scsi bus reset
> sd0(esiop0:0:0:0): command with tag id 0 reset
> sd0(esiop0:0:0:0): command with tag id 1 reset
> sd0(esiop0:0:0:0): command with tag id 2 reset
> sd0(esiop0:0:0:0): command with tag id 3 reset
> sd0(esiop0:0:0:0): command with tag id 4 reset
> sd0(esiop0:0:0:0): command with tag id 5 reset
> sd0(esiop0:0:0:0): command timeout, CDB: 0x2a 00 00 55 80 1f 00 00 60 00
> esiop0: scsi bus reset
> sd0(esiop0:0:0:0): command with tag id 0 reset
> sd0(esiop0:0:0:0): command with tag id 1 reset
> sd0(esiop0:0:0:0): command with tag id 4 reset
> 
> ...
> 
> should I be assuming bad hardware at this point? Or could this be a
> filesystem/data issue on sd0?
> 
> There is also esiop1 that doesn't appear to be affected. It is
> identical, as I have sd0 and sd1 as components in a raidframe raid0 array.
> 
> Any advice would be most appreciated.
> 
> Thanks,
> 
> Louis
>