> SYSTEM ABORT 2052
> FROM SUBSYSTEM 145
> SYSTEM HALT 7, $0804

2052 = SSM_SA_DEALLOCATE_SEC_STORAGE_AND_LOCK_MAP_CORRUPTED

Subsystem 145 = SUBSYS_SEC_STORAGE_MAN

> So is there anyway to safely do the following without bringing the computer
> down?
> 1. Check the drives for potential problems - bad sectors, etc.
> 2. Check the directory structure on USER_VOL_SET_1.
> 3. Check the file structure on USER_VOL_SET_1
> 4. Otherwise diagnose the problem.
> 5. Purge and rebuild any corrupted directory structure on USER_VOL_SET_1 if
> appropriate.


yes, mount the drives on another 3000 and examine/fix them there.
(Backup 3000s are dirt cheap :)

Other than that...everything else is risky, particularly since you already
encountered a system failure.

If it were my system, I'd:

  1) put a trap in to "catch" system_abort calls
     (via two sneaky DEBUG commands)

  2) try mounting the volume set

     If this triggers the system abort, then one of two things will
     be the case:

        a) the rest of the system still runs fine (albeit with one terminal
           now sitting at the start of system_abort :)

           I'd now examine what's going on, and see if I could either fix
           it or bypass the crash.

        b) the system hung/crashed anyway

  3) if the above didn't trigger a system abort, I'd now
     :run fscheck.mpexl.telesup
     and do a "ca all" command.



--
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 *