Managers,
(My original posting is included after.)
It turns out that the /tmp_mnt/cdrom_pro mount was bad, and the only
way to clear it was to get rid of it by inode number using the clri
command.
/usr/etc/clri /dev/rsd0a 3047
After this, I had to /etc/fsck the filesystem /dev/rsd0a and answer yes
to all of the CLEAR, ADJUST, and CORRECT SUPERBLOCK questions, then
reboot. The boot went through and locked up while it was syncing the
filesystems, but after I did an L1A and typed boot, it went through
cleanly. Just for safety's sake, I booted the server again, and it
seems to be working great now.
Thanks to all,
Jay
Problem solved due to help from the following individuals:
casper@fwi.uva.nl
lucas@Nadn.NAVY.MIL
m1cxn01@FRB.GOV
epl@Kodak.COM
strombrg@bingy.acs.uci.edu
m.cooper@bbn49.cv.com
rwing!pat@ole.cdac.com
mike@trdlnk.com
root@wisdom.maf.nasa.gov
pluto!perryh@qiclab.scn.rain.com
Eckhard.Rueggeberg@ts.go.dlr.de
D.Mitchell@dcs.shef.ac.uk
----------------------------------------------------------------
> From ms010 Tue Oct 11 20:01:00 1994
> To: sun-managers@ra.mcs.anl.gov
> Subject: reboot failure; automount problem
>
> Hello Managers,
>
> Please forgive me if this letter does not flow very well, it's my
> first submission.
>
> We are currently running SunOS 4.1.3, and have just experienced a
> particularly frightening problem during a reboot of the server:
> -----------------------------------------
>
> /dev/rsd0a : DIRECTORY CORRUPTED I=3047 OWNER=ROOT MODE=40555
> /dev/rsd0a : SIZE=512 MTIME=SEP8 08:28 1994
> /dev/rsd0a : DIR = /tmp_mnt/cdrom_pro
> /dev/rsd0a : Unexpected Inconsistency; run fsck manually
>
> - THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED INCONSISTENCY:
>
> /dev/rsd0a (/)
>
> Reboot Failed...Help!
>
> Warning - File sytems have not been remounted read/write. Use fsck to
> fix any file system problems, rebooting the system if any problems
> are found with a mounted file system. After file systems have fsck'd
> cleanly, you can remount file systems and finish single-user setup
> using "/etc/rc.single"
>
> -----------------------------------------
>
> At this point, I run the /etc/fsck command and it runs through to the
> point where it asks if you want to :
>
> SALVAGE?
>
> If I type a "yes, no or anything else", it says :
>
> "MEMORY FAULT"
>
> and gives me my prompt back like nothing happened. If I do a
<ctrl-D>
> to continue, it says:
>
> touch: cannot touch /: no write permission
>
> then it proceeds to reboot. At this point, we can still login,
> but will get the same error every time the server boots.
>
> We unmounted /tmp_mnt/cdrom_pro and still got the error. We disabled
> the automounter entirely and still got the error. We then tried to
> ls -R the directory /tmp_mnt/cdrom_pro, and it locked up my desktop -
> no cursor movement, mouse movement, nothin'. If we try to cd into
> the /tmp_mnt/cdrom_pro directory, it hangs again. I have to do an
> L1A to get anywhere.
>
> By doing a man on ln, we find the following that may be a lead:
> -----------------------------------------------------------------
> To remove a file, all hard links to it must be removed,
> including the name by which it was first created; removing
> the last hard link releases the inode associated with the
> file.
> -----------------------------------------------------------------
>
> Could it be a hard link to the cdrom_pro directory that is causing
> the problem? If so, how do I go about locating and annihilating it?
>
> If we boot to single user mode, it starts a loop in the boot process
> after it gives the original message of the corrupt directory. When I
> type my <ctrl-D>, it starts counting down static kernel pages, and
> when it finishes, it starts the boot process over again.
>
> This seems like a very serious problem which is transparent until I
> run a boot. Does anybody have any suggestions, comments, hints,
etc?
>
> Thank you for your time and patience.
>
> Cordially,
> Jay R. Stienstra
> Mid-States Technical
> Dubuque Design Center
> 880 Locust Street, Suite 232
> Dubuque, IA 52001-6700
> E-MAIL: ms010@snowwhite.tx.deere.com
> V-MAIL: 319-582-5152
> FAX: 319-582-5065
>
> |
> --|--
> / | \ M I D-S T A T E S
> ####|____|____|#####################
> ####| | |#####################
> \ | / T E C H N I C A L
> --|--
> |
>
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:09:11 CDT