I called my seller, he told me to just change year. And it worked so CMOS failure is solved. But I still get F1/F2 on fan 4 errors, he told me to disable prompt on errors but I think that's just a workaround. Is there a solution for this?
Unless you can remember changing the battery it's probably discharged -- just change it. You can check the battery with a DMM if you have one, just to be certain.
As for memory errors, the last time I had memory errors it turned out to be a contact issue that I could resolve with a thorough cleaning using a piece of cotton swab soaked in magnetic head cleaner. Contact cleaner would be the best, but most electronic cleaners should work just fine, and if you don't have any of those cleaning liquids, you can use denatured alcohol.
I would most certainly try to clean the contacts before replacement.
regarding the battery message, depending on your system your RAID Controller (if it is a SAS6/iR) might also have a battery, so if it is not specified any further it could be the CMOS battery or the PERC battery.
If it is the CMOS battery, simply replace it by another CR 2032 one.
If it is the RAID backup battery unit (BBU) it depends on the controller for a SAS6/i check out the web for a replacement with the following part number: NU209
If it is a different one, let me know.
Regarding the memory, the PC3L one is a low voltage version of the other DIMM. Mixing works but is not recommended.
You may end up with different limitations regarding speed as all the modules will be powered with the same voltage.
I replaced the CMOS also but everytime I boot it asks to set system time. I did set it and rebooted still displays the message on boot. No orange errors in LED.
Have I installed it correctly? Also if the photo isn't clear I can send some in a different angle
rizexor
11 Posts
5018
0
Posted April 15th, 2021 00:00
I called my seller, he told me to just change year. And it worked so CMOS failure is solved. But I still get F1/F2 on fan 4 errors, he told me to disable prompt on errors but I think that's just a workaround. Is there a solution for this?