are dynamic volumes the culprit?
Hey there - I'm in the same boat as everyone above, I haven't had any luck with anything and I'm wondering: Does it have to do with the dynamic volume? And if so, what's the remedy?
My particular situation was this:
Disk 0
Part 1 - Mac OS X
Part 2 - OS X data
Disk 1
Part 1 - Windows 7 (dynamic volume)
Part 2 - Data storage (dynamic volume)
I wanted to reclaim that OS X data storage and use it for Windows so I re-partitioned / formatted with NTFS. Next boot was "missing OS" and so it began. What *should* have worked was rebuilding BCD with bootrec.exe /rebuildbcd. Alas all I ever got was "error reading filesystem. Make sure drivers are loaded you're not corrupt" yadda yadda. BCDedit /create {bootmgr} would fail with the same error. After running chkdsk c: /f till I was blue in the face, it dawned on me that this *had* to do with the dynamic volume - there was simply nothing left to explain it.
So I've re-installed Win 7 on to Disk 0, part 2 and installed EasyBCD. I did Diagnostic Center / Reset BCD Storage (after "Recreate missing/deleted boot files" suggested I do so). The output of which is:
There is one entry in the Vista Bootloader.
Bootloader Timeout: 5 seconds.
Default OS: Windows Vista
Entry #1
Name: Windows Vista
BCD ID: {default}
Drive: Deleted Partition
Bootloader Path: \Windows\system32\winload.exe
Windows Directory: \Windows
(I added the bolding). It literally is referring to "deleted partition". Keep in mind, this volume is fully availble to me in Explorer, Disk Manager etc.
I can backup / restore now that I'm operational again, but I would ideally like to boot into that installation at Disk 1, part 1.
Any thoughts?
Addendum:
EasyBCD worked any damn way even though it referred to "Deleted Partition"!!!
So I umm...yeah. Ok. Donate - I'll do that.