[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference turris::digital_unix

Title:DIGITAL UNIX(FORMERLY KNOWN AS DEC OSF/1)
Notice:Welcome to the Digital UNIX Conference
Moderator:SMURF::DENHAM
Created:Thu Mar 16 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:10068
Total number of notes:35879

8704.0. "'Memory Fault' on reboot" by CRONIC::PCUMMINGS (The perfect democracy) Tue Feb 04 1997 16:35

    I've got a beauty of a problem.  I brought my system down for a routine
    reboot and it never came back.  It now gets a "n Memory Fault" after 
    the bcheckrc job runs and that's it.  It spews a ton of getty INIT
    "command is respawning too rapidly" and never completes start up.
    
    I take the system to single user, using either /vmunix or /genvmunix,
    run bcheckrc and it fails with the "n Memory Fault", where "n" is
    some number that's not always the same.  This rules out the the likely
    hood of both kernels being bad.  From single-user, the "mount -u /"
    command gives the same Memory Fault.  This is DU v4.0A on a Mustang.
    
    I plugged this same RZ28 into an Alcor and got the same results
    mentioned above booting single-user, /vmunix or /genvmunix.
    
    Interestingly enough, we booted off another system disk on the Alcor
    and was able to mount the problem system disk without problem.  We
    could ls, or cat various file names and even ran 'uerf -f' pointing to
    the binary errlog on the problem disk. 
    
    Is there an anal/disk/repair type tool on DU V4.0A?  There was
    something similar back in V3.0 at one point.
    
    thanx
    paul
T.RTitleUserPersonal
Name		DateLines