Re: UNMOUNTABLE_BOOT_VOLUME

Hi Anna,

Many Thx for the reply. Pls see my reply to Gerry for most of your points
... However also to your last point:
Another course of action for your consideration is to run a Repair install
of the Win2K OS and see if that resolves the problem. Have you considered
such?

I had not thought of this, but I will try it now on the OLD drive to see
what happens and let you know

many thx again

-BB


"Anna" <myname@xxxxxxxxx> wrote in message
news:uaTLlHX2JHA.4272@xxxxxxxxxxxxxxxxxxxxxxx

"Brian Burgess" <bburgess66@xxxxxxxxxxx> wrote in message
news:eHaPitS2JHA.1372@xxxxxxxxxxxxxxxxxxxxxxx
Hi all,

I've been 'googling' this subject for the past two weeks. All posts
seem to suggest following the same set of procedures shown below:

***************************************************************************
1) Boot up your computer from your Windows XP installation CD. Insert the
XP CD into your CD-ROM drive and turn on your computer.

2) Set your BIOS to boot from CD. Your system's BIOS settings can be
opened by hitting the F2, F8, F8 or Delete key on your keyboard as the
computer boots up. The specific key differs depending on your computer's
manufacturer. When you see the message "Press any key to boot from CD,"
tap any key on your keyboard and wait until you see the "Welcome to
Setup" screen.

3) Hit "R" to use your Recovery Console to repair the installation. If
you have a dual-boot computer, you need to select the particular Windows
installation you would like to access.

4) Type in your administrative password when the computer prompts you to.
If you have no password, simply press Enter. This will bring you to the
command prompt.

5) Type in "CHKDSK/R" and press Enter. CHKDSK will now scan and repair
your hard drive. Type Exit when this process is complete

6) Press Enter to restart the computer. Your computer should now boot
properly, without that annoying error.
***************************************************************************

All of this I have followed without success. I do have a special
circumstance also:
This is a dual boot system with Win2K on the primary (FAT32) partition,
and WinXP on the extended (NTFS) partition. Both fail with same error.

This all started occurring after a power failure. The power failure
ended up being a physical defect with the plug into the wall socket. Plug
replaced, power restored, boot problem occurs....

My question in the end of course is 'how to fix'. But I'm also
wondering if (because both windows wont start) is: Could a controller
failure cause this? The motherboard is about 4yrs old. Has two IDE
(UDMA133) controllers built in. Is it possible that a marginal
controller can cause this???

PLZ help

many thx in advance

-BB


Brian:
The problem here is that the cause of this problem (based upon that
specific error message) can arise from diverse effects, both hardware &
software related.

The chkdsk /r command that you invoked (even though it was unsuccessful in
restoring the system to a bootable, functional state) is a "tried & true"
initial effort.

The fact that the problem occurred after a power failure is somewhat
ominous in that it makes one suspicious some hardware component has become
defective as a result. On the other hand this could be nothing more than a
corrupted OS triggered by the power failure.

The very first thing you should now do (assuming you have not already done
this) is check out the HDD with the diagnostic utility available from the
disk's manufacturer. It's conceivable you may be dealing with a defective
HDD.

At this point-in-time probably the most straightforward way to at least
begin the diagnosis of what's causing the problem is to simply install the
Win2K OS onto a different HDD. (I'm assuming, of course, that OS contains
the system/boot files). Hopefully you have or can obtain another HDD
that's available for this purpose. If no problem arises and the system
functions without problems then you know the problem is at least
software-related or possibly the original HDD became defective either as a
consequence of the power glitch or for some other reason.

Another course of action for your consideration is to run a Repair install
of the Win2K OS and see if that resolves the problem. Have you considered
such?
Anna



.

Loading