when DMESG, the following message appears to indicate a problem with the disk
Info fld=0x139066d0end_request:i/o error, Dev SDA, Sector 328230608Buffer I/O error on device SDA, logical block 41028826 SD 0:0:0:0: SCSI error:return code = 0x08000002sda:current:sense Key:medium error ADD. sense:unrecovered Read ErrorInfo fld=0x139066d0end_request:i/o error, Dev SDA, Sector 328230608Buffer I/O error on Devic E SDA, logical block 41028826SD 0:0:0:0: SCSI error:return code = 0x08000002sda:current:sense Key:medium error ADD. sense:unrecovered Read ErrorInfo fld=0x139066d0end_request:i/o error, Dev SDA, Sector 328230608Buffer I/O error on Devi Ce SDA, logical block 41028826SD 0:0:0:0: SCSI error:return code = 0x08000002sda:current:sense Key:medium Error ADD . sense:unrecovered Read ErrorInfo fld=0x139066d0end_request:i/o error, Dev SDA, Sector 328230608Buffer I/O error on Devic E SDA, logical block 41028826SD 0:0:0:0: SCSI error:return code = 0x08000002sda:current:sense Key:medium error ADD. Sense:unrecovered Read error
1. First detect the broken down
Badblocks-s-v-o/ROOT/BB.LOG/DEV/SDA Save the results to Bb.log
[Email protected] ~]# badblocks-s-v-o/root/badblocks.log/dev/0586061784 for ill blocks (read-onlytest): done173 bad blocks found.
Smartctl-a/dev/sda3 (Fast detection of hard drive bad, see Read,write back there is no errors)
2. Logical bad Path repair method
①, Badblocks-s-W/DEV/SDA end Start (end represents the end of the sector that needs to be repaired, and start represents the starting end of the sector that needs to be repaired)
②, Fsck-a/DEV/SDA
After repair and then use badblocks-s-v-o/ROOT/BB.LOG/DEV/SDA monitoring to see if there is still a bad path exists, if the bad word or exist, it means bad road belongs to the hard drive bad. Hard drive bad path to use the Isolation method, first record the detected hard drive bad channel and then partition the hard drive bad path is located in a partition (the size is generally greater than the bad sector size), divided the bad channel partition is not used to achieve the purpose of isolation
3.0 track bad and hard drive bad (ready to change the hard drive)
0 Track Bad track repair method is to isolate 0 tracks, the use of Fdsk partition area from 1 tracks began to partition.
If the hard drive is bad, only quarantine cannot be repaired.
CentOS appears to have disk broken, how to repair and detect.