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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
