Archlinux hangs at random times (seems like a hard drive problem)

Tabs · 2015-02-01 15:21:21

Dear Achlinux users,

my archlinux crashes at random times. It also sometimes refuses to boot and remains stuck when trying to deal with the sda1 partition (ext4). This second situation generally occurs after a hard reboot due to the first situation. The strange thing is that:
- I updated the disk firmware (as requested by smard);
- I run short and full smart tests without troubles
- I run an fsck without troubles (ophaned inodes certainly due to the previous hard reboot)

I put here a log excerpt when there is a crash while "running" (i.e. successfully logged and working on xfce):

-- Logs begin at Sat 2014-05-03 17:34:41 CEST, end at Sun 2015-02-01 15:20:21 CET. --
Feb 01 15:03:35 kenad kernel: INFO: task jbd2/sda1-8:311 blocked for more than 120 seconds.
Feb 01 15:03:35 kenad kernel:       Tainted: P           O   3.18.2-2-ARCH #1
Feb 01 15:03:35 kenad kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 01 15:03:35 kenad kernel: jbd2/sda1-8     D 0000000000000000     0   311      2 0x00000000
Feb 01 15:03:35 kenad kernel:  ffff880212b43b68 0000000000000046 ffff8800da4d2840 0000000000013640
Feb 01 15:03:35 kenad kernel:  ffff880212b43fd8 0000000000013640 ffff880213af4670 ffff8800da4d2840
Feb 01 15:03:35 kenad kernel:  0000000000000005 ffff880212750000 0000000000000005 ffff88020feebb50
Feb 01 15:03:35 kenad kernel: Call Trace:
Feb 01 15:03:35 kenad kernel:  [<ffffffff81283a97>] ? __blk_run_queue+0x37/0x50
Feb 01 15:03:35 kenad kernel:  [<ffffffff81287f77>] ? blk_queue_bio+0x257/0x390
Feb 01 15:03:35 kenad kernel:  [<ffffffff8101e5c9>] ? read_tsc+0x9/0x10
Feb 01 15:03:35 kenad kernel:  [<ffffffff810e12ab>] ? ktime_get+0x3b/0xb0
Feb 01 15:03:35 kenad kernel:  [<ffffffff81551570>] ? bit_wait+0x60/0x60
Feb 01 15:03:35 kenad kernel:  [<ffffffff81550b59>] schedule+0x29/0x70
Feb 01 15:03:35 kenad kernel:  [<ffffffff81550e38>] io_schedule+0x98/0x100
Feb 01 15:03:35 kenad kernel:  [<ffffffff815515a4>] bit_wait_io+0x34/0x60
Feb 01 15:03:35 kenad kernel:  [<ffffffff81551217>] __wait_on_bit+0x67/0x90
Feb 01 15:03:35 kenad kernel:  [<ffffffff81551570>] ? bit_wait+0x60/0x60
Feb 01 15:03:35 kenad kernel:  [<ffffffff815512c1>] out_of_line_wait_on_bit+0x81/0xb0
Feb 01 15:03:35 kenad kernel:  [<ffffffff810b2e70>] ? autoremove_wake_function+0x40/0x40
Feb 01 15:03:35 kenad kernel:  [<ffffffff8120253a>] __wait_on_buffer+0x2a/0x30
Feb 01 15:03:35 kenad kernel:  [<ffffffffa0136018>] jbd2_journal_commit_transaction+0x1a08/0x1a10 [jbd2]
Feb 01 15:03:35 kenad kernel:  [<ffffffffa013b83c>] kjournald2+0xec/0x2a0 [jbd2]
Feb 01 15:03:35 kenad kernel:  [<ffffffff810b2e30>] ? __wake_up_sync+0x20/0x20
Feb 01 15:03:35 kenad kernel:  [<ffffffffa013b750>] ? commit_timeout+0x10/0x10 [jbd2]
Feb 01 15:03:35 kenad kernel:  [<ffffffff81090e0a>] kthread+0xea/0x100
Feb 01 15:03:35 kenad kernel:  [<ffffffff81090d20>] ? kthread_create_on_node+0x1c0/0x1c0
Feb 01 15:03:35 kenad kernel:  [<ffffffff81554bfc>] ret_from_fork+0x7c/0xb0
Feb 01 15:03:35 kenad kernel:  [<ffffffff81090d20>] ? kthread_create_on_node+0x1c0/0x1c0
Feb 01 15:03:35 kenad kernel: INFO: task pool:1123 blocked for more than 120 seconds.
Feb 01 15:03:35 kenad kernel:       Tainted: P           O   3.18.2-2-ARCH #1
Feb 01 15:03:35 kenad kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 01 15:03:35 kenad kernel: pool            D 0000000000000007     0  1123      1 0x00000000
Feb 01 15:03:35 kenad kernel:  ffff8800cbc67aa8 0000000000000082 ffff8801f852eeb0 0000000000013640
Feb 01 15:03:35 kenad kernel:  ffff8800cbc67fd8 0000000000013640 ffff8802139a3250 ffff8801f852eeb0
Feb 01 15:03:35 kenad kernel:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
Feb 01 15:03:35 kenad kernel: Call Trace:
Feb 01 15:03:35 kenad kernel:  [<ffffffff8108ac28>] ? flush_work+0x148/0x170
Feb 01 15:03:35 kenad kernel:  [<ffffffff81550b59>] schedule+0x29/0x70
Feb 01 15:03:35 kenad kernel:  [<ffffffffa006fc3d>] scsi_block_when_processing_errors+0x5d/0xe0 [scsi_mod]
Feb 01 15:03:35 kenad kernel:  [<ffffffff810b2e30>] ? __wake_up_sync+0x20/0x20
Feb 01 15:03:35 kenad kernel:  [<ffffffffa00f13e9>] sd_open+0x59/0x160 [sd_mod]
Feb 01 15:03:35 kenad kernel:  [<ffffffff81208d98>] __blkdev_get+0x3b8/0x4c0
Feb 01 15:03:35 kenad kernel:  [<ffffffff81208ef6>] blkdev_get+0x56/0x3b0
Feb 01 15:03:35 kenad kernel:  [<ffffffff812092b0>] ? blkdev_get_by_dev+0x60/0x60
Feb 01 15:03:35 kenad kernel:  [<ffffffff8120930f>] blkdev_open+0x5f/0x90
Feb 01 15:03:35 kenad kernel:  [<ffffffff811cc982>] do_dentry_open+0x1d2/0x320
Feb 01 15:03:35 kenad kernel:  [<ffffffff811ccdf9>] vfs_open+0x49/0x50
Feb 01 15:03:35 kenad kernel:  [<ffffffff811dda97>] do_last.isra.35+0x347/0xea0
Feb 01 15:03:35 kenad kernel:  [<ffffffff811de6b2>] path_openat+0xc2/0x6e0
Feb 01 15:03:35 kenad kernel:  [<ffffffff81188b00>] ? handle_mm_fault+0xa90/0x1100
Feb 01 15:03:35 kenad kernel:  [<ffffffff811dfc2e>] ? user_path_at_empty+0x6e/0xd0
Feb 01 15:03:35 kenad kernel:  [<ffffffff811dfd59>] do_filp_open+0x49/0xd0
Feb 01 15:03:35 kenad kernel:  [<ffffffff811ed3e7>] ? __alloc_fd+0xa7/0x130
Feb 01 15:03:35 kenad kernel:  [<ffffffff811ce1ae>] do_sys_open+0x14e/0x250
Feb 01 15:03:35 kenad kernel:  [<ffffffff811ce2ce>] SyS_open+0x1e/0x20
Feb 01 15:03:35 kenad kernel:  [<ffffffff81554ca9>] system_call_fastpath+0x12/0x17
Feb 01 15:03:35 kenad kernel: INFO: task kworker/u16:2:991 blocked for more than 120 seconds.
Feb 01 15:03:35 kenad kernel:       Tainted: P           O   3.18.2-2-ARCH #1
Feb 01 15:03:35 kenad kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 01 15:03:35 kenad kernel: kworker/u16:2   D 0000000000000000     0   991      2 0x00000000
Feb 01 15:03:35 kenad kernel: Workqueue: writeback bdi_writeback_workfn (flush-8:0)
Feb 01 15:03:35 kenad kernel:  ffff8801f84eb4c8 0000000000000046 ffff8801f8529420 0000000000013640
Feb 01 15:03:35 kenad kernel:  ffff8801f84ebfd8 0000000000013640 ffff8800da4d0000 ffff8801f8529420
Feb 01 15:03:35 kenad kernel:  0000000000001000 ffffea00083da000 0000000000001000 00000000e81261d0
Feb 01 15:03:35 kenad kernel: Call Trace:
Feb 01 15:03:35 kenad kernel:  [<ffffffff8128c964>] ? blk_rq_map_sg+0x44/0x1a0
Feb 01 15:03:35 kenad kernel:  [<ffffffff81551570>] ? bit_wait+0x60/0x60
Feb 01 15:03:35 kenad kernel:  [<ffffffff81550b59>] schedule+0x29/0x70
Feb 01 15:03:35 kenad kernel:  [<ffffffff81550e38>] io_schedule+0x98/0x100
Feb 01 15:03:35 kenad kernel:  [<ffffffff815515a4>] bit_wait_io+0x34/0x60
Feb 01 15:03:35 kenad kernel:  [<ffffffff815513fb>] __wait_on_bit_lock+0x4b/0xb0
Feb 01 15:03:35 kenad kernel:  [<ffffffff81157253>] ? find_get_entry+0x63/0xb0
Feb 01 15:03:35 kenad kernel:  [<ffffffff81551570>] ? bit_wait+0x60/0x60
Feb 01 15:03:35 kenad kernel:  [<ffffffff815514e1>] out_of_line_wait_on_bit_lock+0x81/0xb0
Feb 01 15:03:35 kenad kernel:  [<ffffffff810b2e70>] ? autoremove_wake_function+0x40/0x40
Feb 01 15:03:35 kenad kernel:  [<ffffffff8120247a>] __lock_buffer+0x2a/0x30
Feb 01 15:03:35 kenad kernel:  [<ffffffffa0132d60>] do_get_write_access+0x260/0x5f0 [jbd2]
Feb 01 15:03:35 kenad kernel:  [<ffffffff812048e1>] ? __getblk_gfp+0x21/0x50
Feb 01 15:03:35 kenad kernel:  [<ffffffffa0133117>] jbd2_journal_get_write_access+0x27/0x40 [jbd2]
Feb 01 15:03:35 kenad kernel:  [<ffffffffa01f4e81>] __ext4_journal_get_write_access+0x31/0x80 [ext4]
Feb 01 15:03:35 kenad kernel:  [<ffffffffa01c6188>] ext4_reserve_inode_write+0x68/0x90 [ext4]
Feb 01 15:03:35 kenad kernel:  [<ffffffffa01eca0b>] ? __ext4_ext_dirty+0x7b/0xb0 [ext4]
Feb 01 15:03:35 kenad kernel:  [<ffffffffa01c61fe>] ext4_mark_inode_dirty+0x4e/0x240 [ext4]
Feb 01 15:03:35 kenad kernel:  [<ffffffffa01eca0b>] __ext4_ext_dirty+0x7b/0xb0 [ext4]
Feb 01 15:03:35 kenad kernel:  [<ffffffffa01ee2d6>] ext4_ext_insert_extent+0x706/0x1370 [ext4]
Feb 01 15:03:35 kenad kernel:  [<ffffffffa01fdcd9>] ? ext4_mb_new_blocks+0x159/0x5d0 [ext4]
Feb 01 15:03:35 kenad kernel:  [<ffffffffa01f1d17>] ext4_ext_map_blocks+0x9b7/0x16e0 [ext4]
Feb 01 15:03:35 kenad kernel:  [<ffffffffa01c3501>] ext4_map_blocks+0x141/0x570 [ext4]
Feb 01 15:03:35 kenad kernel:  [<ffffffffa01c6810>] ? ext4_writepages+0x420/0xd00 [ext4]
Feb 01 15:03:35 kenad kernel:  [<ffffffffa01c6a54>] ext4_writepages+0x664/0xd00 [ext4]
Feb 01 15:03:35 kenad kernel:  [<ffffffff81284d3f>] ? queue_unplugged+0x3f/0xc0
Feb 01 15:03:35 kenad kernel:  [<ffffffff812880c8>] ? blk_finish_plug+0x18/0x60
Feb 01 15:03:35 kenad kernel:  [<ffffffff811643ee>] do_writepages+0x1e/0x30
Feb 01 15:03:35 kenad kernel:  [<ffffffff811fa8e0>] __writeback_single_inode+0x40/0x2b0
Feb 01 15:03:35 kenad kernel:  [<ffffffff811fbe03>] writeback_sb_inodes+0x283/0x460
Feb 01 15:03:35 kenad kernel:  [<ffffffff811fc07f>] __writeback_inodes_wb+0x9f/0xd0
Feb 01 15:03:35 kenad kernel:  [<ffffffff811fc2db>] wb_writeback+0x22b/0x360
Feb 01 15:03:35 kenad kernel:  [<ffffffff811e9401>] ? get_nr_inodes+0x51/0x80
Feb 01 15:03:35 kenad kernel:  [<ffffffff811fc77c>] bdi_writeback_workfn+0x20c/0x4e0
Feb 01 15:03:35 kenad kernel:  [<ffffffff8108b7c5>] process_one_work+0x145/0x400
Feb 01 15:03:35 kenad kernel:  [<ffffffff8108bd8b>] worker_thread+0x6b/0x4a0
Feb 01 15:03:35 kenad kernel:  [<ffffffff8108bd20>] ? init_pwq.part.22+0x10/0x10
Feb 01 15:03:35 kenad kernel:  [<ffffffff81090e0a>] kthread+0xea/0x100
Feb 01 15:03:35 kenad kernel:  [<ffffffff81090d20>] ? kthread_create_on_node+0x1c0/0x1c0
Feb 01 15:03:35 kenad kernel:  [<ffffffff81554bfc>] ret_from_fork+0x7c/0xb0
Feb 01 15:03:35 kenad kernel:  [<ffffffff81090d20>] ? kthread_create_on_node+0x1c0/0x1c0
Feb 01 15:03:35 kenad kernel: INFO: task mozStorage #1:1070 blocked for more than 120 seconds.
Feb 01 15:03:35 kenad kernel:       Tainted: P           O   3.18.2-2-ARCH #1
Feb 01 15:03:35 kenad kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 01 15:03:35 kenad kernel: mozStorage #1   D 0000000000000001     0  1070      1 0x00000000
Feb 01 15:03:35 kenad kernel:  ffff8800bbde7e18 0000000000000086 ffff880212784670 0000000000013640
Feb 01 15:03:35 kenad kernel:  ffff8800bbde7fd8 0000000000013640 ffff8802138e6eb0 ffff880212784670
Feb 01 15:03:35 kenad kernel:  ffff8800bbde7d98 ffffffff8109e6e7 ffffea0007a97480 ffff8801f02bd418
Feb 01 15:03:35 kenad kernel: Call Trace:
Feb 01 15:03:35 kenad kernel:  [<ffffffff8109e6e7>] ? try_to_wake_up+0x1e7/0x380
Feb 01 15:03:35 kenad kernel:  [<ffffffff8109e8e2>] ? default_wake_function+0x12/0x20
Feb 01 15:03:35 kenad kernel:  [<ffffffff81550b59>] schedule+0x29/0x70
Feb 01 15:03:35 kenad kernel:  [<ffffffffa013a7ed>] jbd2_log_wait_commit+0xad/0x130 [jbd2]
Feb 01 15:03:35 kenad kernel:  [<ffffffff810b2e30>] ? __wake_up_sync+0x20/0x20
Feb 01 15:03:35 kenad kernel:  [<ffffffffa013c4bc>] jbd2_complete_transaction+0x7c/0xb0 [jbd2]
Feb 01 15:03:35 kenad kernel:  [<ffffffffa01bdb58>] ext4_sync_file+0x1f8/0x370 [ext4]
Feb 01 15:03:35 kenad kernel:  [<ffffffff812008e1>] do_fsync+0x51/0x80
Feb 01 15:03:35 kenad kernel:  [<ffffffff81200bc3>] SyS_fdatasync+0x13/0x20
Feb 01 15:03:35 kenad kernel:  [<ffffffff81554ca9>] system_call_fastpath+0x12/0x17
Feb 01 15:04:52 kenad systemd[1]: Starting Cleanup of Temporary Directories...
Feb 01 15:04:52 kenad systemd[1]: Started Cleanup of Temporary Directories.
Feb 01 15:05:15 kenad sudo[1127]: pam_unix(sudo:session): session closed for user root
Feb 01 15:05:35 kenad kernel: INFO: task jbd2/sda1-8:311 blocked for more than 120 seconds.
Feb 01 15:05:35 kenad kernel:       Tainted: P           O   3.18.2-2-ARCH #1
Feb 01 15:05:35 kenad kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 01 15:05:35 kenad kernel: jbd2/sda1-8     D 0000000000000000     0   311      2 0x00000000
Feb 01 15:05:35 kenad kernel:  ffff880212b43b68 0000000000000046 ffff8800da4d2840 0000000000013640
Feb 01 15:05:35 kenad kernel:  ffff880212b43fd8 0000000000013640 ffff880213af4670 ffff8800da4d2840
Feb 01 15:05:35 kenad kernel:  0000000000000005 ffff880212750000 0000000000000005 ffff88020feebb50
Feb 01 15:05:35 kenad kernel: Call Trace:
Feb 01 15:05:35 kenad kernel:  [<ffffffff81283a97>] ? __blk_run_queue+0x37/0x50
Feb 01 15:05:35 kenad kernel:  [<ffffffff81287f77>] ? blk_queue_bio+0x257/0x390
Feb 01 15:05:35 kenad kernel:  [<ffffffff8101e5c9>] ? read_tsc+0x9/0x10
Feb 01 15:05:35 kenad kernel:  [<ffffffff810e12ab>] ? ktime_get+0x3b/0xb0
Feb 01 15:05:35 kenad kernel:  [<ffffffff81551570>] ? bit_wait+0x60/0x60
Feb 01 15:05:35 kenad kernel:  [<ffffffff81550b59>] schedule+0x29/0x70
Feb 01 15:05:35 kenad kernel:  [<ffffffff81550e38>] io_schedule+0x98/0x100
Feb 01 15:05:35 kenad kernel:  [<ffffffff815515a4>] bit_wait_io+0x34/0x60
Feb 01 15:05:35 kenad kernel:  [<ffffffff81551217>] __wait_on_bit+0x67/0x90
Feb 01 15:05:35 kenad kernel:  [<ffffffff81551570>] ? bit_wait+0x60/0x60
Feb 01 15:05:35 kenad kernel:  [<ffffffff815512c1>] out_of_line_wait_on_bit+0x81/0xb0
Feb 01 15:05:35 kenad kernel:  [<ffffffff810b2e70>] ? autoremove_wake_function+0x40/0x40
Feb 01 15:05:35 kenad kernel:  [<ffffffff8120253a>] __wait_on_buffer+0x2a/0x30
Feb 01 15:05:35 kenad kernel:  [<ffffffffa0136018>] jbd2_journal_commit_transaction+0x1a08/0x1a10 [jbd2]
Feb 01 15:05:35 kenad kernel:  [<ffffffffa013b83c>] kjournald2+0xec/0x2a0 [jbd2]
Feb 01 15:05:35 kenad kernel:  [<ffffffff810b2e30>] ? __wake_up_sync+0x20/0x20
Feb 01 15:05:35 kenad kernel:  [<ffffffffa013b750>] ? commit_timeout+0x10/0x10 [jbd2]
Feb 01 15:05:35 kenad kernel:  [<ffffffff81090e0a>] kthread+0xea/0x100
Feb 01 15:05:35 kenad kernel:  [<ffffffff81090d20>] ? kthread_create_on_node+0x1c0/0x1c0
Feb 01 15:05:35 kenad kernel:  [<ffffffff81554bfc>] ret_from_fork+0x7c/0xb0
Feb 01 15:05:35 kenad kernel:  [<ffffffff81090d20>] ? kthread_create_on_node+0x1c0/0x1c0
Feb 01 15:05:35 kenad kernel: INFO: task pool:1123 blocked for more than 120 seconds.
Feb 01 15:05:35 kenad kernel:       Tainted: P           O   3.18.2-2-ARCH #1
Feb 01 15:05:35 kenad kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 01 15:05:35 kenad kernel: pool            D 0000000000000007     0  1123      1 0x00000000
Feb 01 15:05:35 kenad kernel:  ffff8800cbc67aa8 0000000000000082 ffff8801f852eeb0 0000000000013640
Feb 01 15:05:35 kenad kernel:  ffff8800cbc67fd8 0000000000013640 ffff8802139a3250 ffff8801f852eeb0
Feb 01 15:05:35 kenad kernel:  0000000000000000 0000000000000000 0000000000000000 0000000000000000
Feb 01 15:05:35 kenad kernel: Call Trace:
Feb 01 15:05:35 kenad kernel:  [<ffffffff8108ac28>] ? flush_work+0x148/0x170
Feb 01 15:05:35 kenad kernel:  [<ffffffff81550b59>] schedule+0x29/0x70
Feb 01 15:05:35 kenad kernel:  [<ffffffffa006fc3d>] scsi_block_when_processing_errors+0x5d/0xe0 [scsi_mod]
Feb 01 15:05:35 kenad kernel:  [<ffffffff810b2e30>] ? __wake_up_sync+0x20/0x20
Feb 01 15:05:35 kenad kernel:  [<ffffffffa00f13e9>] sd_open+0x59/0x160 [sd_mod]
Feb 01 15:05:35 kenad kernel:  [<ffffffff81208d98>] __blkdev_get+0x3b8/0x4c0
Feb 01 15:05:35 kenad kernel:  [<ffffffff81208ef6>] blkdev_get+0x56/0x3b0
Feb 01 15:05:35 kenad kernel:  [<ffffffff812092b0>] ? blkdev_get_by_dev+0x60/0x60
Feb 01 15:05:35 kenad kernel:  [<ffffffff8120930f>] blkdev_open+0x5f/0x90
Feb 01 15:05:35 kenad kernel:  [<ffffffff811cc982>] do_dentry_open+0x1d2/0x320
Feb 01 15:05:35 kenad kernel:  [<ffffffff811ccdf9>] vfs_open+0x49/0x50
Feb 01 15:05:35 kenad kernel:  [<ffffffff811dda97>] do_last.isra.35+0x347/0xea0
Feb 01 15:05:35 kenad kernel:  [<ffffffff811de6b2>] path_openat+0xc2/0x6e0
Feb 01 15:05:35 kenad kernel:  [<ffffffff81188b00>] ? handle_mm_fault+0xa90/0x1100
Feb 01 15:05:35 kenad kernel:  [<ffffffff811dfc2e>] ? user_path_at_empty+0x6e/0xd0
Feb 01 15:05:35 kenad kernel:  [<ffffffff811dfd59>] do_filp_open+0x49/0xd0
Feb 01 15:05:35 kenad kernel:  [<ffffffff811ed3e7>] ? __alloc_fd+0xa7/0x130
Feb 01 15:05:35 kenad kernel:  [<ffffffff811ce1ae>] do_sys_open+0x14e/0x250
Feb 01 15:05:35 kenad kernel:  [<ffffffff811ce2ce>] SyS_open+0x1e/0x20
Feb 01 15:05:35 kenad kernel:  [<ffffffff81554ca9>] system_call_fastpath+0x12/0x17
Feb 01 15:05:35 kenad kernel: INFO: task kworker/u16:2:991 blocked for more than 120 seconds.
Feb 01 15:05:35 kenad kernel:       Tainted: P           O   3.18.2-2-ARCH #1
Feb 01 15:05:35 kenad kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 01 15:05:35 kenad kernel: kworker/u16:2   D 0000000000000000     0   991      2 0x00000000
Feb 01 15:05:35 kenad kernel: Workqueue: writeback bdi_writeback_workfn (flush-8:0)
Feb 01 15:05:35 kenad kernel:  ffff8801f84eb4c8 0000000000000046 ffff8801f8529420 0000000000013640
Feb 01 15:05:35 kenad kernel:  ffff8801f84ebfd8 0000000000013640 ffff8800da4d0000 ffff8801f8529420
Feb 01 15:05:35 kenad kernel:  0000000000001000 ffffea00083da000 0000000000001000 00000000e81261d0
Feb 01 15:05:35 kenad kernel: Call Trace:
Feb 01 15:05:35 kenad kernel:  [<ffffffff8128c964>] ? blk_rq_map_sg+0x44/0x1a0
Feb 01 15:05:35 kenad kernel:  [<ffffffff81551570>] ? bit_wait+0x60/0x60
Feb 01 15:05:35 kenad kernel:  [<ffffffff81550b59>] schedule+0x29/0x70
Feb 01 15:05:35 kenad kernel:  [<ffffffff81550e38>] io_schedule+0x98/0x100
Feb 01 15:05:35 kenad kernel:  [<ffffffff815515a4>] bit_wait_io+0x34/0x60
Feb 01 15:05:35 kenad kernel:  [<ffffffff815513fb>] __wait_on_bit_lock+0x4b/0xb0
Feb 01 15:05:35 kenad kernel:  [<ffffffff81157253>] ? find_get_entry+0x63/0xb0
Feb 01 15:05:35 kenad kernel:  [<ffffffff81551570>] ? bit_wait+0x60/0x60
Feb 01 15:05:35 kenad kernel:  [<ffffffff815514e1>] out_of_line_wait_on_bit_lock+0x81/0xb0
Feb 01 15:05:35 kenad kernel:  [<ffffffff810b2e70>] ? autoremove_wake_function+0x40/0x40
Feb 01 15:05:35 kenad kernel:  [<ffffffff8120247a>] __lock_buffer+0x2a/0x30
Feb 01 15:05:35 kenad kernel:  [<ffffffffa0132d60>] do_get_write_access+0x260/0x5f0 [jbd2]
Feb 01 15:05:35 kenad kernel:  [<ffffffff812048e1>] ? __getblk_gfp+0x21/0x50
Feb 01 15:05:35 kenad kernel:  [<ffffffffa0133117>] jbd2_journal_get_write_access+0x27/0x40 [jbd2]
Feb 01 15:05:35 kenad kernel:  [<ffffffffa01f4e81>] __ext4_journal_get_write_access+0x31/0x80 [ext4]
Feb 01 15:05:35 kenad kernel:  [<ffffffffa01c6188>] ext4_reserve_inode_write+0x68/0x90 [ext4]
Feb 01 15:05:35 kenad kernel:  [<ffffffffa01eca0b>] ? __ext4_ext_dirty+0x7b/0xb0 [ext4]
Feb 01 15:05:35 kenad kernel:  [<ffffffffa01c61fe>] ext4_mark_inode_dirty+0x4e/0x240 [ext4]
Feb 01 15:05:35 kenad kernel:  [<ffffffffa01eca0b>] __ext4_ext_dirty+0x7b/0xb0 [ext4]
Feb 01 15:05:35 kenad kernel:  [<ffffffffa01ee2d6>] ext4_ext_insert_extent+0x706/0x1370 [ext4]
Feb 01 15:05:35 kenad kernel:  [<ffffffffa01fdcd9>] ? ext4_mb_new_blocks+0x159/0x5d0 [ext4]
Feb 01 15:05:35 kenad kernel:  [<ffffffffa01f1d17>] ext4_ext_map_blocks+0x9b7/0x16e0 [ext4]
Feb 01 15:05:35 kenad kernel:  [<ffffffffa01c3501>] ext4_map_blocks+0x141/0x570 [ext4]
Feb 01 15:05:35 kenad kernel:  [<ffffffffa01c6810>] ? ext4_writepages+0x420/0xd00 [ext4]
Feb 01 15:05:35 kenad kernel:  [<ffffffffa01c6a54>] ext4_writepages+0x664/0xd00 [ext4]
Feb 01 15:05:35 kenad kernel:  [<ffffffff81284d3f>] ? queue_unplugged+0x3f/0xc0
Feb 01 15:05:35 kenad kernel:  [<ffffffff812880c8>] ? blk_finish_plug+0x18/0x60
Feb 01 15:05:35 kenad kernel:  [<ffffffff811643ee>] do_writepages+0x1e/0x30
Feb 01 15:05:35 kenad kernel:  [<ffffffff811fa8e0>] __writeback_single_inode+0x40/0x2b0
Feb 01 15:05:35 kenad kernel:  [<ffffffff811fbe03>] writeback_sb_inodes+0x283/0x460
Feb 01 15:05:35 kenad kernel:  [<ffffffff811fc07f>] __writeback_inodes_wb+0x9f/0xd0
Feb 01 15:05:35 kenad kernel:  [<ffffffff811fc2db>] wb_writeback+0x22b/0x360
Feb 01 15:05:35 kenad kernel:  [<ffffffff811e9401>] ? get_nr_inodes+0x51/0x80
Feb 01 15:05:35 kenad kernel:  [<ffffffff811fc77c>] bdi_writeback_workfn+0x20c/0x4e0
Feb 01 15:05:35 kenad kernel:  [<ffffffff8108b7c5>] process_one_work+0x145/0x400
Feb 01 15:05:35 kenad kernel:  [<ffffffff8108bd8b>] worker_thread+0x6b/0x4a0
Feb 01 15:05:35 kenad kernel:  [<ffffffff8108bd20>] ? init_pwq.part.22+0x10/0x10
Feb 01 15:05:35 kenad kernel:  [<ffffffff81090e0a>] kthread+0xea/0x100
Feb 01 15:05:35 kenad kernel:  [<ffffffff81090d20>] ? kthread_create_on_node+0x1c0/0x1c0
Feb 01 15:05:35 kenad kernel:  [<ffffffff81554bfc>] ret_from_fork+0x7c/0xb0
Feb 01 15:05:35 kenad kernel:  [<ffffffff81090d20>] ? kthread_create_on_node+0x1c0/0x1c0
Feb 01 15:05:35 kenad kernel: INFO: task mozStorage #1:1070 blocked for more than 120 seconds.
Feb 01 15:05:35 kenad kernel:       Tainted: P           O   3.18.2-2-ARCH #1
Feb 01 15:05:35 kenad kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 01 15:05:35 kenad kernel: mozStorage #1   D 0000000000000001     0  1070      1 0x00000000
Feb 01 15:05:35 kenad kernel:  ffff8800bbde7e18 0000000000000086 ffff880212784670 0000000000013640
Feb 01 15:05:35 kenad kernel:  ffff8800bbde7fd8 0000000000013640 ffff8802138e6eb0 ffff880212784670
Feb 01 15:05:35 kenad kernel:  ffff8800bbde7d98 ffffffff8109e6e7 ffffea0007a97480 ffff8801f02bd418
Feb 01 15:05:35 kenad kernel: Call Trace:
Feb 01 15:05:35 kenad kernel:  [<ffffffff8109e6e7>] ? try_to_wake_up+0x1e7/0x380
Feb 01 15:05:35 kenad kernel:  [<ffffffff8109e8e2>] ? default_wake_function+0x12/0x20
Feb 01 15:05:35 kenad kernel:  [<ffffffff81550b59>] schedule+0x29/0x70
Feb 01 15:05:35 kenad kernel:  [<ffffffffa013a7ed>] jbd2_log_wait_commit+0xad/0x130 [jbd2]
Feb 01 15:05:35 kenad kernel:  [<ffffffff810b2e30>] ? __wake_up_sync+0x20/0x20
Feb 01 15:05:35 kenad kernel:  [<ffffffffa013c4bc>] jbd2_complete_transaction+0x7c/0xb0 [jbd2]
Feb 01 15:05:35 kenad kernel:  [<ffffffffa01bdb58>] ext4_sync_file+0x1f8/0x370 [ext4]
Feb 01 15:05:35 kenad kernel:  [<ffffffff812008e1>] do_fsync+0x51/0x80
Feb 01 15:05:35 kenad kernel:  [<ffffffff81200bc3>] SyS_fdatasync+0x13/0x20
Feb 01 15:05:35 kenad kernel:  [<ffffffff81554ca9>] system_call_fastpath+0x12/0x17
Feb 01 15:07:35 kenad kernel: INFO: task jbd2/sda1-8:311 blocked for more than 120 seconds.
Feb 01 15:07:35 kenad kernel:       Tainted: P           O   3.18.2-2-ARCH #1
Feb 01 15:07:35 kenad kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 01 15:07:35 kenad kernel: jbd2/sda1-8     D 0000000000000000     0   311      2 0x00000000
Feb 01 15:07:35 kenad kernel:  ffff880212b43b68 0000000000000046 ffff8800da4d2840 0000000000013640
Feb 01 15:07:35 kenad kernel:  ffff880212b43fd8 0000000000013640 ffff880213af4670 ffff8800da4d2840
Feb 01 15:07:35 kenad kernel:  0000000000000005 ffff880212750000 0000000000000005 ffff88020feebb50
Feb 01 15:07:35 kenad kernel: Call Trace:
Feb 01 15:07:35 kenad kernel:  [<ffffffff81283a97>] ? __blk_run_queue+0x37/0x50
Feb 01 15:07:35 kenad kernel:  [<ffffffff81287f77>] ? blk_queue_bio+0x257/0x390
Feb 01 15:07:35 kenad kernel:  [<ffffffff8101e5c9>] ? read_tsc+0x9/0x10
Feb 01 15:07:35 kenad kernel:  [<ffffffff810e12ab>] ? ktime_get+0x3b/0xb0
Feb 01 15:07:35 kenad kernel:  [<ffffffff81551570>] ? bit_wait+0x60/0x60
Feb 01 15:07:35 kenad kernel:  [<ffffffff81550b59>] schedule+0x29/0x70
Feb 01 15:07:35 kenad kernel:  [<ffffffff81550e38>] io_schedule+0x98/0x100
Feb 01 15:07:35 kenad kernel:  [<ffffffff815515a4>] bit_wait_io+0x34/0x60
Feb 01 15:07:35 kenad kernel:  [<ffffffff81551217>] __wait_on_bit+0x67/0x90
Feb 01 15:07:35 kenad kernel:  [<ffffffff81551570>] ? bit_wait+0x60/0x60
Feb 01 15:07:35 kenad kernel:  [<ffffffff815512c1>] out_of_line_wait_on_bit+0x81/0xb0
Feb 01 15:07:35 kenad kernel:  [<ffffffff810b2e70>] ? autoremove_wake_function+0x40/0x40
Feb 01 15:07:35 kenad kernel:  [<ffffffff8120253a>] __wait_on_buffer+0x2a/0x30
Feb 01 15:07:35 kenad kernel:  [<ffffffffa0136018>] jbd2_journal_commit_transaction+0x1a08/0x1a10 [jbd2]
Feb 01 15:07:35 kenad kernel:  [<ffffffffa013b83c>] kjournald2+0xec/0x2a0 [jbd2]
Feb 01 15:07:35 kenad kernel:  [<ffffffff810b2e30>] ? __wake_up_sync+0x20/0x20
Feb 01 15:07:35 kenad kernel:  [<ffffffffa013b750>] ? commit_timeout+0x10/0x10 [jbd2]
Feb 01 15:07:35 kenad kernel:  [<ffffffff81090e0a>] kthread+0xea/0x100
Feb 01 15:07:35 kenad kernel:  [<ffffffff81090d20>] ? kthread_create_on_node+0x1c0/0x1c0
Feb 01 15:07:35 kenad kernel:  [<ffffffff81554bfc>] ret_from_fork+0x7c/0xb0
Feb 01 15:07:35 kenad kernel:  [<ffffffff81090d20>] ? kthread_create_on_node+0x1c0/0x1c0
Feb 01 15:07:35 kenad kernel: INFO: task xfdesktop:576 blocked for more than 120 seconds.
Feb 01 15:07:35 kenad kernel:       Tainted: P           O   3.18.2-2-ARCH #1
Feb 01 15:07:35 kenad kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 01 15:07:35 kenad kernel: xfdesktop       D 0000000000000003     0   576    547 0x00000000
Feb 01 15:07:35 kenad kernel:  ffff8800d16cb968 0000000000000082 ffff880212e94670 0000000000013640
Feb 01 15:07:35 kenad kernel:  ffff8800d16cbfd8 0000000000013640 ffff8802139a0a10 ffff880212e94670
Feb 01 15:07:35 kenad kernel:  ffff88021f4d36b8 ffff8800d163aa00 ffff88021f4d36b8 0000000000000001
Feb 01 15:07:35 kenad kernel: Call Trace:
Feb 01 15:07:35 kenad kernel:  [<ffffffff810a848f>] ? dequeue_entity+0x13f/0x580
Feb 01 15:07:35 kenad kernel:  [<ffffffff810a9831>] ? put_prev_entity+0x31/0x350
Feb 01 15:07:35 kenad kernel:  [<ffffffff810accd4>] ? pick_next_task_fair+0x144/0x520
Feb 01 15:07:35 kenad kernel:  [<ffffffff810136fb>] ? __switch_to+0x1fb/0x600
Feb 01 15:07:35 kenad kernel:  [<ffffffff81551570>] ? bit_wait+0x60/0x60
Feb 01 15:07:35 kenad kernel:  [<ffffffff81550b59>] schedule+0x29/0x70
Feb 01 15:07:35 kenad kernel:  [<ffffffff81550e38>] io_schedule+0x98/0x100
Feb 01 15:07:35 kenad kernel:  [<ffffffff815515a4>] bit_wait_io+0x34/0x60
Feb 01 15:07:35 kenad kernel:  [<ffffffff815513fb>] __wait_on_bit_lock+0x4b/0xb0
Feb 01 15:07:35 kenad kernel:  [<ffffffff81157253>] ? find_get_entry+0x63/0xb0
Feb 01 15:07:35 kenad kernel:  [<ffffffff81551570>] ? bit_wait+0x60/0x60
Feb 01 15:07:35 kenad kernel:  [<ffffffff815514e1>] out_of_line_wait_on_bit_lock+0x81/0xb0
Feb 01 15:07:35 kenad kernel:  [<ffffffff810b2e70>] ? autoremove_wake_function+0x40/0x40
Feb 01 15:07:35 kenad kernel:  [<ffffffff8120247a>] __lock_buffer+0x2a/0x30
Feb 01 15:07:35 kenad kernel:  [<ffffffffa0132d60>] do_get_write_access+0x260/0x5f0 [jbd2]
Feb 01 15:07:35 kenad kernel:  [<ffffffff812048e1>] ? __getblk_gfp+0x21/0x50
Feb 01 15:07:35 kenad kernel:  [<ffffffffa0133117>] jbd2_journal_get_write_access+0x27/0x40 [jbd2]
Feb 01 15:07:35 kenad kernel:  [<ffffffffa01f4e81>] __ext4_journal_get_write_access+0x31/0x80 [ext4]
Feb 01 15:07:35 kenad kernel:  [<ffffffffa01c6188>] ext4_reserve_inode_write+0x68/0x90 [ext4]
Feb 01 15:07:35 kenad kernel:  [<ffffffffa01c97f0>] ? ext4_dirty_inode+0x40/0x60 [ext4]
Feb 01 15:07:35 kenad kernel:  [<ffffffffa01c61fe>] ext4_mark_inode_dirty+0x4e/0x240 [ext4]
Feb 01 15:07:35 kenad kernel:  [<ffffffffa01c97f0>] ext4_dirty_inode+0x40/0x60 [ext4]
Feb 01 15:07:35 kenad kernel:  [<ffffffff811fb0f8>] __mark_inode_dirty+0x38/0x2d0
Feb 01 15:07:35 kenad kernel:  [<ffffffff811ea711>] update_time+0x81/0xc0
Feb 01 15:07:35 kenad kernel:  [<ffffffff810d7af6>] ? current_fs_time+0x16/0x60
Feb 01 15:07:35 kenad kernel:  [<ffffffff811ea960>] file_update_time+0xa0/0xf0
Feb 01 15:07:35 kenad kernel:  [<ffffffff811591b8>] __generic_file_write_iter+0x1b8/0x3b0
Feb 01 15:07:35 kenad kernel:  [<ffffffff811851d4>] ? do_wp_page+0xf4/0x970
Feb 01 15:07:35 kenad kernel:  [<ffffffffa01bcf68>] ext4_file_write_iter+0x128/0x400 [ext4]
Feb 01 15:07:35 kenad kernel:  [<ffffffff810136fb>] ? __switch_to+0x1fb/0x600
Feb 01 15:07:35 kenad kernel:  [<ffffffff811ce8fe>] new_sync_write+0x8e/0xd0
Feb 01 15:07:35 kenad kernel:  [<ffffffff811cf1d7>] vfs_write+0xb7/0x200
Feb 01 15:07:35 kenad kernel:  [<ffffffff811cfd29>] SyS_write+0x59/0xd0
Feb 01 15:07:35 kenad kernel:  [<ffffffff81554ca9>] system_call_fastpath+0x12/0x17

Here is a log excerpt when the crash happen during the boot period, look at the udevd entries:

-- Logs begin at Sat 2014-05-03 17:34:41 CEST, end at Sun 2015-02-01 15:35:26 CET. --
Feb 01 15:35:26 kenad kernel: random: nonblocking pool is initialized
Feb 01 15:35:22 kenad systemd[308]: Failed at step EXEC spawning /bin/plymouth: No such file or directory
Feb 01 15:35:22 kenad systemd[1]: Startup finished in 2.840s (kernel) + 1min 30.253s (userspace) = 1min 33.094s.
Feb 01 15:35:22 kenad systemd[1]: Started Update UTMP about System Boot/Shutdown.
Feb 01 15:35:21 kenad systemd[1]: Starting Update UTMP about System Boot/Shutdown...
Feb 01 15:35:21 kenad systemd[1]: Started Create Volatile Files and Directories.
Feb 01 15:35:21 kenad systemd[1]: Started Restore Sound Card State.
Feb 01 15:35:21 kenad systemd[1]: Started Trigger Flushing of Journal to Persistent Storage.
Feb 01 15:35:22 kenad systemd-journal[181]: Time spent on flushing to /var is 28.904ms for 925 entries.
Feb 01 15:35:22 kenad systemd-journal[181]: Permanent journal is using 1.1G (max allowed 1.1G, trying to leave 1.7G free of 38.9M available → current limit 1.1G).
Feb 01 15:35:21 kenad systemd[1]: Reached target Emergency Mode.
Feb 01 15:35:21 kenad systemd[1]: Starting Emergency Mode.
Feb 01 15:35:21 kenad systemd[1]: Started Emergency Shell.
Feb 01 15:35:21 kenad systemd[1]: Starting Emergency Shell...
Feb 01 15:35:21 kenad systemd[1]: Started Update is Completed.
Feb 01 15:35:21 kenad systemd[1]: Started Rebuild Journal Catalog.
Feb 01 15:35:21 kenad systemd[1]: Starting Create Volatile Files and Directories...
Feb 01 15:35:21 kenad systemd[1]: Starting Restore Sound Card State...
Feb 01 15:35:21 kenad systemd[1]: Started Manage Sound Card State (restore and store).
Feb 01 15:35:21 kenad systemd[1]: Stopped target System Initialization.
Feb 01 15:35:21 kenad systemd[1]: Reached target Sockets.
Feb 01 15:35:21 kenad systemd[1]: Starting Sockets.
Feb 01 15:35:21 kenad systemd[1]: Reached target Timers.
Feb 01 15:35:21 kenad systemd[1]: Starting Timers.
Feb 01 15:35:21 kenad systemd[1]: Reached target Paths.
Feb 01 15:35:21 kenad systemd[1]: Starting Paths.
Feb 01 15:35:21 kenad systemd[1]: Stopped target Basic System.
Feb 01 15:35:21 kenad systemd[1]: Starting Trigger Flushing of Journal to Persistent Storage...
Feb 01 15:35:21 kenad systemd[1]: Stopped Permit User Sessions.
Feb 01 15:35:21 kenad systemd[1]: Stopped Light Display Manager.
Feb 01 15:35:21 kenad systemd[1]: Stopped Daily rotation of log files.
Feb 01 15:35:21 kenad systemd[1]: Closed D-Bus System Message Bus Socket.
Feb 01 15:35:21 kenad systemd[1]: Stopped Login Service.
Feb 01 15:35:21 kenad systemd[1]: Stopped Daily man-db cache update.
Feb 01 15:35:21 kenad systemd[1]: Stopped Daily verification of password and group files.
Feb 01 15:35:21 kenad systemd[1]: Stopped D-Bus System Message Bus.
Feb 01 15:35:21 kenad systemd[1]: Stopped ACPI event daemon.
Feb 01 15:35:21 kenad systemd[1]: Stopped Hardware Abstraction Layer.
Feb 01 15:35:21 kenad systemd[1]: Stopped CUPS Scheduler.
Feb 01 15:35:21 kenad systemd[1]: Reached target Network.
Feb 01 15:35:21 kenad systemd[1]: Starting Network.
Feb 01 15:35:21 kenad systemd[1]: Stopped Network Time Service.
Feb 01 15:35:21 kenad systemd[1]: Stopped Self Monitoring and Reporting Technology (SMART) Daemon.
Feb 01 15:35:21 kenad systemd[1]: Stopped Samba NetBIOS name server.
Feb 01 15:35:21 kenad systemd[1]: Stopped Samba SMB/CIFS server.
Feb 01 15:35:21 kenad systemd[1]: Stopped Modem Manager.
Feb 01 15:35:21 kenad systemd[1]: Stopped Network Manager.
Feb 01 15:35:21 kenad systemd[1]: Stopped target Multi-User System.
Feb 01 15:35:21 kenad systemd[1]: Stopped target Graphical Interface.
Feb 01 15:35:21 kenad systemd[1]: Stopped Daily Cleanup of Temporary Directories.
Feb 01 15:35:21 kenad systemd[1]: Closed CUPS Scheduler.
Feb 01 15:35:21 kenad systemd[1]: Dependency failed for File System Check on /dev/sda1.
Feb 01 15:35:21 kenad systemd[1]: Triggering OnFailure= dependencies of local-fs.target.
Feb 01 15:35:21 kenad systemd[1]: Dependency failed for Local File Systems.
Feb 01 15:35:21 kenad systemd[1]: Dependency failed for /home.
Feb 01 15:35:21 kenad systemd[1]: Timed out waiting for device dev-sda1.device.
Feb 01 15:35:21 kenad systemd[1]: Job dev-sda1.device/start timed out.
Feb 01 15:34:53 kenad systemd-udevd[204]: seq 1406 '/devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sda/sda1' killed
Feb 01 15:34:53 kenad systemd-udevd[204]: worker [205] /devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sda/sda1 timeout; kill it
Feb 01 15:34:23 kenad systemd-udevd[204]: seq 1412 '/devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:1/2:0:1:0/block/sr0' killed
Feb 01 15:34:23 kenad systemd-udevd[204]: worker [212] /devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:1/2:0:1:0/block/sr0 timeout; kill it
Feb 01 15:34:23 kenad systemd-udevd[204]: seq 1405 '/devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sda' killed
Feb 01 15:34:23 kenad systemd-udevd[204]: worker [211] /devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sda timeout; kill it
Feb 01 15:33:53 kenad kernel: mousedev: PS/2 mouse device common for all mice
Feb 01 15:33:53 kenad kernel: input: ImPS/2 Logitech Wheel Mouse as /devices/platform/i8042/serio1/input/input4
Feb 01 15:33:52 kenad kernel: input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input19
Feb 01 15:33:52 kenad kernel: input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input18
Feb 01 15:33:52 kenad kernel: input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input17
Feb 01 15:33:52 kenad kernel: input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input16
Feb 01 15:33:52 kenad systemd[1]: Started Load/Save Random Seed.
Feb 01 15:33:52 kenad kernel: EXT4-fs (sdb2): mounted filesystem with ordered data mode. Opts: data=ordered
Feb 01 15:33:52 kenad systemd[1]: Starting Load/Save Random Seed...
Feb 01 15:33:52 kenad systemd[1]: Mounted /var.
Feb 01 15:33:52 kenad systemd[1]: Mounting /var...
Feb 01 15:33:52 kenad systemd[1]: Started File System Check on /dev/sdb2.
Feb 01 15:33:52 kenad systemd-fsck[287]: /dev/sdb2: clean, 7774/786432 files, 2972328/3145728 blocks
Feb 01 15:33:52 kenad systemd-fsck[287]: /dev/sdb2: Clearing orphaned inode 655761 (uid=1000, gid=100, mode=0100600, size=512)
Feb 01 15:33:52 kenad systemd-fsck[287]: /dev/sdb2: Clearing orphaned inode 655775 (uid=1000, gid=100, mode=0100600, size=32768)
Feb 01 15:33:52 kenad systemd[1]: Mounted /boot.
Feb 01 15:33:52 kenad kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: data=ordered
Feb 01 15:33:52 kenad systemd-fsck[287]: /dev/sdb2: recovering journal
Feb 01 15:33:52 kenad systemd[1]: Starting File System Check on /dev/sdb2...
Feb 01 15:33:52 kenad systemd[1]: Found device KINGSTON_SV300S37A120G var.
Feb 01 15:33:52 kenad systemd[1]: Mounting /boot...
Feb 01 15:33:52 kenad systemd[1]: Started File System Check on /dev/sdb1.
Feb 01 15:33:52 kenad systemd-fsck[275]: /dev/sdb1: clean, 83/76912 files, 47115/307200 blocks
Feb 01 15:33:52 kenad systemd-fsck[275]: /dev/sdb1: recovering journal
Feb 01 15:33:52 kenad kernel: Adding 8388604k swap on /dev/sdb3.  Priority:-1 extents:1 across:8388604k SSFS
Feb 01 15:33:52 kenad systemd[1]: Reached target Swap.
Feb 01 15:33:52 kenad systemd[1]: Starting Swap.
Feb 01 15:33:52 kenad systemd[1]: Activated swap /dev/sdb3.
Feb 01 15:33:52 kenad systemd[1]: Activating swap /dev/sdb3...
Feb 01 15:33:52 kenad systemd[1]: Starting File System Check on /dev/sdb1...
Feb 01 15:33:52 kenad systemd[1]: Found device KINGSTON_SV300S37A120G boot.
Feb 01 15:33:52 kenad systemd[1]: Found device KINGSTON_SV300S37A120G swap.

In this case I endup in a root console where I can try to reboot cleanly (well sometimes and with patience).

I hope you have anything to point to. Browsing the net I tried to reinstall an old version of systemd (216) without success. The bug stated to occur after an upgrade to 218 but I am quite confident this is not related.

Do you think this is a hard drive problem and that the only solution is to change it ? Strange that nothing is detected either by fsck/smartctl. Maybe I do not use the correct fsck options ?

Thanks in advance for your help,

Tabs

nomorewindows · 2015-02-01 18:52:01

At the emergency shell, you should be able to fsck. Smartctl could tell you about your drives perceived health, but you aren't able to boot it.

Tabs · 2015-02-01 19:39:32

Thanks for getting into this nomorewindows,

As I said fsck does not report anything suspicious. And I forgot to mention that /dev/sda1 is my home parition, /dev/sdb is used for booting (/dev/sdb1 to be more precise contains the /boot partition).

Last edited by Tabs (2015-02-01 19:40:05)

nomorewindows · 2015-02-01 20:58:40

Are you sure you're booting from /dev/sdb1?

Tabs · 2015-02-01 21:29:19

100% sure. Here is the output of parted /dev/sdb print:

Model: ATA KINGSTON SV300S3 (scsi)
Disk /dev/sdb: 120GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system     Name  Flags
 1      1049kB  316MB   315MB   ext4            boot  legacy_boot
 2      316MB   13.2GB  12.9GB  ext4            var
 3      13.2GB  21.8GB  8590MB  linux-swap(v1)  swap
 4      21.8GB  120GB   98.2GB  ext4            root

And the one for /dev/sda:

Model: ATA ST2000DM001-9YN1 (scsi)
Disk /dev/sda: 2000GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      32.3kB  2000GB  2000GB  primary  ext4

I am often booting on parted magic to check the drives. From this place I tried to copy a big amount of data using dd from /dev/null to a file on disk (100 Go). This was achieved without any problem. This is why I am so confused:
- on one side every symptom points to a damaged disk;
- but every test I tried indicate that the disk work like a charm.

Last edited by Tabs (2015-02-01 21:34:16)

nomorewindows · 2015-02-01 21:40:20

Why is your /dev/sda using msdos partition table?

Head_on_a_Stick · 2015-02-01 21:55:51

You are not booting from /dev/sdb -- it is a GPT disk and it does not have a BIOS boot partition.

The bootloader must be in the MBR of /dev/sda

Tabs · 2015-02-02 07:56:31

nomorewindows: this is for historical reasons, I was simply not using GPT at that time and switched to GPT for the system drives when I installed Archlinux. Note that the switch was done 2 years ago and that I did not have any problem until now (well ok there is never a problem up to the moment it happens).

Head_On_a_Stick: I though that the legacy_boot flag indicates that the partition can be bootable. I also remenber that the bios is configured to boot on /dev/sdb. But this is only from memory and you might be right, I will check that this evening once I am out of work.

Last edited by Tabs (2015-02-02 07:57:51)

Tabs · 2015-02-02 19:16:17

So the bios is set to boot on KINGSTON SV300S3 (i.e. /dev/sdb)

The strange thing is that both /dev/sd{a,b} contains the bootable magic number (i.e. 0xAA55) at the end of their 512 sector. I am using syslinux as a boot loader and it is installed on /dev/sdb1. I also noted that the first bytes of the /dev/sdb first sector more or less correspond to the first bytes of the file /usr/lib/syslinux/bios/mbr.bin. All this seems to indicate that yes I do boot from /deb/sdb, maybe by uefi ? I have to say I do not remember how I did and I do not know how to check that.

Anyway the system is booting successfully how could that have an influence on my problem ?

Last edited by Tabs (2015-02-02 19:24:03)

Head_on_a_Stick · 2015-02-02 19:30:36

Tabs wrote:

The strange thing is that both /dev/sd{a,b} contains the bootable magic number (i.e. 0xAA55) at the end of their 512 sector. I am using syslinux as a boot loader and it is installed on /dev/sdb1. I also noted that the first bytes of the /dev/sdb first sector more or less correspond to the first bytes of the file /usr/lib/syslinux/bios/mbr.bin. All this seems to indicate that yes I do boot from /deb/sdb, maybe by uefi ? I have to say I do not remember how I did and I do not know how to check that.

The boot flag may be there but the bootloader is not -- read the links I posted.

For booting in EFI-mode, you would need an EFI system partition.

I have no idea what the cause of your problem is though.

Tabs · 2015-03-09 20:53:24

With respect to the bootloader: I removed my sda drive and replaced it by another one (without bootloader) and the system booted up successfully. Anyway I doubt this is related to my problem.

Now that I changed the drive I was expecting not to have troubles anymore but I still have them (exact same problems than reported i nthe first post). So now either it comes from the motherboard or from the system. Any advise of how to proceed ? Should I report a bug ? If yes where, on systemd or archlinux ?

Thanks for your help on this.

Tabs · 2015-03-11 20:11:24

Could you please tell me how to proceed ? i would like to make a bug report but where ?

Tabs · 2015-03-12 09:22:05

I noticed that the first task which is blocked is always jbd2/sda1-8. Maybe the journaling system is crashing ? Or there is a different problem and then the journaling system is always the first blocked because of that other problem.

Just trying to give my toughts and stimulate discussion.

Tabs · 2015-03-13 08:19:30

As a summary + news, I tried the following:
- change of hard drive-> same problem;
- change of partition system (from DOS to GPT) -> same problem;
- update of kernel (to 3.19.1) -> same problem;
- change of partition system (from ext4 to xfs) -> a similar log but with xfs process instead of etx4 journaling process;
- revert to LTS kernel -> no crash for more than one week problem solved.

I will report a kernel bug.

Last edited by Tabs (2015-03-24 19:20:16)

Arch Linux

#1 2015-02-01 15:21:21

Archlinux hangs at random times (seems like a hard drive problem)

#2 2015-02-01 18:52:01

Re: Archlinux hangs at random times (seems like a hard drive problem)

#3 2015-02-01 19:39:32

Re: Archlinux hangs at random times (seems like a hard drive problem)

#4 2015-02-01 20:58:40

Re: Archlinux hangs at random times (seems like a hard drive problem)

#5 2015-02-01 21:29:19

Re: Archlinux hangs at random times (seems like a hard drive problem)

#6 2015-02-01 21:40:20

Re: Archlinux hangs at random times (seems like a hard drive problem)

#7 2015-02-01 21:55:51

Re: Archlinux hangs at random times (seems like a hard drive problem)

#8 2015-02-02 07:56:31

Re: Archlinux hangs at random times (seems like a hard drive problem)

#9 2015-02-02 19:16:17

Re: Archlinux hangs at random times (seems like a hard drive problem)

#10 2015-02-02 19:30:36

Re: Archlinux hangs at random times (seems like a hard drive problem)

#11 2015-03-09 20:53:24

Re: Archlinux hangs at random times (seems like a hard drive problem)

#12 2015-03-11 20:11:24

Re: Archlinux hangs at random times (seems like a hard drive problem)

#13 2015-03-12 09:22:05

Re: Archlinux hangs at random times (seems like a hard drive problem)

#14 2015-03-13 08:19:30

Re: Archlinux hangs at random times (seems like a hard drive problem)

Board footer