[13419] in Hotline Meeting
RE:1-390
daemon@ATHENA.MIT.EDU (jjmorey@Athena.MIT.EDU)
Mon Feb 8 07:12:34 1993
From: jjmorey@Athena.MIT.EDU
To: hotline@Athena.MIT.EDU
Date: Mon, 08 Feb 93 07:12:24 EST
------- Forwarded Message
Received: from ATHENA-AS-WELL.MIT.EDU by po7.MIT.EDU (5.61/4.7) id AA05341; Fri, 5 Feb 93 22:25:48 EST
Received: from KILLER.MIT.EDU by Athena.MIT.EDU with SMTP
id AA09641; Fri, 5 Feb 93 22:25:43 EST
From: larugsi@Athena.MIT.EDU
Received: by killer.MIT.EDU (5.61/4.7) id AA23493; Fri, 5 Feb 93 22:25:40 -0500
Message-Id: <9302060325.AA23493@killer.MIT.EDU>
To: op@Athena.MIT.EDU
Cc: dcns-cluster@Athena.MIT.EDU
Subject: Disk Errors on 5000/25's
Date: Fri, 05 Feb 93 22:25:38 EST
Hi all, ( I am using the M1-390-1 5000/25 as an example)
I have reloaded software yesterday on the 5000/25 (M1-390-1). Dslogger
is still reporting errors on this machine. My question is this. I was under
the impression that when software was loaded, it avoids any bad blocks, and
continues on its merry way. Once a block is bad it must be flagged some how.
Is it possible that DSlogger will always report this error/LBN, because it
knows of its existance via some kept table? Could this system in fact, be o.k.?
--Lou
------- End of Forwarded Message
