Quote:
Originally Posted by Just Ice
i doubt that /var was ever mounted ro as that would mean that the system would have complained way lot earlier as the system does write to /var/adm/messages fairly regularly even if it doesn't need to write to /var/adm/wtmpx ...
The read only response was after the system came up in maintenance mode.
Quote:
i'm convinced that the filesystem had some corruption that gave it a problem booting up ...
Absolutely. I didn't start the troubleshooting on the system. It was handed over to me after the first guy had to go home. It was at the maintenance prompt when I got it. They were unable to Ctrl-Brk to the open boot prom since Chris (the H&E guy) couldn't find the ctrl or brk keys. I picked it up there.
The error I had was along the lines of (it's been two weeks) "can't create utmp".
Attempting to umount /var returned the mount point busy message. Chris hit enter on fsck before I could tell him to type in the specific file system I wanted to check. When it got to /var, it responded that /var was mounted read only.
Quote:
btw, what was the last thing that happened to the server prior to it having the boot problem? was it patched and then rebooted? if patched, was the server in single-user mode or without regular user logins/processes at all during the patching?
According to the team lead, an application (a cisco management package) was being upgraded which required a reboot after it was done.
Carl