| Summary: | Kernel error "Unhandled error code" from hard disk | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | D. Wagner <daw-redhatbugzilla> | ||||||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||||
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 14 | CC: | aquini, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2011-08-24 18:49:17 UTC | Type: | --- | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Attachments: |
|
||||||||||||
Created attachment 503723 [details]
Excerpt from /var/log/messages from when the bug occurred
Created attachment 503724 [details]
Output from hdparm -v
Created attachment 503725 [details]
Output from smartctl -a /dev/sdb
Have you seen this again? No, I haven't seen it again. We'll close this out. If it happens on a current kernel, please reopen. |
Created attachment 503722 [details] Excerpt from dmesg when the error occurred Description of problem: My system recently "froze" after receiving the following error message in my dmesg logs: [1805302.253343] sd 4:0:0:0: [sdb] Unhandled error code [1805302.253347] sd 4:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_TIMEOUT [1805302.253352] sd 4:0:0:0: [sdb] CDB: Write(10): 2a 00 00 89 12 eb 00 00 10 00 [1805302.253365] end_request: I/O error, dev sdb, sector 8983275 [1805302.253389] Aborting journal on device sdb3. [1805302.253623] __journal_remove_journal_head: freeing b_committed_data [1805302.254189] EXT3-fs (sdb3): error: ext3_journal_start_sb: Detected aborted journal [1805302.254195] EXT3-fs (sdb3): error: remounting filesystem read-only ... The filesystem then got mounted read-only and I had to reboot (and manually fsck). I suspect this might have been triggered by running a daily (automatically scheduled) SMART selftest, but I'm not sure. I'm attaching excerpts from dmesg and /var/log/messages when it occurred, as well as other information about my machine. Version-Release number of selected component (if applicable): kernel-2.6.35.13-91.fc14.x86_64 How reproducible: It has happened once before, but I don't know how to force it to occur.