Discussion Locked

MBR problem in W2K?

0 helpful
11 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi folks,

I think I have a problem with the MBR on the hard drive of my IBM ThinkPad T21 (NTFS formatted). Here's what I did that seemed to have caused it:

>> I did a "chkdsk /f" which then prompted me for repair at boot time. So I answered YES and rebooted the computer. When chkdsk was doing its thing, it said something like "$0 index 32161 deleted". Now when I boot up again, it stops right after the POST screen and leaves me with this blinking cursor at the top-lefthand corner.So, after browsing through the various topics on this problem I thought it would be related to the MBR (probably the "$0 index 32161" thing), so I tried the following fixes, which none worked.

1. FIXMBR
2. FIXBOOT
3. FDISK /MBR

Now, I've been chugging along with my work-around. I was able to create a W2K boot floppy(!!) and I've been working like this for the past few days. I guess the boot files are OK, since I am able to boot it from the floppy which was made by simply format and copy the boot files over.

Oh, all ye mighty Disk Drive Gurus... Please rescue me out of this predicament...

Thanks,

Bob

11 replies

by otl

Tried "sys c:" from the A: bootup.

Possible problems with the operating system on the hard drive locking up.

by chialoon

Sorry, don't know what you meant. I made the boot floppy by simply formatting it from NT 4.0 and then copied the existing system files to the floppy. That's why I think the boot files are OK because I could boot the whole system with the floppy, which in turn redirect the boot process to the hard drive.

by shanghai sam

What exactly is the last thing that you see on the screen before you see the blinking cursor? Does it hang right after the devices are detected?

by chialoon

Just the normal POST stuff. The big IBM logo & then the F2 to access system setup and F12 to choose boot device message on the bottom left.

by stryker123

boot with your floppy, once into windows, right-click "My Computer" and select "manage"

go into "Disk Management"

Right-click on your c: drive, if "Mark Partition Active" option is available, click on it, then exit out and reboot, saving any changes.

by chialoon

Thanks, but nope. This option did not show up. I guess it has something to do with this being the only volumne on the drive.

by chialoon

Can't find anything new that I haven't tried. Thanks, though.

A new piece of info. When I run the W2K CD to run Recovery Console, if I run MAP to list devices, here are the devices listed:

?: 0MB \Device\Harddisk0\Partition0
C: NTFS 30521MB \Device\Harddisk0\Partition1
A: \Device\Floppy0
D: \Device\CdRom0

I don't know what the first one is (?). I only have one partition (for drive c:). Perhaps this is the problem?

by stryker123

Bob,

Have you tried a repair from the RC?

Only check "Inspect Boot Sector" and "Restore Startup Environment", otherwise your build will be toasted.

Also, try replacing the ntldr and ntdetect.com from the i386 folder of the Win2k CD in the c:\ root. You'll have to reapply the service pack afterwards.

If this is unsuccessful, try a parallel install, name the install path to \WINNTFIX or something to that effect. If that install boots, edit the boot.ini file [you'll have to remove the read only attbibute] to point to the previous install, give it a new name, such as

multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional ORIGINAL" /fastdetect

also add a few seconds to the "TIMEOUT" variable, 30 should be good, so the boot menu shows up.

by chialoon

(Sorry for the late update, but I've been tied for a while.)

Thanks, but I already tried all the tricks you've described.

Now, the good news is the drive suddenly started working again (without the boot floppy). The bad news is, I still don'tknow what happened and how (or if) I can fix it in the future. There's some wierd Bill Gates voodoo there.... But I'll take what I can get.

This discussion is closed to new replies.