It's probably been done to death on the forums but i still seem to be failing to grasp exactly what its referring to when it says 'Bootmgr image' and what im supposed to be trying to fix x_x
The problem came about when i installed Wubi on my vista home premium 64bit system, but not on the C: drive, on a 1tb datadrive (I: drive) because it had more free space. My C: drive is 3x500gb drives running in raid 5.
The install worked fine, ubuntu ran no issues, but on a reboot it didnt give me a menu to choose an OS. So restarted, and on startup had degraded raid and the corrupt image error. Put the vista dvd in, booted off that and went to repair... got a bluescreen.
On this startup raid is now failed. meh.
The raid cycles between 'failed, not bootable' and 'rebuild, bootable' and that affects what happens each time i boot into the RE. It will hang while searching for installed OS then BSOD again, allow me to go 'next' but not detect my c: drive, and on the rare occasion, pick up my drive and let me access the recovery tools. Im not installing any raid drivers at this point, should i be? lol please forgive any obvious questions..
I've tried the startup repair a few times but it fails to fix the issue.
Tried an offline system restore but it crashed while initialising.
2 chkdsk /r in cmd fixed a bunch of unhappy files. sfc caused a crash. did a /fixmbr and that seemed to accomplish nothing. /fixboot wouldnt work, /scanos and/rebuildbcd crashed also. So i came to the conclusion it was the BCD file. Ended up following the instructions on the neosmart page to completely rebuild the BCD. (My thanks go to whoever made that wonderful page )That all worked smoothly. But i still have the corrupt bootmgr image error, so what am i missing?
Ok, after re-reading another post (MOOTMGR image is corrupt. (i have followed steps on website) - The NeoSmart Forums) if its got something to do with the c:\bootmgr file (imagine that..) i can delete that easy enough, but i dont have access to the startup repair atm, so is there a cmd prompt that can effectively do what the repair does?
The problem came about when i installed Wubi on my vista home premium 64bit system, but not on the C: drive, on a 1tb datadrive (I: drive) because it had more free space. My C: drive is 3x500gb drives running in raid 5.
The install worked fine, ubuntu ran no issues, but on a reboot it didnt give me a menu to choose an OS. So restarted, and on startup had degraded raid and the corrupt image error. Put the vista dvd in, booted off that and went to repair... got a bluescreen.
On this startup raid is now failed. meh.
The raid cycles between 'failed, not bootable' and 'rebuild, bootable' and that affects what happens each time i boot into the RE. It will hang while searching for installed OS then BSOD again, allow me to go 'next' but not detect my c: drive, and on the rare occasion, pick up my drive and let me access the recovery tools. Im not installing any raid drivers at this point, should i be? lol please forgive any obvious questions..
I've tried the startup repair a few times but it fails to fix the issue.
Tried an offline system restore but it crashed while initialising.
2 chkdsk /r in cmd fixed a bunch of unhappy files. sfc caused a crash. did a /fixmbr and that seemed to accomplish nothing. /fixboot wouldnt work, /scanos and/rebuildbcd crashed also. So i came to the conclusion it was the BCD file. Ended up following the instructions on the neosmart page to completely rebuild the BCD. (My thanks go to whoever made that wonderful page )That all worked smoothly. But i still have the corrupt bootmgr image error, so what am i missing?
Ok, after re-reading another post (MOOTMGR image is corrupt. (i have followed steps on website) - The NeoSmart Forums) if its got something to do with the c:\bootmgr file (imagine that..) i can delete that easy enough, but i dont have access to the startup repair atm, so is there a cmd prompt that can effectively do what the repair does?
Last edited: