Unmountable boot volume

[RYU81]

sometimes when i load win7 show me blue screen unmountable boot volume,boot.ini not corrupt,i don't have UDMA option to change in bios,i tries use scandisk for bad sector, to fix any error & use startup repair but i can't find any error to fix it seem my hdd working fine.any help??

http://www.toshiba.ca/web/product.grp?section=1&group=223&product=5616

[myselfidem]

Have you made an dualboot: Windows XP and Windows 7?

[RYU81]

Have you made an dualboot: Windows XP and Windows 7?

no

[myselfidem]

You can find help here:

How to use the Bootrec.exe tool in the Windows Recovery Environment to troubleshoot and repair startup issues in Windows

Unmountable Boot Volume Error Message or BSOD Fix

“bootmgr is compressed” in Windows 7

*Edit1:

If you need the Repair disk:

Windows 7 - System Repair Disc - Create

You can also ask a friend to lend you the CD for Windows 7 Repair Disk with the same architecture of your OS.

*Edit2:

You can also use EasyBCD 2.0.2

Edited December 6, 2010 by myselfidem

[RYU81]

You can find help here:

How to use the Bootrec.exe tool in the Windows Recovery Environment to troubleshoot and repair startup issues in Windows

Unmountable Boot Volume Error Message or BSOD Fix

“bootmgr is compressed” in Windows 7

*Edit1:

If you need the Repair disk:

Windows 7 - System Repair Disc - Create

You can also ask a friend to lend you the CD for Windows 7 Repair Disk with the same architecture of your OS.

*Edit2:

You can also use EasyBCD 2.0.2

thx alot for links i try them all when i'll tell what happen but what useful to use EasyBCD?

[myselfidem]

You can read all about how using EasyBCD here:

EasyBCD Documentation

FAQ

EasyBCD Wikipedia

*Edit:

Bootsect Command-Line Options

Bootsect Command-Line Options

Bootsect.exe updates the master boot code for hard disk partitions to switch between BOOTMGR and NTLDR. You can use this tool to restore the boot sector on your computer. This tool replaces FixFAT and FixNTFS.

Bootsect Commands

Bootsect uses the following conventions:

bootsect.exe {/help | /nt52 | /nt60} {SYS | ALL | <DriveLetter:>} [/force]

For example, to apply the master boot code that is compatible with NTLDR to the volume labeled E, use the following command:

bootsect.exe /nt52 E:

Command Description

/help

Displays these usage instructions.

/nt52

Applies the master boot code that is compatible with NTLDR to SYS, ALL, or <DriveLetter>. The operating system installed on SYS, ALL, or <DriveLetter> must be a previous version of Windows Vista.

/nt60

Applies the master boot code that is compatible with BOOTMGR to SYS, ALL, or <DriveLetter>. The operating system installed on SYS, ALL, or <DriveLetter> must be Windows Vista.

SYS

Updates the master boot code on the system partition used to boot Windows.

ALL

Updates the master boot code on all partitions. ALL does not necessarily update the boot code for each volume. Instead, this option updates the boot code on volumes that can be used as Windows boot volumes, which excludes any dynamic volumes that are not connected with an underlying disk partition. This restriction is present because boot code must be located at the beginning of a disk partition.

<DriveLetter> Updates the master boot code on the volume associated with this drive letter. Boot code will not be updated if either 1) <DriveLetter> is not associated with a volume or

2) <DriveLetter> is associated with a volume not connected to an underlying disk partition.

/force

Forcibly dismounts the volume(s) during the boot code update. You must use this option with caution.

/mbr

Updates the master boot record without changing the partition table on sector 0 of the disk that contains the partition specified by SYS, ALL, or <drive letter>. When used with the /nt52 option, the master boot record is compatible with operating systems older than Windows Vista. When used with the /nt60 option, the master boot record is compatible with Windows® 7, Windows Vista, Windows Server® 2008 or Windows Server® 2008 R2.

If Bootsect.exe cannot gain exclusive volume access, then the file system may overwrite the boot code before the next reboot. Bootsect.exe always attempts to lock and dismount the volume before each update. When /force is specified, a forced dismount is attempted if the initial lock attempt fails. A lock can fail, for example, if files on the destination volume are currently opened by other programs.

When successful, a forced dismount enables exclusive volume access and a reliable boot code update even though the initial lock failed. At the same time, a forced dismount invalidates all open handles to files on the destination volume. This can result in unexpected behavior from the programs that opened these files. Therefore, use this option with caution.

Edited December 7, 2010 by myselfidem

[RYU81]

my friend I try all options still not fix my problem,i think its hardware not software.

[myselfidem]

You can try sfc /scannow

SFC Scannow

*Edit: That happens sometimes with my computer when I disconnect a HDD to connect an other. But after sometimes all it's OK. Maybe it is a contact problem of hard disk..

Edited December 10, 2010 by myselfidem

[RYU81]

You can try sfc /scannow

SFC Scannow

*Edit: That happens sometimes with my computer when I disconnect a HDD to connect an other. But after sometimes all it's OK. Maybe it is a contact problem of hard disk..

i did before nothing wrong in my system

[myselfidem]

You can try to disconnect the hard drive and reconnect. Maybe is a contact problem!