When you have issues with the system powering on or completing POST you should take the system to minimum to POST. Remove all unnecessary hardware to limit the possible points of failure.
The SAS 6/iR comes in several form factors. Which SAS 6/iR do you have and which slot did you install it in the R610? Was it moved from another R610? Since the SAS controller was the last change made to the system the first thing I would do is remove it.
The form factor is show in the photo at the end. I installed it in the dedicated slot for these RAID controllers.
I have now removed that, the SAS drives and am back to as much of a bare bones system as possible. I tried putting in two power units from a unit which is working but that didn't change the error and the failure to boot.
I am back to the original hardware configuration which was working for a day or so. But I am getting this warning on the front panel and the machine stops / halts fans turn off and the machine appears shutdown apart from this scrolling warning across the front panel...
Anything else I can try?
Also, now I have a "used-to-be-working-SAS-6ir-card, which is now a status-unknown-but-suspected-still-good card, back in my other R610's after this. It am guessing that it is unlikely that this would cause these error's in those other R610's isn't it? However, it would be very bad if they went down as well... Any comment on this as well?
I apologize for the late response. The last time I looked at the post the picture was not present.
It is difficult for me to read the part number, but it appears to be YK838. That is the integrated no sled version that is intended to be used in this system in the dedicated/integrated storage slot. It does not appear to be a compatibility issue.
Given that the system has continued the behavior after removing the controller I suspect another component is to blame. If you followed my instructions and took the system to minimum to POST and the error persisted then you will need to start replacing parts. If you have parts available to swap then I would swap the easiest parts like PSU, control pane, etc. If you don't have parts available then I would go with most likely parts. The most likely part would be the system board since voltage regulator modules, power distribution boards, baseboard management controller, and several other components are built into it. The system board has a lot of points of failure.
Since the problem started by installing this card I would be very careful about putting it in another system. Something may have been damaged during the installation, there may have been an ESD, or the card may be faulty and damaged the system board. If you have already installed the card in another system without issue then it is not likely the card itself that started the problem.
Interestingly I had that exact same card working in two different servers previously. I had just extensively tested another server with that card so I think it was something about the system. It appears that the system had never had a RAID card in it at any time. Thus the problem appears to be there. As you say I am now hesitant to put that RAID card that was working into any other systems...
Is it typical that a RAID card can fry the motherboard especially when I had just extensively tested that very same RAID card in two other systems...? Seems kind of weird to me...
If you had to ascribe some blame to this would you say the problem was pre-existing with this dell R610 if the RIAD had never been tested... or was it more likely user error in installing the SAS RAID card (I have done this on number of other occasions and I wore a wrist strap.)
I have to say in the systems I have now worked with previously (4 dell 1950s, 3 dell R610's, a tower server, lots of computers, a custom loop water cooled PC, etc.) this is the first it has ever happened to me that inserting a card has apparently fried something in the motherboard...
In the end if I don't get any joy with the person who sold this computer to me then I will start pulling parts and try and find out where the fault is...
Interestingly I had the exact same problem and the problem ended up being my SATA backplane as well. Unplug it and the machine POSTs and boots fine. Thankfully only about a $13 part on eBay. I was about to pull the CPU's, ram, and set this thing on fire. lol.
In my case though, the problem was my R810. I just swapped out the one in my R610 and dang, I was
back in business.
Guess what? I put the R810 back in my R610 and that also was back up without a hitch. I should have just unplugged and plugged back the power cord as ShaneSingleton suggested.
Petr71
2 Posts
0
November 17th, 2016 14:00
I had on dell r610, e1000 failsafe voltage error, than I CHANGED SATA HDD BACKPLANE
and fixed the problem. Look the picture.
Daniel My
10 Elder
•
6.2K Posts
0
February 8th, 2015 10:00
Hello Jason
When you have issues with the system powering on or completing POST you should take the system to minimum to POST. Remove all unnecessary hardware to limit the possible points of failure.
The SAS 6/iR comes in several form factors. Which SAS 6/iR do you have and which slot did you install it in the R610? Was it moved from another R610? Since the SAS controller was the last change made to the system the first thing I would do is remove it.
Thanks
sysjas
1 Rookie
•
14 Posts
0
February 8th, 2015 15:00
The form factor is show in the photo at the end. I installed it in the dedicated slot for these RAID controllers.
I have now removed that, the SAS drives and am back to as much of a bare bones system as possible. I tried putting in two power units from a unit which is working but that didn't change the error and the failure to boot.
I am back to the original hardware configuration which was working for a day or so. But I am getting this warning on the front panel and the machine stops / halts fans turn off and the machine appears shutdown apart from this scrolling warning across the front panel...
Anything else I can try?
Also, now I have a "used-to-be-working-SAS-6ir-card, which is now a status-unknown-but-suspected-still-good card, back in my other R610's after this. It am guessing that it is unlikely that this would cause these error's in those other R610's isn't it? However, it would be very bad if they went down as well... Any comment on this as well?
Thanks,
Jason
SAS 6ir form factor:
sysjas
1 Rookie
•
14 Posts
0
February 11th, 2015 07:00
Hey there... Any further hints?
Daniel My
10 Elder
•
6.2K Posts
0
February 11th, 2015 09:00
I apologize for the late response. The last time I looked at the post the picture was not present.
It is difficult for me to read the part number, but it appears to be YK838. That is the integrated no sled version that is intended to be used in this system in the dedicated/integrated storage slot. It does not appear to be a compatibility issue.
Given that the system has continued the behavior after removing the controller I suspect another component is to blame. If you followed my instructions and took the system to minimum to POST and the error persisted then you will need to start replacing parts. If you have parts available to swap then I would swap the easiest parts like PSU, control pane, etc. If you don't have parts available then I would go with most likely parts. The most likely part would be the system board since voltage regulator modules, power distribution boards, baseboard management controller, and several other components are built into it. The system board has a lot of points of failure.
Since the problem started by installing this card I would be very careful about putting it in another system. Something may have been damaged during the installation, there may have been an ESD, or the card may be faulty and damaged the system board. If you have already installed the card in another system without issue then it is not likely the card itself that started the problem.
Thanks
sysjas
1 Rookie
•
14 Posts
0
February 15th, 2015 19:00
Thanks Daniel,
Interestingly I had that exact same card working in two different servers previously. I had just extensively tested another server with that card so I think it was something about the system. It appears that the system had never had a RAID card in it at any time. Thus the problem appears to be there. As you say I am now hesitant to put that RAID card that was working into any other systems...
Is it typical that a RAID card can fry the motherboard especially when I had just extensively tested that very same RAID card in two other systems...? Seems kind of weird to me...
If you had to ascribe some blame to this would you say the problem was pre-existing with this dell R610 if the RIAD had never been tested... or was it more likely user error in installing the SAS RAID card (I have done this on number of other occasions and I wore a wrist strap.)
I have to say in the systems I have now worked with previously (4 dell 1950s, 3 dell R610's, a tower server, lots of computers, a custom loop water cooled PC, etc.) this is the first it has ever happened to me that inserting a card has apparently fried something in the motherboard...
In the end if I don't get any joy with the person who sold this computer to me then I will start pulling parts and try and find out where the fault is...
Petr71
2 Posts
1
November 17th, 2016 14:00
Hi, Jason.
I had same problem on R610, E1000: Failsafe voltage error. Contact support.
I changed a SATA HDD back-plane and the problem solved right away.
P/N: CN-0WR7PP-64355-16F-DRBZ-A00 OR 0WR7PP
Look the pictures of it.
So, Good luck. Petr.
ShaneSingleton
1 Message
0
June 12th, 2017 17:00
Interestingly I had the exact same problem and the problem ended up being my SATA backplane as well. Unplug it and the machine POSTs and boots fine. Thankfully only about a $13 part on eBay. I was about to pull the CPU's, ram, and set this thing on fire. lol.
Thanks PETR71!
RegisTazz
1 Message
0
May 28th, 2020 14:00
Worked like a charm., even in 2020!
In my case though, the problem was my R810. I just swapped out the one in my R610 and dang, I was
back in business.
Guess what? I put the R810 back in my R610 and that also was back up without a hitch. I should have just unplugged and plugged back the power cord as ShaneSingleton suggested.
Thanks for the fix buddy. You're THE man!!!!!