Hi,
>  Bad SYSTEM LOGICAL Sector number 0x836470g on ldev 213 (io_status=FFD90071)
> Filename of bad file:
....
> The system is on 7.5 and has MPEMXT3B, which I believe is the 
> appropriate patch for the VA array. Anyone have an idea of what the 
> problem might be?

A bad sector, perhaps?

The number you quoted at the start is bad, ending in a letter "g" ...

You can try tye following (with the correct sector number):

   :ci
   debug
   dsec #213.($xxxx * $100), 40, b
   c

If it hangs, you should be able to hit <break> and enter ":abort".
(That's why I had you do it from a nested CI.)

In the above, the "#" is important...it means decimal.
The "$" is important: it means hex.  
The "xxx" is the full hex number shown by the OS in the "bad sector" 
message.

If the sector is still bad, I'd expect you to get an error.

However, the sector may have been spared by now *and* this means you
probably have one or more sectors of bad data inside your file.

I know of several means of mapping sector # to file name:

1. De-Frag/X from Lund Performance Solutions

   Has a command to map a sector # to a file name

       findsector <ldev> <sector>


2. BADSECTR.PRVXL.TELESUP

   Seems to require a diagnostics password

Stan
-- 
Stan Sieler
[log in to unmask]
www.allegro.com/sieler/wanted/index.html 

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *