repair / filesystem

[jpn1]

We have a development test box that has a corupted / filesystem. I've tried to boot to the cd, but it auto starts the installation. Is there a way I can boot to the cd to manually run the fsck. Here is the output when booting.
SunOS Release 5.9 Version Generic_118558-34 64-bit
Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Hardware watchdog enabled
Configuring ATM interfaces:
configuring IPv4 interfaces: bge0.
Hostname: v215
devfsadm: Cannot find /usr/lib/ld.so.1
Killed
/sbin/rcS: /usr/bin/loadkeys: not found
/etc/rcS.d/S35svm.init: rm: not found
/etc/rcS.d/S35svm.init: grep: not found
WARNING: /proc could not be mounted
/sbin/swapadd: expr: not found
swap: Cannot find /usr/lib/ld.so.1
Killed
fsck: Cannot find /usr/lib/ld.so.1
Killed
The / file system (/dev/rdsk/c1t0d0s0) is being checked.
fsck: Cannot find /usr/lib/ld.so.1
Killed

WARNING - fatal error from fsck - error 137
Unable to repair the / filesystem. Run fsck manually
(fsck -F ufs /dev/rdsk/c1t0d0s0). System will reboot when you exit the shell.

Type control-d to proceed with normal startup,
(or give root password for system maintenance):

 

[linnorm]

Just input the root password at the point where the boot process stops and it'll take you into maintenance mode. You can run the fsck from there.

 

[jpn1]

After I enter the root password I enter the fsck command and here is the output:
Type control-d to proceed with normal startup,
(or give root password for system maintenance):
single-user privilege assigned to /dev/console.
Entering System Maintenance Mode

Oct 12 15:40:27 su: 'su root' succeeded for root on /dev/console
su: No shell /bin/ksh. Trying fallback shell /sbin/sh.
-sh: /bin/i386: not found
-sh: /usr/sbin/quota: not found
-sh: /bin/cat: not found
-sh: /bin/mail: not found
-sh: stty: not found
# fsck -F ufs /dev/rdsk/c1t0d0s0
fsck: Cannot find /usr/lib/ld.so.1
Killed
#

 

[linnorm]

Ouch. In that case booting from cd really is you only option. You can get a terminal window to run the fsck after the installer starts. I don't remember off hand how far you need to get into the installer before you can get the terminal though. After the installer starts try right-clicking the background to get a menu. If one doesn't pop up move to the next step in the installer and try again. I'm sorry I can't be more specific, it's been a couple of months since I've needed to do that.

 

[bfitzmai]

Try using Software Disk 1. From the Ok> prompt, enter command "boot cdrom -s". This will put you in Single User Mode. From there, you should be able to fsck -y /dev/rdsk/c1t0d0s0. The -y will answer Yes to all the "Do you want to fix" questions. Keep in mind the errors you are having usually indicate a bad VTOC or disk. You may want to load a back up VTOC. I have had success a few times doing this. Most of the time the disk is so corrupted that I had to start from scratch.