PC Won't Boot After Crucial M4 Firmware Update

[basslover1]

I decided to check to see if there was a firmware update for my Crucial M4 128GB SSD drive the other day, and there was; 070H.

So I run the update utility, and reboot my machine and I'm presented with a Grub 17 error. Which through me for a loop because I've never installed Linux on this SSD. Then I remembered that the 500GB disk I have at one point did have Ubuntu on it, and apparently still has traces of Grub left.

So then I realized that the boot loader on my SSD had been corrupted/deleted/damaged/etc by the firmware update.

I've tried everything I can find through searching:

Booting from the Win 7 disk and repairing startup, using bootrec.exe/fixmbr /fixboot /rebuildbcd.

I've tried marking the disk as active through windows, through the command prompt off the DVD.

Nothing permanently fixes the issue. I'm currently typing this from the SSD in question, and it's been like this for a while. I can run through some of the various fixes, eventually one will work and I can boot into the OS but I know that the next time I need to restart I'll need to run through the process again because it won't boot.

I'll either be greeted with bootmgr is missing, or (paraphrasing here) no OS found, insert proper disk and press any key to reboot.

I'm all out of ideas. I know a clean install will be a sure fire fix, and it won't take long to do but I really really want to avoid this because if I reformat all of my WMC recordings flagged Copy Once, will no longer work (100+ recordings ) and I don't want to lose them.

What else can I try to actually fix this I don't know what else to search for?

PS. Yes the SSD firmware did actually update.

 

[denis280]

did you try a CMD with the command chkdsk C:/F

 

[basslover1]

did you try a CMD with the command chkdsk C:/F

No I did not. I'll try it later as I don't want to do it now and have it not work then be stuck trying to boot it again for another two hours. I'll report back when I do.

 

[basslover1]

did you try a CMD with the command chkdsk C:/F

Sorry it took so long to get back to you, but I don't always have a few hours to sit down and tackle this problem in case it doesn't start up right away. Of course it's been raining today and we must have had a surge while I was at work so I didn't have much of a choice.

I ran the command you suggested, and the only errors it found (and fixed) were that some empty sectors were marked allocated and something relating to the Master Boot Table (yes I should have taken a picture).

So I rebooted and it loaded up Windows right away. However, because I can't leave well enough alone I restarted at first chance and it's still not working properly. I reboot and it says (paraphrasing) no boot device detected insert device and restart etc. etc.

I booted off the USB and did the startup repair and now here I am typing to you, but I know if I restart again it probably won't be fixed.

 

[denis280]

It should be fixed.and you could also run a sfc/scannow