Example hard-disk error logs on a Linux server

Posted on January 9, 2020 at 4:27 pm

Here is an example of logs related to a failing hard-disk:

root@server:~# cat /var/log/syslog
 
Dec  3 02:35:54 server kernel: [6703851.044036] sd 0:2:0:0: [sda] tag#18 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec  3 02:35:54 server kernel: [6703851.044065] sd 0:2:0:0: [sda] tag#18 CDB: Write(10) 2a 00 31 20 31 00 00 01 00 00
Dec  3 02:35:54 server kernel: [6703851.044071] blk_update_request: I/O error, dev sda, sector 824193280
Dec  3 02:35:54 server kernel: [6703851.044196] sd 0:2:0:0: [sda] tag#12 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec  3 02:35:54 server kernel: [6703851.044202] sd 0:2:0:0: [sda] tag#12 CDB: Write(10) 2a 00 31 20 2b 00 00 01 00 00
Dec  3 02:35:54 server kernel: [6703851.044205] blk_update_request: I/O error, dev sda, sector 824191744
Dec  3 02:35:54 server kernel: [6703851.044271] sd 0:2:0:0: [sda] tag#8 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec  3 02:35:54 server kernel: [6703851.044276] sd 0:2:0:0: [sda] tag#8 CDB: Write(10) 2a 00 31 20 27 00 00 01 00 00
Dec  3 02:35:54 server kernel: [6703851.044279] blk_update_request: I/O error, dev sda, sector 824190720
Dec  3 02:35:54 server kernel: [6703851.044348] sd 0:2:0:0: [sda] tag#17 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec  3 02:35:54 server kernel: [6703851.044353] sd 0:2:0:0: [sda] tag#17 CDB: Write(10) 2a 00 31 20 30 00 00 01 00 00
Dec  3 02:35:54 server kernel: [6703851.044356] blk_update_request: I/O error, dev sda, sector 824193024
Dec  3 02:35:54 server kernel: [6703851.044458] sd 0:2:0:0: [sda] tag#5 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec  3 02:35:54 server kernel: [6703851.044462] sd 0:2:0:0: [sda] tag#5 CDB: Write(10) 2a 00 31 20 24 00 00 01 00 00
Dec  3 02:35:54 server kernel: [6703851.044464] blk_update_request: I/O error, dev sda, sector 824189952
Dec  3 02:35:54 server kernel: [6703851.044526] sd 0:2:0:0: [sda] tag#20 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec  3 02:35:54 server kernel: [6703851.044530] sd 0:2:0:0: [sda] tag#20 CDB: Write(10) 2a 00 31 20 33 00 00 01 00 00
Dec  3 02:35:54 server kernel: [6703851.044532] blk_update_request: I/O error, dev sda, sector 824193792
Dec  3 02:35:54 server kernel: [6703851.044592] sd 0:2:0:0: [sda] tag#7 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec  3 02:35:54 server kernel: [6703851.044595] sd 0:2:0:0: [sda] tag#7 CDB: Write(10) 2a 00 31 20 26 00 00 01 00 00
Dec  3 02:35:54 server kernel: [6703851.044597] blk_update_request: I/O error, dev sda, sector 824190464
Dec  3 02:35:54 server kernel: [6703851.044657] sd 0:2:0:0: [sda] tag#1 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec  3 02:35:54 server kernel: [6703851.044661] sd 0:2:0:0: [sda] tag#1 CDB: Write(10) 2a 00 31 20 20 00 00 01 00 00
Dec  3 02:35:54 server kernel: [6703851.044663] blk_update_request: I/O error, dev sda, sector 824188928
Dec  3 02:35:54 server kernel: [6703851.044722] sd 0:2:0:0: [sda] tag#11 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec  3 02:35:54 server kernel: [6703851.044726] sd 0:2:0:0: [sda] tag#11 CDB: Write(10) 2a 00 31 20 2a 00 00 01 00 00
Dec  3 02:35:54 server kernel: [6703851.044728] blk_update_request: I/O error, dev sda, sector 824191488
Dec  3 02:35:54 server kernel: [6703851.044787] sd 0:2:0:0: [sda] tag#15 FAILED Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Dec  3 02:35:54 server kernel: [6703851.044790] sd 0:2:0:0: [sda] tag#15 CDB: Write(10) 2a 00 31 20 2e 00 00 01 00 00
Dec  3 02:35:54 server kernel: [6703851.044792] blk_update_request: I/O error, dev sda, sector 824192512
Dec  3 02:35:54 server kernel: [6703851.045030] EXT4-fs warning (device sda3): ext4_end_bio:314: I/O error -5 writing to inode 4982294 (offset 79691776 size 4194304 starting block 103024128)
Dec  3 02:35:54 server kernel: [6703851.045048] Buffer I/O error on device sda3, logical block 97576192
Dec  3 02:35:54 server kernel: [6703851.045095] Buffer I/O error on device sda3, logical block 97576193
Dec  3 02:35:54 server kernel: [6703851.045137] Buffer I/O error on device sda3, logical block 97576194
Dec  3 02:35:54 server kernel: [6703851.045178] Buffer I/O error on device sda3, logical block 97576195
Dec  3 02:35:54 server kernel: [6703851.045218] Buffer I/O error on device sda3, logical block 97576196
Dec  3 02:35:54 server kernel: [6703851.045258] Buffer I/O error on device sda3, logical block 97576197
Dec  3 02:35:54 server kernel: [6703851.045298] Buffer I/O error on device sda3, logical block 97576198
Dec  3 02:35:54 server kernel: [6703851.045338] Buffer I/O error on device sda3, logical block 97576199
Dec  3 02:35:54 server kernel: [6703851.045378] Buffer I/O error on device sda3, logical block 97576200
Dec  3 02:35:54 server kernel: [6703851.045418] Buffer I/O error on device sda3, logical block 97576201
Dec  3 02:35:54 server kernel: [6703851.045622] EXT4-fs warning (device sda3): ext4_end_bio:314: I/O error -5 writing to inode 4982294 (offset 79691776 size 4194304 starting block 103023872)
Dec  3 02:35:54 server kernel: [6703851.053635] EXT4-fs warning (device sda3): ext4_end_bio:314: I/O error -5 writing to inode 4982294 (offset 79691776 size 4194304 starting block 103024384)
Dec  3 02:35:54 server kernel: [6703851.055021] EXT4-fs warning (device sda3): ext4_end_bio:314: I/O error -5 writing to inode 4982294 (offset 79691776 size 4194304 starting block 103024640)
Dec  3 02:35:54 server kernel: [6703851.055213] EXT4-fs warning (device sda3): ext4_end_bio:314: I/O error -5 writing to inode 4982294 (offset 83886080 size 1900544 starting block 103026944)
Dec  3 02:35:54 server kernel: [6703851.055433] EXT4-fs warning (device sda3): ext4_end_bio:314: I/O error -5 writing to inode 4982294 (offset 83886080 size 1900544 starting block 103027152)
Dec  3 02:35:54 server kernel: [6703851.059319] EXT4-fs warning (device sda3): ext4_end_bio:314: I/O error -5 writing to inode 4982268 (offset 67108864 size 8388608 starting block 103028992)
Dec  3 02:35:54 server kernel: [6703851.059532] EXT4-fs warning (device sda3): ext4_end_bio:314: I/O error -5 writing to inode 4982268 (offset 67108864 size 8388608 starting block 103029248)
Dec  3 02:35:54 server kernel: [6703851.059801] EXT4-fs warning (device sda3): ext4_end_bio:314: I/O error -5 writing to inode 4982268 (offset 67108864 size 8388608 starting block 103029504)
Dec  3 02:35:54 server kernel: [6703851.060325] EXT4-fs warning (device sda3): ext4_end_bio:314: I/O error -5 writing to inode 4982268 (offset 67108864 size 8388608 starting block 103029760)
Dec  3 02:35:54 server kernel: [6703851.063951] JBD2: Detected IO errors while flushing file data on sda3-8
Dec  3 02:35:54 server kernel: [6703851.063985] Aborting journal on device sda3-8.
Dec  3 02:35:54 server kernel: [6703851.064067] Buffer I/O error on dev sda3, logical block 57180160, lost sync page write
Dec  3 02:35:54 server kernel: [6703851.064118] JBD2: Error -5 detected when updating journal superblock for sda3-8.
Dec  3 02:35:54 server kernel: [6703851.064167] Buffer I/O error on dev sda3, logical block 0, lost sync page write
Dec  3 02:35:54 server kernel: [6703851.064252] EXT4-fs (sda3): previous I/O error to superblock detected
Dec  3 02:35:54 server kernel: [6703851.064387] Buffer I/O error on dev sda3, logical block 0, lost sync page write
Dec  3 02:35:54 server kernel: [6703851.064455] EXT4-fs error (device sda3): ext4_journal_check_start:56: Detected aborted journal
Dec  3 02:35:54 server kernel: [6703851.064459] EXT4-fs error (device sda3): ext4_journal_check_start:56: Detected aborted journal
Dec  3 02:35:54 server kernel: [6703851.064464] EXT4-fs (sda3): Remounting filesystem read-only
Dec  3 02:35:54 server kernel: [6703851.064483] EXT4-fs (sda3): previous I/O error to superblock detected
Dec  3 02:35:54 server kernel: [6703851.064555] Buffer I/O error on dev sda3, logical block 0, lost sync page write
Dec  3 02:35:54 server kernel: [6703851.065602] EXT4-fs error (device sda3) in ext4_do_update_inode:4976: Journal has aborted
Dec  3 02:35:54 server kernel: [6703851.065680] EXT4-fs (sda3): previous I/O error to superblock detected
Dec  3 02:35:54 server kernel: [6703851.065769] Buffer I/O error on dev sda3, logical block 0, lost sync page write
Dec  3 02:35:54 server kernel: [6703851.065814] EXT4-fs error (device sda3): mpage_map_and_submit_extent:2493: comm kworker/u97:3: Failed to mark inode 4981511 dirty
Dec  3 02:35:54 server kernel: [6703851.065908] EXT4-fs (sda3): previous I/O error to superblock detected
Dec  3 02:35:54 server kernel: [6703851.066035] Buffer I/O error on dev sda3, logical block 0, lost sync page write
Dec  3 02:35:54 server kernel: [6703851.066106] EXT4-fs error (device sda3) in ext4_writepages:2803: IO failure
Dec  3 02:35:54 server kernel: [6703851.066169] EXT4-fs (sda3): previous I/O error to superblock detected
Dec  3 02:35:54 server kernel: [6703851.066252] Buffer I/O error on dev sda3, logical block 0, lost sync page write
Dec  3 02:35:54 server kernel: [6703851.066382] Buffer I/O error on dev sda3, logical block 19923068, lost async page write
Dec  3 02:35:54 server kernel: [6703851.066431] Buffer I/O error on dev sda3, logical block 19923072, lost async page write
Dec  3 02:35:54 server kernel: [6703851.066471] Buffer I/O error on dev sda3, logical block 19931231, lost async page write
Dec  3 02:35:54 server kernel: [6703851.066781] JBD2: Detected IO errors while flushing file data on sda3-8
Dec  3 02:35:54 server kernel: [6703851.113024] megaraid_sas 0000:03:00.0: scanning for scsi0...
Dec  3 02:35:54 server kernel: [6703851.113103] megaraid_sas 0000:03:00.0: 6893 (628652089s/0x0001/FATAL) - VD 00/0 is now OFFLINE

Receive updates via email

Other Posts

Updated Posts