06-18-2011
POST error on SunFire V245
I've recently bought an SunFire V245.
2x 2.5ghz x64
4gb ram
4x 73gb sas hdd
and... an blinking 'Identifior led' (white) with 'Service led' (amber) simultaneously.
It boots for +- 5 secs and then the error occurd.
Things done:
Removed all hdd.
Switched cpu
Switched/removed ram
removed and booted WITHOUT nvram
removed and booted WITHOUT battery
I saw that SUN has EOL'ed the V245, so my only option is 'hoping' that there are forums to help me, or waith on an auction for another chance of buying a V245. (this one has cost me €50 so...
)
10 More Discussions You Might Find Interesting
1. Solaris
Hello ,
I am connecting sumfire v245 server to my laptop Through ALOM method.i got the ALOM prompt but after that i am typing sc> console to go to system console but i am not able to,after typing console only this line is coming Type #. to go back to ALOM.
What to do ??
That server having... (5 Replies)
Discussion started by: avi157
5 Replies
2. UNIX for Dummies Questions & Answers
Please Help...
I have two sunfire V245 servers running Apache on Solaris 5.10. Both servers have the same settings and apps. Before we used serial port to connect to ALOM 1.6. We switched to net mgnt port because of virtualization of all our servers.
Situation:
Server 1 applied the solaris... (1 Reply)
Discussion started by: glieu
1 Replies
3. Solaris
Hi all,
I am getting the below error on Solaris sunfire v245 server
Error: can not display this video mode
optimum resolution 1024x768 60Hz
i am not able to resolve this .plz help me out ? (1 Reply)
Discussion started by: saurabh84g
1 Replies
4. Solaris
Hey all.
Wondering - I have a pair of V245's with no internal CD/DVD-ROM drives, and I want to install the latest/greatest Solaris 10.
Booting these machines with an external drive plugged in via USB does no good.
Is jumpstart or installing internal drives the only alternative?
I'm a... (1 Reply)
Discussion started by: b1f30
1 Replies
5. Solaris
Hello All,
I have noticed that one of my servers, the busiest has become increasingly slow to respond and execute commands, the running applications appear to be fine though.
Here is some output from vmstat :-
kthr memory page disk faults cpu
r b... (5 Replies)
Discussion started by: Wez
5 Replies
6. Solaris
Hi all!
I've a machine - SunFire V890, it've been failed by OS error for 2 weeks ago, and now, I must reinstall OS (Solaris 10 2009), the progress was successful, but when I reboot, it displayed the error like :
Error -256: Last trap memory ... access aligned
Error -256: Last trap memory... (1 Reply)
Discussion started by: trantuananh24hg
1 Replies
7. Solaris
Hello All,
We have a v245 that powered itself off for no reason. Searching around we discovered there is a bug were a temp error is being reported but doesnt actually exist, SUN released an EPIC update, the README is shown below but even after upgrading the ALOM to the latest v1.6.10 we do not... (8 Replies)
Discussion started by: Wez
8 Replies
8. Solaris
I'm running Solaris 10 (09/10) on Sun Fire T2000.
This error message is logged repeatedly in /var/adm/messages:
May 22 10:40:33 EBDW01 last message repeated 25 times
May 22 10:40:36 EBDW01 ipmievd: Reading sensors...
May 22 10:40:40 EBDW01 ipmievd: Error obtaining SDR info: Unknown... (4 Replies)
Discussion started by: Sun Fire
4 Replies
9. Solaris
Hi All,
I have an server Sun Fire V245 for which we had been trying to patch.
We get a message that the patch has been applied successfully but while trying to reboot after activating the new lu, the server is not booting up. Had reinstalled lustarter pack, required patches during the patching... (5 Replies)
Discussion started by: Rockyc3400
5 Replies
10. Hardware
Hello.
I have a sun v245 and I have no hard drive for it yet but i would like to connect it to my home router by ethernet cable so I can use Alom remotely. Could someone please tell me how to set it up.
Thank You (1 Reply)
Discussion started by: SunV245
1 Replies
RAM(4) Kernel Interfaces Manual RAM(4)
NAME
ram - ram disk driver
SYNOPSIS
/sys/conf/SYSTEM:
NRAM ram_size # RAM disk size (512-byte blocks)
major device number(s):
block: 3
minor device encoding:
must be zero (0)
DESCRIPTION
The ram pseudo-device provides a very fast extended memory store. It's use is intended for file systems like /tmp and applications which
need to access a reasonably large amount of data quickly.
The amount of memory dedicated to the ram device is controlled by the NRAM definition in units of 512-byte blocks. This is also patchable
in the system binary through the variable ram_size (though a patched system would have to be rebooted before any change took effect; see
adb(1)). This makes it easy to test the effects of different ram disk sizes on system performance. It's important to note that any space
given to the ram device is permanently allocated at system boot time. Dedicating too much memory can adversely affect system performance
by forcing the system to swap heavily as in a memory poor environment.
The block file accesses the ram disk via the system's buffering mechanism through a buffer sharing arrangement with the buffer cache. It
may be read and written without regard to physical disk records. There is no `raw' interface since no speed advantage is gained by such an
interface with the ram disk.
DISK SUPPORT
The ram driver does not support pseudo-disks (partitions). The special files refer to the entire `drive' as a single sequentially
addressed file.
A typical use for the ram disk would be to mount /tmp on it. Note that if this arrangement is recorded in /etc/fstab then /etc/rc will
have to be modified slightly to do a mkfs(8) on the ram disk before the standard file system checks are done.
FILES
/dev/ram block file
/dev/MAKEDEV script to create special files
/dev/MAKEDEV.local script to localize special files
SEE ALSO
hk(4), ra(4), rl(4), rk(4), rp(4), rx(4), si(4), xp(4) dtab(5), autoconfig(8)
DIAGNOSTICS
ram: no space. There is not enough memory to allocate the space needed by the ram disk. The ram disk is disabled. Any attempts to access
it will return an error.
ram: not allocated. No memory was allocated to the ram disk and an attempt was made to open it. Either not enough memory was available at
boot time or the kernel variable ram_size was set to zero.
BUGS
The ram driver is only available under 2.11BSD.
3rd Berkeley Distribution Januray 27, 1996 RAM(4)