Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

3814

January 5th, 2017 18:00

R720xd SAS controller not always detecting SATA drives during boot up

Please, any suggestions are welcome. Even if they sound offensive. I know the simple things are missed more often than we like to admit.

I am chasing an issue with my recently purchased R720xd 3.5” intermittently not recognizing hard drives being connected (during initial boot). Results have been inconsistent, which has made it very challenging to troubleshoot.

During boot, when everything works correctly (typically when first powered on and/or cold) The Hard Drive Backplane briefly flickers all orange LED’s, then a green HDD led with flash a time or two where drives are connected at and then stay on solid. The drives can then be seen in the SAS controller BIOS

During boot, when the drives are not recognized (typically after it has been powered on for a few minutes to warm up), The orange LED’s will either not come on at all, stay on continuous, or stay on for a minute or two then go off. The SAS controller then does not list any drives in the BIOS.

The things I have done are listed below, but I still have results of it working and not working with each thing I have tried. Telling me they are not the cause.

-Swap between the OEM H710 mini and an LSI PCIe HBA

-Swapped out SAS cables

-Only connected one SAS cable at a time

-Only connecting a single HDD (2TB SATA)

-reset CMOS

-disable and enable the OEM H710 RAID controller in BIOS while connected to LSI controller

-Swap out backplane

The only consistent change I get is that it works every time when I have it out in my cold work shop (50degF currently). When the server is in room temperature, it is hit or miss if it shows any drives. I can directly connect only the rear 2.5” drive backplane with a single SAS cable and it registers drives each and every time I try. At that point, I strongly suspected this cause to be a broken solder joint on the SAS expander BGA chip on the BP, which would be effected by the temperature of air being pulled across the backplane. But replacing the backplane yesterday proved the same thing as did swapping cables and such. Still was not working each time.

I also tried to figure out what each and every cable connected to the backplane is for, so I can better understand why the issue appears to be localized to the BP. From what I can tell, the ribbon cable from the motherboard to the BP is just passing through to the left and right rack ears for VGA, power button, and indicators. The USB from the motherboard is also passing through to a rack ear. The two SAS cables go to the HBA controller, and the 3rd SAS cable just joins in the rear BP for the two 2.5” drives along with a multi conductor cable joining the rear BP to the front BP. The BP has two power cables from the motherboard.

Now what I cannot figure out on the BP connection, there is a signal cable (connection labeled “SIG”) with about 10 or 12 wires going from the motherboard to the front BP. Another identical cable goes from the motherboard to the rear BP (maybe it just jumpers through the motherboard from front BP to rear BP, but not sure why it would). I tried booting without this cable connected, but no LED’s flashed or anything on the BP and of course no drives were detected.

Please, any suggestions are welcome. Even if they sound offensive. I know the simple things are missed more often than we like to admit.

January 8th, 2017 13:00

I must have overlooked something when I tried the replacement backplane.  So I continued plugging away at this issue and doing more verifications in testing to get the constants locked in solid.  I then swapped out to the replacement backplane once again, and it has not had an issue since...

7 Technologist

 • 

16.3K Posts

January 5th, 2017 19:00

These aren't NAS or "green" drives for laptops/desktops are they?

January 6th, 2017 06:00

I have been using a few spare drives I have to troubleshoot this.  They are drives I previously ran in my R510 Server.  Seagate Desktop, WD Black, and a couple WD's that have  a generic label which I think became part of the green line later.

Something else to note is that I can boot the system cold with all these drives connected and then pull up the H710 Topology menu and it shows all of them.  I can leave it on that screen for a couple minutes and they just disappear and the topology shows no drives.  That happens while I am in that menu and not doing anything other than looking at the screen.  From then on the drives do not register until the unit is left off for a while.

I tried focusing more on why the BP has a cable to the MoBo labeled as "SIG".  The manual revealed it to be a I2C connection.  I am familiar with this type of serial communication, though this connection has many more wires than I would expect (12c or so) for only being I2C.  I also wonder why it needs I2C, but then maybe for firmware updates would make sense?  Then again, if I disconnect the "SIG" cable connection then it boots with no HDD lights even flickering on the BP, and I could not even get it to see a HDD when booted cold unless I connected the I2C cable back.  Oh, and it appeared that none of the drives even spun up when this cable was disconnected.

Since the I2C connection appears to effect the orange LED's on the BP and the HDD spinning up, I find it very similar to the actual problem that I am having.  Perhaps the issue is linked to this?

Since the rear BP always sees HDD's if I connect a SAS cable directly to it, I swapped the front and rear BP I2C connections at the motherboard.  The problem did not get better or worse.

I also disconnected the rear backplane connection completely, and this did not make it better or worse.

No Events found!

Top