Have hardware errors been logged by Windows?

Article:TECH128041  |  Created: 2010-01-26  |  Updated: 2013-10-29  |  Article URL http://www.symantec.com/docs/TECH128041
Article Type
Technical Solution

Product(s)

Environment

Issue



Have hardware errors been logged by Windows?


Solution



This report examines both the System and Application Event logs to determine if events with the following Event ID have been logged by Windows:

Hardware Errors:
 
  • Event ID 5: Signifies SCSI parity errors. This can be caused by a faulty SCSI card or faulty SCSI termination. If these errors occur, contact the hardware manufacturer.
  • Event ID 7: Signifies bad blocks. This could be the result of a outdated tape device driver issue, faulty media, or dirty read/write heads on the tape drive. Update to the latest Backup Exec Tape Device Drivers, run a cleaning job and replace the media with new media if possible. If the issue continues with new media, please contact the hardware vendor.
  • Event ID 9: Signifies SCSI bus timeouts. These errors usually occur when the SCSI bus resets itself, or the SCSI hardware does not respond in a timely fashion. Sometimes slowing the SCSI bus down can resolve these issues, as well as installing the latest SCSI drivers and firmware.  Another device on the same cable can cause the issue too.  In certain high end servers, moving the SCSI card to a different Peripheral Component Interconnect (PCI) slot, one that does not share the same bus as a RAID controller, has been known to fix these errors. If these errors occur, contact the hardware manufacturer.
  • Event ID 11: Signifies controller errors. These errors are generally caused by hardware that is not functioning correctly. Attempting to slow the SCSI bus down and verifying that the latest SCSI drivers and firmware are loaded can sometimes resolve these issues. If these errors occur, contact the hardware manufacturer.
  • Event ID 15: Signifies the device is not ready for access. These errors usually occur when the device is malfunctioning or configured incorrectly. They may also occur if the incorrect drivers are loaded, or the drivers are not up to date. If these errors occur, contact the hardware manufacturer.

Plug and Play Errors:
 
  • Event ID 271  |  Source "PlugPlayManager":  The Plug and Play operation cannot be completed because a device driver is preventing the device from stopping. The name of the device driver is listed as the vetoing service name below.
  • These often appear when power or connection to backup destination devices have problems, causing them to go offline or Windows to lose the ability to work with them.
  • In all other circumstances the controller connecting the device to the server may need to be examined or its drivers updated.  Contact the hardware manufacturer.
  • Event ID 12  |  Source "PlugPlayManager":  The device %Backup_Device% disappeared from the system without first being prepared for removal.
  • These often appear when power or connection to backup destination devices have problems, causing them to go offline or Windows to lose the ability to work with them.
  • In all other circumstances the controller connecting the device to the server may need to be examined or its drivers updated.  Contact the hardware manufacturer.

 
Delayed Write Failures:
 
  • Event ID 50: {Lost Delayed-Write Data} The system was attempting to transfer file data from Buffers to %Backup_Device%. The write operation failed, and only some of the data may have been written to the file.
  • These can occur during backup and copy operations to and from Fibre, Network, USB or local disks and devices.
  • Examine the device reported in the message to determine if cabling, controller or driver changes are needed.  Contact the hardware manufacturer for additional information.

For additional information regarding the impact of these errors with Backup Exec or Backup Exec System Recovery, please review the links under related documents, contact the hardware manufacturer or Microsoft.

 

Supplemental Materials

ValueV-370-59792-00021
Description

Have hardware errors been logged by Windows?



Legacy ID



347990


Article URL http://www.symantec.com/docs/TECH128041


Terms of use for this information are found in Legal Notices