Date: Tue, 22 Aug 2023 14:38:43 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 273292] ahcich: Message-ID: <bug-273292-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D273292 Bug ID: 273292 Summary: ahcich: Product: Base System Version: 13.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: misc Assignee: bugs@FreeBSD.org Reporter: radicleparticles@gmail.com Full OS release: 13.2-RELEASE-p2 Recently getting numerous ahcich related errors, some related to external S= ATA drives and latest apparently related to internal SATA drive. External: ada3:ahcich0:0:0:0): CAM status: Uncorrectable parity/CRC error (ada3:ahcich0:0:0:0): Retrying command, 3 more tries remain (ada3:ahcich0:0:0:0): WRITE_DMA48. ACB: 35 00 c0 15 67 40 1b 00 00 00 00 08 (ada3:ahcich0:0:0:0): CAM status: Uncorrectable parity/CRC error (ada3:ahcich0:0:0:0): Retrying command, 3 more tries remain ... [ada3: WDC WD3003FZEX-00Z4SA0] In some cases, the above error stream would end with an automatic HDD detachment. Replacing cable, detach/re-attach cable, use different HDD in enclosure: no= ne of these make any difference. These usually occur during large scale file copying. Internal: (aprobe0:ahcich3:0:0:0): CAM status: Uncorrectable parity/CRC error (aprobe0:ahcich3:0:0:0): Error 5, Retry was blocked (aprobe0:ahcich3:0:0:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 0= 0 00 (aprobe0:ahcich3:0:0:0): CAM status: Uncorrectable parity/CRC error (aprobe0:ahcich3:0:0:0): Error 5, Retry was blocked ada0 at ahcich3 bus 0 scbus3 target 0 lun 0 ada0: <WDC WD4500HLHX-01JJPV0 04.05G04> s/n WD-WX41E50J9764 detached (ada0:ahcich3:0:0:0): SETFEATURES ENABLE RCACHE. ACB: ef aa 00 00 00 40 00 = 00 00 00 00 00 (ada0:ahcich3:0:0:0): CAM status: Unconditionally Re-queue Request (ada0:ahcich3:0:0:0): Error 5, Periph was invalidated (ada0:ahcich3:0:0:0): Periph destroyed [ada0: WD4500HLHX-01JJPV0] This just recently "popped up out of nowhere" with drive unattached and not being used. Smart tests don't indicate any particular errors. Not been a problem under FBSD-13.1 or FBSD-12.4. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-273292-227>