Last night our Sun Solaris server backup failed. Backup data is sent to a tape drive everynight.
I looked at the logs today (/var/adm/messages) and I have this:
Sep 12 00:17:50 mint unix: WARNING: ID[SUNWpd.glm.parity_check.6010]
Sep 12 00:17:50 mint unix: WARNING: /pci@1f,4000/scsi@3,1 (glm1):
Sep 12 00:17:50 mint SCSI bus DATA IN phase parity error
Sep 12 00:17:50 mint unix: WARNING: ID[SUNWpd.glm.parity_check.6010]
Sep 12 00:17:50 mint unix: WARNING: /pci@1f,4000/scsi@3,1 (glm1):
Sep 12 00:17:50 mint SCSI bus DATA IN phase parity error
Sep 12 00:17:50 mint unix: WARNING: ID[SUNWpd.glm.parity_check.6010]
Sep 12 00:17:50 mint unix: WARNING: /pci@1f,4000/scsi@3,1 (glm1):
Sep 12 00:17:50 mint SCSI bus DATA IN phase parity error
I have this hundreds and hundres of times until it decided to timeout.
I dont know much about solaris or unix for that matter. What does this error mean?
Could it be as simple as the tape deivce name in our backup script being incorrect [we have confusion over this in the past here] or does this erro suggest something more serious?
Hopefully this is the right forum to post in.
I looked at the logs today (/var/adm/messages) and I have this:
Sep 12 00:17:50 mint unix: WARNING: ID[SUNWpd.glm.parity_check.6010]
Sep 12 00:17:50 mint unix: WARNING: /pci@1f,4000/scsi@3,1 (glm1):
Sep 12 00:17:50 mint SCSI bus DATA IN phase parity error
Sep 12 00:17:50 mint unix: WARNING: ID[SUNWpd.glm.parity_check.6010]
Sep 12 00:17:50 mint unix: WARNING: /pci@1f,4000/scsi@3,1 (glm1):
Sep 12 00:17:50 mint SCSI bus DATA IN phase parity error
Sep 12 00:17:50 mint unix: WARNING: ID[SUNWpd.glm.parity_check.6010]
Sep 12 00:17:50 mint unix: WARNING: /pci@1f,4000/scsi@3,1 (glm1):
Sep 12 00:17:50 mint SCSI bus DATA IN phase parity error
I have this hundreds and hundres of times until it decided to timeout.
I dont know much about solaris or unix for that matter. What does this error mean?
Could it be as simple as the tape deivce name in our backup script being incorrect [we have confusion over this in the past here] or does this erro suggest something more serious?
Hopefully this is the right forum to post in.