Sun Fire X2100 Blinking Status LED...

We have 3 new Sun Fire X2100 servers at my current job. Just recently the status LED (orange) started blinking. The logs show fine and running a prtdiag shows everything up and running fine. Is there a way to turn off the blinking LED? I have gone over every piece of information I can find and have found nothing about how to turn this off once it has started blinking.

This may be one of two issues:
- There's a know ILOM/nge driver bug in eariler releases of S10 x86 (pre 6/06).
- There's a know issue with an older firmware rev of the BIOS/LOM where the net management port hangs/drops out and triggers the blinking fault LED. Do you know what BIOS revision you are at?
Most times a mobo swap is NOT the fix. You may be making the problem worse because we have mobos in the supply chain with older firmware revisions.
On the X2100's I usually have my customers try:
- Moving the RAM in different slots
- Updating the BIOS/LOM firmware
- Running the PC-Check diags
... before I send a field tech out to do major surgery.

Similar Messages

SUN Fire V65 - System Status LED - non-critical condition

Hi guys
We have a Checkpoint Cluster which is made up of 2 Sun Fire V65 servers.
The front panel of the servers are showing the System Status LED lights as Blinking Amber , which sun documenation has listed as
"Blinking amber: Indicates the system is in a non-critical condition" ref: http://dlc.sun.com/pdf/817-2024-12/817-2024-12.pdf
We have resetead the hardware, cleared ,logs, even change HW etc. The light goes away for some time and then returns.
Can anyone advise on what to do?
Sun has the following listed in their Troubleshooting pdf i ref before
"Non-Critical Condition
A non-critical condition is indicated with a blinking amber status LED and signifies
that at least one of the following conditions is present:
¡ Temperature, voltage, or fan non-critical threshold crossing.
¡ Chassis intrusion.
¡ Satellite controller sends a non-critical state, via the Set Fault Indication
command, to the BMC.
¡ A Set Fault Indication command from the system BIOS. The BIOS may use the Set
Fault Indication command to indicate additional, non-critical status such as
system memory or CPU configuration changes"
Is there any Unix / Linux / SPLAT logs I can look at or debugging we can look at.
Thanks in advance

Your initial description mentions that you have swapped various pieces of hardware around. I presume that means you used current parts instead of new-never-used components. Are both of the clustered systems showing the same symptoms?
I can only think of a couple of additional things to try.
Firstly, those are old boxes. V65's went EOL in January 2005, so yours are at least that old if not older. They are x86 architecture. Have you replaced the CR2032 CMOS battery that's on the systemboard? Have you additionally checked for voltage fluctuations in the data center? A marginal power supply can "mostly work" but it can be effected by an AC mains issue.
If that doesn't change anything, then you may need to contact Checkpoint. They may be able to point you toward some sort of heartbeat function that is tripping a fault level when it flip-flops between the two systems.
That's a software investigation and would be outside the scope of this forum.

How to flash bios on Sun Fire X2100 (without cd/dvd drive ) from solaris.

Hi I have the following problem. I need to udpdate bios in my sun fire x2100 (not the m2 version). Installed system on it is the latest solaris 10. I have also one laptop with sxce b107. I need to update bios to support zfs root/mirror.
Both devices are int the one subnet.
I download supplement cd from sun, but I was pretty amazed that there is available only remote update from rhel (32bit) or boot from cd/dvd drive.
Any help is welcome.
Lubos Kocman

1. If an OS is installed:
- log in as you described
- shutdown the server with `init 0`
- this should bring you to the OK prompt
- Insert the bootable system software CDROM into the CDROM drive
- On the OK prompt, type `boot cdrom`
2. If no OS is installed:
- connect to the serial management port with your PC (Hyperterminal)
-> NOTE: you will need a DB-25 Adapter (Part No. 530-2889)
connect this adapter to the serial port of your PC, then connect the adapter
with an RJ45 cable to the serial management port of the server
-> Serial Port Settings in Hyper Terminal:
Duplex: Full
Bit Rate: 9600
Parity: None
Databits: 8
Stopbit: 1
Flow Control: Xon/Xoff
VT100 Emulation (if applicable): ON
- change to the OK prompt by typing `break`
-> if this does not work, try `reset -x`
- make sure your OS Installation CDROM is in the drive
- at the OK prompt, type `boot cdrom`

Cisco 1131AG LWAP status led yellow and other leds blinking green

I have a problem with three AIR-LAP1131AG-E-K9 that joined the controller and the status led turns to yellow after joining the controller while other LEDs are blinking green.
The APs has no coverage at all although the WCS shows that there is coverage and the 4400WLC shows that the AP interfaces are UP. (The ethernet interface and tha 802.11b,g radio interface is up).
The SSID broadcast is enabled.
On the switch the interface is up and there is traffic going in and out of the LAP.
I tired power reset and factory reset for the APs but the problem remains the same.
Any ideas for what might be the problem ?!!
Regards

Yes the clients are not able to see the SSID broadcasted by the AP.
But these APs were functioning normally before without any changes to the WLC config.
I had the same problem with other APs but they went back to normal state after a hardware reset to the APs.

FP-1600 Status LED blinks 17 times.

My FieldPoint bank has 9 modules. I previously had a problem with the FP-TB-10 power and ready lights blinking, but that was because one of my dual-channel modules was not seated correctly. Now the status LED is blinking 17 times. The manual says to contact NI about this. The FieldPoint Explorer seems to find all of the modules correctly, though. Anyone know what's up?

Aaron,
I checked the firmware and the FieldPoint Explorer version, and I'm using 3.20 and 3.0, respectively. When I power cycle the FP-1600, the 17 blinks of the status LED go away. Communication works, and all of the devices are found. However, communication does drop out from time to time, and eventually the status LED begins blinking 17 times again.
A possibly related issue is that the FP-AI-V10 dual-channel module that I have plugged into slot 2 of the FP-TB-10 base causes the FP-TB-10 to flash its power and ready LEDs. Re-seating the FP-AI-V10 seems to fix this, although the module is definitely already clicked into place when I see this problem. Upon reseating (or just pressing on it without removing the module), the FieldPoint Explo
rer program finds this module.
I'm tempted to think that this issue with the FP-TB-10 and FP-AI-V10 are unrelated to the FP-1600's status LED blinking 17 times because even with the FP-TB-10 removed from the bank, I still get the flashing LED.
Any ideas? Also, what is a GPF type error?
Thanks,
Jake

CIsco AIR LAP1131AG E K9 Status LED = Yellow; Ethernet LED = Off; Radio LED = blinking Red, what is this? it isn't in the manual

CIsco AIR LAP1131AG E K9 Status LED = Yellow; Ethernet LED = Off; Radio LED = blinking Red in a pattern, red off then red red, Our AP isn't working it won't show up on our Cisco WLC 2125 anymore and this is the LED indicators, I've checked in the manual and this combination of LEDs do not exists??

No cisco web is working perfectly.
do you have a valid CCO id with smarnet contract ?? then only you can download new IOS for AP:
Autonomous AP image:
http://software.cisco.com/download/release.html?mdfid=279537722&flowid=6775&softwareid=284180979&release=12.4.25d-JA2&relind=AVAILABLE&rellifecycle=ED&reltype=latest
LAP AP image:
http://software.cisco.com/download/release.html?mdfid=279537722&flowid=6775&softwareid=280775090&release=12.4.25e-JAP&relind=AVAILABLE&rellifecycle=ED&reltype=latest
Regards

NI smart camera 1764 Status LED Blinking

I am using NI smart camera 1764. when i am giving 24 V DC supply to the camera then Power & Status LED is blinking continuously in RED colour. on the other hand pass & fail LED also blinking in RED & GREEN colour alternatively. i am not able to connect camera to my computer through ETHERNET cable & cannot use for my application.
Please suggest me the solution as soon as possible.

Have a look at chapter 6 of this manual:
http://www.ni.com/pdf/manuals/372429b.pdf
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies

D400 - system status LED blinking, network LED blinking

Hi - Just recently started experiencing this problem with my D400.
The system status LED is blinking, which according to the user guide means that WHS is either booting or shutting down. The Network LED shows activity.
Problem is that I can't get on the D400 via remote desktop.
Frustrating. Talked with support already, said only option is to send in to depot or find a local resource to troubleshoot or fix. Problem is that we have our music/photos on this thing.
Support also said that if we factory reset data on all drives will be erased.
Looking for help wherever I can get it. Thanks!
Scott

Hi scottdcm, and welcome to the Lenovo User Community!
To get your music/photos off the system before returning it for service, connect the hard drive(s) to another computer with a SATA connection. An external USB/SATA connector or drive enclosure will also do the job.
You can also remove any drives you have added before shipping it for service.
Hope this helps!
I don't work for Lenovo. I'm a crazy volunteer!

Fp-2000 status LED starts blinking

The status led of my FP-2000 started blinking twice after turning off my module and turning it on again, I already updated the firmware to version 10.4 following the indicated steps. I already tried in safe mode, also reset and format disk , always after configuring the IP the status button starts blinking twice, again.
Thank you for your support

Hi Srael
Try following this document to see if you can solve the problem
http://zone.ni.com/devzone/cda/tut/p/id/4466
Greetings
Julio Mena

UCS240 M3 System status LED Amber blinking

Hi Guys
I have a alarm in the UCS240 . The System status LED Amber is blinking, but in the vCenter nothing appears abnormal.
Please see the captures:
-System Event
-System Status
- CPU
- Memory
- Storage
-Temperature
-Platform Alert
TIA
Cristian

Dear Eric
Time :Fri Dec 20 12:55:17 2013
Severity :Warning
Code :F1008
DN :sys/rack-unit-1/board/storage-FLASH-ctlr-1/vd-HV
Probable Cause :equipmentDegraded
Description :Flex Flash Virtual Drive HV Degraded: please check the flash device or the controller
TIA.
Cristian

GD80 Status LED and System Suspend problem

Hi everyone.
My hardware:
- MSI P55-GD80
-BIOS AMI v1.4
-Intel Core i7 860
-OCZ 4GB (2x2GB) 1600MHz CL8 Gold Low-Voltage
-Zotac GeForce GTX 275 896MB
- PSU: Corsair TX850W
-HDD : 1- Seagate Barracuda 7200.12 250GB (ST3250318AS); 2 - Seagate Barracuda 7200.10 500GB (ST3500630AS); 3 - Samsung Spinpoint F3 1TB (HD103SJ)
- Debian GNU/Linux "Squeeze", kernel 2.6.32, amd64
I have a problem with LEDs on motherboard. when they are lighting I can't "wake up" pc from S3 state (aka suspend). It just restarts when wake up event appears.
Actually the lighting LEDs are: 1&2 VTT_PHASE; "LED2" , which indicates active PCI-Express 16x port; CPU Phase LED panel (it shows 8) and + - buttons used for overclocking (OC Gene and these buttons are turned off in BIOS)
But the strangest thing is that the LEDs sometimes turns on and off (actually one day they do, in other they don't) when I turn on computer, even when they are disabled in BIOS (Green Power => Motherboard LED Control) [btw. Touch Panel is disabled and it still works ]
I have cleared CMOS , swapped SATA cables and I have checked RAM and PCI-Express connection (sometimes when I reinsert graphic card everything starts to work well, but for a few days the problem appears again. The same goes to SATA cable )
Anyway it looks to me like an error reporting (or something) but there is nothing about that in the manual. (or it's a BIOS bug).
I have been searching about it, but i haven't found anything.
Anyone had this kind of problem?
EDIT: BIOS upgrade from 1.4 to 1.5 didn't help.

Hi ctemp1,
Alert: sc0 Config Reader (Sun Fire High-End
Systems) A Status Domain A - Domain Status is: In
Recovery
But the domain has not been restart.
$ uptime
12:28pm up 52 day(s), 2:41, 6 users, load
average: 2.35, 2.49, 2.66SunMC is forwarding the status detected by your SMS daemons: so uptime probably isn't showing the whole story. Try a SMS command like "showenvironment -d A" and see what's reported.
Also what version of SMS are you running? SunMC has an update available for the new SC hardware, USIV uniboards, and newer versions of SMS that change the SunMC addon from the name "12k-15k" to "High-end Systems":
http://www.sun.com/download/products.xml?id=431df39d
If it looks like there's a mismatch between what SunMC and SMS are reporting, and you're running a newer version of SMS (i.e. 1.5) then you should give that update a try.
Regards,
[email protected]
http://www.HalcyonInc.com

"Memory Sizing" error on Sun Fire V65x

Hello.
I have some trouble with my old Sun Fire V65x and i hope that you guys can help me out.
I had 2,5GB RAM installed in my server, working flawless. 2 x 256MB and 2 x 1GB modules. 256-modules in Bank 1 and 1GB´s in Bank 2.
To get rid of the boot up warning of wrong memory configuration i moved the 2 1GB modules to bank 3 (as stated in the manual) but that was when the problem started.
In this configuration the server won't go to POST, i tried moving the 1GB modules around between bank 1, 2 & 3 without any result.
The server will not go to POST. No beeps, no nothing. When turning the server on line it starts up, the fans starts running on at maximum speed and that's all, no picture and no POST and the system warning LED turns to red. After a couple of minutes in this state the fans slow down for a couple of seconds and then back to 100% (repeating cycle)
The POST diagnostics LEDs at the back of the main board indicates POST code 13h, "Memory sizing". The main board does not report any defective DIMMs, also worth mentioning is that the 2 256MB DIMMs are working flawlessly in all banks.
I have tried:
Resetting the memory config in BIOS (using the 2x256 DIMMs and then installing the 2 1GB modules.
Moving the memory modules around between different banks, both alone and with the 2 256MB DIMMs present.
Clearing the CMOS settings.
Searching manuals and Google for hours without answer to my problem or what "memory sizing " means in this situation.
System:
Sun Fire V65x
1 CPU
If anyone know the answer to my dilemma and are willing to help me, i would be really grateful.
Sadly i do not have the possibility to test the memory modules in another system.
Best regards. Erik Järlestrand, Sweden.

Hardware. A reboot will probably not do anything. From what I can tell, it's a CPU cache problem. If you do anything, shut the system down completely, turn the power off for a minimum of 20 seconds to let any residual electricty go away, the turn it back on. If the problem returns, you'll most likely need to either get a new CPU module or a new V100. I don't know if the CPU can be removed from the V100 motherboard, but since there are jumper settings for the speed I would assume that you can.

Sun Fire V250 Error while booting

Dear all,
I have one Sun Fire V250 which was down for fews days and when I booted now it gives the following messages after booting. Is it the problem with the memory modules. It has 2 DIMM with each of 1 GB.
Thanks in Advance
sc>+
sc> poweron+
SC Alert: Host System has Reset+
sc> con+
Invalid command. Type 'help' for list of commands.+
sc> console+
Enter #. to return to ALOM.+
*1>Init CPU*
+*1>     UltraSPARC[TM] IIIi, Version 2.4*+
*1>DMMU*
*1>DMMU TLB DATA RAM Access*
*1>DMMU TLB TAGS Access*
*1>IMMU Registers Access*
*1>IMMU TLB DATA RAM Access*
*1>IMMU TLB TAGS Access*
*1>Init mmu regs*
*1>Setup L2 Cache*
*1>L2 Cache Control = 00000000.00f04400*
*1>     Size = 00000000.00100000...*
*1>Scrub and Setup L2 Cache*
*1>Setup and Enable DMMU*
*1>Setup DMMU Miss Handler*
*1>Test and Init Temp Mailbox*
*1>CPU Tick and Tick Compare Registers Test*
*1>CPU Stick and Stick Compare Registers Test*
*1>Setup Int Handlers*
*0>Setup Int Handlers*
*0>Send Int CPU 1*
*1>Send Int to Master CPU*
*0>Initialize I2C Controller*
*0>MB:     Part-Dash-Rev#: 3753130-02-50     Serial#: 020322*
*0>Set CPU/System Speed*
*0>MCR Timing index = 00000000.00000002*
*0>..*
*0>Send MC Timing CPU 1*
*0>Probe Dimms*
*1>Probe Dimms*
*1>Init Mem Controller Regs*
*0>Init Mem Controller Regs*
*1>Set JBUS config reg*
*0>Set JBUS config reg*
*0>IO-Bridge unit 0 init test*
*0>IO-Bridge unit 1 init test*
*0>Do PLL reset*
*0>Setting timing to 8:1 10:1, system frequency 160 MHz, CPU frequency 1280 MHz*
*0>Soft Power-on RST thru SW*
*0>CPUs present in system: 0 1*
+*0>*+
*0>Resume selftest...*
*0>Init SB*
*0>Init CPU*
*0>Init mmu regs*
*0>Setup L2 Cache*
*0>L2 Cache Control = 00000000.00f04400*
*0>     Size = 00000000.00100000...*
*0>Setup and Enable DMMU*
*0>Setup DMMU Miss Handler*
*0>Timing is 8:1 10:1, sys 159 MHz, CPU 1279 MHz, mem 127 MHz.*
+*0>     UltraSPARC[TM] IIIi, Version 2.4*+
*1>Init CPU*
+*1>     UltraSPARC[TM] IIIi, Version 2.4*+
*1>Init mmu regs*
*1>Setup L2 Cache*
*1>L2 Cache Control = 00000000.00f04400*
*1>     Size = 00000000.00100000...*
*1>Setup and Enable DMMU*
*1>Setup DMMU Miss Handler*
*1>Timing is 8:1 10:1, sys 159 MHz, CPU 1279 MHz, mem 127 MHz.*
*0>Initialize I2C Controller*
*1>Init Mem Controller Sequence*
*0>Init Mem Controller Sequence*
*0>IO-Bridge unit 0 init test*
*0>IO-Bridge unit 1 init test*
*0>Select Bank Config*
*0>Probe and Setup Memory*
*0>INFO:     1024MB Bank 0, Dimm Type X4*
*0>INFO:     1024MB Bank 1, Dimm Type X4*
*0>INFO:     No memory detected in Bank 2*
*0>INFO:     No memory detected in Bank 3*
+*0>*+
*0>Data Bitwalk on Master*
*0>     Test Bank 0.*
+*0>*+
*0>ERROR: TEST = Data Bitwalk on Master*
*0>H/W under test = CPU0: Bank0 DIMM0, Motherboard*
*0>Repair Instructions: Replace items in order listed by 'H/W under test' above*
*0>MSG = Pin 79 failed on CPU0: Bank0 DIMM0, Motherboard*
*0>END_ERROR*
*0>     Test Bank 1.*
+*0>*+
*0>ERROR: TEST = Data Bitwalk on Master*
*0>H/W under test = CPU0: Bank1 DIMM0, Motherboard*
*0>Repair Instructions: Replace items in order listed by 'H/W under test' above*
*0>MSG = Pin 79 failed on CPU0: Bank1 DIMM0, Motherboard*
*0>END_ERROR*
+*0>*+
*0>ERROR: TEST = Data Bitwalk on Master*
*0>H/W under test = CPU, Memory, Motherboard*
*0>Repair Instructions: Replace items in order listed by 'H/W under test' above*
*0>MSG =*
*      *** Test Failed!! ****
*0>END_ERROR*
+*0>*+
*0>ERROR: TEST = Data Bitwalk on Master*
*0>H/W under test = CPU, Memory, Motherboard*
*0>Repair Instructions: Replace items in order listed by 'H/W under test' above*
*0>MSG = No good memory available on master CPU 0, rolling over to new Master.*
*0>END_ERROR*
*1>Soft Power-on RST thru SW*
*1>CPUs present in system: 0 1*
*1>OBP->POST Call with %o0=00000000.05002000.*
*1>Diag level set to MIN.*
*1>MFG scrpt mode set to NONE*
*1>I/O port set to TTYA.*
+*1>*+
*1>Start selftest...*
*1>Init SB*
*1>Init CPU*
*1>DMMU*
*1>DMMU TLB DATA RAM Access*
*1>DMMU TLB TAGS Access*
*1>IMMU Registers Access*
*1>IMMU TLB DATA RAM Access*
*1>IMMU TLB TAGS Access*
*1>Init mmu regs*
*1>Setup L2 Cache*
*1>L2 Cache Control = 00000000.00f04400*
*1>     Size = 00000000.00100000...*
*1>Scrub and Setup L2 Cache*
*1>Setup and Enable DMMU*
*1>Setup DMMU Miss Handler*
*1>Test and Init Temp Mailbox*
*1>CPU Tick and Tick Compare Registers Test*
*1>CPU Stick and Stick Compare Registers Test*
*1>Set Timing*
+*1>     UltraSPARC[TM] IIIi, Version 2.4*+
*0>Init CPU*
+*0>     UltraSPARC[TM] IIIi, Version 2.4*+
*0>DMMU*
*0>DMMU TLB DATA RAM Access*
*0>DMMU TLB TAGS Access*
*0>IMMU Registers Access*
*0>IMMU TLB DATA RAM Access*
*0>IMMU TLB TAGS Access*
*0>Init mmu regs*
*0>Setup L2 Cache*
*0>L2 Cache Control = 00000000.00f04400*
*0>     Size = 00000000.00100000...*
*0>Scrub and Setup L2 Cache*
*0>Setup and Enable DMMU*
*0>Setup DMMU Miss Handler*
*0>Test and Init Temp Mailbox*
*0>CPU Tick and Tick Compare Registers Test*
*0>CPU Stick and Stick Compare Registers Test*
*0>Setup Int Handlers*
*1>Setup Int Handlers*
*1>Send Int CPU 0*
*0>Send Int to Master CPU*
*1>Initialize I2C Controller*
*1>MB:     Part-Dash-Rev#: 3753130-02-50     Serial#: 020322*
*1>Set CPU/System Speed*
*1>MCR Timing index = 00000000.00000002*
*1>..*
*1>Send MC Timing CPU 0*
*1>Probe Dimms*
*0>Probe Dimms*
*0>Init Mem Controller Regs*
*1>Init Mem Controller Regs*
*0>Set JBUS config reg*
*1>Set JBUS config reg*
*1>IO-Bridge unit 0 init test*
*1>IO-Bridge unit 1 init test*
*1>Do PLL reset*
*1>Setting timing to 8:1 10:1, system frequency 160 MHz, CPU frequency 1280 MHz*
*1>Soft Power-on RST thru SW*
*1>CPUs present in system: 0 1*
+*1>*+
*1>Resume selftest...*
*1>Init SB*
*1>Init CPU*
*1>Init mmu regs*
*1>Setup L2 Cache*
*1>L2 Cache Control = 00000000.00f04400*
*1>     Size = 00000000.00100000...*
*1>Setup and Enable DMMU*
*1>Setup DMMU Miss Handler*
*1>Timing is 8:1 10:1, sys 159 MHz, CPU 1279 MHz, mem 127 MHz.*
+*1>     UltraSPARC[TM] IIIi, Version 2.4*+
*0>Init CPU*
+*0>     UltraSPARC[TM] IIIi, Version 2.4*+
*0>Init mmu regs*
*0>Setup L2 Cache*
*0>L2 Cache Control = 00000000.00f04400*
*0>     Size = 00000000.00100000...*
*0>Setup and Enable DMMU*
*0>Setup DMMU Miss Handler*
*0>Timing is 8:1 10:1, sys 159 MHz, CPU 1279 MHz, mem 127 MHz.*
*1>Initialize I2C Controller*
*0>Init Mem Controller Sequence*
*1>Init Mem Controller Sequence*
*1>IO-Bridge unit 0 init test*
*1>IO-Bridge unit 1 init test*
*1>Select Bank Config*
*1>Probe and Setup Memory*
*1>INFO: No memory on cpu 1*
+*1>*+
*1>ERROR: TEST = Probe and Setup Memory*
*1>H/W under test = CPU1 Memory*
*1>Repair Instructions: Replace items in order listed by 'H/W under test' above*
*1>MSG = No good memory available on master CPU 1, rolling over to new Master.*
*1>END_ERROR*
*1>ERROR:*
*1>     POST toplevel status has the following failures:*
*1>          CPU0: Bank0 DIMM0, Motherboard*
*1>          CPU0: Bank1 DIMM0, Motherboard*
*1>END_ERROR*
+*1>*+
*1>ERROR:     No good CPUs OR CPUs with good memory left. Calling debug menu.*
*1>     0     Peek/Poke interface*
*1>     1     Dump CPU Regs*
*1>     2     Dump Mem Controller Regs*
*1>     3     Dump Valid DMMU entries*
*1>     4     Dump IMMU entries*
*1>     5     Dump Mailbox*
*1>     6     Dump IO-Bridge regs unit 0*
*1>     7     Dump IO-Bridge regs unit 1*
*1>     8     Allow other CPUs to print*
*1>     9     Do soft reset*
*1>     ?     Help*

I have just experienced this issue while patching Solaris 10 on a V240 system using Live Upgrade.
The issue was resolved by performing a failsafe boot from the console ("boot -F failsafe"), splitting the (new/alt) root mirror, mounting the primary half, performing fsck several times (as filesystem issues were apparrent), then mounting the slice and installing the new bootblock using the version of installboot from the new root and rebuilding the boot archive manually:
# mount /dev/dsk/c1t0d0s4 /a
# /a/usr/sbin/installboot /a/usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/c1t0d0s4
# bootadm update-archive -R /aI note that the OpenSolaris bug linked to above lists four criteria for reproducing this problem:
1. Install u6 ( SUNWCreq ( no mkisofs so we build ufs boot archive )
2. Limit /tmp to 512M ( so forcing the ufs build to happen in /var/run
3. Have seperate /var ( bootadm.c only lofs nosub mounts / when creating the alt root for DAP patching build of boot archive )
4. Install 139555-08
The system I was patching met the last three of these, but not the first one (pkginfo does not show SUNWCreq as being installed). However, this was not an OpenSolaris system, which may make a difference.
Rob

CPU temperature is too high in Solaris 10 sun fire v890 machine

Hi,
I just installed Solaris 10 on a sun fire v890 machine. I used the prtdiag -v command to check the system.
However, It appears to me that the CPU temperatures is higher than the temperature range specified in the technical specification. The server is a standalone node that does not connect to the network or process anything.
Is it a problem? Thank you.
========================= Environmental Status =========================
System Temperatures (Celsius):
Device Temperature Status
CPU0 77 OK
CPU1 76 OK
CPU2 77 OK
CPU3 74 OK
MB 28 OK
IOB 24 OK
DBP0 23 OK
Environmental
AC power      200-240 VAC, 47-63 Hz, 2078 VA
Operating temperature
* 5� C to 35� C (41� F to 95� F), 20% to 80% relative humidity, non condensing, 27� C max. wet bulb
* 2.1 GHz UltraSPARC IV+ processor: ASHRAE Class 3 (35C/900m) and/or 28C/10kft
Non operating temperature      -20� C to 60� C (-4� F to 140� F), 95% at 40� C relative humidity, non condensing
Regards,
Ryan

Hi Rukbat,
Thanks for your reply.
I have displayed the verbose prtdiag -v on the v890 machine.
However, I couldn't find the hard-coded operational ranges. Could you please advise?
Hi Sun-worshiper,
I executed the command and couldn't find the targeted temperature.
bash-3.00# prtpicl -v -c temperature-sensor | more
CPU0_DIE_TEMPERATURE_SENSOR (temperature-sensor, 8d00000e17)
:PSVC_FRU (8d00001ec9TBL)
| (8d0000124bH) |
:PSVC_PHYSICAL_DEVICE (8d00001da6TBL)
| (8d00001278H) |
:PSVC_PARENT (8d00001867TBL)
| (8d00000dadH) |
:PSVC_TS_OVERTEMP_LED (8d00001649TBL)
| (8d0000101aH) | (8d00000de3H) |
:HighShutdownThreshold 105
:HighWarningThreshold 100
:LowShutdownThreshold -15
:LowWarningThreshold -10
:Temperature 52
:FaultInformation NO_FAULT
:State OK
:_class temperature-sensor
:name CPU0_DIE_TEMPERATURE_SENSOR
CPU2_DIE_TEMPERATURE_SENSOR (temperature-sensor, 8d00000e35)
:PSVC_FRU (8d00001ed2TBL)
| (8d0000124bH) |
:PSVC_PHYSICAL_DEVICE (8d00001dafTBL)
| (8d00001287H) |
:PSVC_PARENT (8d00001870TBL)
| (8d00000dadH) |
:PSVC_TS_OVERTEMP_LED (8d00001655TBL)
| (8d0000101aH) | (8d00000de3H) |
:HighShutdownThreshold 105
:HighWarningThreshold 100
:LowShutdownThreshold -15
:LowWarningThreshold -10
:Temperature 52
:FaultInformation NO_FAULT
:State OK
:_class temperature-sensor
:name CPU2_DIE_TEMPERATURE_SENSOR
MB_AMB_TEMPERATURE_SENSOR (temperature-sensor, 8d00000e8f)
:PSVC_FRU (8d00001ef6TBL)
| (8d0000125aH) |
:PSVC_PHYSICAL_DEVICE (8d00001dcaTBL)
| (8d000012f0H) |
:PSVC_PARENT (8d0000188bTBL)
| (8d00000b34H) |
:PSVC_TS_OVERTEMP_LED (8d00001679TBL)
| (8d0000101aH) |
:HighShutdownThreshold 75
:HighWarningThreshold 70
:LowShutdownThreshold -15
:LowWarningThreshold -10
:Temperature 28
:FaultInformation NO_FAULT
:State OK
:_class temperature-sensor
:name MB_AMB_TEMPERATURE_SENSOR
IOB_AMB_TEMPERATURE_SENSOR (temperature-sensor, 8d00000e99)
:PSVC_FRU (8d00001eedTBL)
| (8d0000125fH) |
:PSVC_PHYSICAL_DEVICE (8d00001dcdTBL)
| (8d000012f0H) |
:PSVC_PARENT (8d0000188eTBL)
| (8d00000b34H) |
:PSVC_TS_OVERTEMP_LED (8d0000167cTBL)
| (8d00001014H) |
:HighShutdownThreshold 53
:HighWarningThreshold 48
:LowShutdownThreshold -15
:LowWarningThreshold -10
:Temperature 25
:FaultInformation NO_FAULT
:State OK
:_class temperature-sensor
:name IOB_AMB_TEMPERATURE_SENSOR
DBP0_AMB_TEMPERATURE_SENSOR (temperature-sensor, 8d00000ed9)
:PSVC_FRU (8d00001ef0TBL)
| (8d00001322H) |
:PSVC_PHYSICAL_DEVICE (8d00001dd0TBL)
| (8d00001304H) |
:PSVC_PARENT (8d000018afTBL)
| (8d00000eadH) |
:PSVC_TS_OVERTEMP_LED (8d0000167fTBL)
| (8d00001014H) |
:HighShutdownThreshold 55
:HighWarningThreshold 51
:LowShutdownThreshold -15
:LowWarningThreshold -10
:Temperature 26
:FaultInformation NO_FAULT
:State OK
:_class temperature-sensor
:name DBP0_AMB_TEMPERATURE_SENSOR
Regards,
Ryan
Edited by: puikeong on Mar 5, 2008 6:45 PM
Edited by: puikeong on Mar 5, 2008 6:47 PM

Lenovo 3000 N500 23G Battery Status LED problem.

I am having problems with the Battery Status LED on my new laptop. The LED turns blue at around 22-30% charge and the Hardware manual indicates it should be 95%, also the LED remains lit when fully charged on battery power when it should be off. The biggest problem is that I have no idea on when the battery is charged and I should not need to boot into windows to check this.
I have already returned an identical model to the retailer for the same reason, they did confirm that the unit was faulty and send me another which seems to have the same suspected fault.
Has any one else have the same problem as me, I am not too sure if I should return the 2nd unit for a refund and look elsewhere?
I did contact Lenovo support before and was advised to get it repaired under warranty, I did not need to do this as the unit is less than 30 days old and I wouldbe entitled to a refund or replacement.
Below is an excerpt from the manual I downloaded from this website.
Thanks, Mark.
Blue: The battery is charged to 95% or more of its capacity.
Blinking blue: The battery is being trickle-charged
Orange: The battery is being normally charged
Off: The computer is operating on battery power, and the battery has enough power
Blinking orange: The computer is operating on battery power, and the battery is charged to no more than 8% of capacity.)

The battery is going to fail on this unit; actually it is a defect in the circuit built into the battery the detects charge level. It has been happening quite frequently with IBM/Lenovo batteries these days. If you have warranty left, get the unit in for repair or you will be out of luck like the rest of us who bought these units with failure prone batteries and a poor excuse for product quality. If you care to help your fellow Lenovo owners, call, email, write, picket, jump up and down, do what ever you have to do to voice your concern and complaint to as high a person as you can at IBM and Lenovo. We have to keep the heat on at a corporate level at both IBM and Lenovo, to remind them that there is a price to pay for the fact that they do not care about their customers.

Sun Fire X2100 Blinking Status LED...

Similar Messages

Maybe you are looking for