免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
最近访问板块 发新帖
查看: 2015 | 回复: 7
打印 上一主题 下一主题

求助,是否硬盘坏了? [复制链接]

论坛徽章:
0
跳转到指定楼层
1 [收藏(0)] [报告]
发表于 2006-12-21 10:15 |只看该作者 |倒序浏览
刚刚装的系统,总是报告:
Subject: SMART error (CurrentPendingSector) detected on host: jmwfirewall.test
This email was generated by the smartd daemon running on:

   host name: jmwfirewall.test
  DNS domain: test
  NIS domain: (none)

The following warning/error was logged by the smartd daemon:

Device: /dev/hda, 15 Currently unreadable (pending) sectors

For details see host's SYSLOG (default: /var/log/messages).

You can also use the smartctl utility for further investigation.
No additional email messages about this problem will be sent.

是否硬盘坏了?如何解决?求教

论坛徽章:
0
2 [报告]
发表于 2006-12-21 10:32 |只看该作者
==========================
用grep -i 'error' /var/log/messages*
有没结果,贴出来看一下。

论坛徽章:
0
3 [报告]
发表于 2006-12-21 10:47 |只看该作者
这个嘛?
# grep -i 'error' /var/log/messages*
/var/log/messages:Dec 18 13:39:56 jmwfirewall sendmail[3169]: auxpropfunc error no mechanism available
/var/log/messages:Dec 20 17:47:26 jmwfirewall sendmail[3289]: auxpropfunc error no mechanism available
/var/log/messages.1:Dec 15 14:25:09 jmwfirewall kernel:     ACPI-1134: *** Error: Method execution failed [\RTMP] (Node dbea1a80), AE_AML_UNINITIALIZED_LOCAL
/var/log/messages.1:Dec 15 14:25:09 jmwfirewall kernel:     ACPI-1134: *** Error: Method execution failed [\_TZ_.THRM._TMP] (Node dbea2840), AE_AML_UNINITIALIZED_LOCAL
/var/log/messages.1:Dec 15 14:25:18 jmwfirewall sendmail[3005]: auxpropfunc error no mechanism available
/var/log/messages.1:Dec 15 17:10:14 jmwfirewall kernel:     ACPI-1134: *** Error: Method execution failed [\RTMP] (Node dbea1a80), AE_AML_UNINITIALIZED_LOCAL
/var/log/messages.1:Dec 15 17:10:15 jmwfirewall kernel:     ACPI-1134: *** Error: Method execution failed [\_TZ_.THRM._TMP] (Node dbea2840), AE_AML_UNINITIALIZED_LOCAL

[ 本帖最后由 iamshiyu 于 2006-12-21 10:48 编辑 ]

论坛徽章:
0
4 [报告]
发表于 2006-12-21 10:52 |只看该作者
message里面倒是有很多类似这样的信息:
Dec 21 08:17:24 jmwfirewall smartd[3161]: Device: /dev/hda, 15 Currently unreadble (pending) sectors
Dec 21 08:47:24 jmwfirewall smartd[3161]: Device: /dev/hda, 15 Currently unreadble (pending) sectors
Dec 21 09:17:24 jmwfirewall smartd[3161]: Device: /dev/hda, 15 Currently unreadble (pending) sectors

论坛徽章:
0
5 [报告]
发表于 2006-12-21 10:53 |只看该作者
# smartctl -a /dev/hda
smartctl version 5.33 [i386-redhat-linux-gnu] Copyright (C) 2002-4 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Device Model:     HDS728080PLAT20
Serial Number:    PFD212S2TRMJNE
Firmware Version: PF2OA21B
User Capacity:    82,348,277,760 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   7
ATA Standard is:  ATA/ATAPI-7 T13 1532D revision 1
Local Time is:    Thu Dec 21 10:56:24 2006 CST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00) Offline data collection activity
                                        was never started.
                                        Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever
                                        been run.
Total time to complete Offline
data collection:                 (1828) seconds.
Offline data collection
capabilities:                    (0x5b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        No Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine
recommended polling time:        (   1) minutes.
Extended self-test routine
recommended polling time:        (  31) minutes.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000b   100   100   016    Pre-fail  Always       -       0
  2 Throughput_Performance  0x0005   100   100   050    Pre-fail  Offline      -       0
  3 Spin_Up_Time            0x0007   108   108   024    Pre-fail  Always       -       187 (Average 181)
  4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       407
  5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       1
  7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
  8 Seek_Time_Performance   0x0005   100   100   020    Pre-fail  Offline      -       0
  9 Power_On_Hours          0x0012   100   100   000    Old_age   Always       -       3289
10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       394
192 Power-Off_Retract_Count 0x0032   100   100   050    Old_age   Always       -       519
193 Load_Cycle_Count        0x0012   100   100   050    Old_age   Always       -       519
194 Temperature_Celsius     0x0002   141   141   000    Old_age   Always       -       39 (Lifetime Min/Max 9/54)
196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       1
197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       15
198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       49

SMART Error Log Version: 1
ATA Error Count: 389 (device log contains only the most recent five errors)
        CR = Command Register [HEX]
        FR = Features Register [HEX]
        SC = Sector Count Register [HEX]
        SN = Sector Number Register [HEX]
        CL = Cylinder Low Register [HEX]
        CH = Cylinder High Register [HEX]
        DH = Device/Head Register [HEX]
        DC = Device Command Register [HEX]
        ER = Error register [HEX]
        ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 389 occurred at disk power-on lifetime: 499 hours (20 days + 19 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 01 6d 11 7a e1  Error: UNC at LBA = 0x017a116d = 24777069

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  40 d0 01 6d 11 7a e1 00      01:19:21.100  READ VERIFY SECTOR(S)
  c8 d0 01 24 b0 24 e7 00      01:19:21.100  READ DMA
  40 d0 02 6d 11 7a e1 00      01:19:17.900  READ VERIFY SECTOR(S)
  c8 d0 01 ae 99 b3 e4 00      01:19:17.900  READ DMA
  40 d0 02 6b 11 7a e1 00      01:19:17.900  READ VERIFY SECTOR(S)

Error 388 occurred at disk power-on lifetime: 499 hours (20 days + 19 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 02 6d 11 7a e1  Error: UNC at LBA = 0x017a116d = 24777069

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  40 d0 02 6d 11 7a e1 00      01:19:17.900  READ VERIFY SECTOR(S)
  c8 d0 01 ae 99 b3 e4 00      01:19:17.900  READ DMA
  40 d0 02 6b 11 7a e1 00      01:19:17.900  READ VERIFY SECTOR(S)
  c8 d0 01 38 83 42 e2 00      01:19:17.900  READ DMA
  c8 d0 01 00 00 00 e0 00      01:19:17.900  READ DMA

Error 387 occurred at disk power-on lifetime: 499 hours (20 days + 19 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 02 6d 11 7a e1  Error: UNC at LBA = 0x017a116d = 24777069

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  40 d0 04 6b 11 7a e1 00      01:19:14.600  READ VERIFY SECTOR(S)
  c8 d0 01 00 00 00 e0 00      01:19:14.600  READ DMA
  40 d0 04 67 11 7a e1 00      01:19:14.600  READ VERIFY SECTOR(S)
  c8 d0 01 00 00 00 e0 00      01:19:14.600  READ DMA
  40 d0 08 67 11 7a e1 00      01:19:11.400  READ VERIFY SECTOR(S)

Error 386 occurred at disk power-on lifetime: 499 hours (20 days + 19 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 02 6d 11 7a e1  Error: UNC at LBA = 0x017a116d = 24777069

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  40 d0 08 67 11 7a e1 00      01:19:11.400  READ VERIFY SECTOR(S)
  c8 d0 01 24 b0 24 e7 00      01:19:11.400  READ DMA
  40 d0 08 5f 11 7a e1 00      01:19:11.400  READ VERIFY SECTOR(S)
  c8 d0 01 ae 99 b3 e4 00      01:19:11.400  READ DMA
  40 d0 10 6f 11 7a e1 00      01:19:11.300  READ VERIFY SECTOR(S)

Error 385 occurred at disk power-on lifetime: 499 hours (20 days + 19 hours)
  When the command that caused the error occurred, the device was active or idle.

  After command completion occurred, registers were:
  ER ST SC SN CL CH DH
  -- -- -- -- -- -- --
  40 51 02 6d 11 7a e1  Error: UNC at LBA = 0x017a116d = 24777069

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  40 d0 10 5f 11 7a e1 00      01:19:08.100  READ VERIFY SECTOR(S)
  c8 d0 01 00 00 00 e0 00      01:19:08.100  READ DMA
  40 d0 20 5f 11 7a e1 00      01:19:04.900  READ VERIFY SECTOR(S)
  40 d0 20 3f 11 7a e1 00      01:19:04.900  READ VERIFY SECTOR(S)
  40 d0 40 7f 11 7a e1 00      01:19:04.800  READ VERIFY SECTOR(S)

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]


Warning! SMART Selective Self-Test Log Structure error: invalid SMART checksum.
SMART Selective self-test log data structure revision number 1
SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

论坛徽章:
0
6 [报告]
发表于 2006-12-21 11:40 |只看该作者
smart报告不一定硬盘有错误,如果你能找到硬盘比如/dev/hda的error错误,那说明硬盘真的有错误产生了。
我怀疑你的smart是误报,你的操作系统有没有SeLinux的,如果某些文件被Flask安全引擎挡住也会产生类似的信息的。

论坛徽章:
0
7 [报告]
发表于 2006-12-21 12:39 |只看该作者
原帖由 飘雪心辰 于 2006-12-21 11:40 发表
smart报告不一定硬盘有错误,如果你能找到硬盘比如/dev/hda的error错误,那说明硬盘真的有错误产生了。
我怀疑你的smart是误报,你的操作系统有没有SeLinux的,如果某些文件被Flask安全引擎挡住也会产生类似的信 ...

这样啊?谢谢

论坛徽章:
0
8 [报告]
发表于 2007-01-04 09:04 |只看该作者
我用smartctl尝试修复,结果无法启动了……只好重装,但是重装以后smartd依然会报错(安装的时候已经关掉了selinux)……郁闷
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

北京盛拓优讯信息技术有限公司. 版权所有 京ICP备16024965号-6 北京市公安局海淀分局网监中心备案编号:11010802020122 niuxiaotong@pcpop.com 17352615567
未成年举报专区
中国互联网协会会员  联系我们:huangweiwei@itpub.net
感谢所有关心和支持过ChinaUnix的朋友们 转载本站内容请注明原作者名及出处

清除 Cookies - ChinaUnix - Archiver - WAP - TOP