Bug 196265 - SCSI sense hardware failure asc 3e,2 (timeout on logical unit)
Summary: SCSI sense hardware failure asc 3e,2 (timeout on logical unit)
Status: Closed Overcome By Events
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 10.1-STABLE
Hardware: amd64 Any
: --- Affects Only Me
Assignee: Bugmeister
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-25 12:07 UTC by m_josenhans
Modified: 2025-01-27 00:17 UTC (History)
2 users (show)

See Also:

Attachments
Boot screenshots taken from camera (866.61 KB, image/jpeg)
2014-12-25 12:07 UTC, m_josenhans 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description m_josenhans 2014-12-25 12:07:24 UTC 
Created attachment 150953 [details]
Boot screenshots taken from camera

After boot from freebsd cd 5 failures "SCSI sense hardware failure asc 3e,2 (timeout on logical unit)" occur, then however finally the cd boots from CD-ROM correctly.

See attached screenshots.
Comment 1 William Hooper 2015-10-23 03:29:15 UTC 
I experienced a similar problem while booting from either of two CD-R
discs onto which I'd recorded FreeBSD-10.2-RELEASE-amd64-disc1.iso.

As in the original report, the boot process eventually continued on its 
own, after several sets of console messages like these: 

(cd0:ahcich1:0:0:0): Retrying command (per sense data)
(cd0:ahcich1:0:0:0): READ(10). CDB: 28 00 00 05 65 84 00 00 01 00
(cd0:ahcich1:0:0:0): CAM status: SCSI Status Error
(cd0:ahcich1:0:0:0): SCSI status: Check Condition
(cd0:ahcich1:0:0:0): SCSI sense: HARDWARE FAILURE asc:3e,2 (Timeout on logical unit)
(cd0:ahcich1:0:0:0): Error 5, Retries exhausted
(cd0:ahcich1:0:0:0): cddone: got error 0x5 back

The computer was a Dell Latitude E6420 notebook, with BIOS revision A21
and a TSSTcorp DVD+-RW TS-U633J drive, revision D800 KIN.
Comment 2 Mark Linimon freebsd_committer freebsd_triage 2025-01-26 21:29:14 UTC 
^Triage: I'm sorry that this PR did not get addressed in a timely fashion.

By now, the version that it was created against is long out of support.
Please re-open if it is still a problem on a supported version.
Comment 3 Warner Losh freebsd_committer freebsd_triage 2025-01-26 22:21:56 UTC 
We've done a fair amount of work to make these kinds of errors fail faster, so I think it may be fixed in at least 15-current (which I hope to merge to 14 before its next minor release). If you still have this hardware, please give this a shot. I don't have any more laptops with a CD drive in them, so I can't test it locally.
Comment 4 William Hooper 2025-01-27 00:17:21 UTC 
Thanks for the update. Unfortunately I no longer have the hardware I
mentioned in 2015 or anything like it, so I wouldn't be able to test.