Advertisement
Bullet64

nvme

Aug 25th, 2021
105
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 6.53 KB | None | 0 0
  1. [ 77.623620] EXT4-fs (nvme0n1p1): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
  2. [ 794.074636] nvme nvme0: controller is down; will reset: CSTS=0x3, PCI_STATUS=0x2010
  3. [ 794.201524] nvme nvme0: Shutdown timeout set to 8 seconds
  4. [ 794.209171] nvme nvme0: 4/0/0 default/read/poll queues
  5. [ 824.793898] nvme nvme0: I/O 249 QID 3 timeout, disable controller
  6. [ 824.904606] blk_update_request: I/O error, dev nvme0n1, sector 2186240 op 0x1:(WRITE) flags 0x4000 phys_seg 1 prio class 0
  7. [ 824.905614] blk_update_request: I/O error, dev nvme0n1, sector 2183680 op 0x1:(WRITE) flags 0x4000 phys_seg 2 prio class 0
  8. [ 824.906588] EXT4-fs warning (device nvme0n1p1): ext4_end_bio:342: I/O error 10 writing to inode 12 starting block 274688)
  9. [ 824.906629] blk_update_request: I/O error, dev nvme0n1, sector 2516480 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
  10. [ 824.906674] Buffer I/O error on device nvme0n1p1, logical block 272384
  11. [ 824.907587] blk_update_request: I/O error, dev nvme0n1, sector 2513920 op 0x1:(WRITE) flags 0x4000 phys_seg 1 prio class 0
  12. [ 824.908171] Buffer I/O error on device nvme0n1p1, logical block 272385
  13. [ 824.909121] blk_update_request: I/O error, dev nvme0n1, sector 2511360 op 0x1:(WRITE) flags 0x4000 phys_seg 1 prio class 0
  14. [ 824.909692] Buffer I/O error on device nvme0n1p1, logical block 272386
  15. [ 824.910655] blk_update_request: I/O error, dev nvme0n1, sector 2508800 op 0x1:(WRITE) flags 0x4000 phys_seg 1 prio class 0
  16. [ 824.911226] Buffer I/O error on device nvme0n1p1, logical block 272387
  17. [ 824.912193] EXT4-fs warning (device nvme0n1p1): ext4_end_bio:342: I/O error 10 writing to inode 12 starting block 314624)
  18. [ 824.912766] Buffer I/O error on device nvme0n1p1, logical block 272388
  19. [ 824.912773] blk_update_request: I/O error, dev nvme0n1, sector 2507776 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
  20. [ 824.913343] Buffer I/O error on device nvme0n1p1, logical block 272389
  21. [ 824.914318] blk_update_request: I/O error, dev nvme0n1, sector 2505216 op 0x1:(WRITE) flags 0x4000 phys_seg 1 prio class 0
  22. [ 824.914881] Buffer I/O error on device nvme0n1p1, logical block 272390
  23. [ 824.915829] blk_update_request: I/O error, dev nvme0n1, sector 2502656 op 0x1:(WRITE) flags 0x4000 phys_seg 1 prio class 0
  24. [ 824.916402] Buffer I/O error on device nvme0n1p1, logical block 272391
  25. [ 824.917367] blk_update_request: I/O error, dev nvme0n1, sector 2500096 op 0x1:(WRITE) flags 0x4000 phys_seg 1 prio class 0
  26. [ 824.917939] Buffer I/O error on device nvme0n1p1, logical block 272392
  27. [ 824.918911] EXT4-fs warning (device nvme0n1p1): ext4_end_bio:342: I/O error 10 writing to inode 12 starting block 313600)
  28. [ 824.919476] Buffer I/O error on device nvme0n1p1, logical block 272393
  29. [ 824.919492] EXT4-fs warning (device nvme0n1p1): ext4_end_bio:342: I/O error 10 writing to inode 12 starting block 311552)
  30. [ 824.920070] EXT4-fs warning (device nvme0n1p1): ext4_end_bio:342: I/O error 10 writing to inode 12 starting block 309504)
  31. [ 824.920093] EXT4-fs warning (device nvme0n1p1): ext4_end_bio:342: I/O error 10 writing to inode 12 starting block 307456)
  32. [ 824.920114] EXT4-fs warning (device nvme0n1p1): ext4_end_bio:342: I/O error 10 writing to inode 12 starting block 305408)
  33. [ 824.920136] EXT4-fs warning (device nvme0n1p1): ext4_end_bio:342: I/O error 10 writing to inode 12 starting block 303360)
  34. [ 824.920156] EXT4-fs warning (device nvme0n1p1): ext4_end_bio:342: I/O error 10 writing to inode 12 starting block 301312)
  35. [ 824.920177] EXT4-fs warning (device nvme0n1p1): ext4_end_bio:342: I/O error 10 writing to inode 12 starting block 299264)
  36. [ 824.920453] nvme nvme0: failed to mark controller live state
  37. [ 824.920461] nvme nvme0: Removing after probe failure status: -19
  38. [ 825.034100] nvme0n1: detected capacity change from 1000215216 to 0
  39. [ 825.034140] Aborting journal on device nvme0n1p1-8.
  40. [ 825.034593] EXT4-fs (nvme0n1p1): failed to convert unwritten extents to written extents -- potential data loss! (inode 12, error -30)
  41. [ 825.034604] Buffer I/O error on dev nvme0n1p1, logical block 62423040, lost sync page write
  42. [ 825.035078] EXT4-fs error (device nvme0n1p1) in ext4_reserve_inode_write:5752: Journal has aborted
  43. [ 825.035126] Buffer I/O error on dev nvme0n1p1, logical block 0, lost sync page write
  44. [ 825.035133] EXT4-fs (nvme0n1p1): I/O error while writing superblock
  45. [ 825.035151] EXT4-fs error (device nvme0n1p1): mpage_map_and_submit_extent:2509: inode #12: comm kworker/u8:0: mark_inode_dirty error
  46. [ 825.035169] Buffer I/O error on dev nvme0n1p1, logical block 0, lost sync page write
  47. [ 825.035174] EXT4-fs (nvme0n1p1): I/O error while writing superblock
  48. [ 825.035183] EXT4-fs error (device nvme0n1p1): mpage_map_and_submit_extent:2511: comm kworker/u8:0: Failed to mark inode 12 dirty
  49. [ 825.035199] Buffer I/O error on dev nvme0n1p1, logical block 0, lost sync page write
  50. [ 825.035204] EXT4-fs (nvme0n1p1): I/O error while writing superblock
  51. [ 825.035214] EXT4-fs error (device nvme0n1p1) in ext4_writepages:2813: Journal has aborted
  52. [ 825.035228] Buffer I/O error on dev nvme0n1p1, logical block 0, lost sync page write
  53. [ 825.035234] EXT4-fs (nvme0n1p1): I/O error while writing superblock
  54. [ 825.035245] EXT4-fs error (device nvme0n1p1): ext4_journal_check_start:83: comm kworker/u8:0: Detected aborted journal
  55. [ 825.037072] EXT4-fs error (device nvme0n1p1): ext4_journal_check_start:83: comm kworker/u8:4: Detected aborted journal
  56. [ 825.037178] JBD2: Error -5 detected when updating journal superblock for nvme0n1p1-8.
  57. [ 825.047582] Buffer I/O error on dev nvme0n1p1, logical block 0, lost sync page write
  58. [ 825.048287] EXT4-fs (nvme0n1p1): I/O error while writing superblock
  59. [ 825.048291] EXT4-fs (nvme0n1p1): previous I/O error to superblock detected
  60. [ 825.048841] EXT4-fs (nvme0n1p1): Remounting filesystem read-only
  61. [ 825.049451] Buffer I/O error on dev nvme0n1p1, logical block 0, lost sync page write
  62. [ 825.049979] EXT4-fs (nvme0n1p1): failed to convert unwritten extents to written extents -- potential data loss! (inode 12, error -30)
  63. [ 825.051740] EXT4-fs (nvme0n1p1): I/O error while writing superblock
  64. [ 938.198275] audit: type=1130 audit(1629903260.313:62): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
  65. [ 938.198302] audit: type=1131 audit(1629903260.313:63): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-tmpfiles-clean comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement