Shulou(Shulou.com)06/03 Report--

log message symptom description hard disk relation scsi1: ERROR on channel 0, id 7, lun 0, CDB: Read (10) 00 73 fc 62 bf 00 00 80 00

Info fld=0x73fc6326, Current sdi: sense key Medium Error

Additional sense: Unrecovered read errorSMART specification defines a "Medium Error" error as an unrecoverable error, possibly due to a defect in the media or an error in the recorded data. This error is different from "Hardware Error."

The main reason for Medium Error is that the hard disk is bad, or the data on the hard disk cannot be read or written. (1) Bad hard disk sectors

or (2) The connection signal quality between hard disk and disk controller is unstable, resulting in abnormal data mptbase: ioc1: IOCStatus=804b LogInfo=31080000

Originator={PL}, Code={SATA NCQ Fail All Commands After Error}, SubCode(0×0000)

Native Command Queuing (NCQ), originally to improve server hard disk access control technology, applied to SCSI and SATA 1.0/2.0/3.0 interface hard disk read and write acceleration technology, its interface open disk array RAID has also been improved. By improving the read order of the internal sectors of the hard disk through the coordination of the hard disk firmware, hard disk controller and operating system, the performance of the hard disk can be improved by about 30%, and the wear rate of the hard disk can be slightly reduced. NCQ's efficiency gains are particularly significant for hard disks used on servers.

PL: Protocol layer in the disk controller

end_request: I/O error, dev sdi, sector 1945920256

EXT2-fs error (device sdi1): read_inode_bitmap: Cannot read inode bitmap - block_group = 222, inode_bitmap = 14547217

EXT2-fs error (device sdi1): ext2_get_inode: unable to read inode block - inode=951895, block=15202501

The kernel cannot read data from the file system on the hard disk.

(1) The hard disk sector is bad.

or (2) the hard disk and disk controller connection signal quality is unstable, resulting in abnormal data. mptbase: ioc1: IOCStatus=8000 LogInfo=31110d00

Originator={PL}, Code={Reset}, SubCode(0x0d00)

mptbase: ioc1: IOCStatus=804b LogInfo=31110d00

Originator={PL}, Code={Reset}, SubCode(0x0 d00) The drive is ready to reset the IOC unit of the disk controller. The reason for this operation is that the drive has found that it has failed to read and write hard disk data for many times.

IOCStatus=0×8000

Disk controller configuration pages are shared recursively.

IOCStatus=0×8048

Attempted to read nonexistent super configuration data.

IOCStatus=0x804b

Super data sequence number changed from 0xffffff to 0

This information cannot be used as a basis for hard disk failure. The reason for printing this information is related to the link between the hard disk/disk controller IOC unit/hard disk and the controller. See above for IOC error code meaning. mptscsih: ioc1: attempting task abort! (sc=000001007b4cf340)

scsi1 : destination target 8, lun 0

command = Read (10) 00 5f 2a 4d 3f 00 10 00 00 The disk controller driver attempted to cancel the read/write task. In this example code, the read task at target 8, lun 0 is canceled. This information has no direct contact with whether the hard disk is faulty mptbase: ioc1: IOCStatus=8048 LogInfo=31130000

Originator={PL}, Code={IO Not Yet Executed}, SubCode(0×0000)

Disk controller driver reports current IOC (I/O Controller) unit status code This information has no direct connection with whether the hard disk fails mptscsih: ioc1: task abort: SUCCESS (sc= 00001007 b4cf340) Disk controller driver reports that the read/write task is cancelled successfully This information has no direct connection with whether the hard disk fails mptscsih: ioc1: attempting target reset!

mptscsih: ioc1: attempting bus reset! (sc=000001007b4cf340)

mptscsih: ioc1: Attempting host reset! (sc=000001007b4cf340)

mptbase: Initiating ioc1 recovery

The disk controller driver attempts to reset target/bus/host and restore the IOC (I/O Controller) unit. This information cannot be used as a basis for hard disk failure. The reason for printing this information is related to the link between the hard disk/disk controller IOC unit/hard disk and the controller. scsi: Device offline- not ready after error recovery: host 1 channel 0 id 8 lun 0 hard disk offline, hard disk location is host 1 channel 0 id 8 lun 0 hard disk is in a failed state or missing SCSI error : return code = 0×10000

end_request: I/O error, dev sdj, sector 1596607807

scsi1 (8:0): rejecting I/O to offline deviceThe SCSI layer reports a read/write error on the host 1 channel 0 id 8 lun 0 device with a return code of 0×10000, indicating that the device is no longer in place. Hard disk failure or loss mptsas: ioc1: attaching sata device, channel 0, id 11, lun 0, phy 0 A new hard disk is added to the system, and the hard disk is located at phy 0, the first physical slot. Insert a new hard disk mptsas: ioc0: removing sata device, channel 0, id 21, phy 2 Remove a hard disk from the system. The corresponding physical location of the hard disk is phy 2, i.e. the third physical slot. Removing a hard drive Removing filesystem read-only The filesystem becomes read-only because the filesystem is corrupted and has nothing to do with hard drive failure

Note: This article takes Linux kernel log information using LSI SAS 1064E/1068E SAS controller server as an example, i.e. disk controller driver is mptsas.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.