我不断收到这些消息在我的服务器内核日志（这是负责文件操作）。 我想知道有没有人知道这些问题有多严重。 我不能使用smartmontools，因为磁盘是由拥有自己的（非常有限的tw_cli实用程序）的3ware卡处理的。
[2522065.275739] sd 0:0:1:0: [sdg] CDB: [2522065.275741] Read(10): 28 00 2e 90 97 f8 00 00 08 00 [2522065.275750] end_request: I/O error, dev sdg, sector 781228024 [2522065.281091] Buffer I/O error on device sdg, logical block 97653503 [2522065.287157] sd 0:0:1:0: [sdg] Device not ready [2522065.287163] sd 0:0:1:0: [sdg] [2522065.287166] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [2522065.287168] sd 0:0:1:0: [sdg] [2522065.287170] Sense Key : Not Ready [current] [2522065.287174] sd 0:0:1:0: [sdg] [2522065.287176] Add. Sense: Logical unit not ready, cause not reportable [2522065.287179] sd 0:0:1:0: [sdg] CDB: [2522065.287181] Read(10): 28 00 00 00 00 00 00 00 20 00 [2522065.287190] end_request: I/O error, dev sdg, sector 0 [2522065.291147] Buffer I/O error on device sdg, logical block 0 [2522065.291147] Buffer I/O error on device sdg, logical block 1 [2522065.291147] Buffer I/O error on device sdg, logical block 2 [2522065.308465] sd 0:0:1:0: [sdg] Device not ready [2522065.308465] sd 0:0:1:0: [sdg] [2522065.308465] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [2522065.308465] sd 0:0:1:0: [sdg] [2522065.308465] Sense Key : Not Ready [current] [2522065.308465] sd 0:0:1:0: [sdg] [2522065.308465] Add. Sense: Logical unit not ready, cause not reportable [2522065.308465] sd 0:0:1:0: [sdg] CDB: [2522065.308465] Read(10): 28 00 00 00 00 00 00 00 08 00 [2522065.308465] end_request: I/O error, dev sdg, sector 0 谢谢！
您可以使用智能值：例如：
smartctl -a -d 3ware,2 /dev/twe0
Qout smartctl的手册页：
Under Linux and FreeBSD, to look at ATA disks behind 3ware SCSI RAID controllers, use syntax such as: smartctl -a -d 3ware,2 /dev/sda smartctl -a -d 3ware,0 /dev/twe0 smartctl -a -d 3ware,1 /dev/twa0 where in the argument 3ware,N, the integer N is the disk number (3ware ´port´) within the 3ware ATA RAID controller. The allowed values of N are from 0 to 31 inclusive. The first two forms, which refer to devices /dev/sda-z and /dev/twe0-15, may be used with 3ware series 6000, 7000, and 8000 series controllers that use the 3x-xxxx driver. Note that the /dev/sda-z form is deprecated starting with the Linux 2.6 kernel series and may not be supported by the Linux kernel in the near future. The final form, which refers to devices /dev/twa0-15, must be used with 3ware 9000 series controllers, which use the 3w-9xxx driver. Note that if the special character device nodes /dev/twa? and /dev/twe? do not exist, or exist with the incorrect major or minor numbers, smartctl will recreate them on the fly. Typically /dev/twa0 refers to the first 9000-series controller, /dev/twa1 refers to the second 9000 series controller, and so on. Likewise /dev/twe0 refers to the first 6/7/8000-series controller, /dev/twa1 refers to the second 6/7/8000 series controller, and so on.
有关您的问题的一些想法：
这可能还不是HDD / SSD的全面问题，但我build议尽快更改。
做备份，如果你还没有做到这一点呢！
你可以用类似的东西检查一个问题：
e2fsck -fv /dev/sdX
如果你看到聪明的重新分配的行业，你应该改变我的看法。
您可以使用（例如）访问智能信息：
smartctl -a -d 3ware,N /dev/twa0
N是端口nr，twa0是控制器。
通过以下你可以获得一些接口错误统计信息：
smartctl -l sataphy -d 3ware,N /dev/twa0
通过这个命令，我可以确定我在日志中遇到的“exception情况”是接口/电缆错误的结果，因为CRC计数增加了（最终需要用不同的typesreplace磁盘）。相同的types没有帮助）。 看着它，一个普通的SATA控制器给你更多的信息比一个3Ware端口。
至于“缓冲区错误”，我从来没有这样做，所以我不能推测。 过去我在软件RAID方面有过很多“例外”，这几乎总是失败的先兆。 因此，我现在扫描我的日志。