Any hope for this bootlooping Sun V210?


 
Thread Tools Search this Thread
Operating Systems Solaris Any hope for this bootlooping Sun V210?
# 15  
Old 12-01-2018
Hi hicksd8,


I did eventually get into the LOM by swapping the SCC card for one with a known password, but the first thing I will do if I can get the `OK` prompt is install Solaris and reset the password on the first SCC card.


If only I could get the 'OK' openboot prompt Smilie
# 16  
Old 12-01-2018
It looks like your 'poweron' command is not properly executing and the mobo is not powering up. Hence, no OK> prompt after 'console'.

Here's another live thread where I'm having a similar discussion which might be worth your reading, perhaps not.
Help with Reviving a NETRA240 Pls?

Netra 240 is similar to V240 is similar to V210
# 17  
Old 12-02-2018
Yes, that's what the first mainboard did. The ALOM is corrupted I think. I gave up on that board.



Note that more recently in this thread I'm using a different mainboard.
# 18  
Old 12-03-2018
Hi Vext01,

I have just been through the thread again and have a couple of quick questions/observations.

Firstly, it's fairly obvious (I think) that you are able to get into the ALOM and interact with it - just the ALOM doesn't seem to be communicating correctly with the system.

Secondly you mention that you removed a CPU, I'm not certain on this but from the dim and dark recesses of my memory I have this nagging feeling that these vSeries servers need CPU 0 to boot - although I would expect some better diagnostics than you are getting.

Finally, did you have any joy with the sc> showlogs or the sc> showenvironment commands?

Regards

Gull04
# 19  
Old 12-03-2018
Hi Gull04,


As for CPU, I put both CPUs back in yesterday. I'll try some spare CPUs in slot 0 in case the CPU is faulty, although I'd have hoped that the ALOM would have realised if it was.



Here's the output of those commands:


Code:
sc> poweron
sc> showlogs

Log entries since DEC 03 10:13:29
----------------------------------
DEC 03 10:13:29 : 00060003: "SC System booted."
DEC 03 10:13:32 : 00060000: "SC Login: User admin Logged on."
DEC 03 10:16:23 : 00040001: "SC Request to Power On Host."
sc> showlogs -v
Persistent event log
--------------------
DEC 01 18:49:12 : 00040029: "Host system has shut down."
DEC 01 18:51:07 : 0004003e: "Different SCC detected. SC will reset itself momentarily."
DEC 01 18:51:39 : 00040002: "Host System has Reset"
DEC 01 18:51:52 : 00060003: "SC System booted."
DEC 01 18:52:57 : 00040071: "DISK @ HDD0 has been removed."
DEC 01 18:53:09 : 00040072: "DISK @ HDD1 has been inserted."
DEC 01 18:53:21 : 00040072: "DISK @ HDD0 has been inserted."
DEC 01 18:53:33 : 00040071: "DISK @ HDD0 has been removed."
DEC 01 18:54:16 : 00060004: "SC Request to Reset Host."
DEC 01 18:54:45 : 00040066: "ENCLOSURE_FAN @ F3.RS has FAILED."
DEC 01 18:55:11 : 00060016: "SC Request to execute XIR Reset on the Host."
DEC 01 18:57:44 : 00040002: "Host System has Reset"
DEC 01 18:57:46 : 00060003: "SC System booted."
DEC 01 18:59:31 : 0004000e: "SC Request to Power Off Host Immediately."
DEC 01 18:59:41 : 00040029: "Host system has shut down."

Log entries since DEC 03 10:13:29
----------------------------------
DEC 03 10:13:29 : 00060003: "SC System booted."
DEC 03 10:13:32 : 00060000: "SC Login: User admin Logged on."
DEC 03 10:16:23 : 00040001: "SC Request to Power On Host."


Code:
sc> showenvironment


=============== Environmental Status ===============


--------------------------------------------------------------------------------
System Temperatures (Temperatures in Celsius):
--------------------------------------------------------------------------------
Sensor         Status    Temp LowHard LowSoft LowWarn HighWarn HighSoft HighHard
--------------------------------------------------------------------------------
MB.P0.T_CORE    OK         48     --      --      --     110      115      118
MB.P1.T_CORE    OK         62     --      --      --     110      115      118
MB.T_ENC        OK         20     -6      -3       5      40       48       51

--------------------------------------
Front Status Panel:
--------------------------------------
Keyswitch position: NORMAL

--------------------------------------------------------
System Indicator Status:
--------------------------------------------------------
MB.LOCATE            MB.SERVICE           MB.ACT              
--------------------------------------------------------
OFF                  OFF                  OFF                 

--------------------------------------------
System Disks:
--------------------------------------------
Disk   Status            Service  OK2RM
--------------------------------------------
HDD0   OK                OFF      OFF
HDD1   NOT PRESENT       OFF      OFF

----------------------------------------------------------
Fans (Speeds Revolution Per Minute):
----------------------------------------------------------
Sensor           Status           Speed   Warn    Low
----------------------------------------------------------
F0.RS            UNAVAILABLE         --     --   1000
F1.RS            UNAVAILABLE         --     --   1000
F2.RS            UNAVAILABLE         --     --   1000
F3.RS            UNAVAILABLE         --     --   1000
MB.P0.F0.RS      UNAVAILABLE         --   2000   2000
MB.P0.F1.RS      UNAVAILABLE         --   2000   2000
MB.P1.F0.RS      UNAVAILABLE         --   2000   2000
MB.P1.F1.RS      UNAVAILABLE         --   2000   2000

--------------------------------------------------------------------------------
Voltage sensors (in Volts):
--------------------------------------------------------------------------------
Sensor         Status       Voltage LowSoft LowWarn HighWarn HighSoft
--------------------------------------------------------------------------------
MB.P0.V_CORE   OK             1.47      --    1.26    1.54       --
MB.P1.V_CORE   OK             1.49      --    1.26    1.54       --
MB.V_VTT       OK             1.28      --    1.17    1.43       --
MB.V_GBE_+2V5  OK             2.50      --    2.25    2.75       --
MB.V_GBE_CORE  OK             1.20      --    1.08    1.32       --
MB.V_VCCTM     OK             2.54      --    2.25    2.75       --
MB.V_+2V5      OK             2.58      --    2.34    2.86       --
MB.V_+1V5      OK             1.52      --    1.35    1.65       --
MB.BAT.V_BAT   OK             3.21      --    2.70      --       --

--------------------------------------------
Power Supply Indicators: 
--------------------------------------------
Supply    Active  Service  
--------------------------------------------
PS0       ON      OFF

------------------------------------------------------------------------------
Power Supplies:
------------------------------------------------------------------------------
Supply  Status          Underspeed  Overtemp  Overvolt  Undervolt  Overcurrent
------------------------------------------------------------------------------
PS0     OK              OFF         OFF       OFF       OFF        OFF

----------------------
Current sensors: 
----------------------
Sensor          Status
----------------------
MB.FF_SCSI       OK

# 20  
Old 12-03-2018
Hi Vext01,

As you've had the machine in bits and have replaced the guts, I'm going to stick my neck out and suggest that the connections should be good as they should all have been re-seated during component changes. I'd maybe tempted to swap the PSU if you have one, but the maintenance indicator would generally be on if it was faulty.

It might be that just pulling and re-seating the power supply would be enough.

I'm kind of running out of steam on this, you've changed the MOBO and the CPU's. The fault has remained pretty consistent, from the environmentals it doesn't seem to be power related. I'ts unlikely that this will make any difference, but can you capture the ALOM config and then run a sc> resetsc you'll have to go through the setting up the ALOM again (Although you should just need to change the password as the rest should work).

Additionally something has just come to the fore, didn't happen to me - it was an engineer that I worked with. He had a fault on a v210 or it may have been a v240 - where he replaced the Mother Board and couldn't get to the ok prompt.

Turned out that he'd mixed the matched pairs of memory and that causes the OBP not to start, it didn't supply an error message either - I've been in touch with him and although the Dimm's were the same speed - they had different manufacturers and that was enough.


Regards

Gull04

Last edited by gull04; 12-03-2018 at 09:29 AM.. Reason: More Info
# 21  
Old 12-03-2018
I agree with gull04 that since you've re-seated most things and you still have the same problem then it could be something stupid.

From your post, this worries me:
Quote:
DEC 01 18:59:31 : 0004000e: "SC Request to Power Off Host Immediately."
So where is that coming from? Perhaps some button stuck in on the front panel? Key switch stuck? Or something like that is where I'd be looking.
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. 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

2. 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

3. 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

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

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

6. 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

7. 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
Login or Register to Ask a Question