It looks like the system BIOS is able to detect that an adapter is present, but it is not able to fully communicate with it. I suspect the firmware is locked up or receiving a lot of I/O that is causing delayed responses. The error indicates partial communication is occurring.
Do you have errors on any of the drives? There could be a failed drive that is flooding the the PERC with requests. I would suggest removing any failed drives. If there are no failed drives then I would shut the server down and disconnect all drives. Power the system on with all drives disconnected. If the issue goes away then the problem is with a drive, slot, or cable. If the issue persists then the problem is with the PERC, slot(system board), cable, or backplane. It could also be almost any hardware attached to the system.
Reseating the PERC would be a good place to start. If that does not resolve the issue then you will need to start disconnecting components to rule out points of failure. If you have known good parts to swap then it will be a lot easier to narrow down the problem.
Thanks for the reply. We have tried several of these options. We actually have two identical servers with identical problems.
We have tried: - Running the Controller without drives -> works OK - Running the Controller with some drives -> works OK - Popping in too many drives -> does not work - Removing other drives previously working (leaving the added "non-working" in) -> works OK
Also, everything is brand new. When installing the drives, we had the Server running. We popped in the drives one by one, and all got detected. We even created a RAID from them. Only after a reboot, it started to behave "weird".
The SSD's are Samsung 850 Pro, all with the same Firmware. They are not DELL branded drives. If the exact Serial Numbers and Firmware still matters, I can get you them (need to drive to the Datacenter, as they cannot be read out currently due to the controller issue)
Exact serial number might not be required. But firmware version does matter. Since the drives are not Dell certified, let us not worry about that @ this point of time. Could you please provide the below requested information?
Is the issue seen with Dell certified SSDs?
Complete system details(back plane connected) and for which back plane drives are added if system is dual back plane capable
Drive form factor(2.5” or 1.8”)
Boot mode(BIOS or UEFI)
Is the issue seen consistently irrespective of reboot mechanism.
Complete system details(back plane connected) and for which back plane drives are added if system is dual back plane capable
R730XD, 24x 2.5" backplane, with 2x read-disks, 2 CPU, 384 GB RAM, all drives are connected to the backplane (i don't know if there are 2 backplanes). Using 12 drives seems to work, using 16 drives (0-11 / and the last 20-23) works as well. Using more drives does not work. Different combinations yield different results, so it does not seem to be a single slot/disk. Also, we can reproduce this on 2 different R730XD systems (not using the same disks)
Drive form factor(2.5” or 1.8”)
2.5"
Boot mode(BIOS or UEFI)
BIOS
Is the issue seen consistently irrespective of reboot mechanism.
Is there anything we can do about this? Should I try a support case with DELL?
I would not recommend calling support for issues with 3rd party equipment.
The last thing I would suggest is to take one drive and test it in each slot to make sure there is not a bad slot.
I know that the drives are not certified, but I did not expect that the server would not even boot with them...
When you install equipment that has not been validated to function with the system you should expect this type of behavior. We validate equipment so that you don't have to do it yourself. If you decide to do it yourself then functionality will be trial and error.
This is disappointing :( I think I'm going to try to plow in stock LSI controllers and see if they work. This way, I can also make sure there are no bad slots.
Daniel My
12 Elder
•
6204 Posts
14254
0
Posted November 23rd, 2014 16:00
Hello Michel
It looks like the system BIOS is able to detect that an adapter is present, but it is not able to fully communicate with it. I suspect the firmware is locked up or receiving a lot of I/O that is causing delayed responses. The error indicates partial communication is occurring.
Do you have errors on any of the drives? There could be a failed drive that is flooding the the PERC with requests. I would suggest removing any failed drives. If there are no failed drives then I would shut the server down and disconnect all drives. Power the system on with all drives disconnected. If the issue goes away then the problem is with a drive, slot, or cable. If the issue persists then the problem is with the PERC, slot(system board), cable, or backplane. It could also be almost any hardware attached to the system.
Reseating the PERC would be a good place to start. If that does not resolve the issue then you will need to start disconnecting components to rule out points of failure. If you have known good parts to swap then it will be a lot easier to narrow down the problem.
Thanks