Automated System Recovery Failure

[Danny O'Hanlon]

My Windows XP system has three separate hard drives.
The 80Gb SYSTEM drive is divided into the four partitions:

C:\ (18.86Gb) -- dedicated to the Windows XP OS only. Then
P (28.52Gb)
Q (23.52Gb) and
R (5.78 Gb)

The remaining two separate (backup) drives are similarly partitioned
and mostly empty.

In attempting to bring my system back from a host of irregularities,
the "Last Known Good Configuration" facility did not do the job.
Likewise, numerous attempts at the "System Restore" facility failed to
work (--again! And yes, I did use the emboldened numbers.) Now I find
that even the "Automated System Recovery" facility will not work.

When engaging the ASR, I get the Bluescreen message:

"Unable to restore the configuration of your system. The capacity of
your current system disk drive is insufficient, and cannot be used to
recover the partitions on the original system disk. The replacement
hard disk drives must be at least as large as the disks present on the
original system."
(So much for Microsoft's arsenal of system recovery facilities.
Bloody useless.)

Now, having suspecting something like this might arise, I made certain
that the C: Drive was well under half full. (Of the available 18.86 Gb
on C:, 7.89Gb is used, with 10.9Gb reported as "free".)

You can understand why the message perplexes me.

QUESTIONS:

1) Why does ASR think I am trying to employ a "replacement" drive?
2) Given my setup as described, how do I get the ASR to work?
3) What if I cant?

Regards,
Dan O'Hanlon

 

[Guest]

Who partitioned your harddrive? C, P, Q and R???
An 80gb hd should have no more than 2 partitions at most 3, a "C" and
maybe "E" or "F". No wonder you've got problems.
Ranish Partition Manager v2.44 Beta
http://www.pcworld.com/downloads/file_download/0,fid,6170,fileidx,1,00.asp

 

[Guest]

I did. I've been using computers (and Windows OS) daily for ten years
now--have even built and rebuilt four or five. In all that time I have yet to
hear anything of what you say regarding the limitations on the number of
partitions on a drive of that size--or, that it makes the slightest
difference what letters you assign to them. There is nothing on this either,
in the shelf-full of books I have on Windows OS.
As it happens, my B, D, E, F, G, and H, are already accounted for. I also
have two other hard drives on my system that are similarly partitioned
(--with no problems whatsoever.) That accounts for my use of higher letters.

I'm not saying you are wrong. I am saying that if you are right, this is
precisely the type of information that Microsoft should point out on every
possible occasion and more than obviously.

I would like to say I appreciate your input, but all you have really offered
is another question, and callous criticism of water already passed under a
bridge. Being effectively labeled an idiot is not something I tend to feel
grateful for.

Anyone out there who can offer actual assistance?

D. O'H

 

[Guest]

Hello to all,
Regarding all previous on this posting, I feel the need to restate my needs.
Before using Microsoft's Windows XP's Automated System Recovery (ASR)
feature, I had consulted Microsoft's Review Article Q298278 for advice--and
where it states that:
"...before you run ASR, make sure that the drive that you specify for the
..bkf file is not the boot or system volume. "
--which is why I put the .bkf file on a completely different hard drive.
Well, I have news for Microsoft. When you specifiy a partition on a separate
drive, it STILL might not work. It didn't in my case, anyway--and there's not
alot you can do (beyond the above, and if you believe Microsoft's hype) to
get it wrong. Well, obviously there is.
My system is convinced that I am trying, not only to restore my system to a
different drive, but also that this so-called "replacement" drive is smaller
than my existing C: drive. Hence the refusal to function.
What of XP's arsenal of restorative functions? First employed was: "Last
Known Good Configuration" --Failed. Secondly, came the "System Restore"
facility. --Failed! (and yes, I did use the emboldened numbers.)
Now, finding myself fallen into some sort of ASR Black Hole, with an
evidently completely useless ASR backup, I find myself also faced with the
nightmare of needing to reformat my C: drive.
All this, despite my having painfully sought out Microsoft's extraordinarily
limited advice on the subject. (You would think, as I did, and from the
little that Micorsoft has to say about it, that "you simply can't do this
thing wrong!)
The ASR facility in particular, is about "knowing"--knowing--that, if worst
comes to worst, this at least, will work--and that there will be NO "even
worse than worst"! Unfortunately, there is, and I am now in that position.
Ths leaves me with a SERIOUS question: What if it happens again?
Not wanting to make the same mistake twice, what do I do? What procedure can
I follow to know--and I mean "know", should I ever run into this nightmare
again and have to use "Automated System Recovery" (ASR) again--that it
actually will work?
I have to find out what I did wrong, so that I can avoid that possibility ih
the future--otherwise it finally will be LINUX for me!
Tell me therefore, somebody, please: what to be sure and NOT do when setting
up the ASR.
Fed up the Gills!
Dan O'H