On Fri, 4 Oct 1996 14:34:54 +0300 (EET DST) 
 Jukka Marin <jmarin@pyy.jmp.fi> wrote:

 > Oct  4 02:01:06 muikku /netbsd: wdc0: lost interrupt: status 50<drdy,dsc> error 0
 > Oct  4 02:01:06 muikku /netbsd: wdc0: lost interrupt: reading 2@wd0:2112838
 > Oct  4 02:01:06 muikku /netbsd: wdc0: lost interrupt: status 50<drdy,dsc> error 0
 > Oct  4 02:01:06 muikku /netbsd: wdc0: lost interrupt: reading 2@wd0:2112838
 > Oct  4 02:01:06 muikku /netbsd: wdc0: lost interrupt: status 50<drdy,dsc> error 0
 > Oct  4 02:01:06 muikku /netbsd: wdc0: lost interrupt: reading 1@wd0:2112838
 > Oct  4 02:01:06 muikku /netbsd: wdc0: lost interrupt: status 50<drdy,dsc> error 0
 > Oct  4 02:01:06 muikku /netbsd: wdc0: lost interrupt: reading 1@wd0:2112838
 > 
 > Are these dangerous?  What should I do about them?  Is my disk dying?  Has
 > some data been lost?  Am I just being a paranoid? :-)

I think I heard something about encountering that error when the disk hit
a bad block... (seems like the error detection code could use a little
improvement...)  Anyhow, notice it's the same block each time.  I bet
it's a bad block...

(For clarification, the error format is <nblks>@<drive>:<blkno>)

Jason R. Thorpe                                       thorpej@nas.nasa.gov
NASA Ames Research Center                               Home: 408.866.1912
NAS: M/S 258-6                                          Work: 415.604.0935
Moffett Field, CA 94035                                Pager: 415.428.6939