Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!sdd.hp.com!apollo!mort
From: mort@apollo.HP.COM (Stephen Moriarty)
Newsgroups: comp.sys.apollo
Subject: Re: SR9.7 help...believe it or not
Message-ID: <51d6408e.20b6d@apollo.HP.COM>
Date: 28 May 91 18:31:00 GMT
References: <1991May24.064211.17918@news.cs.indiana.edu>
Sender: root@apollo.HP.COM
Reply-To: mort@apollo.HP.COM (Stephen Moriarty)
Organization: Hewlett-Packard Apollo Division - Chelmsford, MA
Lines: 25

In article <1991May24.064211.17918@news.cs.indiana.edu> houghton@iuvax.cs.indiana.edu (Ric Houghton) writes:
>  On boot up, I get the following message:
>    ....(PM_$Init): 80080009
>  :
>   if I type stcode 80080009, I get:
>      OS/disk manageer
>      disk data check
>
>  Does any one have an idea what's going on, or could someone suggest
>a few things to try?

      80009 means that the sector being read is not readable.  Usually
you can just add this sector to the badspot list.  The way to do this 
is get the node up to the boot shell and look at the lsyserr log.  This
will give you the disk address that is bad.  This block should be added
to the badspot list and salvol run on the drive.  In this case you also
will need to find the file that has the badspot and replace that file as 
well.  Salvol should give you this information.  This is usually not 
sufficient reason to replace the drive.  There is probably one sector
causing all the problems.


ARPA: mort@apollo.hp.com        UUCP: ...{decvax, umix, mit-eddie}!apollo!mort
Apollo, a fond memory of Hewlett Packard, 300 Apollo Drive, Chelmsford, MA. 01824
              Argue for your limitations, and they are yours.