首页新闻找找看学习计划

Read-only file system

0
悬赏园豆:20 [待解决问题]

Ubuntu 18.04 其中一个磁盘经常出现 Read-only file system 这个问题,重启机器可以解决,但是过一段时间还会出现,已经差试过的办法:

  1. 更换磁盘
  2. 更换数据线
  3. 数据线插入主板其他插口
    问题依然没有解决
    kernel log:
Dec  2 20:50:10 trinite kernel: [3973919.215458] ata5.00: failed command: WRITE FPDMA QUEUED
Dec  2 20:50:10 trinite kernel: [3973919.215463] ata5.00: cmd 61/00:e0:00:82:10/06:00:14:00:00/40 tag 28 ncq dma 786432 out
Dec  2 20:50:10 trinite kernel: [3973919.215463]          res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec  2 20:50:10 trinite kernel: [3973919.215465] ata5.00: status: { DRDY }
Dec  2 20:50:10 trinite kernel: [3973919.215467] ata5.00: failed command: WRITE FPDMA QUEUED
Dec  2 20:50:10 trinite kernel: [3973919.215472] ata5.00: cmd 61/88:f0:78:11:10/06:00:14:00:00/40 tag 30 ncq dma 856064 out
Dec  2 20:50:10 trinite kernel: [3973919.215472]          res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Dec  2 20:50:10 trinite kernel: [3973919.215474] ata5.00: status: { DRDY }
Dec  2 20:50:10 trinite kernel: [3973919.215479] ata5: hard resetting link
Dec  2 20:50:15 trinite kernel: [3973924.575110] ata5: link is slow to respond, please be patient (ready=0)
Dec  2 20:50:20 trinite kernel: [3973929.267111] ata5: COMRESET failed (errno=-16)
Dec  2 20:50:20 trinite kernel: [3973929.267121] ata5: hard resetting link
Dec  2 20:50:25 trinite kernel: [3973934.623067] ata5: link is slow to respond, please be patient (ready=0)
Dec  2 20:50:30 trinite kernel: [3973939.315067] ata5: COMRESET failed (errno=-16)
Dec  2 20:50:30 trinite kernel: [3973939.315076] ata5: hard resetting link
Dec  2 20:50:35 trinite kernel: [3973944.670959] ata5: link is slow to respond, please be patient (ready=0)
Dec  2 20:51:05 trinite kernel: [3973974.346887] ata5: COMRESET failed (errno=-16)
Dec  2 20:51:05 trinite kernel: [3973974.346897] ata5: limiting SATA link speed to 1.5 Gbps
Dec  2 20:51:05 trinite kernel: [3973974.346899] ata5: hard resetting link
Dec  2 20:51:10 trinite kernel: [3973979.398857] ata5: COMRESET failed (errno=-16)
Dec  2 20:51:10 trinite kernel: [3973979.398868] ata5: reset failed, giving up
Dec  2 20:51:10 trinite kernel: [3973979.398872] ata5.00: disabled
Dec  2 20:51:10 trinite kernel: [3973979.398951] ata5: EH complete
Dec  2 20:51:10 trinite kernel: [3973979.399017] sd 4:0:0:0: [sdb] tag#29 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec  2 20:51:10 trinite kernel: [3973979.399023] sd 4:0:0:0: [sdb] tag#29 CDB: Write(10) 2a 00 14 10 11 78 00 06 88 00
Dec  2 20:51:10 trinite kernel: [3973979.399026] print_req_error: I/O error, dev sdb, sector 336597368
Dec  2 20:51:10 trinite kernel: [3973979.399036] EXT4-fs warning (device sdb1): ext4_end_bio:323: I/O error 10 writing to inode 7208981 (offset 25165824 size 8388608 starting block 42074880)
Dec  2 20:51:10 trinite kernel: [3973979.399040] Buffer I/O error on device sdb1, logical block 42074112
Dec  2 20:51:10 trinite kernel: [3973979.399055] Buffer I/O error on device sdb1, logical block 42074113
Dec  2 20:51:10 trinite kernel: [3973979.399058] Buffer I/O error on device sdb1, logical block 42074114
Dec  2 20:51:10 trinite kernel: [3973979.399062] Buffer I/O error on device sdb1, logical block 42074115
Dec  2 20:51:10 trinite kernel: [3973979.399065] Buffer I/O error on device sdb1, logical block 42074116
Dec  2 20:51:10 trinite kernel: [3973979.399068] Buffer I/O error on device sdb1, logical block 42074117
Dec  2 20:51:10 trinite kernel: [3973979.399071] Buffer I/O error on device sdb1, logical block 42074118
Dec  2 20:51:10 trinite kernel: [3973979.399074] Buffer I/O error on device sdb1, logical block 42074119
Dec  2 20:51:10 trinite kernel: [3973979.399077] Buffer I/O error on device sdb1, logical block 42074120
Dec  2 20:51:10 trinite kernel: [3973979.399080] Buffer I/O error on device sdb1, logical block 42074121
Dec  2 20:51:10 trinite kernel: [3973979.399755] sd 4:0:0:0: [sdb] tag#30 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec  2 20:51:10 trinite kernel: [3973979.399758] sd 4:0:0:0: [sdb] tag#30 CDB: Write(10) 2a 00 14 10 82 00 00 06 00 00
Dec  2 20:51:10 trinite kernel: [3973979.399760] print_req_error: I/O error, dev sdb, sector 336626176
Dec  2 20:51:10 trinite kernel: [3973979.399781] sd 4:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec  2 20:51:10 trinite kernel: [3973979.399784] sd 4:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 14 10 78 00 00 0a 00 00
Dec  2 20:51:10 trinite kernel: [3973979.399785] print_req_error: I/O error, dev sdb, sector 336623616
Dec  2 20:51:10 trinite kernel: [3973979.399793] EXT4-fs warning (device sdb1): ext4_end_bio:323: I/O error 10 writing to inode 7208981 (offset 33554432 size 8388608 starting block 42078464)
Dec  2 20:51:10 trinite kernel: [3973979.400130] sd 4:0:0:0: [sdb] tag#1 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec  2 20:51:10 trinite kernel: [3973979.400132] sd 4:0:0:0: [sdb] tag#1 CDB: Write(10) 2a 00 14 10 72 00 00 06 00 00
Dec  2 20:51:10 trinite kernel: [3973979.400134] print_req_error: I/O error, dev sdb, sector 336622080
Dec  2 20:51:10 trinite kernel: [3973979.400151] sd 4:0:0:0: [sdb] tag#2 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec  2 20:51:10 trinite kernel: [3973979.400153] sd 4:0:0:0: [sdb] tag#2 CDB: Write(10) 2a 00 14 10 68 00 00 0a 00 00
Dec  2 20:51:10 trinite kernel: [3973979.400155] print_req_error: I/O error, dev sdb, sector 336619520
Dec  2 20:51:10 trinite kernel: [3973979.400162] EXT4-fs warning (device sdb1): ext4_end_bio:323: I/O error 10 writing to inode 7208981 (offset 33554432 size 8388608 starting block 42077952)
Dec  2 20:51:10 trinite kernel: [3973979.400488] sd 4:0:0:0: [sdb] tag#3 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec  2 20:51:10 trinite kernel: [3973979.401210] sd 4:0:0:0: [sdb] tag#7 CDB: Write(10) 2a 00 14 10 44 80 00 03 80 00
Dec  2 20:51:10 trinite kernel: [3973979.401211] print_req_error: I/O error, dev sdb, sector 336610432
Dec  2 20:51:10 trinite kernel: [3973979.401220] Buffer I/O error on dev sdb1, logical block 40894468, lost async page write
Dec  2 20:51:10 trinite kernel: [3973979.401230] Buffer I/O error on dev sdb1, logical block 39845894, lost async page write
Dec  2 20:51:10 trinite kernel: [3973979.401237] Buffer I/O error on dev sdb1, logical block 39321615, lost async page write
Dec  2 20:51:10 trinite kernel: [3973979.401245] Buffer I/O error on dev sdb1, logical block 39321610, lost async page write
Dec  2 20:51:10 trinite kernel: [3973979.401251] Buffer I/O error on dev sdb1, logical block 38273038, lost async page write
Dec  2 20:51:10 trinite kernel: [3973979.401259] Buffer I/O error on dev sdb1, logical block 38273032, lost async page write
Dec  2 20:51:10 trinite kernel: [3973979.401262] Buffer I/O error on dev sdb1, logical block 38273033, lost async page write
Dec  2 20:51:10 trinite kernel: [3973979.401272] Buffer I/O error on dev sdb1, logical block 38273034, lost async page write
Dec  2 20:51:10 trinite kernel: [3973979.401278] Buffer I/O error on dev sdb1, logical block 38273030, lost async page write
Dec  2 20:51:10 trinite kernel: [3973979.401285] Buffer I/O error on dev sdb1, logical block 28874588, lost async page write
Dec  2 20:51:10 trinite kernel: [3973979.401334] EXT4-fs warning (device sdb1): ext4_end_bio:323: I/O error 10 writing to inode 7208981 (offset 25165824 size 8388608 starting block 42076416)
Dec  2 20:51:10 trinite kernel: [3973979.401693] EXT4-fs warning (device sdb1): ext4_end_bio:323: I/O error 10 writing to inode 7208981 (offset 25165824 size 8388608 starting block 42075904)
Dec  2 20:51:10 trinite kernel: [3973979.402055] EXT4-fs warning (device sdb1): ext4_end_bio:323: I/O error 10 writing to inode 7208981 (offset 25165824 size 8388608 starting block 42075392)
Dec  2 20:51:10 trinite kernel: [3973979.402691] EXT4-fs warning (device sdb1): ext4_end_bio:323: I/O error 10 writing to inode 7208981 (offset 41943040 size 8388608 starting block 45990656)
Dec  2 20:51:10 trinite kernel: [3973979.403181] EXT4-fs warning (device sdb1): ext4_end_bio:323: I/O error 10 writing to inode 7208981 (offset 41943040 size 8388608 starting block 45991168)
Dec  2 20:51:10 trinite kernel: [3973979.408944] EXT4-fs error (device sdb1): ext4_wait_block_bitmap:524: comm kworker/u24:2: Cannot read block bitmap - block_group = 1493, block_bitmap = 48758789
Dec  2 20:51:10 trinite kernel: [3973979.409005] EXT4-fs (sdb1): Delayed block allocation failed for inode 7209029 at logical offset 22528 with max blocks 2048 with error 5
Dec  2 20:51:10 trinite kernel: [3973979.409008] EXT4-fs (sdb1): This should not happen!! Data will be lost
Dec  2 20:51:10 trinite kernel: [3973979.409008]
Dec  2 20:51:10 trinite kernel: [3973979.409855] EXT4-fs (sdb1): Delayed block allocation failed for inode 7214823 at logical offset 12548 with max blocks 2048 with error 5
Dec  2 20:51:10 trinite kernel: [3973979.409858] EXT4-fs (sdb1): This should not happen!! Data will be lost
Dec  2 20:51:10 trinite kernel: [3973979.409858]
Dec  2 20:51:10 trinite kernel: [3973979.411190] EXT4-fs (sdb1): Delayed block allocation failed for inode 7214797 at logical offset 12586 with max blocks 2048 with error 5
Dec  2 20:51:10 trinite kernel: [3973979.411193] EXT4-fs (sdb1): This should not happen!! Data will be lost
Dec  2 20:51:10 trinite kernel: [3973979.411193]
Dec  2 20:51:10 trinite kernel: [3973979.412655] JBD2: Detected IO errors while flushing file data on sdb1-8
Dec  2 20:51:10 trinite kernel: [3973979.412666] Aborting journal on device sdb1-8.
Dec  2 20:51:10 trinite kernel: [3973979.412679] EXT4-fs (sdb1): previous I/O error to superblock detected
Dec  2 20:51:10 trinite kernel: [3973979.412694] JBD2: Error -5 detected when updating journal superblock for sdb1-8.
Dec  2 20:51:10 trinite kernel: [3973979.412703] EXT4-fs error (device sdb1): ext4_journal_check_start:61: Detected aborted journal
Dec  2 20:51:10 trinite kernel: [3973979.412704] EXT4-fs (sdb1): Remounting filesystem read-only
Dec  2 20:51:10 trinite kernel: [3973979.412706] EXT4-fs (sdb1): previous I/O error to superblock detected
Dec  2 20:51:10 trinite kernel: [3973979.416412] JBD2: Detected IO errors while flushing file data on sdb1-8
Dec  2 20:58:07 trinite kernel: [3974396.377371] scsi_io_completion: 140 callbacks suppressed
Dec  2 20:58:07 trinite kernel: [3974396.377375] sd 4:0:0:0: [sdb] tag#24 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec  2 20:58:07 trinite kernel: [3974396.377378] sd 4:0:0:0: [sdb] tag#24 CDB: ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
Dec  2 21:08:07 trinite kernel: [3974996.465856] sd 4:0:0:0: [sdb] tag#27 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec  2 21:08:07 trinite kernel: [3974996.465859] sd 4:0:0:0: [sdb] tag#27 CDB: ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
Dec  2 21:18:07 trinite kernel: [3975596.379251] sd 4:0:0:0: [sdb] tag#29 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec  2 21:18:07 trinite kernel: [3975596.379254] sd 4:0:0:0: [sdb] tag#29 CDB: ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
Dec  2 21:28:07 trinite kernel: [3976196.470885] sd 4:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec  2 21:28:07 trinite kernel: [3976196.470889] sd 4:0:0:0: [sdb] tag#0 CDB: ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
Dec  2 21:38:07 trinite kernel: [3976796.464696] sd 4:0:0:0: [sdb] tag#2 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec  2 21:38:07 trinite kernel: [3976796.464700] sd 4:0:0:0: [sdb] tag#2 CDB: ATA command pass through(16) 85 06 20 00 00 00 00 00 00 00 00 00 00 00 e5 00
Dec  2 21:38:34 trinite kernel: [3976823.350765] rfkill: input handler enabled

leo.rd的主页 leo.rd | 初学一级 | 园豆:191
提问于:2019-12-03 13:41
< >
分享
清除回答草稿
   您需要登录以后才能回答,未注册用户请先注册