[doveman2]

Just like me. I fixed it by changing the whole STORAGE partition to an USB pen instead and I didn't have a single problem after that.

Yes, but even when using USB it's quite likely you'll be left with an unbootable system if you experience these mmc0 errors when your Pi boots in order to apply a software update (updates to the SD-based kernel.img, bootcode.bin etc.). The only solution (other than avoiding/eliminating the mmc0 errors) is to move /storage to USB/NFS, and apply SD-card based updates manually using a PC (ie. disable auto-update, and never allow the Pi to write to the SD card, basically).

Yes, that is exactly what happens to me... Corruption after each update!

Does this mean that if I either disable the overclock before updating (my past experience shows that this ALWAYS cause corruption in SD card) or manually move SYSTEM and KERNEL files to the SD SYSTEM partition (via PC), it should work?

Any downside of moving these files manually (other than MD5 not being checked)?

When using the USB, the only time the SD should be written to (with the risk of corruption) is when updating, so disabling the overclock before updating should be all that's required. I don't see any advantage in moving the files manually, as that still involves writing to the SD and therefore needs the overclock disabling first.

What I'd like to see ideally to make this less complex is an automated method where it disables the overclock, reboots (now not overclocked) and installs the updates, reboots again and re-enables the overclock and reboots a last time (now with the overclock re-enabled), to save the user having to do all this manually.