Data In Phase Parity Error
Contents |
too longNext: SCSI transport failed: reason 'reset'SCSI bus DATA IN phase parity
Parity Error Detection
error 原因 この障害が発生する最大の原因は、動作確認されていないのハードウェアにあります。PC 市場に出回っている SCSI デバイスの中には、UNIX 市場の製品に求められる高速入出力の要件を満たしていないものがあります。また、他の原因として、配線または終端の設定が不適切、電力が不安定といったことも考えられます。このパリティエラーがあるとデータ転送は行われないため、データが損傷している可能性は低くなります。 対処方法 バス上のすべての SCSI デバイスがサンの動作確認されたハードウェアであることを確認します。次に、すべてのケーブルの合計が 6 メートル未満であり、すべての SCSI 接続部が正しく終端されていることを確認します。電力が不安定な場合は、無停電電源装置を取り付けてください。 Previous: save: SYSTEM error, Arg list too longNext: SCSI transport failed: reason 'reset' © 2010, Oracle Corporation and/or its affiliates
having exposure on VXVM, Clustering, Virtualization etc.,. If you find something useful, a comment would be appreciated to let other viewers also know that the solution/method work(ed) for you. Friday, December 13, 2013 SCSI bus DATA nmi parity error IN phase parity error CauseThe most common cause of this problem is unapproved hardware. Some
Pci Parity Error
SCSIdevices for the PC market do not meet the high I/O speed requirements for theUNIX market. Other possible causes of this problem parity error 4x4 are improper cabling ortermination, and power fluctuations. Data corruption is possible, but unlikely tooccur, because this parity error prevents data transfer.ActionCheck that all SCSI devices on the bus are Sun-approved hardware. Then verify thatall cables measure https://docs.oracle.com/cd/E19455-01/806-2720/msgs-741/index.html no longer than six meters total and that all SCSI connections areproperly terminated. If power fluctuations are occurring, invest in an uninterruptiblepower supply. SCSI transport failed: reason 'reset' CauseThis message indicates that the system sent data over the SCSI bus, but the datanever reached its destination because of a SCSI bus reset. The most common cause ofthis condition is conflicting SCSI targets. Data corruption is possible, but unlikely tooccur, because this failure http://schalwad.blogspot.com/2013/12/scsi-bus-data-in-phase-parity-error.html prevents data transfer.ActionVerify that all cables measure no longer than six meters total and that all SCSIconnections are properly terminated. If power surges are a problem, acquire a surgesuppressor or an uninterruptible power supply.A machine's internal disk drive is usually SCSI target 3. Make sure that external andsecondary disk drives are targeted to 1, 2, or 0, and do not conflict with each other.Also, make sure that tape drives are targeted to 4 or 5, and CD drives to 6, avoidingany conflict with each other or with disk drives. If the targeting of the internal diskdrive is in question, power off the machine, remove all external drives, turn on thepower, and from the PROM monitor run the probe-scsi-all or probe-scsicommand.If SCSI device targeting is acceptable, memory configuration could be the problem.Ensure that high-capacity memory chips (such as 4-Mbyte SIMMs) are in lowerbanks, while lower-capacity memory chips (such as 1-Mbyte SIMMs) are in theupper banks.SPARC systems do not always support third-party CD-ROM drives, and cangenerate a similar unknown vendor error message. Check with the CD-ROMvendor for specific configuration requirements.Some third-party disk drives have a read-ahead cache that interferes with the Solarisdevice drivers. Make sure that any existing read-ahead cache facility is turned off. Posted by santosh chalwad at 4:09 PM Reactions: Email ThisBlogThis!Share to TwitterShare to Face
IP isWhoisCalculatorTool PointsNewsNews tip?ForumsAll ForumsHot TopicsGalleryInfoHardwareAll FAQsSite FAQDSL FAQCable TechAboutcontactabout uscommunityISP FAQAdd ISPISP Ind. ForumsJoin Search similar:Raid 5 troublesModem Losing Connection to Router every day/couple of daysRaid 5 "degraded" driveESXi 5.1 will not see new RAID0... Forums → Software and Operating Systems → Unix http://www.dslreports.com/forum/r5132752-Is-there-a-way-to-fix-this and Linux → Is there a way to fix this.. uniqs413 Share http://www.verycomputer.com/39_77df1e7191170db3_1.htm « Mandrake 9 Theme/Style permission • Konquer crashes on hidden files opening/seach: » TaoronI Fly the FlagPremium Memberjoin:2000-10-22Apopka, FL Taoron Premium Member 2002-Nov-26 11:56 am Is there a way to fix this..WARNING: /pci@8,700000/scsi@1 (glm2): SCSI bus DATA IN phase parity errorWARNING: /pci@8,700000/scsi@1 (glm2): SCSI bus DATA IN phase parity error parity errorWARNING: /pci@8,700000/scsi@1 (glm2): SCSI bus DATA IN phase parity errorWARNING: /pci@8,700000/scsi@1 (glm2): SCSI bus DATA IN phase parity errorWARNING: /pci@8,700000/scsi@1 (glm2): SCSI bus DATA IN phase parity errorWARNING: /pci@8,700000/scsi@1 (glm2): SCSI bus DATA IN phase parity errorWARNING: /pci@8,700000/scsi@1 (glm2): SCSI bus DATA IN phase parity errorWARNING: /pci@8,700000/scsi@1 (glm2): SCSI bus DATA IN phase parity errorWARNING: /pci@8,700000/scsi@1 (glm2): SCSI bus data in phase DATA IN phase parity errorWARNING: /pci@8,700000/scsi@1 (glm2): SCSI bus DATA IN phase parity errorOr am I screwed? This is a Sun Sparc running Solaris 8, and 2 SCSI drives.. but only one of them contain data (not RAID 1 yet) · actions · 2002-Nov-26 11:56 am · shdesignsPowered By Infinite Improbabilty DrivePremium Memberjoin:2000-12-01Stone Mountain, GAkudos:1 shdesigns Premium Member 2002-Nov-26 12:06 pm Do you have a terminator installed or termination on only the last drive? · actions · 2002-Nov-26 12:06 pm · TaoronI Fly the FlagPremium Memberjoin:2000-10-22Apopka, FL Taoron Premium Member 2002-Nov-26 12:10 pm said by shdesigns:Do you have a terminator installed or termination on only the last drive? I'm sure these drives are already terminated. They are internal to the Sunfire 280R.It requested that I do a manual fschk and I did that.. did a reboot and got these parity errors. · actions · 2002-Nov-26 12:10 pm · DA OHDo, Or Do Not. There Is No 'try'.join:2002-01-07Denver, CO DA OH to Taoron Member 2002-Nov-26 1:47 pm to Taoronsaid by www.sunsolve.sun.com:If the messages look like this:Mar 24 06:58:10
Sun systems operational, and i've currently got an SS2 booting to the point where it reads in the image and starts to run thru the device-list ... it correctly identifies the two attached disks, and then the following starts spewing out: esp0: SCSI bus DATA IN phase parity error sd0a: Error for command "read" sd0a: Error level: Retryable sd0a: Block 64, Absolute Block 106 sd0a: Sense key: Aborted Command sd0a: vendor 'CDC' error code 0x48 Can anyone tell me what this is saying? The fact that the kernel can be read off of the disk in the first place would seem to argue against there being an absolute problem with "reading", wouldn't it? i happen to know there's another root, for a SS1+, on the other disk, but when i try to boot it up just for yucks, i get exactly the same thing reported from sd1a but with different blocks, as might be expected. Still, *both* disks Going South at the same time? AND i recall now that i *can* successfully boot the SS1+ kernel when the disk that has the SS2 kernel isn't attached. One other screwy thing: when i power on the disk boxes, the SS2-kernel disk doesn't spin up until i unplug the SCSI cable, then it spins up, i reattach the cable, and what i described above ensues. i pulled both disk and cartridge-tape out of the original box and stuck them into a spare, thinking it might be the SCSI connector on the box, but now i'm starting to wonder if it's either the disk itself, or the tape. Does any of this sound familiar to anyone? Thanks, folks. doug -- dr _|_)oug USmail: Sci.Comp.Support/Cornell Theory Center (_| 737 Rhodes Hall/C.U./Ithaca/N.Y./14853-3801 (_|__ MaBelle: 607-254-8686 Fax: 607-254-8888 | MOOs: doug/DougE/Strider/Dun'a'dan Top SS2 boot problem -- "SCSI bus DATA IN phase parity error" by George Robbi » Sat, 20 Sep 1997 04:00:00 >G'day ... >i'm trying to get some legacy Sun systems operational, and i've >currently got an SS2 booting to the point where it reads in the image >and starts to run thru the device-list ... it correctly identifies the >two attached disks, and then the following starts spewing out: >esp0: SCSI b