- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- event id 5 parity error
StoreEver Tape Storage
1752817
Members
4048
Online
108789
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-15-2003 10:27 AM
08-15-2003 10:27 AM
event id 5 parity error
I'm getting a parity error on my ML530 with an external hp sdlt1 160/320 tape driver. I have windows 2000 server sp3 installed. Additionally, the controller it's connected to is a compaq 64-bit ultra2 scsi contorller /p with the latest driver v5.24.0.0 from 11/12/2002. Here is the exact error: A parity error was detected on \Device\Scsi\Cpq32fs21.
I have had the tape drive replaced 3 times, the system board with builtin scsi controller replaced once, new scsi cable, new terminator, and updated/back dated drivers a few times.
I would like to get some insight into fixing this problem. I've found an artilce on adaptec's site about a parity error that is similar to what I'm experiencing. It says you will need to check the parity settings on the scsi controller and the tape drive. My question is are there parity settings for my tape drive and scsi controller. I can't find very good documentation on either on the hp website.
I've attached a copy of the error from the event log on my machine for reference. Thanks for your help.
-Russ
I have had the tape drive replaced 3 times, the system board with builtin scsi controller replaced once, new scsi cable, new terminator, and updated/back dated drivers a few times.
I would like to get some insight into fixing this problem. I've found an artilce on adaptec's site about a parity error that is similar to what I'm experiencing. It says you will need to check the parity settings on the scsi controller and the tape drive. My question is are there parity settings for my tape drive and scsi controller. I can't find very good documentation on either on the hp website.
I've attached a copy of the error from the event log on my machine for reference. Thanks for your help.
-Russ
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-18-2003 10:47 AM
08-18-2003 10:47 AM
Re: event id 5 parity error
Parity errors are almost never a software/driver problem and very rarely are due to hardware such as the tape drive or HBA.
Most of the time parity errors are caused by something wrong in the SCSI cabling. A frequent and often overlooked cause is too long of a cable or the wong type of cable. Also somewhat common is a bad terminator. Less common but still relatively common is some sort of interference problem. If the server and tape drive are attached to different UPS's there could be a voltage level difference. If there are any high emission electronics anywhere around the cable it can cause signal loss. If there are ferrite beads on the SCSI cables you can lose signal.
Hard to point to anything specific on a problem like this but hopefully this will give you some ideas where you might look.
Most of the time parity errors are caused by something wrong in the SCSI cabling. A frequent and often overlooked cause is too long of a cable or the wong type of cable. Also somewhat common is a bad terminator. Less common but still relatively common is some sort of interference problem. If the server and tape drive are attached to different UPS's there could be a voltage level difference. If there are any high emission electronics anywhere around the cable it can cause signal loss. If there are ferrite beads on the SCSI cables you can lose signal.
Hard to point to anything specific on a problem like this but hopefully this will give you some ideas where you might look.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP