WDC WD20EARS (2TB) - проблема диагностирования ¶
От: cosmonaut 9 марта 2012 г. 2:43
[b]WDC WD20EARS[/b]
использую Linux (Ubuntu 10.04 LTS), HDD целиком отформатирован в ext4
монтируется как [b]/home[/b] - т.е. активно используется, особенно торрентами
1-й раз сбойнул, когда на него залил 100...150 гигов, linux стал ругаться, что ошибка ввода/вывода (дословно не помню) - отнёс по гарантии - вернули, сказали все тесты прошёл - я отформатировал как обычно в ext4 и в работу...
2-й раз сбойнул через пару-тройку месяцев также при заполнении до определённого объёма, только перестал определяться в BIOS - отнёс по гарантии - вернули - увиделся в BIOS (!) - снова отформатировал как обычно в ext4 и в работу... только в этот раз подключил через внешний контейнер USB
3-й раз сбойнул когда заполнил его уже гигов на 400 - опять ошибка при записи и всё - тупо отключился...
вот сегодня дошли руки, подключил его в другой комп, запустил тестирование:
[b]badblocks -w -s -v /dev/sdb[/b] - т.е. тестирование с режимом запись/чтение
пока винт тестируется - проверил SMART:
[tt]
sudo smartctl -a /dev/sdb
smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Device Model: WDC WD20EARS-00MVWB0
Serial Number: WD-WMAZA3552388
Firmware Version: 51.0AB51
User Capacity: 2 000 398 934 016 bytes
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Fri Mar 9 00:44:09 2012 MSK
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: (0x84) Offline data collection activity
was suspended by an interrupting command from host.
Auto Offline Data Collection: Enabled.
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: (37200) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
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: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 255) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x3035) SCT Status supported.
SCT Feature Control supported.
SCT Data Table supported.
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 0x002f 200 200 051 Pre-fail Always - 0
3 Spin_Up_Time 0x0027 253 253 021 Pre-fail Always - 1316
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 73
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0
9 Power_On_Hours 0x0032 096 096 000 Old_age Always - 3156
10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 68
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 59
193 Load_Cycle_Count 0x0032 164 164 000 Old_age Always - 110941
194 Temperature_Celsius 0x0022 113 097 000 Old_age Always - 37
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 1
198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 1
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 1
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed without error 00% 126 -
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.
[/tt]
[color=red]... пока тестировался винт и я писал этот пост - винт сбойнул ![/color]
в логах следующее:
[tt]
Mar 9 01:11:26 space-next kernel: [ 8691.423776] ata4: link is slow to respond, please be patient (ready=0)
Mar 9 01:11:31 space-next kernel: [ 8696.400359] ata4: device not ready (errno=-16), forcing hardreset
Mar 9 01:11:31 space-next kernel: [ 8696.400368] ata4: soft resetting link
Mar 9 01:11:37 space-next kernel: [ 8701.588613] ata4: link is slow to respond, please be patient (ready=0)
Mar 9 01:11:41 space-next kernel: [ 8706.397481] ata4: soft resetting link
Mar 9 01:11:47 space-next kernel: [ 8711.585737] ata4: link is slow to respond, please be patient (ready=0)
Mar 9 01:11:51 space-next kernel: [ 8716.394583] ata4: soft resetting link
Mar 9 01:11:57 space-next kernel: [ 8721.582856] ata4: link is slow to respond, please be patient (ready=0)
Mar 9 01:12:19 space-next kernel: [ 8744.166159] ata4.00: configured for UDMA/133
Mar 9 01:12:19 space-next kernel: [ 8744.166165] ata4.00: device reported invalid CHS sector 0
Mar 9 01:12:19 space-next kernel: [ 8744.166172] ata4: EH complete
Mar 9 01:13:24 space-next kernel: [ 8809.252268] ata4: link is slow to respond, please be patient (ready=0)
Mar 9 01:13:29 space-next kernel: [ 8814.228863] ata4: device not ready (errno=-16), forcing hardreset
Mar 9 01:13:29 space-next kernel: [ 8814.228872] ata4: soft resetting link
Mar 9 01:13:35 space-next kernel: [ 8819.417138] ata4: link is slow to respond, please be patient (ready=0)
Mar 9 01:13:39 space-next kernel: [ 8824.225971] ata4: soft resetting link
Mar 9 01:13:45 space-next kernel: [ 8829.414230] ata4: link is slow to respond, please be patient (ready=0)
Mar 9 01:13:49 space-next kernel: [ 8834.223090] ata4: soft resetting link
Mar 9 01:13:55 space-next kernel: [ 8839.411351] ata4: link is slow to respond, please be patient (ready=0)
Mar 9 01:14:19 space-next kernel: [ 8864.135014] ata4.00: configured for UDMA/133
Mar 9 01:14:19 space-next kernel: [ 8864.135021] ata4.00: device reported invalid CHS sector 0
Mar 9 01:14:19 space-next kernel: [ 8864.135030] ata4: EH complete
Mar 9 01:14:32 space-next kernel: [ 8877.151136] ata4: link is slow to respond, please be patient (ready=0)
Mar 9 01:14:37 space-next kernel: [ 8882.127721] ata4: device not ready (errno=-16), forcing hardreset
Mar 9 01:14:37 space-next kernel: [ 8882.127740] ata4: soft resetting link
Mar 9 01:14:43 space-next kernel: [ 8887.316002] ata4: link is slow to respond, please be patient (ready=0)
Mar 9 01:14:47 space-next kernel: [ 8892.124888] ata4: soft resetting link
Mar 9 01:14:53 space-next kernel: [ 8897.313108] ata4: link is slow to respond, please be patient (ready=0)
Mar 9 01:14:57 space-next kernel: [ 8902.121943] ata4: soft resetting link
Mar 9 01:15:03 space-next kernel: [ 8907.310206] ata4: link is slow to respond, please be patient (ready=0)
Mar 9 01:15:33 space-next kernel: [ 8937.113828] ata4: soft resetting link
Mar 9 01:15:38 space-next kernel: [ 8942.134346] ata4.00: disabled
Mar 9 01:15:38 space-next kernel: [ 8942.134363] ata4: EH complete
Mar 9 01:15:38 space-next kernel: [ 8942.134400] sd 3:0:0:0: [sdb] Unhandled error code
[/tt]
...потом много подобных сообщений типа (как я понимаю винт уже отвалился):
[tt]
Mar 9 01:15:38 space-next kernel: [ 8942.134400] sd 3:0:0:0: [sdb] Unhandled error code
Mar 9 01:15:38 space-next kernel: [ 8942.134402] sd 3:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Mar 9 01:15:38 space-next kernel: [ 8942.134405] sd 3:0:0:0: [sdb] CDB: Write(10): 2a 00 32 08 d4 00 00 00 80 00
Mar 9 01:15:38 space-next kernel: [ 8942.134590] sd 3:0:0:0: [sdb] Unhandled error code
Mar 9 01:15:38 space-next kernel: [ 8942.134593] sd 3:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
Mar 9 01:15:38 space-next kernel: [ 8942.134596] sd 3:0:0:0: [sdb] CDB: Read(10): 28 00 32 08 d4 00 00 00 08 00
[/tt]
... да и smartctl теперь не видит винта:
[tt]sudo smartctl -a /dev/sdb
smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
Short INQUIRY response, skip product id
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
[/tt]
Надо опять нести в гарантию, прошу помочь советом, что хоть такое может быть с этим диском, может кто сталкивался с подобным ?