Ric Houghton <houghton@iuvax.cs.indiana.edu> (05/24/91)
There exists an SR9.7 node in my our network that is causing some
problems.
On boot up, I get the following message:
....(PM_$Init): 80080009
Apollo phase II shell.....
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? If you don't have any suggestions on a fix,
please suggest a rather large building that I can drop this thing off
of..... and an airline that has chep one-way tickets to Cuba.
Thanks,
Ric Houghton
houghton@cs.indiana.edumort@apollo.HP.COM (Stephen Moriarty) (05/29/91)
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.
randall@bcstec.boeing.com (Michael Randall) (06/04/91)
In article <1991May24.064211.17918@news.cs.indiana.edu>, houghton@iuvax.cs.indiana.edu (Ric Houghton) writes: > > There exists an SR9.7 node in my our network that is causing some > ....(PM_$Init): 80080009 > if I type stcode 80080009, I get: > OS/disk manageer > disk data check Possibly the disk controller is going bad. Other option is a drop in the power line voltage has caused the disk to write garbage on itself. If you can, INVOL it and reload. If my faded memory serves me correctly however, it seems I saw that more often when the controller was going bad. -- -------------------- Peace Love & E-Mail --------------------------------- Michael W. Randall | Ha ha ha... (Funny stuff goes here) randall@bcstec.boeing.com | ... He he he... ...!uunet!bcstec!randall | ... Ho ho ho...