BMW 520d F10 2012 - iDrive - White Screen - Mount Timeout
BMW 520d F10 2012 - iDrive - White Screen - Mount Timeout
Author
Discussion

David-6by2e

Original Poster:

1 posts

99 months

Thursday 4th May 2017
quotequote all
Hi,

Hoping that someone can help me with an intermittent issue I have with my UK 2012 BMW 520d F10.

Sometimes (no real pattern) my idrive screen comes up white with a message stating Mount Check Wait and a further message stating Mount Timeout (I have attached an image of this).

I work in IT and believe that the mount message is due to it trying to mount a storage volume but why is this happening?

I dont have an additional bmw hard drive and I do use a usb drive for mp3's. I have got this message though when the usb drive is unplugged.

I have searched and searched but it appears no one else has reported this issue. I have also searched for a method to reboot the idrive - everything points at holding the mute/volume knob down for 25 seconds but this doesnt work either on the error screen or when the idrive is working fine. I have also tried the method for older idrives which is to hold the mute/volume knob and the eject button together for a period of time again with no joy.

My idrive doesnt have sat nav and doesnt have dab. I have also updated the fireware to the latest official version and the problem still persists.

Thanks in advance for any help and I hope someone knows what is going on here.

Dave


sasquartch

109 posts

118 months

Wednesday 17th May 2017
quotequote all
There is a guy on f30.bimmerpost.com called vorph who will probably be able to help

Not for free though I don't think

Jonesy23

4,650 posts

152 months

Wednesday 17th May 2017
quotequote all
Looks more like a startup failure in the firmware, along the lines of what you'd get with U-Boot, though you'd only expect that at power up.

Usual sequence in embedded stuff involves loading the bootloader from a small bit of ROM/Flash then doing early device init then doing the full load by mounting & booting the main storage device (like eMMC or SD or whatever).

Could be there is a latent fault with the embedded storage & it's starting to struggle to work.

This could also explain the magic key sequences not working if it's failing before they've been initialised.