11-13-2014
Quote:
Originally Posted by
achenle
Did you use ECC memory?
Did you use IBM memory, or something off-the-shelf?
What are the BIOS memory settings?
Either you used the wrong memory, the BIOS settings are incorrect, or your memory is bad.
And IBM servers tend to work only with IBM memory. You might get them to work with non-IBM memory, but you're lucky if it works.
yeah I use ECC Memory especially for X4100 M2 Server Sun Fire Microsystem same as the manufacture of the server.
whether this have relate with BIOS memory settings?
If I move memory 1 GB in A0, B0, A1, and B1 slots, the system will appear this message "bank interleave requested but not enable" but I can enter in Linux System and work correctly
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi everybody
i am trying to telnet to sun server from win xp machine but getting message "x21 error connection closed by remote user". i had make changes in /etc/default/login & /etc/fuser file still i have not getting telnet access. my win xp machines ip is 10.205.121.177 & sun server ip is... (1 Reply)
Discussion started by: pshelke
1 Replies
2. Solaris
I have looked all over the bios configuration to enable hardware virtualization and found nothing. Could someone tell if this server support it and if so where I go to enable that feature. By the way this is a x86 server. (0 Replies)
Discussion started by: jsandova
0 Replies
3. Solaris
Hi
I am fresher in Virtualisation in solaris 10.I need to know how to install and configure guest OS, I have a server Sun T2000 with solaris 10 OS BASE.
How to install logical domain, what are the prerequest for installing l domain
can some one guide me what are the basic requirement to... (2 Replies)
Discussion started by: solaris8in
2 Replies
4. Solaris
I have a sun fire v240 server.
The output of prtdiag -v shows a failed fan.
There are 3 fans for cooling system board.
There is 1 fan for each of the powersupply (There are 2 powersupplies)
From the below output how do i know which fan is bad and whats its location... (3 Replies)
Discussion started by: Tirmazi
3 Replies
5. Solaris
==============================
ALOM BOOTMON v1.3.1
ALOM Build Release: 001
Reset register: f0000000 EHRS ESRS LLRS SWRS
ALOM POST 1.0
Dual Port Memory Test, PASSED.
TTY External - Internal Loopback Test
TTY External - Internal Loopback Test, PASSED.
TTYC - Internal Loopback Test
TTYC -... (4 Replies)
Discussion started by: Sameer Naik
4 Replies
6. Ubuntu
Hi
I have two Sun Fire X4100 machines with Ubuntu 12.04 installed on them.
I am able to configure the Net Mgt port with an IP address and access the ILOM from the browser. I can also boot the Ubuntu installed and redirect the output.
The issue i have is that when i configure the network... (0 Replies)
Discussion started by: kaf3773
0 Replies
7. Solaris
cat note
Hi Sun Solaris Experts,
When I try to install Solaris 8 10/00 OS via the Solaris 8 Installation Disk on our Sun Fire V490 Server using the command , I get:
boot: cannot open kernel/sparcv9/unix
which means it can't find the unix kernel file on the installation disk .
By the way, I... (5 Replies)
Discussion started by: ssabet
5 Replies
8. Solaris
Hi Solaris/Unix Experts,
I've installed Oracle Solaris 10 1/13 on a Sun Fire V490 Server via its external Serial Port using a Cisco Console Cable connected to my Laptop PC running SecureCRT terminal emulation software emulating VT100 Terminal.
The Sun Fire V490 server has two on-board... (1 Reply)
Discussion started by: ssabet
1 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)