Guest User

NUC10i5 - Ubuntu Server 20.04.02 - syslog

a guest
Feb 25th, 2021
94
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. Feb 25 13:03:22 nuc10i5 systemd[1]: Starting Message of the Day...
  2. Feb 25 13:03:24 nuc10i5 50-motd-news[28250]:  * Introducing self-healing high availability clusters in MicroK8s.
  3. Feb 25 13:03:24 nuc10i5 50-motd-news[28250]:    Simple, hardened, Kubernetes for production, from RaspberryPi to DC.
  4. Feb 25 13:03:24 nuc10i5 50-motd-news[28250]:      https://microk8s.io/high-availability
  5. Feb 25 13:03:24 nuc10i5 systemd[1]: motd-news.service: Succeeded.
  6. Feb 25 13:03:24 nuc10i5 systemd[1]: Finished Message of the Day.
  7. Feb 25 13:17:01 nuc10i5 CRON[28727]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
  8. Feb 25 13:24:49 nuc10i5 kernel: [20433.758435] nvme nvme0: I/O 896 QID 1 timeout, aborting
  9. Feb 25 13:24:49 nuc10i5 kernel: [20433.758445] nvme nvme0: I/O 946 QID 6 timeout, aborting
  10. Feb 25 13:24:49 nuc10i5 kernel: [20433.758447] nvme nvme0: I/O 947 QID 6 timeout, aborting
  11. Feb 25 13:24:49 nuc10i5 kernel: [20433.758450] nvme nvme0: I/O 428 QID 7 timeout, aborting
  12. Feb 25 13:24:49 nuc10i5 kernel: [20433.758452] nvme nvme0: I/O 429 QID 7 timeout, aborting
  13. Feb 25 13:25:20 nuc10i5 kernel: [20464.478093] nvme nvme0: I/O 896 QID 1 timeout, reset controller
  14. Feb 25 13:25:50 nuc10i5 kernel: [20495.197942] nvme nvme0: I/O 12 QID 0 timeout, reset controller
  15. Feb 25 13:26:37 nuc10i5 kernel: [20542.301810] INFO: task jbd2/nvme0n1p2-:354 blocked for more than 120 seconds.
  16. Feb 25 13:26:37 nuc10i5 kernel: [20542.301860]       Not tainted 5.4.0-65-generic #73-Ubuntu
  17. Feb 25 13:26:37 nuc10i5 kernel: [20542.301892] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  18. Feb 25 13:26:37 nuc10i5 kernel: [20542.301939] jbd2/nvme0n1p2- D    0   354      2 0x80004000
  19. Feb 25 13:26:37 nuc10i5 kernel: [20542.301940] Call Trace:
  20. Feb 25 13:26:37 nuc10i5 kernel: [20542.301945]  __schedule+0x2e3/0x740
  21. Feb 25 13:26:37 nuc10i5 kernel: [20542.301947]  ? dma_direct_map_sg+0x44/0xb0
  22. Feb 25 13:26:37 nuc10i5 kernel: [20542.301948]  schedule+0x42/0xb0
  23. Feb 25 13:26:37 nuc10i5 kernel: [20542.301949]  io_schedule+0x16/0x40
  24. Feb 25 13:26:37 nuc10i5 kernel: [20542.301950]  rq_qos_wait+0x106/0x180
  25. Feb 25 13:26:37 nuc10i5 kernel: [20542.301952]  ? __wbt_done+0x40/0x40
  26. Feb 25 13:26:37 nuc10i5 kernel: [20542.301952]  ? sysv68_partition+0x2d0/0x2d0
  27. Feb 25 13:26:37 nuc10i5 kernel: [20542.301953]  ? wbt_cleanup_cb+0x20/0x20
  28. Feb 25 13:26:37 nuc10i5 kernel: [20542.301954]  wbt_wait+0x9f/0xf0
  29. Feb 25 13:26:37 nuc10i5 kernel: [20542.301955]  __rq_qos_throttle+0x28/0x40
  30. Feb 25 13:26:37 nuc10i5 kernel: [20542.301957]  blk_mq_make_request+0x100/0x5b0
  31. Feb 25 13:26:37 nuc10i5 kernel: [20542.301958]  generic_make_request+0xcf/0x320
  32. Feb 25 13:26:37 nuc10i5 kernel: [20542.301959]  submit_bio+0x48/0x1d0
  33. Feb 25 13:26:37 nuc10i5 kernel: [20542.301960]  ? bio_add_page+0x6a/0x90
  34. Feb 25 13:26:37 nuc10i5 kernel: [20542.301962]  submit_bh_wbc+0x182/0x1b0
  35. Feb 25 13:26:37 nuc10i5 kernel: [20542.301963]  write_dirty_buffer+0x4e/0x90
  36. Feb 25 13:26:37 nuc10i5 kernel: [20542.301964]  flush_descriptor.part.0+0x3c/0x60
  37. Feb 25 13:26:37 nuc10i5 kernel: [20542.301965]  jbd2_journal_write_revoke_records+0x24b/0x270
  38. Feb 25 13:26:37 nuc10i5 kernel: [20542.301966]  jbd2_journal_commit_transaction+0x45b/0x17e8
  39. Feb 25 13:26:37 nuc10i5 kernel: [20542.301967]  ? __switch_to_asm+0x40/0x70
  40. Feb 25 13:26:37 nuc10i5 kernel: [20542.301968]  ? __switch_to_asm+0x34/0x70
  41. Feb 25 13:26:37 nuc10i5 kernel: [20542.301969]  ? __switch_to_asm+0x34/0x70
  42. Feb 25 13:26:37 nuc10i5 kernel: [20542.301970]  ? __switch_to_asm+0x40/0x70
  43. Feb 25 13:26:37 nuc10i5 kernel: [20542.301971]  ? __switch_to_asm+0x40/0x70
  44. Feb 25 13:26:37 nuc10i5 kernel: [20542.301972]  ? __switch_to_asm+0x40/0x70
  45. Feb 25 13:26:37 nuc10i5 kernel: [20542.301973]  ? __switch_to_asm+0x34/0x70
  46. Feb 25 13:26:37 nuc10i5 kernel: [20542.301974]  ? __switch_to_asm+0x34/0x70
  47. Feb 25 13:26:37 nuc10i5 kernel: [20542.301975]  ? try_to_del_timer_sync+0x54/0x80
  48. Feb 25 13:26:37 nuc10i5 kernel: [20542.301976]  kjournald2+0xb6/0x280
  49. Feb 25 13:26:37 nuc10i5 kernel: [20542.301978]  ? wait_woken+0x80/0x80
  50. Feb 25 13:26:37 nuc10i5 kernel: [20542.301979]  kthread+0x104/0x140
  51. Feb 25 13:26:37 nuc10i5 kernel: [20542.301980]  ? commit_timeout+0x20/0x20
  52. Feb 25 13:26:37 nuc10i5 kernel: [20542.301980]  ? kthread_park+0x90/0x90
  53. Feb 25 13:26:37 nuc10i5 kernel: [20542.301982]  ret_from_fork+0x1f/0x40
  54. Feb 25 13:26:37 nuc10i5 kernel: [20542.302026] INFO: task python3:4235 blocked for more than 120 seconds.
  55. Feb 25 13:26:37 nuc10i5 kernel: [20542.302066]       Not tainted 5.4.0-65-generic #73-Ubuntu
  56. Feb 25 13:26:37 nuc10i5 kernel: [20542.302098] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  57. Feb 25 13:26:37 nuc10i5 kernel: [20542.302145] python3         D    0  4235   3763 0x00000320
  58. Feb 25 13:26:37 nuc10i5 kernel: [20542.302146] Call Trace:
  59. Feb 25 13:26:37 nuc10i5 kernel: [20542.302147]  __schedule+0x2e3/0x740
  60. Feb 25 13:26:37 nuc10i5 kernel: [20542.302148]  ? bit_wait_timeout+0xa0/0xa0
  61. Feb 25 13:26:37 nuc10i5 kernel: [20542.302149]  schedule+0x42/0xb0
  62. Feb 25 13:26:37 nuc10i5 kernel: [20542.302150]  io_schedule+0x16/0x40
  63. Feb 25 13:26:37 nuc10i5 kernel: [20542.302151]  bit_wait_io+0x11/0x50
  64. Feb 25 13:26:37 nuc10i5 kernel: [20542.302151]  __wait_on_bit+0x33/0xa0
  65. Feb 25 13:26:37 nuc10i5 kernel: [20542.302152]  out_of_line_wait_on_bit+0x8d/0xb0
  66. Feb 25 13:26:37 nuc10i5 kernel: [20542.302153]  ? var_wake_function+0x30/0x30
  67. Feb 25 13:26:37 nuc10i5 kernel: [20542.302154]  __wait_on_buffer+0x34/0x40
  68. Feb 25 13:26:37 nuc10i5 kernel: [20542.302156]  ext4_block_write_begin+0x429/0x520
  69. Feb 25 13:26:37 nuc10i5 kernel: [20542.302157]  ? ext4_da_map_blocks.constprop.0+0x380/0x380
  70. Feb 25 13:26:37 nuc10i5 kernel: [20542.302159]  ? __ext4_journal_start_sb+0x69/0x120
  71. Feb 25 13:26:37 nuc10i5 kernel: [20542.302160]  ext4_da_write_begin+0x1cf/0x460
  72. Feb 25 13:26:37 nuc10i5 kernel: [20542.302162]  generic_perform_write+0xc2/0x1c0
  73. Feb 25 13:26:37 nuc10i5 kernel: [20542.302164]  ? file_update_time+0xf7/0x140
  74. Feb 25 13:26:37 nuc10i5 kernel: [20542.302165]  __generic_file_write_iter+0x107/0x1d0
  75. Feb 25 13:26:37 nuc10i5 kernel: [20542.302166]  ext4_file_write_iter+0xb9/0x360
  76. Feb 25 13:26:37 nuc10i5 kernel: [20542.302167]  new_sync_write+0x125/0x1c0
  77. Feb 25 13:26:37 nuc10i5 kernel: [20542.302168]  __vfs_write+0x29/0x40
  78. Feb 25 13:26:37 nuc10i5 kernel: [20542.302169]  vfs_write+0xb9/0x1a0
  79. Feb 25 13:26:37 nuc10i5 kernel: [20542.302170]  ksys_write+0x67/0xe0
  80. Feb 25 13:26:37 nuc10i5 kernel: [20542.302171]  __x64_sys_write+0x1a/0x20
  81. Feb 25 13:26:37 nuc10i5 kernel: [20542.302173]  do_syscall_64+0x57/0x190
  82. Feb 25 13:26:37 nuc10i5 kernel: [20542.302174]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  83. Feb 25 13:26:37 nuc10i5 kernel: [20542.302175] RIP: 0033:0x7f542edf4257
  84. Feb 25 13:26:37 nuc10i5 kernel: [20542.302178] Code: Bad RIP value.
  85. Feb 25 13:26:37 nuc10i5 kernel: [20542.302179] RSP: 002b:00007f5401ff8b00 EFLAGS: 00000293 ORIG_RAX: 0000000000000001
  86. Feb 25 13:26:37 nuc10i5 kernel: [20542.302180] RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f542edf4257
  87. Feb 25 13:26:37 nuc10i5 kernel: [20542.302180] RDX: 00000000000000de RSI: 00007f53f0008e40 RDI: 0000000000000003
  88. Feb 25 13:26:37 nuc10i5 kernel: [20542.302181] RBP: 00007f53f0008e40 R08: 0000000000000000 R09: 0000000000000000
  89. Feb 25 13:26:37 nuc10i5 kernel: [20542.302181] R10: 0000000000000000 R11: 0000000000000293 R12: 00000000000000de
  90. Feb 25 13:26:37 nuc10i5 kernel: [20542.302181] R13: 00007f53f0008e40 R14: 00000000004cb420 R15: 0000000002821820
  91. Feb 25 13:26:37 nuc10i5 kernel: [20542.302201] INFO: task kworker/u16:6:27762 blocked for more than 120 seconds.
  92. Feb 25 13:26:37 nuc10i5 kernel: [20542.302244]       Not tainted 5.4.0-65-generic #73-Ubuntu
  93. Feb 25 13:26:37 nuc10i5 kernel: [20542.302276] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  94. Feb 25 13:26:37 nuc10i5 kernel: [20542.302323] kworker/u16:6   D    0 27762      2 0x80004000
  95. Feb 25 13:26:37 nuc10i5 kernel: [20542.302325] Workqueue: writeback wb_workfn (flush-259:0)
  96. Feb 25 13:26:37 nuc10i5 kernel: [20542.302326] Call Trace:
  97. Feb 25 13:26:37 nuc10i5 kernel: [20542.302327]  __schedule+0x2e3/0x740
  98. Feb 25 13:26:37 nuc10i5 kernel: [20542.302328]  schedule+0x42/0xb0
  99. Feb 25 13:26:37 nuc10i5 kernel: [20542.302329]  io_schedule+0x16/0x40
  100. Feb 25 13:26:37 nuc10i5 kernel: [20542.302330]  rq_qos_wait+0x106/0x180
  101. Feb 25 13:26:37 nuc10i5 kernel: [20542.302331]  ? __wbt_done+0x40/0x40
  102. Feb 25 13:26:37 nuc10i5 kernel: [20542.302331]  ? sysv68_partition+0x2d0/0x2d0
  103. Feb 25 13:26:37 nuc10i5 kernel: [20542.302332]  ? wbt_cleanup_cb+0x20/0x20
  104. Feb 25 13:26:37 nuc10i5 kernel: [20542.302333]  wbt_wait+0x9f/0xf0
  105. Feb 25 13:26:37 nuc10i5 kernel: [20542.302334]  __rq_qos_throttle+0x28/0x40
  106. Feb 25 13:26:37 nuc10i5 kernel: [20542.302335]  blk_mq_make_request+0x100/0x5b0
  107. Feb 25 13:26:37 nuc10i5 kernel: [20542.302336]  generic_make_request+0xcf/0x320
  108. Feb 25 13:26:37 nuc10i5 kernel: [20542.302336]  submit_bio+0x48/0x1d0
  109. Feb 25 13:26:37 nuc10i5 kernel: [20542.302338]  ext4_io_submit+0x4d/0x60
  110. Feb 25 13:26:37 nuc10i5 kernel: [20542.302339]  ext4_writepages+0x673/0x950
  111. Feb 25 13:26:37 nuc10i5 kernel: [20542.302340]  do_writepages+0x43/0xd0
  112. Feb 25 13:26:37 nuc10i5 kernel: [20542.302341]  ? do_writepages+0x43/0xd0
  113. Feb 25 13:26:37 nuc10i5 kernel: [20542.302342]  ? ttwu_do_wakeup+0x1e/0x150
  114. Feb 25 13:26:37 nuc10i5 kernel: [20542.302345]  __writeback_single_inode+0x44/0x350
  115. Feb 25 13:26:37 nuc10i5 kernel: [20542.302346]  writeback_sb_inodes+0x22d/0x4b0
  116. Feb 25 13:26:37 nuc10i5 kernel: [20542.302348]  __writeback_inodes_wb+0x56/0xf0
  117. Feb 25 13:26:37 nuc10i5 kernel: [20542.302349]  wb_writeback+0x20c/0x2f0
  118. Feb 25 13:26:37 nuc10i5 kernel: [20542.302350]  ? dev_map_alloc+0x50/0x270
  119. Feb 25 13:26:37 nuc10i5 kernel: [20542.302351]  ? cpumask_next+0x1b/0x20
  120. Feb 25 13:26:37 nuc10i5 kernel: [20542.302352]  wb_workfn+0x3a5/0x4f0
  121. Feb 25 13:26:37 nuc10i5 kernel: [20542.302353]  ? __switch_to_asm+0x40/0x70
  122. Feb 25 13:26:37 nuc10i5 kernel: [20542.302354]  ? __switch_to_asm+0x34/0x70
  123. Feb 25 13:26:37 nuc10i5 kernel: [20542.302355]  ? __switch_to_asm+0x40/0x70
  124. Feb 25 13:26:37 nuc10i5 kernel: [20542.302356]  ? __switch_to_asm+0x34/0x70
  125. Feb 25 13:26:37 nuc10i5 kernel: [20542.302357]  ? __switch_to_asm+0x40/0x70
  126. Feb 25 13:26:37 nuc10i5 kernel: [20542.302358]  ? __switch_to+0x7f/0x470
  127. Feb 25 13:26:37 nuc10i5 kernel: [20542.302359]  ? __switch_to_asm+0x40/0x70
  128. Feb 25 13:26:37 nuc10i5 kernel: [20542.302360]  ? __switch_to_asm+0x34/0x70
  129. Feb 25 13:26:37 nuc10i5 kernel: [20542.302362]  process_one_work+0x1eb/0x3b0
  130. Feb 25 13:26:37 nuc10i5 kernel: [20542.302363]  worker_thread+0x4d/0x400
  131. Feb 25 13:26:37 nuc10i5 kernel: [20542.302364]  kthread+0x104/0x140
  132. Feb 25 13:26:37 nuc10i5 kernel: [20542.302365]  ? process_one_work+0x3b0/0x3b0
  133. Feb 25 13:26:37 nuc10i5 kernel: [20542.302365]  ? kthread_park+0x90/0x90
  134. Feb 25 13:26:37 nuc10i5 kernel: [20542.302366]  ret_from_fork+0x1f/0x40
  135. Feb 25 13:28:22 nuc10i5 kernel: [20646.493369] nvme nvme0: Device not ready; aborting reset
  136. Feb 25 13:28:22 nuc10i5 kernel: [20646.509541] blk_update_request: I/O error, dev nvme0n1, sector 652083392 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
  137. Feb 25 13:28:22 nuc10i5 kernel: [20646.509573] blk_update_request: I/O error, dev nvme0n1, sector 118437640 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0
  138. Feb 25 13:28:22 nuc10i5 kernel: [20646.509619] blk_update_request: I/O error, dev nvme0n1, sector 118437896 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0
  139. Feb 25 13:28:22 nuc10i5 kernel: [20646.509654] nvme nvme0: Abort status: 0x371
  140. Feb 25 13:28:22 nuc10i5 kernel: [20646.509655] nvme nvme0: Abort status: 0x371
  141. Feb 25 13:28:22 nuc10i5 kernel: [20646.509656] nvme nvme0: Abort status: 0x371
  142. Feb 25 13:28:22 nuc10i5 kernel: [20646.509656] nvme nvme0: Abort status: 0x371
  143. Feb 25 13:28:22 nuc10i5 kernel: [20646.509657] nvme nvme0: Abort status: 0x371
  144. Feb 25 13:28:38 nuc10i5 kernel: [20663.133387] INFO: task qbittorrent-nox:2892 blocked for more than 120 seconds.
  145. Feb 25 13:28:38 nuc10i5 kernel: [20663.133408]       Not tainted 5.4.0-65-generic #73-Ubuntu
  146. Feb 25 13:28:38 nuc10i5 kernel: [20663.133420] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  147. Feb 25 13:28:38 nuc10i5 kernel: [20663.133437] qbittorrent-nox D    0  2892   2889 0x00004320
  148. Feb 25 13:28:38 nuc10i5 kernel: [20663.133438] Call Trace:
  149. Feb 25 13:28:38 nuc10i5 kernel: [20663.133443]  __schedule+0x2e3/0x740
  150. Feb 25 13:28:38 nuc10i5 kernel: [20663.133446]  ? __ext4_handle_dirty_metadata+0x58/0x1a0
  151. Feb 25 13:28:38 nuc10i5 kernel: [20663.133447]  schedule+0x42/0xb0
  152. Feb 25 13:28:38 nuc10i5 kernel: [20663.133449]  blk_queue_enter+0x160/0x200
  153. Feb 25 13:28:38 nuc10i5 kernel: [20663.133450]  ? wait_woken+0x80/0x80
  154. Feb 25 13:28:38 nuc10i5 kernel: [20663.133451]  generic_make_request+0x94/0x320
  155. Feb 25 13:28:38 nuc10i5 kernel: [20663.133453]  ? jbd2_journal_stop+0xf2/0x400
  156. Feb 25 13:28:38 nuc10i5 kernel: [20663.133454]  submit_bio+0x48/0x1d0
  157. Feb 25 13:28:38 nuc10i5 kernel: [20663.133456]  ext4_io_submit+0x4d/0x60
  158. Feb 25 13:28:38 nuc10i5 kernel: [20663.133456]  ext4_writepages+0x673/0x950
  159. Feb 25 13:28:38 nuc10i5 kernel: [20663.133459]  do_writepages+0x43/0xd0
  160. Feb 25 13:28:38 nuc10i5 kernel: [20663.133460]  ? do_writepages+0x43/0xd0
  161. Feb 25 13:28:38 nuc10i5 kernel: [20663.133461]  __filemap_fdatawrite_range+0xd5/0x110
  162. Feb 25 13:28:38 nuc10i5 kernel: [20663.133463]  file_write_and_wait_range+0x74/0xc0
  163. Feb 25 13:28:38 nuc10i5 kernel: [20663.133464]  ext4_sync_file+0x8f/0x3b0
  164. Feb 25 13:28:38 nuc10i5 kernel: [20663.133465]  vfs_fsync_range+0x49/0x80
  165. Feb 25 13:28:38 nuc10i5 kernel: [20663.133467]  ? __fget_light+0x57/0x70
  166. Feb 25 13:28:38 nuc10i5 kernel: [20663.133468]  do_fsync+0x3d/0x70
  167. Feb 25 13:28:38 nuc10i5 kernel: [20663.133469]  __x64_sys_fdatasync+0x17/0x20
  168. Feb 25 13:28:38 nuc10i5 kernel: [20663.133471]  do_syscall_64+0x57/0x190
  169. Feb 25 13:28:38 nuc10i5 kernel: [20663.133472]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  170. Feb 25 13:28:38 nuc10i5 kernel: [20663.133473] RIP: 0033:0x7f54a9d6c3eb
  171. Feb 25 13:28:38 nuc10i5 kernel: [20663.133477] Code: Bad RIP value.
  172. Feb 25 13:28:38 nuc10i5 kernel: [20663.133477] RSP: 002b:00007ffc3bdff640 EFLAGS: 00000293 ORIG_RAX: 000000000000004b
  173. Feb 25 13:28:38 nuc10i5 kernel: [20663.133479] RAX: ffffffffffffffda RBX: 0000000000000067 RCX: 00007f54a9d6c3eb
  174. Feb 25 13:28:38 nuc10i5 kernel: [20663.133479] RDX: 0000000000000067 RSI: 000056261ee1b2a8 RDI: 000000000000000e
  175. Feb 25 13:28:38 nuc10i5 kernel: [20663.133479] RBP: 000000000000000e R08: 0000000000000000 R09: 000056261edc5e2c
  176. Feb 25 13:28:38 nuc10i5 kernel: [20663.133480] R10: 0000000000000020 R11: 0000000000000293 R12: 000056261ee1b2a8
  177. Feb 25 13:28:38 nuc10i5 kernel: [20663.133480] R13: 0000000000000067 R14: 0000000000000067 R15: 000056261ee1b290
  178. Feb 25 13:28:38 nuc10i5 kernel: [20663.133484] INFO: task Radarr:28978 blocked for more than 120 seconds.
  179. Feb 25 13:28:38 nuc10i5 kernel: [20663.133498]       Not tainted 5.4.0-65-generic #73-Ubuntu
  180. Feb 25 13:28:38 nuc10i5 kernel: [20663.133511] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  181. Feb 25 13:28:38 nuc10i5 kernel: [20663.133528] Radarr          D    0 28978   2942 0x00004320
  182. Feb 25 13:28:38 nuc10i5 kernel: [20663.133528] Call Trace:
  183. Feb 25 13:28:38 nuc10i5 kernel: [20663.133530]  __schedule+0x2e3/0x740
  184. Feb 25 13:28:38 nuc10i5 kernel: [20663.133531]  schedule+0x42/0xb0
  185. Feb 25 13:28:38 nuc10i5 kernel: [20663.133532]  blk_queue_enter+0x160/0x200
  186. Feb 25 13:28:38 nuc10i5 kernel: [20663.133533]  ? wait_woken+0x80/0x80
  187. Feb 25 13:28:38 nuc10i5 kernel: [20663.133533]  generic_make_request+0x94/0x320
  188. Feb 25 13:28:38 nuc10i5 kernel: [20663.133535]  ? jbd2_journal_stop+0xf2/0x400
  189. Feb 25 13:28:38 nuc10i5 kernel: [20663.133535]  submit_bio+0x48/0x1d0
  190. Feb 25 13:28:38 nuc10i5 kernel: [20663.133537]  ext4_io_submit+0x4d/0x60
  191. Feb 25 13:28:38 nuc10i5 kernel: [20663.133537]  ext4_writepages+0x673/0x950
  192. Feb 25 13:28:38 nuc10i5 kernel: [20663.133539]  do_writepages+0x43/0xd0
  193. Feb 25 13:28:38 nuc10i5 kernel: [20663.133540]  ? do_writepages+0x43/0xd0
  194. Feb 25 13:28:38 nuc10i5 kernel: [20663.133541]  __filemap_fdatawrite_range+0xd5/0x110
  195. Feb 25 13:28:38 nuc10i5 kernel: [20663.133542]  file_write_and_wait_range+0x74/0xc0
  196. Feb 25 13:28:38 nuc10i5 kernel: [20663.133543]  ext4_sync_file+0x8f/0x3b0
  197. Feb 25 13:28:38 nuc10i5 kernel: [20663.133544]  vfs_fsync_range+0x49/0x80
  198. Feb 25 13:28:38 nuc10i5 kernel: [20663.133545]  ? __fget_light+0x57/0x70
  199. Feb 25 13:28:38 nuc10i5 kernel: [20663.133546]  do_fsync+0x3d/0x70
  200. Feb 25 13:28:38 nuc10i5 kernel: [20663.133547]  __x64_sys_fdatasync+0x17/0x20
  201. Feb 25 13:28:38 nuc10i5 kernel: [20663.133548]  do_syscall_64+0x57/0x190
  202. Feb 25 13:28:38 nuc10i5 kernel: [20663.133549]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  203. Feb 25 13:28:38 nuc10i5 kernel: [20663.133549] RIP: 0033:0x7efe47f343eb
  204. Feb 25 13:28:38 nuc10i5 kernel: [20663.133550] Code: Bad RIP value.
  205. Feb 25 13:28:38 nuc10i5 kernel: [20663.133551] RSP: 002b:00007efda5ff7cb0 EFLAGS: 00000293 ORIG_RAX: 000000000000004b
  206. Feb 25 13:28:38 nuc10i5 kernel: [20663.133552] RAX: ffffffffffffffda RBX: 00007efd5802dc68 RCX: 00007efe47f343eb
  207. Feb 25 13:28:38 nuc10i5 kernel: [20663.133552] RDX: 0000000000000020 RSI: 0000000000000002 RDI: 00000000000000e2
  208. Feb 25 13:28:38 nuc10i5 kernel: [20663.133552] RBP: 000000000000000a R08: 0000000000000000 R09: 00000000a7fd23f9
  209. Feb 25 13:28:38 nuc10i5 kernel: [20663.133553] R10: 0000000000000000 R11: 0000000000000293 R12: 00007efd5803e5d0
  210. Feb 25 13:28:38 nuc10i5 kernel: [20663.133553] R13: 0000000000000000 R14: 00007efda5ff7d60 R15: 00007efd5802dbd8
  211. Feb 25 13:28:38 nuc10i5 kernel: [20663.133557] INFO: task python3:4235 blocked for more than 241 seconds.
  212. Feb 25 13:28:38 nuc10i5 kernel: [20663.133571]       Not tainted 5.4.0-65-generic #73-Ubuntu
  213. Feb 25 13:28:38 nuc10i5 kernel: [20663.133583] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  214. Feb 25 13:28:38 nuc10i5 kernel: [20663.133599] python3         D    0  4235   3763 0x00000320
  215. Feb 25 13:28:38 nuc10i5 kernel: [20663.133600] Call Trace:
  216. Feb 25 13:28:38 nuc10i5 kernel: [20663.133601]  __schedule+0x2e3/0x740
  217. Feb 25 13:28:38 nuc10i5 kernel: [20663.133602]  ? bit_wait_timeout+0xa0/0xa0
  218. Feb 25 13:28:38 nuc10i5 kernel: [20663.133603]  schedule+0x42/0xb0
  219. Feb 25 13:28:38 nuc10i5 kernel: [20663.133604]  io_schedule+0x16/0x40
  220. Feb 25 13:28:38 nuc10i5 kernel: [20663.133604]  bit_wait_io+0x11/0x50
  221. Feb 25 13:28:38 nuc10i5 kernel: [20663.133605]  __wait_on_bit+0x33/0xa0
  222. Feb 25 13:28:38 nuc10i5 kernel: [20663.133606]  out_of_line_wait_on_bit+0x8d/0xb0
  223. Feb 25 13:28:38 nuc10i5 kernel: [20663.133607]  ? var_wake_function+0x30/0x30
  224. Feb 25 13:28:38 nuc10i5 kernel: [20663.133608]  __wait_on_buffer+0x34/0x40
  225. Feb 25 13:28:38 nuc10i5 kernel: [20663.133610]  ext4_block_write_begin+0x429/0x520
  226. Feb 25 13:28:38 nuc10i5 kernel: [20663.133611]  ? ext4_da_map_blocks.constprop.0+0x380/0x380
  227. Feb 25 13:28:38 nuc10i5 kernel: [20663.133612]  ? __ext4_journal_start_sb+0x69/0x120
  228. Feb 25 13:28:38 nuc10i5 kernel: [20663.133613]  ext4_da_write_begin+0x1cf/0x460
  229. Feb 25 13:28:38 nuc10i5 kernel: [20663.133614]  generic_perform_write+0xc2/0x1c0
  230. Feb 25 13:28:38 nuc10i5 kernel: [20663.133616]  ? file_update_time+0xf7/0x140
  231. Feb 25 13:28:38 nuc10i5 kernel: [20663.133617]  __generic_file_write_iter+0x107/0x1d0
  232. Feb 25 13:28:38 nuc10i5 kernel: [20663.133618]  ext4_file_write_iter+0xb9/0x360
  233. Feb 25 13:28:38 nuc10i5 kernel: [20663.133620]  new_sync_write+0x125/0x1c0
  234. Feb 25 13:28:38 nuc10i5 kernel: [20663.133621]  __vfs_write+0x29/0x40
  235. Feb 25 13:28:38 nuc10i5 kernel: [20663.133622]  vfs_write+0xb9/0x1a0
  236. Feb 25 13:28:38 nuc10i5 kernel: [20663.133623]  ksys_write+0x67/0xe0
  237. Feb 25 13:28:38 nuc10i5 kernel: [20663.133624]  __x64_sys_write+0x1a/0x20
  238. Feb 25 13:28:38 nuc10i5 kernel: [20663.133625]  do_syscall_64+0x57/0x190
  239. Feb 25 13:28:38 nuc10i5 kernel: [20663.133626]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  240. Feb 25 13:28:38 nuc10i5 kernel: [20663.133627] RIP: 0033:0x7f542edf4257
  241. Feb 25 13:28:38 nuc10i5 kernel: [20663.133627] Code: Bad RIP value.
  242. Feb 25 13:28:38 nuc10i5 kernel: [20663.133628] RSP: 002b:00007f5401ff8b00 EFLAGS: 00000293 ORIG_RAX: 0000000000000001
  243. Feb 25 13:28:38 nuc10i5 kernel: [20663.133628] RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f542edf4257
  244. Feb 25 13:28:38 nuc10i5 kernel: [20663.133629] RDX: 00000000000000de RSI: 00007f53f0008e40 RDI: 0000000000000003
  245. Feb 25 13:28:38 nuc10i5 kernel: [20663.133629] RBP: 00007f53f0008e40 R08: 0000000000000000 R09: 0000000000000000
  246. Feb 25 13:28:38 nuc10i5 kernel: [20663.133630] R10: 0000000000000000 R11: 0000000000000293 R12: 00000000000000de
  247. Feb 25 13:28:38 nuc10i5 kernel: [20663.133630] R13: 00007f53f0008e40 R14: 00000000004cb420 R15: 0000000002821820
  248. Feb 25 13:30:22 nuc10i5 kernel: [20767.100740] nvme nvme0: Device not ready; aborting reset
  249. Feb 25 13:30:22 nuc10i5 kernel: [20767.100796] nvme nvme0: Removing after probe failure status: -19
  250. Feb 25 13:30:39 nuc10i5 kernel: [20783.964708] INFO: task jbd2/nvme0n1p2-:354 blocked for more than 120 seconds.
  251. Feb 25 13:30:39 nuc10i5 kernel: [20783.964729]       Not tainted 5.4.0-65-generic #73-Ubuntu
  252. Feb 25 13:30:39 nuc10i5 kernel: [20783.964741] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  253. Feb 25 13:30:39 nuc10i5 kernel: [20783.964758] jbd2/nvme0n1p2- D    0   354      2 0x80004000
  254. Feb 25 13:30:39 nuc10i5 kernel: [20783.964759] Call Trace:
  255. Feb 25 13:30:39 nuc10i5 kernel: [20783.964764]  __schedule+0x2e3/0x740
  256. Feb 25 13:30:39 nuc10i5 kernel: [20783.964765]  schedule+0x42/0xb0
  257. Feb 25 13:30:39 nuc10i5 kernel: [20783.964767]  blk_queue_enter+0x160/0x200
  258. Feb 25 13:30:39 nuc10i5 kernel: [20783.964769]  ? wait_woken+0x80/0x80
  259. Feb 25 13:30:39 nuc10i5 kernel: [20783.964770]  generic_make_request+0x94/0x320
  260. Feb 25 13:30:39 nuc10i5 kernel: [20783.964771]  submit_bio+0x48/0x1d0
  261. Feb 25 13:30:39 nuc10i5 kernel: [20783.964772]  ? bio_add_page+0x6a/0x90
  262. Feb 25 13:30:39 nuc10i5 kernel: [20783.964774]  submit_bh_wbc+0x182/0x1b0
  263. Feb 25 13:30:39 nuc10i5 kernel: [20783.964775]  submit_bh+0x13/0x20
  264. Feb 25 13:30:39 nuc10i5 kernel: [20783.964776]  jbd2_journal_commit_transaction+0x5cc/0x17e8
  265. Feb 25 13:30:39 nuc10i5 kernel: [20783.964778]  ? __switch_to_asm+0x40/0x70
  266. Feb 25 13:30:39 nuc10i5 kernel: [20783.964779]  kjournald2+0xb6/0x280
  267. Feb 25 13:30:39 nuc10i5 kernel: [20783.964780]  ? wait_woken+0x80/0x80
  268. Feb 25 13:30:39 nuc10i5 kernel: [20783.964782]  kthread+0x104/0x140
  269. Feb 25 13:30:39 nuc10i5 kernel: [20783.964782]  ? commit_timeout+0x20/0x20
  270. Feb 25 13:30:39 nuc10i5 kernel: [20783.964783]  ? kthread_park+0x90/0x90
  271. Feb 25 13:30:39 nuc10i5 kernel: [20783.964784]  ret_from_fork+0x1f/0x40
  272. Feb 25 13:30:39 nuc10i5 kernel: [20783.964786] INFO: task systemd-journal:435 blocked for more than 120 seconds.
  273. Feb 25 13:30:39 nuc10i5 kernel: [20783.964801]       Not tainted 5.4.0-65-generic #73-Ubuntu
  274. Feb 25 13:30:39 nuc10i5 kernel: [20783.964826] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  275. Feb 25 13:30:39 nuc10i5 kernel: [20783.964842] systemd-journal D    0   435      1 0x00004320
  276. Feb 25 13:30:39 nuc10i5 kernel: [20783.964842] Call Trace:
  277. Feb 25 13:30:39 nuc10i5 kernel: [20783.964844]  __schedule+0x2e3/0x740
  278. Feb 25 13:30:39 nuc10i5 kernel: [20783.964845]  schedule+0x42/0xb0
  279. Feb 25 13:30:39 nuc10i5 kernel: [20783.964845]  io_schedule+0x16/0x40
  280. Feb 25 13:30:39 nuc10i5 kernel: [20783.964848]  wait_on_page_bit+0x11c/0x200
  281. Feb 25 13:30:39 nuc10i5 kernel: [20783.964849]  ? file_fdatawait_range+0x30/0x30
  282. Feb 25 13:30:39 nuc10i5 kernel: [20783.964850]  wait_on_page_writeback+0x43/0x90
  283. Feb 25 13:30:39 nuc10i5 kernel: [20783.964851]  __filemap_fdatawait_range+0x98/0x100
  284. Feb 25 13:30:39 nuc10i5 kernel: [20783.964852]  ? __filemap_fdatawrite_range+0xe1/0x110
  285. Feb 25 13:30:39 nuc10i5 kernel: [20783.964853]  file_write_and_wait_range+0xa0/0xc0
  286. Feb 25 13:30:39 nuc10i5 kernel: [20783.964855]  ext4_sync_file+0x8f/0x3b0
  287. Feb 25 13:30:39 nuc10i5 kernel: [20783.964856]  vfs_fsync_range+0x49/0x80
  288. Feb 25 13:30:39 nuc10i5 kernel: [20783.964857]  do_fsync+0x3d/0x70
  289. Feb 25 13:30:39 nuc10i5 kernel: [20783.964857]  __x64_sys_fsync+0x14/0x20
  290. Feb 25 13:30:39 nuc10i5 kernel: [20783.964859]  do_syscall_64+0x57/0x190
  291. Feb 25 13:30:39 nuc10i5 kernel: [20783.964860]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  292. Feb 25 13:30:39 nuc10i5 kernel: [20783.964861] RIP: 0033:0x7f99241ea32b
  293. Feb 25 13:30:39 nuc10i5 kernel: [20783.964865] Code: Bad RIP value.
  294. Feb 25 13:30:39 nuc10i5 kernel: [20783.964865] RSP: 002b:00007ffe82a184f0 EFLAGS: 00000293 ORIG_RAX: 000000000000004a
  295. Feb 25 13:30:39 nuc10i5 kernel: [20783.964866] RAX: ffffffffffffffda RBX: 000055af75d42890 RCX: 00007f99241ea32b
  296. Feb 25 13:30:39 nuc10i5 kernel: [20783.964867] RDX: 00007f99242cb000 RSI: 000055af75d3d730 RDI: 0000000000000016
  297. Feb 25 13:30:39 nuc10i5 kernel: [20783.964867] RBP: 0000000000000001 R08: 0000000000000000 R09: 00007ffe82a18648
  298. Feb 25 13:30:39 nuc10i5 kernel: [20783.964867] R10: 00007f9924035848 R11: 0000000000000293 R12: 00007ffe82a18648
  299. Feb 25 13:30:39 nuc10i5 kernel: [20783.964868] R13: 00007ffe82a18640 R14: 000055af75d42890 R15: 000055af75d56150
  300. Feb 25 13:30:39 nuc10i5 kernel: [20783.964911] INFO: task qbittorrent-nox:2892 blocked for more than 241 seconds.
  301. Feb 25 13:30:39 nuc10i5 kernel: [20783.964926]       Not tainted 5.4.0-65-generic #73-Ubuntu
  302. Feb 25 13:30:39 nuc10i5 kernel: [20783.964937] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  303. Feb 25 13:30:39 nuc10i5 kernel: [20783.964952] qbittorrent-nox D    0  2892   2889 0x00004320
  304. Feb 25 13:30:39 nuc10i5 kernel: [20783.964953] Call Trace:
  305. Feb 25 13:30:39 nuc10i5 kernel: [20783.964954]  __schedule+0x2e3/0x740
  306. Feb 25 13:30:39 nuc10i5 kernel: [20783.964956]  ? __ext4_handle_dirty_metadata+0x58/0x1a0
  307. Feb 25 13:30:39 nuc10i5 kernel: [20783.964957]  schedule+0x42/0xb0
  308. Feb 25 13:30:39 nuc10i5 kernel: [20783.964958]  blk_queue_enter+0x160/0x200
  309. Feb 25 13:30:39 nuc10i5 kernel: [20783.964959]  ? wait_woken+0x80/0x80
  310. Feb 25 13:30:39 nuc10i5 kernel: [20783.964960]  generic_make_request+0x94/0x320
  311. Feb 25 13:30:39 nuc10i5 kernel: [20783.964961]  ? jbd2_journal_stop+0xf2/0x400
  312. Feb 25 13:30:39 nuc10i5 kernel: [20783.964962]  submit_bio+0x48/0x1d0
  313. Feb 25 13:30:39 nuc10i5 kernel: [20783.964964]  ext4_io_submit+0x4d/0x60
  314. Feb 25 13:30:39 nuc10i5 kernel: [20783.964965]  ext4_writepages+0x673/0x950
  315. Feb 25 13:30:39 nuc10i5 kernel: [20783.964966]  do_writepages+0x43/0xd0
  316. Feb 25 13:30:39 nuc10i5 kernel: [20783.964967]  ? do_writepages+0x43/0xd0
  317. Feb 25 13:30:39 nuc10i5 kernel: [20783.964968]  __filemap_fdatawrite_range+0xd5/0x110
  318. Feb 25 13:30:39 nuc10i5 kernel: [20783.964970]  file_write_and_wait_range+0x74/0xc0
  319. Feb 25 13:30:39 nuc10i5 kernel: [20783.964971]  ext4_sync_file+0x8f/0x3b0
  320. Feb 25 13:30:39 nuc10i5 kernel: [20783.964971]  vfs_fsync_range+0x49/0x80
  321. Feb 25 13:30:39 nuc10i5 kernel: [20783.964973]  ? __fget_light+0x57/0x70
  322. Feb 25 13:30:39 nuc10i5 kernel: [20783.964974]  do_fsync+0x3d/0x70
  323. Feb 25 13:30:39 nuc10i5 kernel: [20783.964974]  __x64_sys_fdatasync+0x17/0x20
  324. Feb 25 13:30:39 nuc10i5 kernel: [20783.964975]  do_syscall_64+0x57/0x190
  325. Feb 25 13:30:39 nuc10i5 kernel: [20783.964977]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  326. Feb 25 13:30:39 nuc10i5 kernel: [20783.964977] RIP: 0033:0x7f54a9d6c3eb
  327. Feb 25 13:30:39 nuc10i5 kernel: [20783.964978] Code: Bad RIP value.
  328. Feb 25 13:30:39 nuc10i5 kernel: [20783.964978] RSP: 002b:00007ffc3bdff640 EFLAGS: 00000293 ORIG_RAX: 000000000000004b
  329. Feb 25 13:30:39 nuc10i5 kernel: [20783.964979] RAX: ffffffffffffffda RBX: 0000000000000067 RCX: 00007f54a9d6c3eb
  330. Feb 25 13:30:39 nuc10i5 kernel: [20783.964979] RDX: 0000000000000067 RSI: 000056261ee1b2a8 RDI: 000000000000000e
  331. Feb 25 13:30:39 nuc10i5 kernel: [20783.964980] RBP: 000000000000000e R08: 0000000000000000 R09: 000056261edc5e2c
  332. Feb 25 13:30:39 nuc10i5 kernel: [20783.964980] R10: 0000000000000020 R11: 0000000000000293 R12: 000056261ee1b2a8
  333. Feb 25 13:30:39 nuc10i5 kernel: [20783.964981] R13: 0000000000000067 R14: 0000000000000067 R15: 000056261ee1b290
  334. Feb 25 13:30:39 nuc10i5 kernel: [20783.964984] INFO: task Radarr:28978 blocked for more than 241 seconds.
  335. Feb 25 13:30:39 nuc10i5 kernel: [20783.964998]       Not tainted 5.4.0-65-generic #73-Ubuntu
  336. Feb 25 13:30:39 nuc10i5 kernel: [20783.965009] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
  337. Feb 25 13:30:39 nuc10i5 kernel: [20783.965024] Radarr          D    0 28978   2942 0x00004320
  338. Feb 25 13:30:39 nuc10i5 kernel: [20783.965025] Call Trace:
  339. Feb 25 13:30:39 nuc10i5 kernel: [20783.965026]  __schedule+0x2e3/0x740
  340. Feb 25 13:30:39 nuc10i5 kernel: [20783.965027]  schedule+0x42/0xb0
  341. Feb 25 13:30:39 nuc10i5 kernel: [20783.965028]  blk_queue_enter+0x160/0x200
  342. Feb 25 13:30:39 nuc10i5 kernel: [20783.965029]  ? wait_woken+0x80/0x80
  343. Feb 25 13:30:39 nuc10i5 kernel: [20783.965029]  generic_make_request+0x94/0x320
  344. Feb 25 13:30:39 nuc10i5 kernel: [20783.965031]  ? jbd2_journal_stop+0xf2/0x400
  345. Feb 25 13:30:39 nuc10i5 kernel: [20783.965031]  submit_bio+0x48/0x1d0
  346. Feb 25 13:30:39 nuc10i5 kernel: [20783.965032]  ext4_io_submit+0x4d/0x60
  347. Feb 25 13:30:39 nuc10i5 kernel: [20783.965033]  ext4_writepages+0x673/0x950
  348. Feb 25 13:30:39 nuc10i5 kernel: [20783.965035]  do_writepages+0x43/0xd0
  349. Feb 25 13:30:39 nuc10i5 kernel: [20783.965035]  ? do_writepages+0x43/0xd0
  350. Feb 25 13:30:39 nuc10i5 kernel: [20783.965037]  __filemap_fdatawrite_range+0xd5/0x110
  351. Feb 25 13:30:39 nuc10i5 kernel: [20783.965038]  file_write_and_wait_range+0x74/0xc0
  352. Feb 25 13:30:39 nuc10i5 kernel: [20783.965039]  ext4_sync_file+0x8f/0x3b0
  353. Feb 25 13:30:39 nuc10i5 kernel: [20783.965040]  vfs_fsync_range+0x49/0x80
  354. Feb 25 13:30:39 nuc10i5 kernel: [20783.965040]  ? __fget_light+0x57/0x70
  355. Feb 25 13:30:39 nuc10i5 kernel: [20783.965041]  do_fsync+0x3d/0x70
  356. Feb 25 13:30:39 nuc10i5 kernel: [20783.965042]  __x64_sys_fdatasync+0x17/0x20
  357. Feb 25 13:30:39 nuc10i5 kernel: [20783.965043]  do_syscall_64+0x57/0x190
  358. Feb 25 13:30:39 nuc10i5 kernel: [20783.965044]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  359. Feb 25 13:30:39 nuc10i5 kernel: [20783.965044] RIP: 0033:0x7efe47f343eb
  360. Feb 25 13:30:39 nuc10i5 kernel: [20783.965045] Code: Bad RIP value.
  361. Feb 25 13:30:39 nuc10i5 kernel: [20783.965046] RSP: 002b:00007efda5ff7cb0 EFLAGS: 00000293 ORIG_RAX: 000000000000004b
  362. Feb 25 13:30:39 nuc10i5 kernel: [20783.965046] RAX: ffffffffffffffda RBX: 00007efd5802dc68 RCX: 00007efe47f343eb
  363. Feb 25 13:30:39 nuc10i5 kernel: [20783.965047] RDX: 0000000000000020 RSI: 0000000000000002 RDI: 00000000000000e2
  364. Feb 25 13:30:39 nuc10i5 kernel: [20783.965047] RBP: 000000000000000a R08: 0000000000000000 R09: 00000000a7fd23f9
  365. Feb 25 13:30:39 nuc10i5 kernel: [20783.965047] R10: 0000000000000000 R11: 0000000000000293 R12: 00007efd5803e5d0
  366. Feb 25 13:30:39 nuc10i5 kernel: [20783.965048] R13: 0000000000000000 R14: 00007efda5ff7d60 R15: 00007efd5802dbd8
  367. Feb 25 13:32:23 nuc10i5 kernel: [20887.671965] nvme nvme0: Device not ready; aborting reset
  368. Feb 25 13:32:23 nuc10i5 kernel: [20887.672170] EXT4-fs warning (device nvme0n1p2): ext4_end_bio:309: I/O error 10 writing to inode 20321000 (offset 28672 size 8192 starting block 110799742)
  369. Feb 25 13:32:23 nuc10i5 kernel: [20887.672173] Buffer I/O error on device nvme0n1p2, logical block 110668414
  370. Feb 25 13:32:23 nuc10i5 kernel: [20887.672176] EXT4-fs warning (device nvme0n1p2): ext4_end_bio:309: I/O error 10 writing to inode 20320258 (offset 0 size 4096 starting block 81490282)
  371. Feb 25 13:32:23 nuc10i5 kernel: [20887.672178] blk_update_request: I/O error, dev nvme0n1, sector 940922880 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
  372. Feb 25 13:32:23 nuc10i5 kernel: [20887.672180] blk_update_request: I/O error, dev nvme0n1, sector 117502688 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
  373. Feb 25 13:32:23 nuc10i5 kernel: [20887.672181] blk_update_request: I/O error, dev nvme0n1, sector 122684928 op 0x1:(WRITE) flags 0x4000 phys_seg 2 prio class 0
  374. Feb 25 13:32:23 nuc10i5 kernel: [20887.672183] EXT4-fs warning (device nvme0n1p2): ext4_end_bio:309: I/O error 10 writing to inode 29363420 (offset 0 size 0 starting block 117615361)
  375. Feb 25 13:32:23 nuc10i5 kernel: [20887.672214] Buffer I/O error on device nvme0n1p2, logical block 117484032
  376. Feb 25 13:32:23 nuc10i5 kernel: [20887.672229] blk_update_request: I/O error, dev nvme0n1, sector 122684672 op 0x1:(WRITE) flags 0x4000 phys_seg 1 prio class 0
  377. Feb 25 13:32:23 nuc10i5 kernel: [20887.672230] blk_update_request: I/O error, dev nvme0n1, sector 122684416 op 0x1:(WRITE) flags 0x4000 phys_seg 2 prio class 0
  378. Feb 25 13:32:23 nuc10i5 kernel: [20887.672231] blk_update_request: I/O error, dev nvme0n1, sector 122684160 op 0x1:(WRITE) flags 0x4000 phys_seg 1 prio class 0
  379. Feb 25 13:32:23 nuc10i5 kernel: [20887.672233] EXT4-fs warning (device nvme0n1p2): ext4_end_bio:309: I/O error 10 writing to inode 20320259 (offset 0 size 4096 starting block 110799741)
  380. Feb 25 13:32:23 nuc10i5 kernel: [20887.672234] blk_update_request: I/O error, dev nvme0n1, sector 122683904 op 0x1:(WRITE) flags 0x4000 phys_seg 2 prio class 0
  381. Feb 25 13:32:23 nuc10i5 kernel: [20887.672235] Buffer I/O error on device nvme0n1p2, logical block 110668413
  382. Feb 25 13:32:23 nuc10i5 kernel: [20887.672236] blk_update_request: I/O error, dev nvme0n1, sector 122683648 op 0x1:(WRITE) flags 0x4000 phys_seg 1 prio class 0
  383. Feb 25 13:32:23 nuc10i5 kernel: [20887.672236] Buffer I/O error on device nvme0n1p2, logical block 110668415
  384. Feb 25 13:32:23 nuc10i5 kernel: [20887.672237] blk_update_request: I/O error, dev nvme0n1, sector 122683392 op 0x1:(WRITE) flags 0x4000 phys_seg 2 prio class 0
  385. Feb 25 13:32:23 nuc10i5 kernel: [20887.672239] blk_update_request: I/O error, dev nvme0n1, sector 122683136 op 0x1:(WRITE) flags 0x4000 phys_seg 1 prio class 0
  386. Feb 25 13:32:23 nuc10i5 kernel: [20887.672241] EXT4-fs warning (device nvme0n1p2): ext4_end_bio:309: I/O error 10 writing to inode 23594014 (offset 1568669696 size 8388608 starting block 15335680)
  387. Feb 25 13:32:23 nuc10i5 kernel: [20887.672242] Buffer I/O error on device nvme0n1p2, logical block 15202304
  388. Feb 25 13:32:23 nuc10i5 kernel: [20887.672244] EXT4-fs warning (device nvme0n1p2): ext4_end_bio:309: I/O error 10 writing to inode 20321000 (offset 0 size 0 starting block 81492218)
  389. Feb 25 13:32:23 nuc10i5 kernel: [20887.672264] Buffer I/O error on device nvme0n1p2, logical block 81360889
  390. Feb 25 13:32:23 nuc10i5 kernel: [20887.672363] Buffer I/O error on device nvme0n1p2, logical block 15202305
  391. Feb 25 13:32:23 nuc10i5 kernel: [20887.672364] Buffer I/O error on device nvme0n1p2, logical block 15202306
  392. Feb 25 13:32:23 nuc10i5 kernel: [20887.672365] Buffer I/O error on device nvme0n1p2, logical block 15202307
  393. Feb 25 13:32:23 nuc10i5 kernel: [20887.672365] Buffer I/O error on device nvme0n1p2, logical block 15202308
  394. Feb 25 13:32:23 nuc10i5 kernel: [20887.672563] Write-error on swap-device (259:0:4321848)
  395. Feb 25 13:32:23 nuc10i5 kernel: [20887.673109] EXT4-fs warning (device nvme0n1p2): ext4_end_bio:309: I/O error 10 writing to inode 29363420 (offset 0 size 0 starting block 117615360)
  396. Feb 25 13:32:23 nuc10i5 kernel: [20887.673116] EXT4-fs warning (device nvme0n1p2): ext4_end_bio:309: I/O error 10 writing to inode 20321004 (offset 0 size 4096 starting block 81496269)
  397. Feb 25 13:32:23 nuc10i5 kernel: [20887.673126] Buffer I/O error on dev nvme0n1p2, logical block 61023869, lost sync page write
  398. Feb 25 13:32:23 nuc10i5 kernel: [20887.673203] EXT4-fs warning (device nvme0n1p2): ext4_end_bio:309: I/O error 10 writing to inode 29363420 (offset 0 size 0 starting block 160542)
  399.  
RAW Paste Data