karron@MCIRPS2.MED.NYU.EDU (09/22/90)
What does this error message mean on my console (not in syslog): command 82 try 1 ips0d1s7: bn=65873 IOPB word1=821E unrecovered 'drive faulted' Is this a real problem ? Or is this noise ? I get this once and a while. Which disk is causing it ? Which controller ? dan. +-----------------------------------------------------------------------------+ | karron@nyu.edu Dan Karron | | . . . . . . . . . . . . . . New York University Medical Center | | 560 First Avenue \ \ Pager <1> (212) 397 9330 | | New York, New York 10016 \**\ <2> 10896 <3> <your-number-here> | | (212) 340 5210 \**\__________________________________________ | +-----------------------------------------------------------------------------+
jeremy@perf2.asd.sgi.com (Jeremy Higdon) (09/24/90)
In article <9009221751.AA01139@mcirps2.med.nyu.edu>, karron@MCIRPS2.MED.NYU.EDU writes: > > > > What does this error message mean on my console (not in syslog): > > command 82 try 1 ips0d1s7: bn=65873 IOPB > word1=821E unrecovered 'drive faulted' > > Is this a real problem ? Or is this noise ? > > I get this once and a while. Which disk is causing it ? Which > controller ? > It is a real problem, but for now the system is recovering. The driver will retry 3 or 4 times on errors like this. ESDI controller 0, drive 1
karron@MCIRPS2.MED.NYU.EDU (09/25/90)
>In article <9009221751.AA01139@mcirps2.med.nyu.edu>, karron@MCIRPS2.MED.NYU.EDU writes: >> >> >> >> What does this error message mean on my console (not in syslog): >> >> command 82 try 1 ips0d1s7: bn=65873 IOPB >> word1=821E unrecovered 'drive faulted' >> >> Is this a real problem ? Or is this noise ? >> Is data being corrupted, or is it being correctly read ? My real concern is that is the error such that the ecc (error correction code) in the drive is unable to correct the error. If the error is unrecovered, is it retried and correctly recovered later ? dan. . +-----------------------------------------------------------------------------+ | karron@nyu.edu Dan Karron | | . . . . . . . . . . . . . . New York University Medical Center | | 560 First Avenue \ \ Pager <1> (212) 397 9330 | | New York, New York 10016 \**\ <2> 10896 <3> <your-number-here> | | (212) 340 5210 \**\__________________________________________ | +-----------------------------------------------------------------------------+
jeremy@perf2.asd.sgi.com (Jeremy Higdon) (09/26/90)
In article <9009241956.AA08505@mcirps2.med.nyu.edu>, karron@MCIRPS2.MED.NYU.EDU writes: > >In article <9009221751.AA01139@mcirps2.med.nyu.edu>, karron@MCIRPS2.MED.NYU.EDU > writes: > >> > >> > >> > >> What does this error message mean on my console (not in syslog): > >> > >> command 82 try 1 ips0d1s7: bn=65873 IOPB > >> word1=821E unrecovered 'drive faulted' > >> > >> Is this a real problem ? Or is this noise ? > >> > > Is data being corrupted, or is it being correctly read ? > My real concern is that is the error such that the ecc (error > correction code) in the drive is unable to correct the error. > > If the error is unrecovered, is it retried and correctly recovered later ? > This error is not a media error, thus ECC correction is not being done. It indicates that the drive is in a 'faulted' state. If the error is unrecoverable, you will see "try 2", "try 3", etc., in place of "try 1" above. It could be that the cables are a little loose (there are three between the controller and the drive), or the drive could just be tired.