Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: After power failure, SunFireV240 with SOLARIS 5.9 cannot start
Operating Systems Solaris After power failure, SunFireV240 with SOLARIS 5.9 cannot start Post 302678691 by doudou2012 on Sunday 29th of July 2012 12:10:35 PM
Old 07-29-2012
After power failure, SunFireV240 with SOLARIS 5.9 cannot start
SUNW, Sun Fire V240 Spare
Sun OS Release 5.9
After a power failure
we try to start the server
We have the following messages:

Quote:
# reboot
syncing file systems... done
rebooting...
SC Alert: Host System has Reset
Probing system devices
Probing memory
Probing I/O buses
Probing system devices
Probing memory
Probing I/O buses

Sun Fire V240, No Keyboard
Copyright 2006 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.22.19, 4096 MB memory installed, Serial #75022208.
Ethernet address 0:14:4f:78:bf:80, Host ID: 8478bf80.

Initializing 15MB of memory at addr 123f002000 -

Initializing 16MB of memory at addr 123e002000 -

Initializing 992MB of memory at addr 1200000000 /-

Initializing 1024MB of memory at addr 1000000000 /-

Initializing 1024MB of memory at addr 200000000 /-

Initializing 1024MB of memory at addr 0 /-

Rebooting with command: boot
Boot device: /pci@1c,600000/scsi@2/disk@0,0:a File and args:
|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\
SunOS Release 5.9 Version Generic_112233-12 64-bit
Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|Hardware watchdog enabled
configuring IPv4 interfaces:ifconfig: #::::::::::::::: bad address
ifconfig: #::::::::::::::: bad address
bge0ifconfig: #::::::::::::::: bad address
ifconfig: #::::::::::::::: bad address
bge1.
Hostname: wap
The / file system (/dev/rdsk/c1t0d0s0) is being checked.
/dev/rdsk/c1t0d0s0: UNREF DIR I=318848 OWNER=root MODE=40755
/dev/rdsk/c1t0d0s0: SIZE=512 MTIME=Jul 19 18:10 2012 (RECONNECTED)
/dev/rdsk/c1t0d0s0: DIR I=318848 CONNECTED. PARENT WAS I=3
/dev/rdsk/c1t0d0s0: UNREF DIR I=288952 OWNER=root MODE=40755
/dev/rdsk/c1t0d0s0: SIZE=512 MTIME=Jul 19 18:10 2012 (RECONNECTED)
/dev/rdsk/c1t0d0s0: DIR I=288952 CONNECTED. PARENT WAS I=288951
/dev/rdsk/c1t0d0s0: UNREF DIR I=288951 OWNER=root MODE=40755
/dev/rdsk/c1t0d0s0: SIZE=512 MTIME=Jul 19 18:10 2012 (RECONNECTED)
/dev/rdsk/c1t0d0s0: DIR I=288951 CONNECTED. PARENT WAS I=8
/dev/rdsk/c1t0d0s0: LINK COUNT lost+found I=3 OWNER=root MODE=40700
/dev/rdsk/c1t0d0s0: SIZE=8192 MTIME=May 20 20:50 2008 COUNT 5 SHOULD BE 9
/dev/rdsk/c1t0d0s0: LINK COUNT INCREASING
/dev/rdsk/c1t0d0s0: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
WARNING - Unable to repair the / filesystem. Run fsck
manually (fsck -F ufs /dev/rdsk/c1t0d0s0). 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):
Thanks for your assistance
Last edited by doudou2012; 07-29-2012 at 01:19 PM..
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

solaris second cd failure

We have a problem on a Sparc Ultra 5 box when installing solaris. We boot from the CD-ROM then go through the install procedure adding IP address, domain, routing details, hard disk layout etc.. The problem arises when asked for the 2nd CD at this point you do get the option to "skip"... (1 Reply)
Discussion started by: hcclnoodles
1 Replies

2. UNIX for Dummies Questions & Answers

Restart on power failure

How do I configure my workstation (Solaris 9) to restart and perform any check disk automatically if there is a power failure? Thanks. (1 Reply)
Discussion started by: here2learn
1 Replies

3. Solaris

solaris 10 not resuming from power save mode.

Dear Frnz, i have a ultra 45 with solaris 10 installed. I face a weird issue in that. once the machine goes to power save mode i am not able to bring the machine back by hitting the keys in keyboard or moving the mouse. I am able to rsh the machine from another machine. To bring the... (1 Reply)
Discussion started by: sriram.s
1 Replies

4. Solaris

Automatic reboot does not work after power failure

Hi all, I have a server SUN FUJITSU in solaris 10 ; result of uname -a is : SunOS MOBD1 5.10 Generic_118833-03 sun4us sparc FJSV,GPUZC-M I have configured the eeprom to auto-boot as usual and this automatic reboot does not work in case of power failure. I must type "boot" on the prompt "ok"... (5 Replies)
Discussion started by: aribault
5 Replies

5. SCO

file system not getting mounted in read write mode after system power failure

After System power get failed File system is not getting mounted in read- write mode (1 Reply)
Discussion started by: gtkpmbpl
1 Replies

6. UNIX for Dummies Questions & Answers

boot up failure unix sco after power failure

hi power went out. next day unix sco wont boot up error code 303. any help appreciated as we are clueless. (11 Replies)
Discussion started by: fredthayer
11 Replies

7. Linux

How to start pc automatically when power comes (Server)?

Can anyone tell me how to start pc automatically when power comes, here I just want to start server automatically, on boot, my server starts automatically because I have written some startup commands in rc.local file but if power fails, then how can I boot automatically (2 Replies)
Discussion started by: Akshay Hegde
2 Replies

8. UNIX for Dummies Questions & Answers

Power failure: file damage?

~#hello -all, Many UNIX/Linux/BSD/etc books warn about turn off the puter without a proper shutdown. This can damage files which are open at that moment. Seems logical to me. My question is.. does the system warn you when there are damaged files when the system is up again? I had a power failure... (7 Replies)
Discussion started by: raylier
7 Replies

LEARN ABOUT X11R4

installboot

installboot(1M) 														   installboot(1M)

NAME

       installboot - install bootblocks in a disk partition

SYNOPSIS

       installboot bootblk raw-disk-device

       The boot(1M) program, ufsboot, is loaded from disk by the bootblock program which resides in the boot area of a disk partition.

       The  ufs  boot objects are platform-dependent, and reside in the /usr/platform/platform-name/lib/fs/ufs directory. The platform name can be
       found using the -i option of uname(1).

       The installboot utility is a SPARC only program. It is not supported on the  architecture.  users should use installgrub(1M) instead.

       bootblk	       The name of the bootblock code.

       raw-disk-device The name of the disk device onto which the bootblock code is to be installed; it must be a character device which is  read-
		       able and writable. Naming conventions for a SCSI or IPI drive are c?t?d?s? and c?d?s? for an IDE drive.

       Example 1: Installing UFS Boot Block

       To install a ufs boot block on slice 0 of target 0 on controller 1 of the platform where the command is being run, use:

	      example# installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk 
		   /dev/rdsk/c1t0d0s0

       /usr/platform/platform-name/lib/fs/ufs

	   directory where ufs boot objects reside.

       /platform/platform-name/ufsboot

	   second level program to boot from a disk or CD

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWcsu			   |
       +-----------------------------+-----------------------------+

       od(1), uname(1), boot(1M), init(1M), kadb(1M), kernel(1M), monitor(1M), reboot(1M), rpc.bootparamd(1M), init.d(4), attributes(5)

WARNINGS

       The installboot utility fails if the bootblk or openfirmware files do not exist or if the raw disk device is not a character device.

								    11 Apr 2005 						   installboot(1M)
All times are GMT -4. The time now is 12:03 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy