Verifying DMI Pool Data, HANG

  • Thread starter Thread starter Bob T
  • Start date Start date
B

Bob T

System: W2K, Fat 32.

I had a bad Maxtor hard drive. Got a new one. Used their
program to move the old data to the new drive. The old
drive was set as Master, new, as slave. The first
question the Maxtor copy program asked was if I were going
to use the new drive as the boot drive (so it could get
the boot information copied correctly.)

After successfull transfer, I reset the new drive as
master, took the old drive out of the system.

I needed to check a file on the old drive. I reinstalled
it, but as slave on the IDE cable. Everything booted ok.
And looked fine.

I saw one anomaly with cluser size for a logical drive on
the new HD.

I told Partition Magic to resize the cluster to match the
old drive.

It said it did and would have to reboot.

Upon rebooting, my system hung at "Verifying DMI POOL
DATA."

I ran the PM rescue disks and it tells me that their is a
PM boot manager (now) on the system, but isn't running.
Evidently, PM got confused when it saw the new drive with
boot info & the old drive, with boot info.

I tried to use fdisk/mbr, but that had no effect.
I unplugged the IDE cable and power to the drives. Took
out the old drive. But still the new drive hangs.

I used PM's program to take off the "disk (boot) manager"
program, but that didn't help either. I put it back on.

Partition Magic's solution is to SYS the C drive. How do
you SYS W2K? It can't be done, can it?

Do I need to copy the old drives, boot info to the new
drive, head 0? I did manage to get into the system,
through floppies, after I took off PM's "disk manager."
It shows all the Partitiion info & drive sizes.
Everything looks ok.

I don't want to loose my new drive. I just put info on it
that I can't get back.

Any suggestions how to get the boot SYS back on to my W2k
so I can get past the "Verifying DMI Pool Data?"

Help desperately needed.

Thank you,
Bob
I decided to compare
 
Hi, Bob.

Unplug your old (now slave) drive. Boot from the Win2K CD-ROM and Repair
the new (now primary master) drive, choosing only to Inspect the startup
environment. (It's been a couple of years since I upgraded to WinXP, so my
memory of Win2K's Repair dialog may not be exact, but you should be able to
find it.)

AFTER repairing the new drive, put the old one back in. Win2K Setup and
Repair can get confused when more than one drive is hooked up, especially if
both have Active primary partitions.
Partition Magic's solution is to SYS the C drive. How do
you SYS W2K? It can't be done, can it?
Click to expand...

Sure. But if you SYS C:, then it will NOT boot into Win2K! That, among
other things, replaces the WinNT-style boot sector, which loads ntldr, with
the DOS-style boot sector, which loads io.sys and msdos.sys and knows
NOTHING of NT.

I've used Partition Magic, but only for partitioning, never for
multi-booting. The native multi-booting system Microsoft built into WinNT4,
Win2K and WinXP works just fine for me. I think trying to mix'n'match the
native system with the PM system may be what's causing much of your problem.

The Win2K Repair procedure should get you back to booting into Win2K on the
new drive. After that, Disk Management should be the only tool you need to
get your drives organized. I'm amazed that many sophisticated users STILL
haven't found Disk Management, over three years after it was introduced on
the original Win2K CD-ROM in February 2000! MS buried under lots of
mouse-clicks; I find it faster to just type at the Run prompt:
diskmgmt.msc. Study the program AND the Help file; they explain a LOT about
hard drives and file systems. DM can't resize (shrink or grow) volumes, but
it can create and delete partitions, format them, assign drive letters, etc.
It's a great tool.

RC
 
Back
Top