XP Raid lost after sfc /scannow

[Guest]

This is the situation: system drive c on 40gb ide, data drive d on two 160gb
sata disks managed by XP with its striping.
I've had some OS problem, so decided to perform a SFC /SCANNOW. After
reboot, I could not see anymore the raid disks in disk management. No drive
at all. Tried to reistall the Intel Application Accelerator Raid edition that
came with motherboard, and after reboot I could see two separate 160gb disks,
marker as dynamic and one of them as "missing", with no data on them
(unreadable).
In System volume information I have no registry saved before the SFC, and
system restore has no restore point before sfc.
Is there a way to rollback to the situation before SFC? Does sfc save a
backup copy of files that replaces?
Thanks a lot and sorry for my bad english.

Simone, Italy

 

[R. McCarty]

You used a Stripe set for a Desktop PC ? I'm not sure how an SFC
would break a Stripe set. Also, which configuration/setup did the RAID
use ? XP's native Disk Management of the Intel ? In other words you
can create/manage a Raid natively with Disk Management or by using
the Intel software. Which ever one you created the Stripe set with is
the one you need to maintain it with. Be careful and go slowly, once
you break a Stripe set you may have lost the data permanently.

 

[Guest]

From disk management I had created a stripe set, it's not managed from a
third part software, all made from xp disk management. But if I restore
system to the point after SFC, I can not see any of the 2 disks, I see them
only after i install IAA, that is not the software I had used to build the
stripe set. What should I do to see again disks without installing IAA? They
are not present at all in disk management...

 

[R. McCarty]

Maybe I follow your sequence. Did SFC /Scannow and then the RAID
disappeared. You installed Intel's IAA (Which wasn't originally on the
PC ?) Using Disk Mgmt., you can see both physical drives as Dynamic
but one of the drives shows no content in the Bar representation of the
drive ? Is that correct - or is the problem that ONLY one of the 160 Gig
drives appears in Disk Management ? Either way, I would uninstall the
Intel RAID support software. Just want to make sure I clearly understand
what your conditions exist.

 

[Guest]

Ok, some new stuff.
I took the system back to the restore point created after SFC (the oldest I
have).
At this point, in disk management I see NO disks at all, apart of C:.
Then I reistalled the promise raid controller's driver, and now I can see 2
disks in disk management, the first called "Disk 0", dinamic, 160gb, with no
partition and the sign "non riuscito" (something like "unable to"), and the
second, called "Missing", dinamic, 160gb and unable to.
Is there no way to roll back the sfc mods?

 

[R. McCarty]

Not that I'm aware of. Normally, SFC /Scannow shouldn't really find
any discrepancies - because Windows File Protection is always active.
It would quietly replace any "Dll Hell" type conditions. Besides, SFC
wouldn't have monitored or affected a 3rd-Party driver like the Promise
RAID. It's hard to give you any specific advise with the drive info you
are getting from Disk Management.

 

[Guest]

Not even a SFC Log file to know what has it changed?

 

[R. McCarty]

Surprisingly No - Usually WFP will log an event when something is
overwritten and the trigger starts a replacement. But I thought of
that and went back to my notes (necessary with age) and there was
a notation about SFC not logging it's activity. Wish I could offer
more constructive advise - You might want to check with Promise
and see if they have a customer forum. If so, you'll likely get more
precise advise on how to proceed.

 

[Guest]

Unfortunately there's no Promise support forum.
I found an interesting thing in the event viewer, right after it finished
the SFC sca:

Event id: 60052
Windows build succesfully upgraded from 2600 to 2600.

What does it mean? My costumer said that after SFC, pc rebooted, and stayed
about 3 or 4 minutes reading from cd with a strange light blue screen before
login mask...