Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- [ 280.394070] nvme nvme0: I/O 68 QID 3 timeout, disable controller
- [ 280.476248] I/O error, dev nvme0n1, sector 5757952 op 0x1:(WRITE) flags 0x4000 phys_seg 57 prio class 0
- [ 280.477165] I/O error, dev nvme0n1, sector 5751808 op 0x1:(WRITE) flags 0x0 phys_seg 3 prio class 0
- [ 280.477993] I/O error, dev nvme0n1, sector 5749248 op 0x1:(WRITE) flags 0x4000 phys_seg 30 prio class 0
- [ 280.478851] I/O error, dev nvme0n1, sector 5746688 op 0x1:(WRITE) flags 0x4000 phys_seg 3 prio class 0
- [ 280.479699] I/O error, dev nvme0n1, sector 5744128 op 0x1:(WRITE) flags 0x4000 phys_seg 6 prio class 0
- [ 280.480545] I/O error, dev nvme0n1, sector 5741568 op 0x1:(WRITE) flags 0x4000 phys_seg 7 prio class 0
- [ 280.481390] I/O error, dev nvme0n1, sector 5734760 op 0x1:(WRITE) flags 0x0 phys_seg 101 prio class 0
- [ 280.482228] EXT4-fs warning (device nvme0n1p1): ext4_end_bio:342: I/O error 10 writing to inode 12 starting block 717004)
- [ 280.483224] I/O error, dev nvme0n1, sector 5732864 op 0x1:(WRITE) flags 0x4000 phys_seg 127 prio class 0
- [ 280.484208] I/O error, dev nvme0n1, sector 5730304 op 0x1:(WRITE) flags 0x4000 phys_seg 57 prio class 0
- [ 280.485077] I/O error, dev nvme0n1, sector 5727744 op 0x1:(WRITE) flags 0x4000 phys_seg 4 prio class 0
- [ 280.485946] EXT4-fs warning (device nvme0n1p1): ext4_end_bio:342: I/O error 10 writing to inode 12 starting block 714952)
- [ 280.487056] EXT4-fs warning (device nvme0n1p1): ext4_end_bio:342: I/O error 10 writing to inode 12 starting block 704686)
- [ 280.488097] EXT4-fs warning (device nvme0n1p1): ext4_end_bio:342: I/O error 10 writing to inode 12 starting block 701817)
- [ 280.489113] EXT4-fs warning (device nvme0n1p1): ext4_end_bio:342: I/O error 10 writing to inode 12 starting block 701021)
- [ 280.490170] EXT4-fs warning (device nvme0n1p1): ext4_end_bio:342: I/O error 10 writing to inode 12 starting block 718976)
- [ 280.491221] EXT4-fs warning (device nvme0n1p1): ext4_end_bio:342: I/O error 10 writing to inode 12 starting block 716845)
- [ 280.491348] Buffer I/O error on device nvme0n1p1, logical block 716800
- [ 280.492255] EXT4-fs warning (device nvme0n1p1): ext4_end_bio:342: I/O error 10 writing to inode 12 starting block 712801)
- [ 280.492836] Buffer I/O error on device nvme0n1p1, logical block 716801
- [ 280.493774] EXT4-fs warning (device nvme0n1p1): ext4_end_bio:342: I/O error 10 writing to inode 12 starting block 711872)
- [ 280.494462] Buffer I/O error on device nvme0n1p1, logical block 716802
- [ 280.495409] EXT4-fs warning (device nvme0n1p1): ext4_end_bio:342: I/O error 10 writing to inode 12 starting block 710784)
- [ 280.495972] Buffer I/O error on device nvme0n1p1, logical block 716803
- [ 280.497361] nvme nvme0: failed to mark controller live state
- [ 280.497510] Buffer I/O error on device nvme0n1p1, logical block 716804
- [ 280.498017] nvme nvme0: Removing after probe failure status: -19
- [ 280.498599] Buffer I/O error on device nvme0n1p1, logical block 716805
- [ 280.498623] Buffer I/O error on device nvme0n1p1, logical block 716806
- [ 280.498624] Aborting journal on device nvme0n1p1-8.
- [ 280.498687] Buffer I/O error on dev nvme0n1p1, logical block 60850176, lost sync page write
- [ 280.498730] JBD2: Error -5 detected when updating journal superblock for nvme0n1p1-8.
- [ 280.498885] EXT4-fs error (device nvme0n1p1) in ext4_reserve_inode_write:5706: Journal has aborted
- [ 280.499008] Buffer I/O error on dev nvme0n1p1, logical block 0, lost sync page write
- [ 280.499045] EXT4-fs (nvme0n1p1): I/O error while writing superblock
- [ 280.499064] EXT4-fs (nvme0n1p1): Remounting filesystem read-only
- [ 280.499079] EXT4-fs error (device nvme0n1p1): ext4_dirty_inode:5902: inode #12: comm dd: mark_inode_dirty error
- [ 280.499137] Buffer I/O error on dev nvme0n1p1, logical block 0, lost sync page write
- [ 280.499731] Buffer I/O error on device nvme0n1p1, logical block 716807
- [ 280.500426] EXT4-fs (nvme0n1p1): I/O error while writing superblock
- [ 280.500565] EXT4-fs error (device nvme0n1p1): ext4_check_bdev_write_error:217: comm kworker/u8:3: Error while async write back metadata
- [ 280.500621] EXT4-fs (nvme0n1p1): previous I/O error to superblock detected
- [ 280.500763] Buffer I/O error on device nvme0n1p1, logical block 716808
- [ 280.509652] Buffer I/O error on device nvme0n1p1, logical block 716809
- [ 280.513829] EXT4-fs (nvme0n1p1): failed to convert unwritten extents to written extents -- potential data loss! (inode 12, error -30)
- [ 280.518748] EXT4-fs (nvme0n1p1): failed to convert unwritten extents to written extents -- potential data loss! (inode 12, error -30)
- [ 280.523709] EXT4-fs (nvme0n1p1): failed to convert unwritten extents to written extents -- potential data loss! (inode 12, error -30)
- [ 280.528938] EXT4-fs (nvme0n1p1): failed to convert unwritten extents to written extents -- potential data loss! (inode 12, error -30)
- [ 280.534211] EXT4-fs (nvme0n1p1): failed to convert unwritten extents to written extents -- potential data loss! (inode 12, error -30)
- [ 280.539449] EXT4-fs (nvme0n1p1): failed to convert unwritten extents to written extents -- potential data loss! (inode 12, error -30)
- [ 280.594064] nvme0n1: detected capacity change from 976773168 to 0
- [ 280.594082] Buffer I/O error on dev nvme0n1p1, logical block 0, lost sync page write
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement