/dev/sde3 and /dev/sdf1 work fine in an mdraid array. /dev/sde4 and /dev/sdf2 are a part of a Windows mirrored volume. /dev/sdf3 is a Windows recovery partition. When booting into Windows, I can normally use the system and access the mirrored system volume. However, the Disk Management Snap-In goes crazy:

The actual physical drives are present with no information whatsoever. Nevertheless, all the individual volumes can be seen, and function properly despite the x marks - SYSTEM (C:) is doing a fine job re-synchronising after all this, it can be accessed and is currently being used as a system volume.

diskpart confirms this situation:

Physical drives cannot be seen when listing, but can be selected anyway and investigated further. All the actual volumes show up as they should:

but when examined more thoroughly, they seem to be coming from some non-existent disks:

Virtual Disk Service error: The disk's extent information is corrupted. seems to indicate quite verbosely that the current state of the LDM metadata does not conform to some Microsoft standard anymore.

Is there any way to investigate this further and potentially fix this issue without recreating the whole disk partitioning scheme from scratch? It seems there's not much one can use to diagnose LDM issues. I will try to get a database dump attached in due course.

I'm especially looking for some hints as to what to look for when analyzing the LDM database.

I don't suppose you have Microsoft System Center Data Protection Manager, do you? All my googling seems to refer to one of their PowerShell scripts.
–
Katherine VillyardJun 28 '13 at 20:20

Unfortunately not, no such service is available in this case (typical separated workstation). My searches did not reveal much either, presumably due to the semi-proprietary nature of the LDM standard. I think not much can be done in this case, but I thought posting here, though a long shot, is my last resort. For the time being, I'm happy that despite this malformed database, all the volumes get recognized by the system and are available for normal use. I hope it stays that way until a more permanent solution can be found (or the problem ceases to exist along with some hardware upgrade).
–
Karol PiczakJun 29 '13 at 23:59

I see your Boot drive has a status of Rebuild. Once it completes, see if the error goes away. Also ...did you try a chkdsk on the affected disk to see if it finds anything?
–
Nathan CJun 30 '13 at 22:41