主数据驱动器出现 I/O 错误

主数据驱动器出现 I/O 错误

我的主数据驱动器出现各种奇怪的 I/O 错误:

(tail of dmesg output)
[ 7081.267852] sd 4:0:0:0: [sdb] Unhandled error code
[ 7081.267856] sd 4:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[ 7081.267860] sd 4:0:0:0: [sdb] CDB: Read(10): 28 00 36 c4 48 d0 00 00 08 00
[ 7081.267870] end_request: I/O error, dev sdb, sector 918833360
[ 7081.270431] sd 4:0:0:0: [sdb] Unhandled error code
[ 7081.270435] sd 4:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[ 7081.270439] sd 4:0:0:0: [sdb] CDB: Read(10): 28 00 36 c4 48 d0 00 00 08 00
[ 7081.270449] end_request: I/O error, dev sdb, sector 918833360
[ 7081.468662] sd 4:0:0:0: [sdb] Unhandled error code
[ 7081.468667] sd 4:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
[ 7081.468671] sd 4:0:0:0: [sdb] CDB: Read(10): 28 00 36 c4 48 d0 00 00 08 00
[ 7081.468681] end_request: I/O error, dev sdb, sector 918833360
saad@Home-Server:~$ tail /var/log/syslog
Mar 15 14:23:19 Home-Server kernel: [ 7081.270431] sd 4:0:0:0: [sdb] Unhandled error code
Mar 15 14:23:19 Home-Server kernel: [ 7081.270435] sd 4:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Mar 15 14:23:19 Home-Server kernel: [ 7081.270439] sd 4:0:0:0: [sdb] CDB: Read(10): 28 00 36 c4 48 d0 00 00 08 00
Mar 15 14:23:19 Home-Server kernel: [ 7081.270449] end_request: I/O error, dev sdb, sector 918833360
Mar 15 14:23:19 Home-Server kernel: [ 7081.468662] sd 4:0:0:0: [sdb] Unhandled error code
Mar 15 14:23:19 Home-Server kernel: [ 7081.468667] sd 4:0:0:0: [sdb]  Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Mar 15 14:23:19 Home-Server kernel: [ 7081.468671] sd 4:0:0:0: [sdb] CDB: Read(10): 28 00 36 c4 48 d0 00 00 08 00
Mar 15 14:23:19 Home-Server kernel: [ 7081.468681] end_request: I/O error, dev sdb, sector 918833360

驱动器坏了吗?还是 mbr 损坏问题?

答案1

到目前为止,MBR 不太可能存在 - 要么是驱动器问题,要么是随机损坏,如果还没有备份,请尽快备份!

然后你需要在其上运行 fsck 和 badblocks:

sudo -i
fsck -t ext4 /dev/sdb1 # or whatever partition it is..
e2fsck -c /dev/sdb

badblocks 的手册页建议以这种方式执行,而不是直接执行。如果它有 SMART 监控,那么请查看日志并运行测试。

相关内容