• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 714
  • Last Modified:

winXP with intel raid boot failure

Greetings!
Asus P6T Deluxe V2  MB Intel i920 4GB  ICH10R RAID 0+1  running about a year.
After power failure, on boot receive this message after Windows splash screen. "The Logon User Interface DLL I:\WINDOWS\system32\awgina.dll failed to load."  The normal way to recover appears to be, to start in Safe Mode and edit the Registry to correctly poiint to MSgina.dll  However, Safe Mode does not complete the boot, after messages "Windows is starting up, Loading your personal settings, logging off, saving your setting, Loading your personal settings, and continues looping these messages.
Another way is to use the Install repair from the Original install disk.  Using this disk, and pressing F6 to load the RAID drivers, when it asks for the RAID driver disk, it fails to recognize the disk.  After creating a new RAID driver disk from the MB disk and trying again, same result. Downloaded latest version from ASUS site and made another F6 disk, same results.  Another way is to use the recovery console, but install crashes with a suggestion to use CHKDSK /F before the Recovery console option is available. The Intel Matrix Storage Manager (option ROM v8.0.0.1038) shows all disks normal. But, Status = Verify

Apparently the RAID array is not properly seen by Windows on Boot.  Do not have a clue why the install disk does not recognize the 'F6' driver disk.
Any clues?
Thanks,
Have fun,
Paxton
0
jpaxtonss
Asked:
jpaxtonss
  • 4
  • 4
  • 3
  • +2
1 Solution
 
lee555J5Commented:
It could be a floppy drive issue. Do you have another drive, even a USB floppy drive? 
0
 
jpaxtonssAuthor Commented:
Thanks for the idea.
Seems unlikely as a pretty new drive, and only one in the machine (from which I did the original install).  I have two DVD/CD drives, so I could put the files on  the other one and see if I can change drive letters, somehow I think not, or I could swap the floppy or add another.

But, I will open the box and swap it with a known good floppy, tomorrow

have fun, Paxton
0
 
arnoldCommented:
you can use nliteos.net and slipstream the Motherboard drivers along with any other vendor drivers as well as updates and install it with the drivers already included.
0
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
jpaxtonssAuthor Commented:
Thanks for that idea, I guess you mean nliteos.com
I will investigate that approach

Have fun, paxton
0
 
DavidPresidentCommented:
arnold gave good advice on slipstreaming the driver ... A few things you may not be aware of in the RAID that may contribute to the problem

* You probably have inconsistencies between the two pairs of RAID1 disks.   If, for example, block #123 on disk1 does not equal block #123 on disk3 then you have a mismatch.  This can lead to data loss because you have a 50-50 chance that one disk is incorrect. The algorithms which dictate the data that will be chosen varies from controller to controller, and sometimes even firmware.

* In your scenario, it is possible that you have inconsistency and the RAID controller gave you the incorrect data.

A vast majority of this comes up after power failures.  The "STATUS=VERIFY" is usually a good hint.

A CHKDSK would be a big mistake.  The RAID controller may very well be able to sort out which disk has the trusted data.  Run a data consistency check/restore.    THEN run CHKDSK.  

Note I am somewhat oversimplifying things, and not getting into all possible scenarios, but the moral is to run data consistency checks often, always after a power failure.  This lets the data redundancy potentially repair the damage.

0
 
DavidPresidentCommented:
Ideally, run data consistency/repair NOW, through the BIOS.  Any I/Os from windows O/S, or even loading/repairing the O/S will lessen chances of recovery.
0
 
jpaxtonsCommented:
Thanks, dlethe.

  I think your response makes sense, Of course I did not even attempt a chkdsk!
I have not found how to run the data consistency check in the BIOS, yet.  I can find no tools, just the Intel Matrix storage manager as reported above.  I will investigate that.  If you happen to know how to invoke those tools, I appreciate it.

I have had a disk failure some 6-8 months ago, replaced it with a new one, and it rebuilt fine.  I thought I had a bullet proof Windows, machine....NOT!

Have fun,
Paxton
0
 
DavidPresidentCommented:
Sorry, I do not use the Matrix controllers, they are for all intents and purposes ... crap.  But I guess I'm not telling you something you already don't know.   I find it unusual that there is no such process  Your initial message had "STATUS=VERIFY", so perhaps they call it VERIFY?   I would head over to the intel mobo site, find the appropriate controller and look into this.  You can kick it off before going to bed.

There are software tools that can do the same thing, go to runtime.org, and download the reconstructor.  Free to try, and the great thing about it, is that it will tell you where the problems are.  You give them money if you want to fix them, but be forewarned, that this software is not privy to anything in the NVRAM of the motherboard that might indicate which disk can be trusted more than the other.

I cranked out an article last week about these sort of things, and I've been told it is a great article, as they gave it a community pick, EE approved and EditorsChoice, so worth reading.  

http://www.experts-exchange.com/articles/Storage/Misc/Disk-drive-reliability-overview.html


0
 
jpaxtonsCommented:
dlethe,
Thanks again for your help and suggestions.  not surprised to hear your evaluation of the intel RAID.  The Status Verify was just there in the BIOS display, it shows all 4 disks being OK.  The only menu selections are as I remember, create an array, destroy an array, exit, etc.
I went to the intel site and joined their community board, but  the confirm email never showed up, so, can't log in, but it knows my email address, so will have to use a different email to try again.  I will keep at it
tomorrow is another day
Have fun,
Paxton
0
 
DavidPresidentCommented:
All disks could well be perfectly good.  We have already established that the data isn't correct, at least on the .DLL you originally reported.  So now next step is to see if the correct version of the DLL, and any other files,  is correct on one of the other disk drives.
0
 
jpaxtonsCommented:
Thanks for all the tips.  However, I do not think we have proved any bad data, as I believe it is a bogus message and the 'array drive' is not visible to the OS.
But, making some progress, as I have made a bartPE with the runtime.org tool plugin.  The bartPE begins the boot, offers an F6, shows the Window XP splash screen, then scrashes at the same spot BSOD (where it suggests  running CHKDSK /F).  This is without using F6 to install the raid driver software.  And, I have now determined that in fact the diskette (one of the new ones with various chip reader slots) is not functioning.  So, after yoga, will take the machine to the bench, and get a working floppy so I can install the driver.  I am surprised that this bartPE boot failed, as I was under the impression that the OS was going to run solely from the CD and from there could analyze my raid situation.

Have fun!
0
 
jpaxtonsCommented:
Getting close.  Turns out Lee55J5's suggestion of a bad floppy drive was right on!  I had put a heftier Power supply in the box last month, and had mis connected the power to the floppy...fried the connecter...ooouuh cockpit error.  been through bartPE, but did not use, did windows install repair, and replaced a hard drive, Now working with command line edit of the registery,  I will post complete details and results tomorrow.
Thanks, all.

Have fun
Paxton
0
 
jpaxtonssAuthor Commented:
Greetings!
Replaced bad floppy drive
ran Windows xp Install disk , F6 added the ICH10R raid drivers
ran repair of existing installation

reboot, and now, shows one raid disk with errors  (same position as a disk replaced about 9 mos ago)

and continued to "The Login User Interface DLL  I:\WINDOWS\system32\awgina.dll failed to load"

replaced bad disk

now, BIOS shows "non-RAID member"
set to 'member' amd status changes to "Rebuild"  Says rebuilding completes in the OS

boots to :Windows xp Splash screen, then  "The Login User Interface DLL  I:\WINDOWS\system32\awgina.dll failed to load"

restart in safe mode  -  new disk now, not detected!

open case reseat disk cables (now suspecting bad or intermittend or marginal connector sata port) on motherboard)
RAID controller looks ok, all disks members, set to rebuild in OS
boot in safe mode with networking....  "The Login User Interface DLL  I:\WINDOWS\system32\awgina.dll failed to load"

reboot safe mode with command prompt....windows is starting up...got to command prompt!!  c:
(seems should be I:) the raid array... but is says Volume in Drive C is Ozma  (the name of the raid volume) which is also the machine name.
When I first installed the RAID10 array, it came up assigned to I:  I could not figure out why, so went ahead and used it that way
Now, apparently it is C:
Anyhow, at http://support.microsoft.com/kb/817142 it suggests Delete the GinaDLL registry entry.


Now that I have a command prompt, I learned how use REG command ( http://www.computerhope.com/reg.htm ) is good help

using REG QUERY I looked at the entry and found that it was pointing to drive I.  Since there is now no drive I, the load fails
Probably the problem from the beginning, somehow, the software RAID had changed to drive C from Drive I after the power failure.

Maybe dlethe could enlighten us on how that can happen. (attached is a report of the RAID now)

Deleting HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\WinLogon  GinaDLL
and reboot and came up normally.  But, of course since I had done an "Install Repair" all Windows updates are lost and still lots of pointers to I drive hanging around, so probably a day of clean up is required.  Interetingly MSIE8 would not connect to Windows update, so downloaded MSIE8 using Firefox, installed it and then could connect to update.micrsoft to begin the clean up task.

Thanks for all your help!

Have fun, Paxton
ReportR1.txt
0

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

  • 4
  • 4
  • 3
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now