Bootmgr missing & the volume does not contain a recognized file system

[backrowcentre]

Bootmgr missing & the volume does not contain a recognized file system

I have a toshiba laptop running on windows 7. One day I turned it on and it said "bootmgr is missing press ctrl alt delete to restart."

I have been researching how to fix it and have made a repair cd, which boots it and sends me to the start up process, but when I get to the command prompt option and type "bootrec/fixboot" it says "the volume does not contain a recognized file system."

I have no idea what's wrong and i've been trying to search the problem for hours, any help is appreciated.

 

[Night Hawk]

Welcome to SF! backrowcentre

There are a few other options like the Startup repair tool intended to replace boot files as well as others when not able to boot into 7. Running that a few times will often correct a boot problem.

The other command to use at the command prompt option would be the use of the "bootrec /rebuildbcd" command where that will scan for any 7 installation and prompt you for seeing that added into the boot list. The other option at the command prompt would be the DiskPart tool where you type the following.

DiskPart = starts partition manager
List Disk = llst all hard drives
Select Disk # = usually 0 like Disk 0
List Volume = lists all partitions
Select Volume = in case of hidden recovery partition being at front of drive you would Select volume 2
Active = marks partition as active
Assign(option and used mainly for things like making external HDs/usb flash drives bootable) = assigns drive letter
exit

The Startup repair is generally the quick and easy when all boot files are still present while that may take a second run at times. http://www.sevenforums.com/tutorials/681-startup-repair.html

 

[gregrocker]

Work through these steps for Troubleshooting Windows 7 Failure to Boot
so you'll know you've tried everything possible, including testing your HD and checking disk, if necessary copying out files to run Recovery or Clean Reinstall - Factory OEM Windows 7 .

 

[backrowcentre]

Hey guys, thanks it worked and it is up and running again. The only problem is the network adapters have disappeared and I cannot connect to the internet. it says windows could not find a driver for your network adapter.

 

[Night Hawk]

You likely need to power down and unplug the dsl or cable modem you use for a half minute or so. If the modem lacks an on/off switch ismply unplug the ac adapter for that as well any router plugged into it.

Once that is seen to replug the modem by itself and turn it on to allow it to resync with your ISP. Then the next step is to plug a routed in if you have one and allow that to pose as your pc. That then establishes a new private IP and Mac address.

The last step is to power up the pc and head for the Control Panel if the network icon is still seeing a red X on it if set visible to go into the Network & Sharing Center. If the automatic discovery box is already checked off in the IE options>Connections tab you should see "Local Network connected". If not then you would run the Network troubleshooting tool.

The method refreshes everything from modem to nic card(separate ethernet card), onboard WLan(wired network), or usb adapter if you have a hard wired setup. For WiFi you wouldn't have any ethernet cable needing to be plugged back in and simply run the troubleshoot connection option.

 

[gregrocker]

Go to the Toshiba Support Downloads webpage for your computer model to download and install the latest driver.

If what you did is Clean Reinstall - Factory OEM Windows 7 then the steps given in the blue link are quite specific about how to handle drivers, including putting the wireless driver on a stick or CD so you can get online quickly to update the rest of your drivers from optional Windows Updates.

 

[Night Hawk]

What model number is the laptop? That would be a help having the full number since an A205 might see something like A206-S103 on the end since the A205 model series will have several models. Toshiba will have the WLan if present as well as the WiFi drivers depending on which adapter it uses.

 

[shinseiryuu]

Hi,
I am posting this to help those after me who encounter this same problem.

Booting into windows gives an NTLDR missing error, not fixable even after attempting bootrec commands in Win7 Recovery Mode (via install disk). When attempting command bootrec /fixboot, I encountered the "volume does not contain a recognized file system," error.

I discovered the fix was to run Win7 Repair via install disk, and at the command prompt, type in

bootsect /ntfs60 C: (replace drive letter with your boot drive letter)

This will re-apply the master boot code despite bootrec /fixboot's failure.

Hope this helps someone in the future...

 

[gregrocker]

Bootrec /rebuildBCD can also accomplish this, as well as when Win7 Repair console cannot detect an OS to repair: Use Bootrec.exe in the Windows RE to troubleshoot startup issues

This is included in Troubleshooting Windows 7 Failure to Start

 

[shinseiryuu]

The reason why I post this solution is because I had tried all bootrec commands, including rebuildBCD. Despite the BCD being correct, the boot sector was still nonfunctional. Theoretically, bootrec /fixboot should be able to fix this as well, but for whatever reason - that failed as well, giving the cryptic "volume does not contain a recognized file system" error.

Bootsect is an alternative command that I have not found mentioned in many solution threads. I am certain this will help certain people who have tried everything else.

 

[gregrocker]

Yes, if the BCD is intact and correct, bootsect is another way to make it bootable.

We once included bootsect with all bootrec commands and probably should do so again. Thanks for the reminder.

 

[Night Hawk]

Hi,
I am posting this to help those after me who encounter this same problem.

Booting into windows gives an NTLDR missing error, not fixable even after attempting bootrec commands in Win7 Recovery Mode (via install disk). When attempting command bootrec /fixboot, I encountered the "volume does not contain a recognized file system," error.

I discovered the fix was to run Win7 Repair via install disk, and at the command prompt, type in

bootsect /ntfs60 C: (replace drive letter with your boot drive letter)

This will re-apply the master boot code despite bootrec /fixboot's failure.

Hope this helps someone in the future...

That's a good point to mention on the thread here since often a volume can become somewhat tainted resulting in disk errors causing startup issues. A good reference that describes how to use that command in some more detail can be found at How To Use Bootsect /nt60 To Update the Volume Boot Code to BOOTMGR

 

[Anshad Edavana]

Theoretically, bootrec /fixboot should be able to fix this as well, but for whatever reason - that failed as well, giving the cryptic "volume does not contain a recognized file system" error.

"Unrecognized file system" message might be an indication of damaged file systems and/or surface defects (may be partial damage ). I would first run CHKDSK /R against the "Active/System" partition before trying to rewrite MBR or boot sector.

 

[Night Hawk]

I couldn't agree more about that! I ran into that type of issue when trying to dual boot 7 with the W8 Preview where both ended up stalling until unplugging each drive to run the tool on each separately. That got 7 back running again on the spot while the preview was finally tossed once I had that back again for the look.

Something happened to each volume without any major system files damaged however. the Disk Check tool with repair switch simply corrected what the start up repair tool or other commands couldn't do at the time.