06-24-2013
Solaris V440 keeps crashing
Hi,
I have Sun Solaris V440, every two days or so, the system crashes and it's at OK prompt. After that I do the FSCK and clear all the bad sectors. Then system stays up for close to 48 hours. Then it crashes again. I checked the logs and I don't see anything under /var/adm/messages file.
How can I find what's wrong with the system?
Please advise. Thanks.
10 More Discussions You Might Find Interesting
1. Solaris
Hi Friends,
My solaris box V440 got stucked. I couldn't accessit from the remote console. Finally i restarted the box.
Can you tell me what are the ways we can find out the issues
and what are the logs we can check other than /var/log/messages.
Thanks
Jinu (1 Reply)
Discussion started by: Jinu
1 Replies
2. Solaris
Hi,
My system is crashing with following error .. i tried to boot from the network and unencapsulated the root disk from SVM .. but still not able to boot the box , can any one point me to some direction .. i do not want to build the box new as of now just want to troubleshoot if possible..
... (3 Replies)
Discussion started by: fugitive
3 Replies
3. Solaris
I installed solaris 10 in my amd based system with 512 mb ram. After installation it booted poping up the grub menu...after that...
It showed something like....rougly
syncing file systems.... ................ done (not all i/o completed)
dumping kernel compreesion ratio 2:1 succeded... (1 Reply)
Discussion started by: aji1729
1 Replies
4. Solaris
Hello,
I've a very weird problem with one of the machines. When I try to boot off a working DVD that I used to install another system with it spits out the following message:
Sun Fire V440, No Keyboard
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.22.33, 8192 MB... (14 Replies)
Discussion started by: stoci
14 Replies
5. Solaris
Hi:
I bougth an used Sun Fire v440, and It have a firmware password. When I turn on the server, it ask for firmware password. (I don 't know what is the correct password). I can access to SC, but when I want to access to OBP, Firmware Password appears again. I remove the battery for two hours,... (1 Reply)
Discussion started by: mguazzardo
1 Replies
6. Solaris
Hello Admins,
Howz it going?
Coming to our forum after long time.
Well, a solaris x86 system on my vmware workstation is facing a big trouble.
I did a file system check on root file system. And after reboot, I am getting an error for both normal mode and fail safe mode.
I have... (4 Replies)
Discussion started by: snchaudhari2
4 Replies
7. UNIX for Dummies Questions & Answers
Over the last month or so my CentOS server has been crashing for reasons I do not know. It has been running for over a year with regular yum updates without problems. The load on the server is perfectly normal with CPU usage at 5-6% and RAM usage at less than half of 32GB of RAM (multiple smaller... (3 Replies)
Discussion started by: spinner0205
3 Replies
8. Solaris
Got a T2000 which has got the 2.5" SAS drives. Want to be able, if I can, to connect to USB caddy and connect to a V440.
Anyone ever tried this? To be honest, having problems even finding a SAS-USB caddy. (0 Replies)
Discussion started by: psychocandy
0 Replies
9. Solaris
Hi,
I have a SUN Fire V440 server running Solaris 8. One of the 4 disks do not appear when issued the format command. The "ready to remove" LED is not on either.
Metastat command warns that this disk "Needs maintenace". Can I just shutdown and power off the machine and then insert an... (5 Replies)
Discussion started by: Echo68
5 Replies
10. Solaris
Hi there,
I have a V440 Server based on Sun Microsystem with Solaris OS.
Is there any way to auto power on the system only with cabling the V440 with 220 v?
Thanks! (10 Replies)
Discussion started by: proof_enrique
10 Replies
reboot(1M) reboot(1M)
NAME
reboot - restart the operating system
SYNOPSIS
/usr/sbin/reboot [-dlnq] [boot_arguments]
The reboot utility restarts the kernel. The kernel is loaded into memory by the PROM monitor, which transfers control to the loaded kernel.
Although reboot can be run by the super-user at any time, shutdown(1M) is normally used first to warn all users logged in of the impending
loss of service. See shutdown(1M) for details.
The reboot utility performs a sync(1M) operation on the disks, and then a multi-user reboot is initiated. See init(1M) for details. On
systems, reboot may also update the boot archive as needed to ensure a successful reboot.
The reboot utility normally logs the reboot to the system log daemon, syslogd(1M), and places a shutdown record in the login accounting
file /var/adm/wtmpx. These actions are inhibited if the -n or -q options are present.
Normally, the system reboots itself at power-up or after crashes.
The following options are supported:
-d Force a system crash dump before rebooting. See dumpadm(1M) for information on configuring system crash dumps.
-l Suppress sending a message to the system log daemon, syslogd(1M) about who executed reboot.
-n Avoid calling sync(2) and do not log the reboot to syslogd(1M) or to /var/adm/wtmpx. The kernel still attempts to sync
filesystems prior to reboot, except if the -d option is also present. If -d is used with -n, the kernel does not attempt to
sync filesystems.
-q Quick. Reboot quickly and ungracefully, without shutting down running processes first.
The following operands are supported:
boot_arguments An optional boot_arguments specifies arguments to the uadmin(2) function that are passed to the boot program and kernel
upon restart. The form and list of arguments is described in the boot(1M) and kernel(1M) man pages.. If the arguments are
specified, whitespace between them is replaced by single spaces unless the whitespace is quoted for the shell. If the
boot_arguments begin with a hyphen, they must be preceded by the -- delimiter (two hyphens) to denote the end of the reboot
argument list.
Example 1: Passing the -r and -v Arguments to boot
In the following example, the delimiter -- (two hyphens) must be used to separate the options of reboot from the arguments of boot(1M).
example# reboot -dl -- -rv
Example 2: Rebooting Using a Specific Disk and Kernel
The following example reboots using a specific disk and kernel.
example# reboot disk1 kernel.test/unix
/var/adm/wtmpx login accounting file
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
mdb(1), boot(1M), dumpadm(1M), fsck(1M), halt(1M), init(1M), kernel(1M), shutdown(1M), sync(1M), syslogd(1M), sync(2), uadmin(2),
reboot(3C), attributes(5)
The reboot utility does not execute the scripts in /etc/rcnum.d or execute shutdown actions in inittab(4). To ensure a complete shutdown
of system services, use shutdown(1M) or init(1M) to reboot a Solaris system.
11 Apr 2005 reboot(1M)