Boot manager is missing on Satellite A105-S2051 laptop

arben pllana

• 1006 Answers
• Posted on Jul 20, 2008

SOURCE: boot mgr

email me and i will send instructions how to do that : [email protected]

SOURCE: Installing windows XP - Error encountered

Can you reboot and get into windows or is now corrupt?

What do you mean by 'uninstalled XP'??

You cant uninstall it unless you format the drive, in which case the recovery discs are now probably useless as they rely on a folder on the HDD called i386.

Recovery discs normally dont have the OS on them, they rely on the I386 folder to gather info about the computer and then restores it to the state when it was new.

If you can acess the system, reboot and go into the bios and change the boot sequence to CD, then insert the first recovery disc. then save the settings and the computer will reboot and start the recovery process again, this should clear up the error.

If it does not it will be because the i386 folder is missing in which case you can either explore the recovery discs for it or you will have to buy a copy of Windows XP.

SOURCE: Toshiba Satellite a135-s4427 Boot Manager Missing

its not the hard drive my frined, its the boot loader it has been deleted or it has been compressed the only way to fix this is to use the recovery cd you have, to boot from cd-rom you need to go into bios which is usualy F2 or F5 key, then under boot manager or somthing is the primary and secondary boot, change the primary to CD-ROM, then save it and restart then it should boot from cd-rom then you have do a start-up recovery.

SOURCE: cd/dvdrw drive disappears

try booting in safe mode and see it comes up then

SOURCE: cant install OS BOOTMGR is missing

Usually the installer should have a function to allow you to wipe the disk, or delete partitions.

If it doesn't, and you do not care about the hard disk content, and it is acceptable to wipe out the entire hard disk, you can do so in Linux.

(There is a utility which will do everything for you - Darik's Boot and Nuke, you find it at http://www.dban.org/ . I'm also giving you the "manual" instructions below, though).

Boot with Ubuntu Live, open Terminal, become root with 'su'.

Now you need to know how your disk is "seen" by Linux. Since you only have the one disk and nonexistent disks will fail, we can try all the likely hard disk names. The first command that does NOT fail saying "No such device" is the good one:

fdisk /dev/sda
fdisk /dev/hda
fdisk /dev/cciss/c0d0
fdisk /dev/rd/c0d0
fdisk /dev/ida/c0d0

One of these commands (likely the first or second) will give you a menu ending in "Command (m for help)". type "p" and press Enter to list partitions; there should be only one and it should be a Linux type, probably 83. If it isn't, stop - something's wrong. But it should be.

The first column will say something like "/dev/sda3". Note the number at the end, here "3". You'll likely have "1".

Now type, "d" and press Enter. You'll be asked which partition to delete. Type the same number you saw earlier. Type "w" and Enter to save changes and exit. Type "q" and Enter to exit without changes. The partition can still be recovered, but the disk is now "unlocked".

Reboot and install the OS of your choice. The previous hard disk contents will be permanently lost, and you'll get a shiny new empty partition with a working OS.

You can also erase the disk without using fdisk (but you still need to know how it's named, and for that you can use fdisk) by typing

dd if = /dev/zero of = /dev/sda bs=1M count = 12

Here we suppose the disk turned out to be /dev/sda.

This will write twelve megabytes of zeroes to the beginning of the disk, effectively wiping any OS information there could be there. All disk data are as good as lost. The disk is now, to all installing purposes, a perfect blank. Reboot and install the OS of your choice.

Just for the record, omitting "count" will zealously wipe out the whole hard disk surface, all partitions, all data, irretrievably (except using residual hysteresis detection equipment - doubt if even NSA would take the trouble). This can be handy when decommissioning computers.

There are also