Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Solaris 10 will not Boot Properly

Status
Not open for further replies.

chungste

IS-IT--Management
Oct 2, 2006
3
US
I am running Solaris 10 on a SPARC Sun Enterprise 420R server. It was working properly, when there was a problem with the power and it shut off without a proper shutdown.

When I boot I get the following error:
=========================================
Error: svc:/system/filesystem/root:default failed to mount /boot (see 'svcs -x' for details)
[ system/filesystem/root:default failed fatally (see 'svcs -x' for details) ]
Requesting System Maintenance Mode
Console login service(s) cannot run
=========================================

I then enter in my root password for system maintenance. When I run svcs -x, this is the output:
=========================================
svc:/system/filesystem/root:default (root file system mount)
Reason: Start method exited with $SMF_EXIT_ERR_FATAL
see: see: /etc/svc/volatile/system-filesystem-root:default.log
Impact: 44 dependent services are not running. (use -v for list.)

svc:/network/rpc/gss:default (Generic Security Service)
State: uninitialized since Sat......
Reason: Restarter svc:network/inetd:default is not running
See: See: gssd(1M)
Impact: 10 dependent services are not running. (Use -v for list)

svc:/application/print/server:default (LP print server)
State: disabled since Sat Sep 30.....
Reason: Disabled by an administrator
See: See: lpsched(1M)
Impact: 1 dependent service is not running. (Use -V for list)
=========================================
The output for svcs -v is too long to type out here, but it lists all the dependent services, I presume.

The content of the file /etc/svc/volatile/system-filesystem-root:default.log is:
=========================================
[start + 1.91s Enabled. ]
[start + 2.87s Executing start method ("/lib/svc/method/fs-root") ]
ERROR: /sbin/mount -F ufs /boot failed, err=1
mount: Mount point cannot be determined
[ start + 3.12s Method "start" exited with status 95 ]
=========================================

When I try to run /sbin/mount -F ufs /boot from the command prompt itself, I get a similar error... Mount point cannot be determined.

I have also tried running the command /sbin/mount -a which seems to work in terms of mounting the entire filesystem. At that point I can browse all data, but have no idea how to get the services started and server fully booted.

I have fun fsck and it runs completely with no prompts or errors.

Here is also a copy of my /etc/vfstab:
=========================================
#device to mount #device to fsck mount point FS type fsck pass mount at boot mount options

fs - /dev/fs fs - no -
/proc - /proc proc - no -
/dev/dsk/c0t0d0s1 - - swap - no -
/dev/dsk/c0t0d0s0 /dev/rdsk/c0t0d0s0 / ufs 1 no -
/dev/dsk/c0t0d0s5 /dev/rdsk/c0t0d0s5 /usr ufs 1 no -
/dev/dsk/c0t0d0s4 /dev/rdsk/c0t0d0s4 /var/ ufs 1 no -
/dev/dsk/c0t0d0s7 /dev/rdsk/c0t0d0s7 /export/home ufs 2 yes -
/dev/dsk/c0t0d0s3 /dev/rdsk/c0t0d0s3 /opt ufs 2 yes -
/devices - /devices devfs - no -
ctfs - /system/contract ctfs - no -
objfs - /system/object objfs - no -
swap - /tmp tmpfs - yes -
/dev/dsk/c0t1d0s0 /dev/rdsk/c0t1d0s0 /data ufs 1 yes -
=========================================
Sorry for the formatting, I had to type it out since I can't get any files directly off of the server.

The last entry in the vfstab file is the only entry I added myself. It is a secondary hard disk that I mounted to the directory /data. Everything else was automatically created at install according to the partitions that I defined.

Any ideas Solaris experts?
 
That's kind of freaky... if there's no /boot mentioned in vfstab then why is it trying to mount one... when you say fsck was okay, did you fsck all of the filesystems or any particular one?

Annihilannic.
 
Annihilannic: Others have said that the problem is "freaky" as well. I ran fsck with no parameters. It went through each slice I believe, adn did not prompt for any repairs or errors.
 
To anyone who cares about the solution to this problem, here are the steps I performed:

1) mount -o remount,rw /
This was run because I couldn't edit any files in the / filesystem
2) echo >> /etc/vfstab
This is to add the newline to the end of the vfstab file.

Rebooted, and everything came up fine.
 
I am not in front of a Solaris 10 server right now, but why would it try to mount /boot on SPARC? I can see /boot on x86 which it needs, but it shouldn't need that on SPARC. Maybe I just don't recall ever seeing /boot on my SPARCs on Solaris 10.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top