Sponsored Content
Operating Systems Solaris Any hope for this bootlooping Sun V210? Post 303026542 by vext01 on Thursday 29th of November 2018 02:24:58 PM
Old 11-29-2018
Hi gull04,


Thanks for your ongoing patience with this thread!


I'm not at the machine, but off the top of my head `poweron:


  • does indeed turn the system on and spins up the fans.
  • generates the "system power on event" message.
  • a few fan failure messages.



About the fans, one fan failure message was a CPU fan, I removed that CPU entirely as I believe the system should work with only 1 CPU anyway. There was also one chassis fan failure. Again I don't think that would stop the system booting. (I have spares which I will fit if I can get the system to boot).


IIRC, once the system is in the poweron state, `console -f` should give an 'ok>' prompt after hitting 'console -f' (and enter twice).



I can get you the exact ALOM messages later when I'm at the system.

------ Post updated at 06:48 PM ------

I replaced the fans on the CPU.


The console output looks like this:


Code:
sc> poweron
sc> 
SC Alert: SC System booted.

sc> console -f
Enter #. to return to ALOM.

SC Alert: VOLTAGE_SENSOR @ MB.BAT.V_BAT has exceeded low warning threshold.


I can hit enter as many times as I like, but no 'ok' prompt.


If the CPU were bad, the ALOM would know, right?

------ Post updated at 07:24 PM ------

I also tried resetting nvram, and provideing a bootscript like:


Code:
setenv output-mode ttya


no cigar.
 

7 More Discussions You Might Find Interesting

1. Solaris

Sun Fire v210 display card

hi all, how can install a display card on a sun fire v210. regards. marcel (2 Replies)
Discussion started by: marcelious
2 Replies

2. Solaris

V210 to V440

I recently acquired a server for home use. Currently, I'm running a V210. I was wondering of a way to basically swap hard drives into the V440. I would like to avoid reinstall on the V440 for many reasons. Currently on the V440, when I try to boot up it forces itself into System Maintenance... (1 Reply)
Discussion started by: adelsin
1 Replies

3. Solaris

V210 to V440

I'm currently trying to move a perfectly find harddrive from a V210 to a V440. From what I can tell, the disk labeling a bit different, (V210 is c1t0d0 and V440 is c0t0d0). My question is, what all do I have to change to get the V440 to boot off of this with very little complications. Right now, it... (21 Replies)
Discussion started by: adelsin
21 Replies

4. Solaris

Booting error in Sun V210

Sun Fire V210, No Keyboard Copyright 1998-2003 Sun Microsystems, Inc. All rights reserved. OpenBoot 4.13.2, 4096 MB memory installed, Serial #61203679. Ethernet address 0:3:ba:a5:e4:df, Host ID: 83a5e4df. Boot device: net File and args: 100 Mbps FDX Link up Timeout waiting for... (5 Replies)
Discussion started by: Mrudhul
5 Replies

5. Solaris

Connect using ALOM to Sun Fire V210

I have bought from eBay a second hand Sun Fire V210 server and I'm really stumped at the lack of complete instructions on how to connect to it. I don't have a Windows machine, I've only got Ubuntu and OS X computers. None of them have an old RS-232 port on them either. In saying that, I have... (12 Replies)
Discussion started by: danijeljames
12 Replies

6. UNIX for Dummies Questions & Answers

New to Forum & Sun Surefire V210 Access

Purchased a Sun Surefire V210 Server off eBay. Unable to Access the Terminal Mode via the Terminal MGT. Using Windows 7 home, and downloaded the ConEmu. The ConEmu brings up a Command line on the PC, and that's it. Being new to all this, I was expecting a Login prompt to pop up. Read the... (22 Replies)
Discussion started by: screenprintr
22 Replies

7. Solaris

Sun Fire V210 CPU Fan Temp too high?

Hey, I have a V210 with a failed CPU fan. The temperature is currently at 84C and I've been asked to wait a few weeks before replacing as its a production system and it cant be shut down yet. Is it too hot? Do I risk killing the CPU at this temp? Its been like this for a few weeks now... (5 Replies)
Discussion started by: magarvo
5 Replies
FANCONTROL(8)						      System Manager's Manual						     FANCONTROL(8)

NAME
fancontrol - automated software based fan speed regulation SYNOPSIS
fancontrol [configfile] DESCRIPTION
fancontrol is a shell script for use with lm_sensors. It reads its configuration from a file, then calculates fan speeds from temperatures and sets the corresponding PWM outputs to the computed values. WARNING
Please be careful when using the fan control features of your mainboard, in addition to the risk of burning your CPU, at higher tempera- tures there will be a higher wearout of your other hardware components, too. So if you plan to use these components in 50 years, maybe you shouldn't use fancontrol at all. Also please keep in mind most fans aren't designed to be powered by a PWMed voltage. In practice it doesn't seem to be a major issue, the fans will get slightly warmer, just be sure to have a temperature alarm and/or shut- down call, in case some fan fails, because you probably won't hear it anymore ;) CONFIGURATION
For easy configuration, there's a script named pwmconfig(8) which lets you interactively write your configuration file for fancontrol. Alternatively you can write this file yourself using the information from this manpage. Since most of you are going to use pwmconfig(8) script, the config file syntax will be discussed last. First I'm going to describe the var- ious variables available for changing fancontrol's behaviour: INTERVAL This variable defines at which interval in seconds the main loop of fancontrol will be executed DEVPATH Maps hwmon class devices to physical devices. This lets fancontrol check that the configuration file is still up-to-date. DEVNAME Records hwmon class device names. This lets fancontrol check that the configuration file is still up-to-date. FCTEMPS Maps PWM outputs to temperature sensors so fancontrol knows which temperature sensors should be used for calculation of new values for the corresponding PWM outputs. FCFANS Records the association between a PWM output and a fan input. Then fancontrol can check the fan speed and restart it if it stops unexpectedly. MINTEMP The temperature below which the fan gets switched to minimum speed. MAXTEMP The temperature over which the fan gets switched to maximum speed. MINSTART Sets the minimum speed at which the fan begins spinning. You should use a safe value to be sure it works, even when the fan gets old. MINSTOP The minimum speed at which the fan still spins. Use a safe value here, too. MINPWM The PWM value to use when the temperature is below MINTEMP. Typically, this will be either 0 if it is OK for the fan to plain stop, or the same value as MINSTOP if you don't want the fan to ever stop. If this value isn't defined, it defaults to 0 (stopped fan). MAXPWM The PWM value to use when the temperature is over MAXTEMP. If this value isn't defined, it defaults to 255 (full speed). The configuration file format is a bit strange: VARIABLE=chip/pwmdev=value chip/pwmdev2=value2 VARIABLE2=... Each variable has its own line. The variable name is followed by an equal sign and the device=value pairs. These consist of the path to the pwm output for which the value is valid, equal sign followed by the value and are separated by a blank. Path can be absolute or relative (from /sys/bus/i2c/devices or /sys/class/hwmon depending on the kernel version). Example: MINTEMP=hwmon0/device/pwm1=40 hwmon0/device/pwm2=54 You have to play with the temperature values a bit to get happy. For initial setup I recommend using the pwmconfig script. Small changes can be made by editing the config file directly following the rules above. Upon starting, fancontrol will make sure that all referenced devices do exist and match what they were at configuration time, and that all referenced sysfs files do exist. If not, it will quit immediately, upon the assumption that the configuration file may be out-of-sync with the loaded kernel drivers. THE ALGORITHM
fancontrol first reads its configuration, writes it to arrays and loops its main function. This function gets the temperatures and fanspeeds from kernel driver files and calculates new speeds depending on temperature changes, but only if the temp is between MINTEMP and MAXTEMP. After that, the new values are written to the PWM outputs. Currently the speed increases quadratically with rising temperature. This way you won't hear your fans most of the time at best. SEE ALSO
pwmconfig(8), sensors(1). AUTHOR
Marius Reiner <marius.reiner@hdev.de> lm-sensors 3 September 2009 FANCONTROL(8)
All times are GMT -4. The time now is 06:01 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy