Tag Archives: blk_update_request: I/O error

How to Solve Disk blk_update_request: I/O error

When booting Linux on the hardware with the floppy drive controller turned on, the following prompt will appear:
blk_update_request: I/O error, dev fd0, sector 0

Solve the error message by closing the floppy drive module:

#
# /etc/modprobe.d/modprobe.conf
#
blacklist floppy

Attempt 2:

<strong>When dmesg, the following message appears indicating a problem with the disk</strong><br><br>Info fld=0x139066d0
end_request: I/O error, dev sda, sector 328230608
Buffer I/O error  on  device sda, logical block 41028826
sd 0:0:0:0: SCSI error:  return  code = 0x08000002
sda: Current: sense key: Medium Error
     Add. Sense: Unrecovered read error
Info fld=0x139066d0
end_request: I/O error, dev sda, sector 328230608
Buffer I/O error  on  device sda, logical block 41028826
sd 0:0:0:0: SCSI error:  return  code = 0x08000002
sda: Current: sense key: Medium Error
     Add. Sense: Unrecovered read error
Info fld=0x139066d0
end_request: I/O error, dev sda, sector 328230608
Buffer I/O error  on  device sda, logical block 41028826
sd 0:0:0:0: SCSI error:  return  code = 0x08000002
sda: Current: sense key: Medium Error
     Add. Sense: Unrecovered read error
Info fld=0x139066d0
end_request: I/O error, dev sda, sector 328230608
Buffer I/O error  on  device sda, logical block 41028826
sd 0:0:0:0: SCSI error:  return  code = 0x08000002
sda: Current: sense key: Medium Error
     Add. Sense: Unrecovered read error

1. First detect the failure

badblocks -s -v -o /root/bb.log /dev/sda save the result to bb.log

[root@logging ~]# badblocks -s -v -o /root/badblocks.log /dev/sda
Checking blocks 0 to 586061784
Checking for bad blocks (read-only test): done                                
Pass completed, 173 bad blocks found.

 

smartctl -a /dev/sda3 (Quickly detect bad sectors on the hard disk, see if there are errors behind read and write)

2. Logic bad sectors repair method

①, badblocks -s -w /dev/sda END START (END represents the end of the sector that needs to be repaired, START represents the beginning of the sector that needs to be repaired)
②, fsck -a /dev/sda

After repairing, use badblocks -s -v -o /root/bb.log /dev/sda to monitor whether there are any bad sectors. If the bad sectors still exist, it means that the bad sectors are hard disk bad sectors. The hard disk bad sectors should be isolated. Firstly, record the detected bad sectors of the hard disk and then divide the sectors where the hard disk bad sectors are located in a partition (the size is generally larger than the size of the bad sector), and the divided bad sector partitions are not used. Can achieve the purpose of isolation

3. 0 bad track and hard drive (ready to change hard drive)

The repair method for bad tracks of track 0 is to isolate track 0, and when using fdsk to divide the area, start dividing the area from track 1.

If it is a bad sector of the hard disk, it can only be isolated but not repaired