Here's my dilema: I've been trying to add a unipack(18GB)hdd to my Sparc5 workstation. I formatted and partitioned the drive to use all avail space using c0t2d0s6. Not thinking I added the following line to the vfstab file; /dev/dsk/c0t2d0s6 /dev/rdsk/c0t2d0s6 /usr ufs yes yes which in turn overlapped my c0t3d0s6 /usr partition causing my system to only boot into "read-only" mode. How can I change the rights to the vfstab file to delete the line I previously added?(If thats what will fix my prob.) I'm a newbie to solaris and I would greatly appreciate any and all help. Thanks! Below is some screen ouput to help clarify my situation. The system is being restarted. syncing file systems... done rebooting... Resetting ... SPARCstation 5, No Keyboard ROM Rev. 2.29, 128 MB memory installed, Serial #8910848. Ethernet address 8:0:20:87:f8:0, Host ID: 8087f800. Rebooting with command: Boot device: /iommu/sbus/espdma@5,8400000/esp@5,8800000/sd@3,0 File and args: SunOS Release 5.8 Version Generic_108528-11 32-bit Copyright 1983-2001 Sun Microsystems, Inc. All rights reserved. configuring IPv4 interfaces: le0. Hostname: sparc1 The file system () is being checked. fsck: line in vfstab has too few entries WARNING - Unable to repair the filesystem. Run fsck manually (fsck -F ). Exit the shell when done to continue the boot process. Type control-d to proceed with normal startup, (or give root password for system maintenance): Login incorrect 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 Jan 28 12:09:06 su: 'su root' succeeded for root on /dev/console Sun Microsystems Inc. SunOS 5.8 Generic February 2000 # bash bash-2.03# newfs -N /dev/rdsk/c0t3d0s3 /dev/rdsk/c0t3d0s3: 524400 sectors in 345 cylinders of 19 tracks, 80 sectors 256.1MB in 22 cyl groups (16 c/g, 11.88MB/g, 5696 i/g) super-block backups (for fsck -F ufs -o b=#) at: 32, 24432, 48832, 73232, 97632, 122032, 146432, 170832, 195232, 219632, 244032, 268432, 292832, 317232, 341632, 366032, 390432, 414832, 439232, 463632, 488032, 512432, bash-2.03# fsck -o b=32 /dev/rdsk/c0t2d0s3 fsck: line in vfstab has too few entries bash-2.03# exit exit # resuming system initialization Usage: mount [-v | -p] mount [-F FSType] [-V] [current_options] [-o specific_options] {special | mount_point} mount [-F FSType] [-V] [current_options] [-o specific_options] special mount_point mount -a [-F FSType ] [-V] [current_options] [-o specific_options] [mount_point ...] The /usr file system (/dev/rdsk/c0t3d0s6) is being checked. /dev/rdsk/c0t3d0s6: is stable. failed to open /etc/coreadm.confsyseventd: Unable to open daemon lock file '/etc /sysevent/syseventd_lock': 'Read-only file system'mount: warning: line for "/dev /dsk/c0t2d0s6" in vfstab has too few entries mount: warning: line for "/dev/dsk/c0t2d0s6" in vfstab has too few entries The system is coming up. Please wait. /sbin/mountall: /tmp/sh840: cannot create rm: Unable to remove directory /tmp: Read-only file system mkdir: Failed to make directory "/tmp"; Read-only file system chown: /tmp: Read-only file system NIS domainname is riviera.com /etc/rc2.d/S69inet: /tmp/ifconfig.102: cannot create grep: can't open /tmp/ifconfig.102 /etc/rc2.d/S69inet: test: argument expected starting rpc services: rpcbind keyserv done. Setting netmask of le0 to 255.255.255.0 Setting default IPv4 interface for multicast: add net 224.0/4: gateway sparc1 mount: warning: line for "/usr" in vfstab has too few entries mount: warning: line for "/usr" in vfstab has too few entries syslog service starting. cron could not unlink FIFO: No such file or directory cron aborted: cannot create fifo queue ! cannot create fifo queue Wed Jan 28 12:14:14 2004 ! ******* CRON ABORTED ******** Wed Jan 28 12:14:14 2004 dumpadm: failed to open /etc/dumpadm.conf: Read-only file system syslogd: symlink to doorfile failed : Read-only file system Print services started. /usr/sbin/pmconfig: Can't open /etc/.cpr_config to update changes: Read-only fil e system /dev/bd.off: Read-only file system mkdir: Read-only file system volume management starting. The system is ready. sparc1 console login:

Boot from an OS cd. OK> boot cdrom During the install, tell it you want to cancel and you are sure. You will have a live mini system with a temporary mount directory. mount your root partition mount /dev/rdsk/c0t3d0s0 /a edit the /a/etc/vfstab file with your favorite editor. Save the changes, unmount, reboot.

I tried it and this is the response I got. # mount /dev/rdsk/c0t3d0s0 /a mount: /dev/rdsk/c0t3d0s0 not a block device # I booted with the "web install" cd. Does it matter or do I need to boot using Sparc Disk 1 bin?

Hi! You have done everthing right except for one little tiny misstake. You can't mount a "raw" device (character device) since this device. You must use the corresponding block-device file when mounting. All you need to do is to change the "rdsk" in the path to "dsk". The correct command should look like this: mount /dev/dsk/c0t3d0s0 /a //TechMark

It's getting there. I was able to mount /dev/dsk/c0t3d0s0 /a and change the vfstab file back to the following: /dev/dsk/c0t3d0s6 /dev/rdsk/c0t3d0s6 /usr ufs 1 no - /dev/dsk/c0t3d0s1 /dev/rdsk/c0t3d0s1 /var ufs 1 no - /dev/dsk/c0t1d0s7 /dev/rdsk/c0t1d0s7 /export/home ufs 2 yes - /dev/dsk/c0t1d0s5 /dev/rdsk/c0t1d0s5 /opt ufs 2 yes - but after some error msgs I can login in as root but have to manually mount the s7 /export/home dir and s5 /opt dir. I then try to start a vncserver session and it gives me the following errors: bash-2.03# vncserver -geometry 800x600 xauth: error in locking authority file //.Xauthority xauth: error in locking authority file //.Xauthority sh: //.vnc/sparc1:1.log: cannot create sh: //.vnc/sparc1:1.pid: cannot create New 'X' desktop is sparc1:1 Starting applications specified in //.vnc/xstartup Log file is //.vnc/sparc1:1.log sh: //.vnc/sparc1:1.log: cannot create Any suggestions? You guys have been right on the money so far! Thanks RS