1753504
Members
4969
Online
108794
Solutions
Allways
A conmputer must have an operational primary CPU.
So CPU 1 (0) and VRM, must be OK.
Speaking Proliant:
If a Proliant detect a CPU as defective, it will ASR and disable the defective CPU.
When you replace the def. CPU, you must manually mark it as repaired in the IML, and reboot the server to activate the new CPU.
In your case:
You have deactivated CPU 1 (0).
Sou you need to mark it repaired in the IML, but you can't do that, becaurse, it is the primary CPU, that has failed.
Solution:
Put in a known goog CPU and VRM in socket 1 (0)
Clear the CMOS, using the switch on the system I/O bd.
Check inside the lid, wich switch to use.
I believe it's sw6, but better check.
Allways.
Fist thing to do before adding / upgrading CPU.
You must upgrade BIOS.
If you got an old BIOS, it might not have the micro code for the new CPU.
BR
/jag
A conmputer must have an operational primary CPU.
So CPU 1 (0) and VRM, must be OK.
Speaking Proliant:
If a Proliant detect a CPU as defective, it will ASR and disable the defective CPU.
When you replace the def. CPU, you must manually mark it as repaired in the IML, and reboot the server to activate the new CPU.
In your case:
You have deactivated CPU 1 (0).
Sou you need to mark it repaired in the IML, but you can't do that, becaurse, it is the primary CPU, that has failed.
Solution:
Put in a known goog CPU and VRM in socket 1 (0)
Clear the CMOS, using the switch on the system I/O bd.
Check inside the lid, wich switch to use.
I believe it's sw6, but better check.
Allways.
Fist thing to do before adding / upgrading CPU.
You must upgrade BIOS.
If you got an old BIOS, it might not have the micro code for the new CPU.
BR
/jag
Yes.
If CPU 1 (0), has been marked bad. It doesn't matter how manny new CPU's you put in, it will remain "bad" and disabled, until you mark it as repaired!.
The server does not figure out, that you have replaced the CPU by it self, you mut tell it, by marking the failed CPU as repaired..
So if CPU 1 or VRM 1 has gone bad. You must replace the faulty part, and mark it as repaired.
And the only way to do so, is to use the switch.
This is an issue with the primary CPU only.
BR
/jag
If CPU 1 (0), has been marked bad. It doesn't matter how manny new CPU's you put in, it will remain "bad" and disabled, until you mark it as repaired!.
The server does not figure out, that you have replaced the CPU by it self, you mut tell it, by marking the failed CPU as repaired..
So if CPU 1 or VRM 1 has gone bad. You must replace the faulty part, and mark it as repaired.
And the only way to do so, is to use the switch.
This is an issue with the primary CPU only.
BR
/jag
To clear cmos:
Hit sw 6, power on for 10 secs.
Then its cleared
Power off, put sw 6 back to default.
Power on to check
Have you chekked the lid, that it's sw 6?
I totally agree with you, that 2 defective sets is very rare.
Did you clear the cmos, with both sets?
install set 1, clear cmos
Test
Install set 2, clear cmos
Test
Are you sure, you are using correct CPU + VRM. Is part numbers the same?
If you have done the aboave
Then you do have a problem.
Possibly:
System I/O board
A bad original set, and a incompatible set.
Trouble shooting would be easier if you had a full known good set, and then test all components one by one.
Note:
When you remove the heatzink, cooling paste must be replaced!
It's ok to test, but before putting it into production, old paste must be cleaned away and new applied
BR
/jag
Hit sw 6, power on for 10 secs.
Then its cleared
Power off, put sw 6 back to default.
Power on to check
Have you chekked the lid, that it's sw 6?
I totally agree with you, that 2 defective sets is very rare.
Did you clear the cmos, with both sets?
install set 1, clear cmos
Test
Install set 2, clear cmos
Test
Are you sure, you are using correct CPU + VRM. Is part numbers the same?
If you have done the aboave
Then you do have a problem.
Possibly:
System I/O board
A bad original set, and a incompatible set.
Trouble shooting would be easier if you had a full known good set, and then test all components one by one.
Note:
When you remove the heatzink, cooling paste must be replaced!
It's ok to test, but before putting it into production, old paste must be cleaned away and new applied
BR
/jag
Yes
This is ment for both of you.
2 bad CPU's or 2 bad VRM's, is not the most likely.
I agree on that.
But regarding adding CPU's or having a failed CPU (Including the VRM).
There's 3 issues (Traps).
1. There's must be a functional CPU in socket 1.
2. CPU's must be supportet, it might require a BIOS upgrade before adding.
Due to new micro codes.
3. A proliant disable failed CPU's.
To get CPU activated after replacement, it must be marked as repaired in the IML, then server must be rebootet.
So if you get a defective CPU 1.
You need to clear the CMOS, wich also clear the IML, and replace the CPU. And hopefully your BIOS have the micro codes for the new CPU.
And yes, it can all be down to a failed system I/O board.
BR
/jag
This is ment for both of you.
2 bad CPU's or 2 bad VRM's, is not the most likely.
I agree on that.
But regarding adding CPU's or having a failed CPU (Including the VRM).
There's 3 issues (Traps).
1. There's must be a functional CPU in socket 1.
2. CPU's must be supportet, it might require a BIOS upgrade before adding.
Due to new micro codes.
3. A proliant disable failed CPU's.
To get CPU activated after replacement, it must be marked as repaired in the IML, then server must be rebootet.
So if you get a defective CPU 1.
You need to clear the CMOS, wich also clear the IML, and replace the CPU. And hopefully your BIOS have the micro codes for the new CPU.
And yes, it can all be down to a failed system I/O board.
BR
/jag