NF7-S Hangs at Verifying DMI pool message
I just finished completing a Windows XP installation on my two WD Raptors connected to an Abit NF-7S. Being concerned about backing my OS up, I used Norton Ghost to make an image of the OS partition to one of my data drives. Everything went fine until the Bootup process hung at the Verifying DMI Pool Data message.
I've tried rebooting, resetting my CMOS jumper, checking hard drive cables, and I've force updated the ESCD in my BIOS. Is there anything else I can do? Maybe reflash the BIOS? Reinstall the OS over itself? Windows recovery console? Any HELP is greatly welcome and appreciated! Happy holidays...at least it was when my computer was working!
I've tried rebooting, resetting my CMOS jumper, checking hard drive cables, and I've force updated the ESCD in my BIOS. Is there anything else I can do? Maybe reflash the BIOS? Reinstall the OS over itself? Windows recovery console? Any HELP is greatly welcome and appreciated! Happy holidays...at least it was when my computer was working!
0
Comments
IF you imaged the thing, and then got no further than the BIOS DMI table update, it might be trying what to do with TWO bootable drives.
Are the RAPTORs RAIDed??? If so, check your RAID BIOS and see if it has errors, this can hang a BIOS near that point, as Ghost does NOT knowe how to backup inside a RAID volume, it will happily make a real driect access partition to image to on ramining space. I HOPE you did not manage to let Ghost try to overwrite end of drive, your volume is BROKEN if so. What year version of Ghost???
I hate to say this, but this is one reason I do not use Ghost much on anythng RAIDed, it does not like logical volumes, and likes to hide its backup partition. IF it thought it had one drive from RAID controller, it might have tried to partition create ACROSS BOTH DRIVES. Ghost Professional (Enterprise) knows more about RAID than the home version of Ghost, a LOT more. Give it a real unraided drive for backup TARGET, it will usually do OK, if there is partiion room after overhead for a partition create and then backup to fit. BUT, it is persistant enough that on RAID, you wipe things you did not want to if you create a non-RAID image in a RAID volume by mistake. I use other tools for this backup chore.
John.
ADD: Yeah, try what Thrax says, but I think part of the problem is that RAID is enabled, RAID BIOS hung with an invalid drive structure in volume, and siolly DMI lookup hung cuz RAID BIOS went non-repsonsive and main BIOS had RAID on.
Both memory and HDs unplugged and reinserted. No change.
Ageek,
It was Ghost 2003. I was careful to select the C: drive (RAID) as source and F: drive (IDE Backup) as destination, but you never know. How come you never told me Ghost was a POS with RAID?! Just joking, man.
I appreciate both of your help. I also just reflashed the BIOS with no luck. I'm thinking of reinstalling XP over itself now unless you all can think of anything else. Somehow either Ghost FUBAR'ed my OS drives or I did.
I think you've done everything of merit, unless someone has a spectacular idea we've forgotten.
Any other program recommendations that do the same thing (Driveimage)..or do they all choke on RAIDed OSs?
THEN you would have a HIDDEN RAID volume, the one you want to boot from, and visible copy, the IDE drive which might even be bootable....
Reboot, write down RAID BIOS settings, shut down computer, unplug SATA, reboot and enter BIOS and tell it to boot from HDD-0 if you backed up to a primary master IDE hookup, see what happens. Every once in awhile a Ghost user manages to let it hide the source and leave the target unhidden, and ghost will then typically amke TARGET bootable and source unbootable. IF the IDE boot works, you can do it again, with target the RAID, and see what happens. Leave it to hide source, and you have backup and possibly a bootable RAID volume if you reset RAID to what you wrote down and plug in SATA again before doing backup. Some Ghost CDS are nice, they let you CD boot in an emergency, and make floppies to run Ghost off of, if you have no floppy boot.
That is the ONLY set of things that could cause this other than a radical fubar by Ghost. IF you fubarred your RAID image, one way to fix, which will take a long while, is to low-level or zero pack the drives as individual drives, then reestablish a RAID ARRAY, and if IDE boots to XP, then you can do a recovery to the RAID from your IDE if it has a viable backup actually done on it.
John.
Either of you know a safer way to image a RAID OS partition (on NF7-S SATA controllers) to a PATA hard drive on the standard mobo IDE connectors for backup purposes?
it seems that you were much smarter than me on Ghost. It sounds like DriveImage worked like a charm. Would you recommend I try that to image my OS? If so, any tips or suggestions.
John.
thanks,
john
When I find the cure I will repost.
I am running the bios 27 from the windows based flash utility.Are you using it as well?