[Bug 1092883] Re: Disk report of Unhandled error code
James Harris, this would be a clear cut case of HDD failure, with your log substantiating this: end_request: I/O error, dev sde, sector 1857458688 There is no more simplifying it, or changing the log output, I/O error is I/O error. You are welcome to use Checkbox as noted in https://help.ubuntu.com/community/Checkbox to further substantiate this, but it would just be confirming what is known already. Please feel free to report any future bugs you may find. ** Changed in: linux (Ubuntu) Importance: Medium = Wishlist ** Changed in: linux (Ubuntu) Status: Confirmed = Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1092883 Title: Disk report of Unhandled error code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1092883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1092883] Re: Disk report of Unhandled error code
** Description changed:
Repeated message such as
Dec 21 10:56:03 s01 kernel: [12597.472089] sd 8:0:0:0: [sde] Unhandled error
code
Dec 21 10:56:03 s01 kernel: [12597.472093] sd 8:0:0:0: [sde] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec 21 10:56:03 s01 kernel: [12597.472098] sd 8:0:0:0: [sde] CDB: Read(10):
28 00 6e b6 92 00 00 02 00 00
Dec 21 10:56:03 s01 kernel: [12597.472113] end_request: I/O error, dev sde,
sector 1857458688
Once this occurs it is reported a number of times per second apparently
on a continuous basis. The sector number does increase but I'm not sure
whether the disk driver is really trying to access the disk.
To show the above log entries in context here are a few lines before
them and a few after.
Dec 21 10:55:03 s01 kernel: [12537.438622] ata9.00: exception Emask 0x10 SAct
0x1 SErr 0x8 action 0xe frozen
Dec 21 10:55:03 s01 kernel: [12537.438628] ata9.00: irq_stat 0x00100010, PHY
RDY changed
Dec 21 10:55:03 s01 kernel: [12537.438633] ata9: SError: { 10B8B }
Dec 21 10:55:03 s01 kernel: [12537.438638] ata9.00: failed command: READ
FPDMA QUEUED
Dec 21 10:55:03 s01 kernel: [12537.438646] ata9.00: cmd
60/00:00:00:92:b6/02:00:6e:00:00/40 tag 0 ncq 262144 in
Dec 21 10:55:03 s01 kernel: [12537.438648] res
f2/36:00:00:00:00/00:00:00:01:f2/00 Emask 0x12 (ATA bus error)
Dec 21 10:55:03 s01 kernel: [12537.438652] ata9.00: status: { Busy }
Dec 21 10:55:03 s01 kernel: [12537.438655] ata9.00: error: { IDNF ABRT }
Dec 21 10:55:03 s01 kernel: [12537.438662] ata9: hard resetting link
Dec 21 10:55:13 s01 kernel: [12547.444041] ata9: softreset failed (timeout)
Dec 21 10:55:13 s01 kernel: [12547.444048] ata9: hard resetting link
Dec 21 10:55:23 s01 kernel: [12557.456048] ata9: softreset failed (timeout)
Dec 21 10:55:23 s01 kernel: [12557.456055] ata9: hard resetting link
Dec 21 10:55:58 s01 kernel: [12592.460049] ata9: softreset failed (timeout)
Dec 21 10:55:58 s01 kernel: [12592.460057] ata9: limiting SATA link speed to
1.5 Gbps
Dec 21 10:55:58 s01 kernel: [12592.460061] ata9: hard resetting link
Dec 21 10:56:03 s01 kernel: [12597.472038] ata9: softreset failed (timeout)
Dec 21 10:56:03 s01 kernel: [12597.472046] ata9: reset failed, giving up
Dec 21 10:56:03 s01 kernel: [12597.472050] ata9.00: disabled
Dec 21 10:56:03 s01 kernel: [12597.472064] ata9: EH complete
Dec 21 10:56:03 s01 kernel: [12597.472089] sd 8:0:0:0: [sde] Unhandled error
code
Dec 21 10:56:03 s01 kernel: [12597.472093] sd 8:0:0:0: [sde] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec 21 10:56:03 s01 kernel: [12597.472098] sd 8:0:0:0: [sde] CDB: Read(10):
28 00 6e b6 92 00 00 02 00 00
Dec 21 10:56:03 s01 kernel: [12597.472113] end_request: I/O error, dev sde,
sector 1857458688
Dec 21 10:56:03 s01 kernel: [12597.472250] sd 8:0:0:0: [sde] Unhandled error
code
Dec 21 10:56:03 s01 kernel: [12597.472254] sd 8:0:0:0: [sde] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec 21 10:56:03 s01 kernel: [12597.472258] sd 8:0:0:0: [sde] CDB: Read(10):
28 00 6e b6 92 00 00 00 08 00
Dec 21 10:56:03 s01 kernel: [12597.472271] end_request: I/O error, dev sde,
sector 1857458688
Dec 21 10:56:03 s01 kernel: [12597.472378] sd 8:0:0:0: [sde] Unhandled error
code
Dec 21 10:56:03 s01 kernel: [12597.472381] sd 8:0:0:0: [sde] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec 21 10:56:03 s01 kernel: [12597.472386] sd 8:0:0:0: [sde] CDB: Read(10):
28 00 6e b6 92 08 00 00 08 00
Dec 21 10:56:03 s01 kernel: [12597.472398] end_request: I/O error, dev sde,
sector 1857458696
Dec 21 10:56:03 s01 kernel: [12597.473888] sd 8:0:0:0: [sde] Unhandled error
code
Dec 21 10:56:03 s01 kernel: [12597.473891] sd 8:0:0:0: [sde] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec 21 10:56:03 s01 kernel: [12597.473896] sd 8:0:0:0: [sde] CDB: Read(10):
28 00 6e b6 92 10 00 00 08 00
Dec 21 10:56:03 s01 kernel: [12597.473910] end_request: I/O error, dev sde,
sector 1857458704
Dec 21 10:56:03 s01 kernel: [12597.473953] sd 8:0:0:0: [sde] Unhandled error
code
Dec 21 10:56:03 s01 kernel: [12597.473957] sd 8:0:0:0: [sde] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec 21 10:56:03 s01 kernel: [12597.473962] sd 8:0:0:0: [sde] CDB: Read(10):
28 00 6e b6 92 18 00 00 08 00
Dec 21 10:56:03 s01 kernel: [12597.473976] end_request: I/O error, dev sde,
sector 1857458712
Dec 21 10:56:03 s01 kernel: [12597.474014] sd 8:0:0:0: [sde] Unhandled error
code
Dec 21 10:56:03 s01 kernel: [12597.474017] sd 8:0:0:0: [sde] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec 21 10:56:03 s01 kernel: [12597.474022] sd 8:0:0:0: [sde] CDB: Read(10):
28 00 6e b6 92 20 00 00 08 00
Dec 21 10:56:03 s01 kernel: [12597.474035] end_request: I/O error, dev sde,
sector 1857458720
Dec 21 10:56:03 s01 kernel: [12597.474073] sd 8:0:0:0: [sde] Unhandled error
code
Dec 21 10:56:03 s01 kernel: [12597.474087]
[Bug 1092883] Re: Disk report of Unhandled error code
** Tags added: bios-outdated needs-upstream-testing regression-potential -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1092883 Title: Disk report of Unhandled error code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1092883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1092883] Re: Disk report of Unhandled error code
The issue occurred again. Will try to make some sense of it. Whatever is causing the initial failure of access to one of the disks, when the error occurs the kernel or driver subsystem seems to go into an infinite loop (or a number of infinite loops - see below). Even if the disk is pulled from the machine (SATA, hot swap) the kernel continues to emit the error messages and does not recognise removal of the device. After the kernel reports: Jan 29 22:17:15 s01 kernel: [772716.664170] ata9.00: disabled Jan 29 22:17:15 s01 kernel: [772716.664176] ata9: EH complete it then starts what seem to be a number of loops - possibly because there are different disk requests outstanding (but that is just a guess) - each reporting: Jan 29 22:17:15 s01 kernel: [772716.664204] sd 8:0:0:0: [sdg] Unhandled error code Jan 29 22:17:15 s01 kernel: [772716.664207] sd 8:0:0:0: [sdg] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK Here are some examples of lines that were reported thousands of times (about 70 reports per second) until the machine was rebooted. Jan 29 22:17:15 s01 kernel: [772716.664331] end_request: I/O error, dev sdg, sector 4096 Jan 29 22:17:15 s01 kernel: [772716.672247] end_request: I/O error, dev sdg, sector 3388584944 Both of the above were always to the same sector. Jan 29 22:17:15 s01 kernel: [772716.685014] EXT2-fs (sdg2): error: read_block_bitmap: Cannot read block bitmap - block_group = 12926, block_bitmap = 423572606 This was always the same block_bitmap number. HTH, James -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1092883 Title: Disk report of Unhandled error code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1092883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1092883] Re: Disk report of Unhandled error code
** Tags added: kernel-unable-to-test-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1092883 Title: Disk report of Unhandled error code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1092883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1092883] Re: Disk report of Unhandled error code
Updated to latest kernel. At the time I downloaded it the latest was slightly after the one Joseph pointed me to so used the latest one. The stanza it added to menu.lst was title Ubuntu 12.04.1 LTS, kernel 3.8.0-030800rc2-generic root(hd0,2) kernel /boot/vmlinuz-3.8.0-030800rc2-generic root=LABEL=s01-root ro initrd /boot/initrd.img-3.8.0-030800rc2-generic quiet Unfortunately - the machine behaved oddly on the updated kernel. Even keyboard input was garbled. Had to use power button to reboot. So was unable to verify whether the problem exists on the new kernel. Sorry. As directed have added the tag kernel-unable-to-test-upstream. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1092883 Title: Disk report of Unhandled error code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1092883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1092883] Re: Disk report of Unhandled error code
Will try to test the upstream kernel and then report back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1092883 Title: Disk report of Unhandled error code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1092883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1092883] Re: Disk report of Unhandled error code
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.8 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc1-raring/ ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1092883 Title: Disk report of Unhandled error code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1092883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1092883] Re: Disk report of Unhandled error code
This shouldn't have been closed as a disk issue. The bug report wasn't for the disk error but that Linux didn't handle the error! That handling could be as simple as reporting what was wrong but if Linux doesn't recognise the error code it can never know if it is handling it correctly. ** Changed in: linux (Ubuntu) Status: Invalid = New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1092883 Title: Disk report of Unhandled error code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1092883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1092883] Re: Disk report of Unhandled error code
Not sure if it is related but the following has happened since recent upgrade to kernel 3.2.0-35-generic-pae. Once it happens the machine has long pauses between certain operations (GUI updates like alt-tab, responding to command-line commands like lsb_release -a, and file accesses such as directory reads) as if it waits for something and times out before responding. Again, is it possible that disk errors are not being properly understood by the kernel or drivers? Jan 2 16:05:26 s01 kernel: [ 3600.304094] INFO: task flush-8:32:3521 blocked for more than 120 seconds. Jan 2 16:05:26 s01 kernel: [ 3600.304098] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Jan 2 16:05:26 s01 kernel: [ 3600.304102] flush-8:32 D 0 3521 2 0x Jan 2 16:05:26 s01 kernel: [ 3600.304109] cf53bba8 0046 f6b59658 c88340b8 c180b020 c1931e00 c1931e00 Jan 2 16:05:26 s01 kernel: [ 3600.304119] 989c16d8 0327 f7bbae00 e0e88000 c180b020 00164400 0282 0006 Jan 2 16:05:26 s01 kernel: [ 3600.304128] 0010 e0872200 f6b59658 cf53bb94 f6b59658 0010 cf53bbb0 0246 Jan 2 16:05:26 s01 kernel: [ 3600.304138] Call Trace: Jan 2 16:05:26 s01 kernel: [ 3600.304148] [c15a6445] schedule+0x35/0x50 Jan 2 16:05:26 s01 kernel: [ 3600.304153] [c15a64d8] io_schedule+0x78/0xb0 Jan 2 16:05:26 s01 kernel: [ 3600.304158] [c129726d] get_request_wait+0xbd/0x190 Jan 2 16:05:26 s01 kernel: [ 3600.304165] [c12a8343] ? cfq_merge+0x63/0x90 Jan 2 16:05:26 s01 kernel: [ 3600.304171] [c107a090] ? add_wait_queue+0x50/0x50 Jan 2 16:05:26 s01 kernel: [ 3600.304175] [c1297f82] blk_queue_bio+0x62/0x2e0 Jan 2 16:05:26 s01 kernel: [ 3600.304190] [c12950d9] generic_make_request.part.47+0x59/0x90 Jan 2 16:05:26 s01 kernel: [ 3600.304194] [c1296cc7] generic_make_request+0x57/0x60 Jan 2 16:05:26 s01 kernel: [ 3600.304198] [c1296d3f] submit_bio+0x6f/0x100 Jan 2 16:05:26 s01 kernel: [ 3600.304203] [c1174640] ? bio_alloc_bioset+0x40/0xc0 Jan 2 16:05:26 s01 kernel: [ 3600.304208] [c116f2a1] submit_bh+0xd1/0x100 Jan 2 16:05:26 s01 kernel: [ 3600.304212] [c11720bb] __block_write_full_page+0x22b/0x390 Jan 2 16:05:26 s01 kernel: [ 3600.304216] [c11761c0] ? blkdev_get_blocks+0xe0/0xe0 Jan 2 16:05:26 s01 kernel: [ 3600.304220] [c1172931] block_write_full_page_endio+0xa1/0xe0 Jan 2 16:05:26 s01 kernel: [ 3600.304224] [c1170310] ? end_buffer_async_read+0x110/0x110 Jan 2 16:05:26 s01 kernel: [ 3600.304228] [c11761c0] ? blkdev_get_blocks+0xe0/0xe0 Jan 2 16:05:26 s01 kernel: [ 3600.304233] [c1016000] ? vt8237_force_hpet_resume+0x40/0x70 Jan 2 16:05:26 s01 kernel: [ 3600.304237] [c1172987] block_write_full_page+0x17/0x20 Jan 2 16:05:26 s01 kernel: [ 3600.304241] [c1170310] ? end_buffer_async_read+0x110/0x110 Jan 2 16:05:26 s01 kernel: [ 3600.304245] [c11756c4] blkdev_writepage+0x14/0x20 Jan 2 16:05:26 s01 kernel: [ 3600.304249] [c10fe490] __writepage+0x10/0x40 Jan 2 16:05:26 s01 kernel: [ 3600.304253] [c10fec53] write_cache_pages+0x193/0x3f0 Jan 2 16:05:26 s01 kernel: [ 3600.304258] [c10fe480] ? set_page_dirty_lock+0x50/0x50 Jan 2 16:05:26 s01 kernel: [ 3600.304262] [c10feeec] generic_writepages+0x3c/0x60 Jan 2 16:05:26 s01 kernel: [ 3600.304266] [c10ffc42] do_writepages+0x22/0x40 Jan 2 16:05:26 s01 kernel: [ 3600.304271] [c11690a9] writeback_single_inode+0x129/0x390 Jan 2 16:05:26 s01 kernel: [ 3600.304275] [c1169649] writeback_sb_inodes+0x159/0x1f0 Jan 2 16:05:26 s01 kernel: [ 3600.304279] [c1169754] __writeback_inodes_wb+0x74/0xa0 Jan 2 16:05:26 s01 kernel: [ 3600.304283] [c11699ab] wb_writeback+0x22b/0x2d0 Jan 2 16:05:26 s01 kernel: [ 3600.304287] [c10ff49a] ? global_dirty_limits+0x2a/0x120 Jan 2 16:05:26 s01 kernel: [ 3600.304291] [c116a747] wb_do_writeback+0x137/0x160 Jan 2 16:05:26 s01 kernel: [ 3600.304297] [c1068e6b] ? lock_timer_base.isra.30+0x2b/0x50 Jan 2 16:05:26 s01 kernel: [ 3600.304301] [c116a7e5] bdi_writeback_thread+0x75/0x240 Jan 2 16:05:26 s01 kernel: [ 3600.304305] [c116a770] ? wb_do_writeback+0x160/0x160 Jan 2 16:05:26 s01 kernel: [ 3600.304309] [c107987d] kthread+0x6d/0x80 Jan 2 16:05:26 s01 kernel: [ 3600.304313] [c1079810] ? flush_kthread_worker+0x80/0x80 Jan 2 16:05:26 s01 kernel: [ 3600.304318] [c15af7be] kernel_thread_helper+0x6/0x10 and a few minutes later: Jan 2 16:07:54 s01 udevd[2955]: timeout 'udisks-part-id /dev/sdc1' Jan 2 16:07:55 s01 udevd[2955]: timeout: killing 'udisks-part-id /dev/sdc1' [3537] Jan 2 16:07:55 s01 udevd[2955]: 'udisks-part-id /dev/sdc1' [3537] terminated by signal 9 (Killed) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1092883 Title: Disk report of Unhandled error code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1092883/+subscriptions -- ubuntu-bugs mailing list
[Bug 1092883] Re: Disk report of Unhandled error code
your hard disk is in a bad state. I close this report --- Ubuntu Bug Squad volunteer triager http://wiki.ubuntu.com/BugSquad ** Tags added: hardware-error ** Changed in: linux (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1092883 Title: Disk report of Unhandled error code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1092883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
