1. Try 1:
Blk_update_request: I/O error, dev fd0, Sector 0 error resolved

Reference document:

https://bbs.archlinux.org/viewtopic.php?pid=1166918#p1166918
http://www.cyberciti.biz/faq/linux-end_request-ioerror-dev-fd0-sector0/

blk_update_request: I/O error, dev fd0, sector 0 when booting Linux on hardware with floppy drive controller on
Resolve the error message by closing the floppy drive module:
#
# /etc/modprobe.d/modprobe.conf
#
blacklist floppy
Try 2:

1. First detect the failure
Badblock-s-v-o /root/bb.log /dev/sda save the results 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 errors after read and write)
2. Repair method of logical bad path

, badblock-s-w /dev/sda END START (END stands for the END of the sector to be repaired, START stands for the beginning of the sector to be repaired)
, fsck-a /dev/sda
After the repair, badblock-s-v-o /root/bb.log /dev/sda will be used to monitor for bad tracks. If there are bad tracks, it is a bad hard drive. Hard disk bad way to use the isolation method, first of all, the monitoring of the hard disk bad way and then partition when the hard disk bad way in the sector is divided in a partition (size is generally greater than the size of the bad sector), the partition of the bad way partition can achieve the purpose of isolation
3. 0 Bad track and hard drive (ready to replace hard drive)
The repair method of bad track of 0 track is to isolate track of 0 track. When using FDSK to divide the area, divide the area from track of 1.
If it's a bad drive, it can only be quarantined and not repaired
 

Reproduced in: https://www.cnblogs.com/wangjq19920210/p/9238910.html