UNSOLVED

vladry

updated

10 years ago

V

vladry

1 Message

0

665

August 15th, 2016 08:00

PowerEdge R730dx FlexBay conversion problem

Hello.

as the subject says I am trying to convert a PE R730dx server that was originally ordered without flexbay support so I can use the flexbay for SSD drives.

last year I have ordered an R730dx with IDSDM module to be used for OS (MS Server 2012 R2  Hyper-V setup)

unfortunately  for the last several month I have been having a lot of issues with SD card and IDSDM module, to the point of DELL had to replace the module twice, an SD cards twice and even replace the whole MB as the server have been crushing left and right.

during the whole troubleshooting routine I traced the issue to be the incompatibility of OS with SD install. the SD cards and IDSDM module have been trashed to the point of failure  by Hyper-V install. 

it is simply too much writes and reads for that setup.  maybe other Hypervisors are capable with running on SD cards byt it seams not Hyper-V. (amd yes it was a Hyper-V core install, no desktop or anything.)

after extensive back and force with DELL support reps, I come up with a plan to add a flex bay support to the enclosure. I found the parts needed and was assured by support reps that it will  work even if it is not officially supported by DELL sales team , ie. I could not order the parts via sales reps and need to go through replacement part division.  I got the parts last week and have a little issue.

all parts fit just fine except the SAS cable. PartNo:08RJM1.

the cable comes with a straight end connector on one end (go to the MB SAS port ) and angled connector on the other(go to SAS connector on the flexbay back-plain )

the angled connector is does not fit as it is blocked by a square 1" x 1" stand off on the chassis.

looks like it is where the lock for the  chassis cover is. 

I know that there is a configuration for this server that supports flex bay. and even my search for it returns the same part number for chassis on both configurations.

so how is it that on the officially supported setup it works and on my it is not?

please help.

No Responses