blk_update_request: critical target error on USB HDD after kernel upgrade #951
Description
As I can't reopen #703 so it's more "visible", I open a new thread and copy the last post. I apologize if this isn't the right way of doing this.
I think this issue have risen again, the only difference I see is that the log message changed from "end_request" to "blk_update_request", but behaviour seems the same:
Apr 14 13:00:39 raspberrypi kernel: [ 561.226469] blk_update_request: critical target error, dev sda, sector 404211137
Apr 14 13:00:39 raspberrypi kernel: [ 561.226579] Aborting journal on device sda2-8.
Apr 14 13:00:40 raspberrypi kernel: [ 563.043697] EXT4-fs error (device sda2): ext4_journal_check_start:56: Detected aborted journal
Apr 14 13:00:40 raspberrypi kernel: [ 563.057031] EXT4-fs (sda2): Remounting filesystem read-only
Apr 14 13:00:51 raspberrypi kernel: [ 574.083665] EXT4-fs error (device sda2): ext4_put_super:789: Couldn't clean up the journal
If I try to fsck:
Apr 14 12:45:24 raspberrypi kernel: [ 1603.653290] EXT4-fs error (device sda2): ext4_put_super:789: Couldn't clean up the journal
Apr 14 12:45:30 raspberrypi kernel: [ 1610.138494] blk_update_request: critical target error, dev sda, sector 0
Apr 14 12:45:30 raspberrypi kernel: [ 1610.197294] blk_update_request: critical target error, dev sda, sector 0
Apr 14 12:45:30 raspberrypi kernel: [ 1610.203760] blk_update_request: critical target error, dev sda, sector 0
Apr 14 12:46:41 raspberrypi kernel: [ 1681.278773] blk_update_request: critical target error, dev sda, sector 0
Apr 14 12:46:41 raspberrypi kernel: [ 1681.282161] blk_update_request: critical target error, dev sda, sector 0
Apr 14 12:46:41 raspberrypi kernel: [ 1681.283998] blk_update_request: critical target error, dev sda, sector 0
Based on my tests, last working commit is Hexxeh/rpi-firmware@f74b921
Broken from Hexxeh/rpi-firmware@cad071a and onwards.