Unsolved
This post is more than 5 years old
1 Message
0
200862
Dell M610 blade does not power up on M1000e chassie
The M1000e Blade Enclouse had 16 slots. When any M610 or M600 blade is inserted in one particular slot, it does not successfully power up. The green power light just blinks on the blade and on the Dell Chassis Management Controller, it just says the device is initializing. Blades in other slots power up fine.
Kong Yang
180 Posts
0
November 21st, 2011 12:00
So it's just that one slot that's not correctly posting your blade servers, correct? If that's the case, you could have a bad slot. You may want to open up a support case.
wayne.gordon
1 Message
0
June 25th, 2013 10:00
Hi, I have just come across this issue but it occurs on two new bladed and happens to the four enclosure slots I have tried?
Quick pull apart of all components to remove RAm / HDD / etc as cause and it still happens.
In the process of loggin a DELL support call but did you end up finding the solution?
Klug_fr
11 Posts
0
July 1st, 2013 01:00
Exactly the same issue here.
We have a M1000e currently running with eight blades (four M600 and four M605).
I tried to add two M610 and... Nothing.
The power button on the M610 blinks slowly when trying to power them up.
The chassis sees there's something in the slot but is unable to get any information out of it (no serial, no power state, nothing at all).
A virtual reseat "works", the blades are disconnected then reconnected without error (in the CMC Log)...
Karta
6 Posts
0
July 9th, 2013 01:00
Whta is the CMC version ? Please try doing CMC failover if you have redundant CMC.
Klug_fr
11 Posts
0
July 18th, 2013 02:00
It didn't work, the two blades are still "unavailable".
Klug_fr
11 Posts
0
July 18th, 2013 02:00
CMC was 4.2 and I upgraded it to 4.4. Same problem.
I'll try the failover, just in case...
Klug_fr
11 Posts
0
July 19th, 2013 02:00
Case has been opened.
I might be a "too old" BIOS on the blade/iDRAC (way too old for the CMC).
Motherboard (with newer BIOS) is shipped for exchange.
Klug_fr
11 Posts
0
July 24th, 2013 03:00
Fixed by changing the motherboards...