System defekt nach Netzteilausfall?!

[Hunduster]

Tag zusammen,

gestern morgen ist das Netzteil meines Server durchgeknallt. Habe es direkt gegen ein neues ersetzt allerdings habe ich nun mehrere Probleme.

Es handelt sich hier um einen Windows Server 2003 R2 x64 Standard Edition.

Seid dem Ausfall findet er 3 IDE Platten nicht mehr. Im Bios werden sie angezeigt aber nicht im System. Weiterhin bekomm ich immer den Fehler Generic Host Process hat einen Fehler ermittelt und musste beendet werden. Auch mein AVK bekomm ich nicht mehr gestartet.

Dann habe ich nun mal vom Erd Commander gestartet und er bekommt auch keine Systeminformationen aufgerufen. Rödelt nur wie blöd.

Was denkt ihr? Hardware defekt (Mainboard Systemplatte etc?) oder kann das System wirklich durch den kanll des Netzteiles einen mitbekommen haben?

Nachtrag: Der Erd Commander konnte die Informationen nun ermitteln und auch die Platten anzeigen. Allerdings zeigt er mir von der Systemplatte nur eine Partition anstatt 2.

[mamamia]

Servus.. Hört sich sehr nach dem Mainboard an.

Du kannst die einzelnen Komponenten wie RAM und die 3 Platten ja mal in einem anderen System prüfen.

Kann schon möglich sein, dass dein Board eine Spannungsspitze abbekommen hat.

Hast du nen anderen Rechner vor Ort zum testen? Wenn ja, dann mach..

[Hunduster]

Leider hab ich keinen Rechner wo die Komponenten reinpassen würden. Die Kisten die ich hier stehen habe sind alle was älter. Und ich selber arbeite an einem Notebook. Aber wenn das Mainboard einen an der Klatsche hat dann dürfte er mir doch auch die PLatten im Bios nicht anzeigen oder?!

[geloescht_Fisi_Markus]

sind die IDE dynamische oder Basisdatenträger?

[Hunduster]

Die IDE sind alles Basisdatenträger also nur NTFS mit Daten drauf

Die Systemplatte ist eine S-ATA Platte

[Hunduster]

Also die 2. Partiton der Systemplatte wird doch angezeigt wurde unter einem anderen Buchstaben gemounten (Ich rede vom Erd Commander), mein Fehler. Aber die anderen Fehler bestehen weiterhin.

[mamamia]

Mach am besten mal nen Image von deinem System, bevor sich das komplett zerschießt.

Ne Reperaturinstallation kannste dann auch noch evtl durchführen lassen.

Haste mal nen Systemcheck unabhängig vom Windows gestartet (BartsPE oä)

Vllt iss durch den Systemcrash auch was am Windows kaputtgegangen.. Eventlog?

[geloescht_Fisi_Markus]

da hat mamamia recht!

hatte mal so einen fall auf einem laptop..

habe dann die HD auf ne andere mit trueima geklont, dieser cloe war dann lauffähig...

[Hunduster]

Einen Systemcheck habe ich noch nicht durchgeführt da ich grad nichts passendes zur hand habe.

Im EventLog stehen 2 Dinge:

SPTD Error

Event ID: 4

Driver detected an internal error in it's data structures for .

Disk Warning

Event ID: 51

An Error was detected on device during a paging operation

[geloescht_Fisi_Markus]

welches eventlog??

[Hunduster]

Vom System

[geloescht_Fisi_Markus]

ok, ddann brauche ich jetzt noch die quelle

die steht beim eintrag oben rechts

[Hunduster]

Bei dem SPTD Error ist Source: SPTD

Bei dem Disk Warning Source: Disk

[geloescht_Fisi_Markus]

zur id 4

In one case, according to a newsgroup post, this event was related to Deamon Tools and a security update from Microsoft. Apparently, uninstalling M914784 will solve the problem. Just go to add/remove programs, check the box at the top that says show updates, find the M914784 update and remove it.

zur 51

Glauber (Last update 3/11/2007):

From a newsgroup post: "A Buggy NForce SATA driver caused the problem. Disabling Native Command Queuing (NCQ) in the Nvidia SATA driver resolved it". See the link to "Abit Forum Thread" for some other useful information.

Anonymous (Last update 9/27/2006):

In my case, going to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\PrefetchParameters" and setting the value for "EnablePrefetcher" to 1 solved the problem.

Gavin Seabrook (Last update 7/26/2006):

In my case, the games were randomly shutting down and sometimes window pop-ups occurred saying Delayed Write Failure. There was a problem with my MFT (Master File Table) file. Using the program "Diskeeper", I changed its size (creating a new one). Note: you need to use the Diskeeper Professional version (There is a trial for it available). Since then I have not had any more problems with games shutting down or files being lost.

See M174619 and M227350 for information about the Master File Table.

Dave Murphy (Last update 5/23/2006):

In testing a new configuration on our terminal servers, we ran into this error under moderate user load. We started with two brand new servers with 8GB of RAM, using Windows 2003 Enterprise Server. We used the "/PAE" and the "/3GB" switches on the server to increase available memory to 8GB. The paging file was set to anywhere from 2048 to 4096. At one point, we let the server set the paging file at a whopping 8000 MB. The paging activity increased so much that it caused disk thrashing on the server and these errors were logged. The server would then slow to a crawl and more or less had to be rebooted. After removing the "/PAE" and the "/3GB" switches, the error has not been encountered under similar user loads. Rather than using the full 8GB of RAM, we put the RAM into 4GB with mirroring instead.

MÃ¥rten Edelbrink (Last update 4/17/2006):

I received this error along with EventID 50 from source Ntfs (and EventID 11 from source disk and EventID 5 from source atapi), when I had the paging file and my virtual disks on the same physical disk. When I moved the paging file to another disk the errors stopped.

Mihai Andrei (Last update 2/9/2006):

This event may occur when you try to write data to a Serial Bus Protocol 2 (SBP-2) device, such as an IEEE (Institute of Electrical and Electronics Engineers) 1394 drive. See M885464 for a hotfix applicable to Microsoft Windows XP.

See "Dell Support Document Number: TT1091520" and "Dell Support Document Number: TT1091518" for additional information about this event.

Ionut Marin (Last update 8/16/2005):

As per Microsoft: "An input/output (I/O) request to a memory-mapped file failed and the operation was retried. If these events are logged regularly on a primary system drive, replace the device. Otherwise, no user action is required". See MSW2KDB for more details on this event.

This event may appear if you have a Windows server booting from a Storage Area Network (SAN). See M305547 for more detailed information.

As per Microsoft: "This problem occurs if an Input/Output (I/O) operation to a hard disk is unsuccessful. When an I/O operation to a hard disk is unsuccessful, Windows Server 2003 logs Event ID 51 in the system log. This problem occurs even if the I/O operation is retried and is subsequently successful". See M834910 for a hotfix.

As per Microsoft: "This problem occurs if you have installed one or more storage devices that do not support cache commands. The Windows 2000 SP4 Disk.sys driver writes many events to the system log when it performs write operations to a storage device that does not support cache commands". See M830051 for a hotfix.

From a newsgroup post: "If you have Intel's Application Accelerator installed this is what can cause the error. I have found that it is a false detection and it is nothing to you should worry about. I read it on Intel's web site. I get this error sometimes but it never causes any problems".

See M835473 for additional information on this event.

Al Marklin (Last update 11/8/2004):

This error is generated along with EventID 32 from source Disk (and erroneously error 34), when Windows 2000 SP4 is installed in a system with and Iomega Zip 250. I have tracked this for several months without loss of data, and it appears to be spurious though it does fill up the System log.

From M324916: "The Iomega Zip 250 drive does not support requests by the operating system to turn off write caching. Because of this, an Event ID 32 warning is logged in the event log. This warning is by design. Event ID 34s are then incorrectly generated in the event log every time you start your computer, although they are supposed to be Event ID 32s".

Per Ionut Marin's comment: "The Windows 2000 SP4 Disk.sys driver writes many events to the system log when it performs write operations to a storage device that does not support cache commands. See M830051 for a hotfix".

Anonymous (Last update 8/19/2004):

To fix this problem I disabled the “Write cache†feature on my disk. To do this go to Device Manager -> Disk Drives, right click on your disk and choose Properties. Here you can disable this feature.

Mashiki (Last update 6/27/2004):

Intel's Application Accelerator does seem to cause, the event ID 51 in many instances. The best advice is to troubleshoot the actual code in each instance (see M244780). I have now seen this in many computers, those I have built and my own. This code does seem to come up in all of them; they all use the chipset I845 or I850. Only with the most recent driver release from Intel (2.3.0.2160) does this happen. The drives and memory are fine. The specific code in each case is a 0x40 SRB_STATUS_QUEUE_FROZEN, I believe it’s an error in the IAA driver itself. Removing the IAA, removes the problem in each instance.

Michael Papalabrou (Last update 5/17/2004):

If this disk is your system disk or a disk that contains sensitive data, consider taking regular backups and/or replacing this disk as soon as possible. It will fail soon. In my system it started generating errors, it had degraded performance and it failed a month later.

Captain Fizz (Last update 2/9/2004):

I had the same message due to a faulty HDD.

Anonymous (Last update 10/15/2003):

I was burning a cd with Nero Burning Rom 6 + data verification. The data verification did freeze near 97%, and after 3 minutes I aborted the process and the event log reported this warning.

Adrian Grigorof (Last update 8/2/2003):

This event may be recorded when a digital camera is attached to the system to transfer images from its internal hard drive to the computer. If the camera's batteries run out of power during this process one of the effects is the recording of this message. An example of device reported in such cases is "\Device\Harddisk2\DR10" - and it is the footprint of an IBM SmartMedia hard drive.

Ron Glaister (Last update 5/9/2003):

This will also occur on a Windows 2000 server connected to a compaq EMA SAN (HSG80s) utilizing triple-mirroring. When the "Broken" mirror set is inserted back into the SAN for remirroring, you will see this occur. Compaq claims this is entirely normal and from my end, has occurred since it was installed and has never affected anything.

Kmex

This event occurs when multiple clusters that are attached to the same storage subsystem are not configured properly. See M304415 and M311081 links.

Brian Soegaard (AKA Cerw)

According to Microsoft, this error can be hardware related. See the information provided for event 9 and 11.

Pablo Rivera

On a Windows 2000 server, this error could be caused when a process is taking a long time to process data on the partition that holds the page file. Processes like a scheduled virus scan on all partitions, a file backup procedure, or just by having the page file on a fragmented and heavily utilized partition that has little free space.

If the error only happens at the same time as one of the above scheduled tasks, you may not need to worry, as long as it goes away after the task is done and the page file returns to normal.

Check Microsoft articles M123747 and M197379 to learn more about page file and performance.

Anonymous

See M244780.

Quelle: eventid.net

[mamamia]

Hey Markus, nen Link hätts doch auch getan :D

[Hunduster]

Also ich habe jetzt erstmal 2 Programme runter geschmissen die ich kürzlich drauf gespielt hatte. Darunter auch Deamon Tools welches ich installiert hatte da mein Server kein optisches Laufwerk eingebaut hat. Nun läuft er wieder. Ich werde das ganze jetzt erstaml beobachten.

Das Security Update M914784 ist bei mir nicht installiert.

[geloescht_Fisi_Markus]

na siehste...

[Hunduster]

Leider nein... Hat mittendrin wieder die Platten verloren hab nun 3 mal neugestartet ohne das er sie bisher wieder gefunden hat. Er findet immer nur die gleiche; die sata Systemplatte und die 500er IDE

[geloescht_Fisi_Markus]

ok...

wenn genug platten hast clone das system 1. als sicherung und 2. als arbeitskopie mit der testen kannst...

wenn die arbeitskopie kaputtgeht hast noch immer die sicherung.. und das system bleibt unberührt..

noch ein tipp zum clonen, nicht startende systeme lassen sich meist NICHT mit GHOST clonen, also bitte Trueimage nehmen