磁盘blk_update_request: I/O error

简介: 1、尝试1:解决 blk_update_request: I/O error, dev fd0, sector 0 错误参考文档:https://bbs.archlinux.org/viewtopic.

1、尝试1:

解决 blk_update_request: I/O error, dev fd0, sector 0 错误

https://bbs.archlinux.org/viewtopic.php?pid=1166918#p1166918

http://www.cyberciti.biz/faq/linux-end_request-ioerror-dev-fd0-sector0/

在开启了软驱驱动控制器的硬件上引导 Linux 时会出现如下提示:
blk_update_request: I/O error, dev fd0, sector 0

通过在关闭软驱模块来解决错误提示:

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

尝试2:

<strong>当dmesg的时候,出现下面的信息说明磁盘有问题</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. 首先检测下坏掉

badblocks -s -v -o /root/bb.log /dev/sda  将结果保存到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 (快速检测硬盘坏道,看read,write 后面有没有errors)

2. 逻辑坏道修复方法

①、badblocks -s -w /dev/sda END START (END代表需要修复的扇区末端,START代表需要修复的扇区起始端)
②、fsck -a /dev/sda

修复后再用badblocks -s -v -o /root/bb.log /dev/sda监测看是否还有坏道存在,如果坏道还是存在的话说明坏道属于硬盘坏道。硬盘坏道要用隔离方法,首先记录监测出的硬盘坏道然后分区的时候把硬盘坏道所在的扇区分在一个分区(大小一般大于坏扇区大小),划分出的坏道分区不使用即可达到隔离的目的

3. 0磁道坏道和硬盘坏道(准备换硬盘)

0磁道坏道的修复方法是隔离0磁道,使用fdsk划分区的时候从1磁道开始划分区。

如果是硬盘坏道的话,只能隔离不能修复

 

相关文章
|
8月前
ES集群报错 failed to send join request to maste
ES集群报错 failed to send join request to maste
101 0
|
Web App开发 Cloud Native Docker
删除容器报错:Error response from daemon: conflict: unable to delete
云原生日益普及的现在,docker容器化成为现有很多服务的改进方向,docker凭借更高效的利用系统资源、更快速的启动时间、一致的运行环境、持续支付和部署、更轻松的迁移、更轻松的维护和拓展等优势,迅速走红。但是,很多容器部署后在回收时,都会遇到各种各样的问题,比如今天讨论的删除镜像的问题,有时候删除操作会莫名其妙的报错。
756 1
|
11月前
iSCSI Login negotiation failed. lost page write due to I/O error on 盘变成read only
iscsi mount的盘的突然变成read only,在系统日志messages中有下面的记录
147 0
|
索引
ES报错:“type“=>“cluster_block_exception“, “reason“=>“blocked by: [FORBIDDEN/12/index read-only / allow
ES报错:“type“=>“cluster_block_exception“, “reason“=>“blocked by: [FORBIDDEN/12/index read-only / allow
273 0
ES报错:“type“=>“cluster_block_exception“, “reason“=>“blocked by: [FORBIDDEN/12/index read-only / allow
PHPExcel在高版本PHP7中,Writer-&gt;save出现ERR_INVALID_RESPONSE错误的解决方法
PHPExcel在高版本PHP7中,Writer-&gt;save出现ERR_INVALID_RESPONSE错误的解决方法
203 0
|
Python
pip 安装库失败问题:Retrying (Retry(total=4, connect=None, read=None, redirect=None, status =None)),原因及解决办法
pip 安装库失败问题:Retrying (Retry(total=4, connect=None, read=None, redirect=None, status =None)),原因及解决办法
12330 0
|
Oracle 关系型数据库 Linux
Alert 日志报错:ORA-2730x OS Failure Message: No Buffer Space Available
今天巡检遇到数据库报错 ORA-2730x 错误,数据库版本为Oracle 11204 (x86_64),错误日志如下:
Alert 日志报错:ORA-2730x OS Failure Message: No Buffer Space Available
callbackend entry point - iwfndcl_mgw_request_manager~read_entity
007. callbackend entry point - /iwfnd/cl_mgw_request_manager~read_entity Created by Wang, Jerry, last modified on Jan 06, 2015
146 0
callbackend entry point - iwfndcl_mgw_request_manager~read_entity
|
Docker 容器
Error response from daemon: conflict: unable to delete 31f279e888c0 (must be forced) - image is bein
Error response from daemon: conflict: unable to delete 31f279e888c0 (must be forced) - image is bein
133 0
Error response from daemon: conflict: unable to delete 31f279e888c0 (must be forced) - image is bein