Thanks to all who responded to me!
Tom Jones, Oscar Goosens, Timothy Lindgren, Ray (firstname.lastname@example.org),
Victor Churchill, Sean Harding, Frank Smith, Rajan (email@example.com),
Marty W. Bullock (yes, a very quite night :) ).
All suggested to run fsck while in boot cdrom -s mode.
Well, I did it, and you know what I got? No problems with any of
Let me get you back in time.
After machine went down, I got the office and restated machine in boot -s
mode. There were a problems almost on all partitions c0t0d0s*, but they
were solved with fsck.
Besides c0t0d0s* we also have a /dev/md/dsk partitions, and one of them
had a serious problem with inodes, so I decided to comment out it in
/etc/vfstab. The machine has no keyboard/monitor, so I accessed to that
machine thru console on terminal server. I edited vfstab with vi and
And after that I got a problem with /usr.
After boot cdrom -s and no problem reported by fsck, I've checked
/etc/vfstab and found that /usr was commented out instead of /dev/md
Morale of my (stupid) story is that always use the correct TERM= while
working thru console while accessing terminal server from your X-window
session. In my case, wrong TERM= + vi + me messed up /etc/vfstab.
After correction of /etc/fstab and fsck of /dev/md/rdsk/* machine is up
Thanks a lot to all of you, guys!
Sorry for bothering you.
-- Kins Orekhov Outlook Technologies, Inc. E-mail: firstname.lastname@example.org Phone: 773-775-2099, ext. 226 http://swoop.outlook.net
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:14:04 CDT