We help IT Professionals succeed at work.

Stop Error on W2k3 with external sata harddisk

Theo
Theo asked
on
Medium Priority
630 Views
Last Modified: 2012-05-06
I am trying to connect an external harddisk (LaCie d2 Quadra) to my Windows 2003 SBS server which runs on a HP Proliant ML 115. I have installed a bracket, connected it to an internal sata connector and then connect that to the sata port on the drive. When I switch it on however I get a stop error:
event category 102
event id 1003
error code 1000007e
parameter 1 c0000005
parameter 2: f8485716
parameter 3: f889a900
parameter 4: f889a5fc

The computer then reboots, but the stop error comes always back unless I switch the drive off.

When I connect the drive to an USB-port it is recognized, then it searches for software which it cannot find and then never becomes available.

When I connect the drive through usb on a workstation It runs without problems.

How do I get this drive running on w2003?
Comment
Watch Question

CERTIFIED EXPERT
Most Valuable Expert 2015

Commented:
This is usually a driver problem. Look for *.dmp files on your server, zip the last 3 of them and upload them using the Link below:

http://www.ee-stuff.com/

Author

Commented:
Thanks, but what kind of dumps do you want. I have collected three dumps and they are together 350 mb (zipped) whereas the site you referred me to has a limit of 20 mb.

TR

CERTIFIED EXPERT
Most Valuable Expert 2015

Commented:
If they are that large, change the setting in Windows to create small memory dumps, and not full dumps. Then invoke the crash by connecting the external drive and zip those new dumps. You can change this setting via Control Panel, System, Advanced, Startup and Recovery - Settings, Write debugging information.

Author

Commented:
I have uploaded the files, yesterday (sunday). I hope you received them. The system asked for an identification of the question and I used the title for that.

Thanks

TR
CERTIFIED EXPERT
Most Valuable Expert 2015

Commented:
No, they don't seem to be there. Upload them again, then be sure to post a Link to them.
CERTIFIED EXPERT
Most Valuable Expert 2015

Commented:
Your crashes are being caused by partmgr.sys. Try updating that tool or disable it.

Author

Commented:
Right, that what the BSOD told me as well. Did you do something special or can I learn this for future BSOD's as well?

I'll try to update the file to a later version I found at MS and let you know.
Thx sofar.

Author

Commented:
Well I have tried both. I upgraded to a much newer version of the file and I disabled the Volume Shadow Copy Service that uses this file partmgr.sys. But it hardky makes a difference. before the bsod stayed on for a minute and then the system restarted constantly, now the system immediately restarts when I switch on the hd and does so continuously while showing a BSOD in a flash every time. The error message in the event log remains the same however. Although the BSOD stays on so short that I cannot verify whether partmgr.sys is involved this time.
Two recent dumps are here: http://www.richel.org/ee/Dmps2ThRichel.zip

Thanks
CERTIFIED EXPERT
Most Valuable Expert 2015

Commented:
It looks like the new version of the file isn't the correct one for your installed OS. Try running sfc /scannow and after that run windows updates.

Author

Commented:
Done that twice now and alas to no avail. The sfc program seems to start normally, asks for the Windows cd and then starts to compare, but at the end it just stops and disappears, no message about being finished or having done something. Went to Windows Update afterwards, but got no messages about new software being available. Meanwhile the partmgr.sys versions that I installed yesterday (and which was not the original version from Windows) was still there, so no restoration had taken place.
CERTIFIED EXPERT
Most Valuable Expert 2015

Commented:
That sounds strange. I'd start with testing the RAM and the HD's. Possibly a chkdsk x on all internal driveletters could also be a good thing, but depending on the disk size and number of errors it could take a long time. You'll find the tools like memtest86+ and the HD manufacturer's diagnostic utilities on the UBCD. If the hardware tests out OK, I'd consider a fresh windows installation.

http://ultimatebootcd.com

Author

Commented:
I will do that, but let me add some extra information.
* The LaCie external harddisk is recognized by the bios
* I have never been able to connect two USB printers (HP Deskjet and Dymo). They are recognized but the XP-drivers refuse to install ( I was told these should work with 2003 as well).

Just wanted to have said this.
Thanks sofar

Author

Commented:
Well no luck I have made three bootable cd's with different memtest progs that all run on other systems, but will not boot on that machine
CERTIFIED EXPERT
Most Valuable Expert 2015

Commented:
If that server also has a floppy drive, you can also get the floppy version of memtest86+ and boot from that. You could also try to use a powered USB hub between the server and the external HD. This can sometimes eliminate some power issues, particularly if you also had issues with other devices.

Author

Commented:
Yes, but the problem has worsened now. I removed one root hub in device manager. It didnt come back however. Scanning for hardware changes produced no results whatsoever. Then I removed another USB device in device manager. I couldnt restart the computer thereafter, got the error message that the Secuirity Account Manager failed to initiatlize ( Error 0xc00002e1. ) I am aware that there is a hotfix for this, but the only way I can get into my system is through the recovery console. Can I use that to copy the hotfix dll?
I cannot get in Directory Services Restore Mode.
I could install a a fresh copy of W2k3, but then I'd lose the entire domain wouldnt I?
 )

Author

Commented:
I have downloaded the hotfix now and seen that it ought to be possible to replace a dll with the recovery console. However: the hotfix contains two documents, both self extracting cabinets. One (from the 'Symbols-file)contains a ntds.pdb file, but the other (also a selft extracting cab-file that wants to start update.exe )  I dare not to open on a xp computer. I suppose the uypdate exe converts the .pdb file to a dll
CERTIFIED EXPERT
Most Valuable Expert 2015

Commented:
Why not run those patches on an XP box? Just be sure you have a backup or that box isn't essential.

Author

Commented:
OK I will do that. meanwhile I have verified that the original ntdsa.dll is still present, maybe it is corrupted though. I suppose I should just copy that file? (after renaming the old one?)
CERTIFIED EXPERT
Most Valuable Expert 2015

Commented:
Yes.

Author

Commented:
Well I am not lucky. I copied the new file, but now I have two error messages (and directory services still doesnt start.

Err message 1 is nr 0xc0000227 and the other comes from lsass.exe saying that the procedure entry point for DbUpdateBackupTimestamps (like that, one word) could not be found in ntdsa.dll

Author

Commented:
I ought to add: error nr 1 said Transaction recover failed and did also come from lsass.exe
CERTIFIED EXPERT
Most Valuable Expert 2015
Commented:
It looks more and more likea new installation and then restore from backup.

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts

Author

Commented:
Well there is no back up yet, that's what the new harddisk was for ;-), but noimportant data will be lost.

Author

Commented:
Had to rebuild the domain, but everything works now
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.