Sponsored Content
Special Forums Hardware Multi-bit ECC Error on X4100 M2 Server Sun Fire Post 302925272 by hhaswan on Saturday 15th of November 2014 10:20:36 AM
Old 11-15-2014
Quote:
Originally Posted by hicksd8
If you've not already done it, I would disable "quick boot" in the BIOS to force the machine to test all it's memory during POST.

The A1+B1 slot configuration each side is correct according to the book.

Perhaps there's a faulty DIMM. If so, with "quick boot" disabled POST should crash and tell you something.
I didn't see option "quick boot" in BIOS system. Do you have any solutions for this?
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

unable to telnet from win xp to sun fire v880 server

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

Does the Sun fire x4100 support HVM?

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

How to create Logical domain in Sun Fire T2000 server

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

Sun Fire V240 server Fan replacement

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

Need Help, I want to reset password for Sun Fire T2000 Server

============================== 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

Ubuntu Install on Sun Fire X4100 network issues

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

Help with Solaris 8 10/00 Installation on Sun Fire V490 Server

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

Solaris 10 1/13 & Sun Fire V490 Server

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
BOOT0CFG(8)						    BSD System Manager's Manual 					       BOOT0CFG(8)

NAME
boot0cfg -- boot manager installation/configuration utility SYNOPSIS
boot0cfg [-Bv] [-b boot0] [-d drive] [-e bell character] [-f file] [-i volume-id] [-m mask] [-o options] [-s slice] [-t ticks] disk DESCRIPTION
The FreeBSD 'boot0' boot manager permits the operator to select from which disk and slice an i386 machine (PC) is booted. Note that what are referred to here as ``slices'' are typically called ``partitions'' in non-BSD documentation relating to the PC. Typi- cally, only non-removable disks are sliced. The boot0cfg utility optionally installs the 'boot0' boot manager on the specified disk; and allows various operational parameters to be con- figured. On PCs, a boot manager typically occupies sector 0 of a disk, which is known as the Master Boot Record (MBR). The MBR contains both code (to which control is passed by the PC BIOS) and data (an embedded table of defined slices). The options are: -B Install the 'boot0' boot manager. This option causes MBR code to be replaced, without affecting the embedded slice table. -b boot0 Specify which 'boot0' image to use. The default is /boot/boot0 which will use the video card as output, alternatively /boot/boot0sio can be used for output to the COM1 port. (Be aware that nothing will be output to the COM1 port unless the modem signals DSR and CTS are active.) -d drive Specify the drive number used by the PC BIOS in referencing the drive which contains the specified disk. Typically this will be 0x80 for the first hard drive, 0x81 for the second hard drive, and so on; however any integer between 0 and 0xff is acceptable here. -e bell character Set the character to be printed in case of input error. -f file Specify that a backup copy of the preexisting MBR should be written to file. This file is created if it does not exist, and replaced if it does. -i volume-id Specifies a volume-id (in the form XXXX-XXXX) to be saved at location 0x1b8 in the MBR. This information is sometimes used by NT, XP and Vista to identify the disk drive. The option is only compatible with version 2.00 of the 512-byte boot block. -m mask Specify slices to be enabled/disabled, where mask is an integer between 0 (no slices enabled) and 0xf (all four slices enabled). Each mask bit enables corresponding slice if set to 1. The least significant bit of the mask corresponds to slice 1, the most sig- nificant bit of the mask corresponds to slice 4. -o options A comma-separated string of any of the following options may be specified (with ``no'' prepended as necessary): packet Use the disk packet (BIOS INT 0x13 extensions) interface, as opposed to the legacy (CHS) interface, when doing disk I/O. This allows booting above cylinder 1023, but requires specific BIOS support. The default is 'packet'. setdrv Forces the drive containing the disk to be referenced using drive number definable by means of the -d option. The default is 'nosetdrv'. update Allow the MBR to be updated by the boot manager. (The MBR may be updated to flag slices as 'active', and to save slice selection information.) This is the default; a 'noupdate' option causes the MBR to be treated as read-only. -s slice Set the default boot selection to slice. Values between 1 and 4 refer to slices; a value of 5 refers to the option of booting from a second disk. The special string ``PXE'' or a value of 6 can be used to boot via PXE. -t ticks Set the timeout value to ticks. (There are approximately 18.2 ticks per second.) -v Verbose: display information about the slices defined, etc. FILES
/boot/boot0 The default 'boot0' image /boot/boot0sio Image for serial consoles (COM1,9600,8,N,1,MODEM) EXIT STATUS
The boot0cfg utility exits 0 on success, and >0 if an error occurs. EXAMPLES
To boot slice 2 on the next boot: boot0cfg -s 2 ada0 To enable just slices 1 and 3 in the menu: boot0cfg -m 0x5 ada0 To go back to non-interactive booting, use fdisk(8) to install the default MBR: fdisk -B ada0 SEE ALSO
geom(4), boot(8), fdisk(8), gpart(8) AUTHORS
Robert Nordier <rnordier@FreeBSD.org> BUGS
Use of the 'packet' option may cause 'boot0' to fail, depending on the nature of BIOS support. Use of the 'setdrv' option with an incorrect -d operand may cause the boot0 code to write the MBR to the wrong disk, thus trashing its previ- ous content. Be careful. BSD
October 1, 2013 BSD
All times are GMT -4. The time now is 02:33 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy