MD3820F error code 5E dF

can you help me with that hack version ? I accept the risk

i see the controller has 2 msata drives .i should do with both or just one as you suggested

please remove the download link i already downloaded it  .thanks you

Sure no problem. Before doing that, can you check your firmware version to see that it is 08.25.14.60, with NVSRAM version N2701-825890-004. If it is not at that version, upgrade it with the latest dell download at:

https://www.dell.com/support/home/ko-kr/product-support/product/powervault-md3820f/drivers

If the version is right, what you will have to do is:

(1) Disassemble the controller. You will need to take off the FC adapter sitting on top of the main RAID controller by untightening three screws. Just pull up that daughter card strong enough so that a connector hidden below can get detached from the main card.

(2) Take out mSATA chip from the main controller and connect it to any computer. You may need an mSATA to USB converter (~$3).

(3) Mount the first partition on mSATA. Find /fw/active/Diagnostic, and replace it with my hacked version. You can download my file at

https://drive.google.com/file/d/1tigBbvhPKKjko6gxAKaCIhq5Im-mmVn6/view?usp=share_link

(4) Re-assemble everything and reboot.

That's just it. Please let me know how it went as soon as you finish. I feel uncomfortable about leaving the file worldwide accessible for a long time.  

The one that's directly below the Fibre Channel daughter card is the one you need to touch. You can actually unplug the second card that's in line with the cache-backup (LiFePo) battery. My controller does not have that mSATA at all. You probably have to modify the second card too if you wish to keep it there. My guess is, that second card is a backup mSATA that will kick in if the first card dies like mine.

Doing the same stuff. Also Trying to find the memory for this controller, found the same ECC low profile, not 2800 but 1600, does anyone now, is the memory specs stored in firmware? 

Hi, I could not access any information about whether the memory properties are stored in the firmware. Although I wouldn't expect it to be like that, I'm not sure. The MD3820F controller has the following memory specifications: PowerVault_MD3_Family_SS.pdf (https://dell.to/3zRoWBg)

Single controller: 2GB, 4GB cache
Dual controller: 2GB, 4GB, 8GB cache
The data sheet does not mention the RAM specifications for the controller.

I had this same problem on MD3420 - i've replaced RTC battery in both controllers and after that controllers hangs on RTC error.

I fixed that by setting RTC time using serial console.

To do that you will have to:

- press ctrl + break

- press esc

- then you need enter vx shell credentials

- enter command M (Boot operation menu)

- choose 6 - Set Real Time Clock

- then you have mannualy set time and date

After setting that, RTC Error disappeared.

So I was having the same issue a few days back and I found this thread. I have found a solution that worked, without hacking the firmware.

You let the controller boot up completely.

Press the break once so it comes it with something like "Press S for service bla bla bla" but you DO NOT press S. You press the ESC key.

Now there is a login promt.

Username is shellUsr

Password is DF4m/2> (might be deleted by Dell they seem hell bent on NOT giving this away, but is decently easy to find on google)

Now you get a promt which looks just like: "->"

Here you can do stuff like netShowCfg to see ip addresses of the system. You can also run netSetCfg to set the network.

But all you do is put an upper case m: "M" and press enter.

Now you get a menu. In this menu you press I think it was 6 to set the time of the controller.

Set the time to the current one.

Reboot and controller does not spew out RTC errors all the time, and boots without you having to press "C" for continue every boot.

Did this on 2 controllers, worked both times.

I did think at first the error comes because time is not correct. It goes back to it's "default" which is 2015 i think it was. Adding the system to the storage manager and sync the time didn't work. For some reason the storage manager was reporting correct time for the controller all the time, but in this menu the controller was reporting it was 2015. Set the time to current and BAM, no issues.

As far as I understand the storage manager does not set the same time on the controller, somehow it just keeps it in it's own cache, without actually changing the time on the controller.

I hope this helped whomever is in the same situation maybe years from now, and can benefit from it.

@Jelle​ Thank you so much. You saved our MD3460 which had exactly this problem. I'd buy you a few beers if you were around xD. Again, thank you very much!

@Jelle​ I have no words to thank you as much as you deserve! Thanks for the user and pass information! You just save our MD3460!