gmirror - отваливается винт

[Гость]

День добрый!

3 года проработало зеркало - теперь начал отваливаться винт.

ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=50944512
ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=52328704
ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=87725312
ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=136697088
ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=186122496
ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=231917568
ad6: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=278320128
ad6: TIMEOUT - WRITE_DMA48 retrying (0 retries left) LBA=278320128
ad6: FAILURE - WRITE_DMA48 timed out LBA=278320128
GEOM_MIRROR: Synchronization request failed (error=5). ad6[WRITE(offset=142499905536, length=131072)]
GEOM_MIRROR: Device gm0: provider ad6 disconnected.
GEOM_MIRROR: Device gm0: rebuilding provider ad6 stopped.

При этом происходят жуткие тормоза. Машина на 1-2 минуты становится не доступной. ad6 проверен - сбойных кластеров нет.

[Хостинг HostFood.ru]

Тарифы на хостинг в России, от 12 рублей: https://www.host-food.ru/tariffs/hosting/
Тарифы на виртуальные сервера (VPS/VDS/KVM) в РФ, от 189 руб.: https://www.host-food.ru/tariffs/virtualny-server-vps/
Выделенные сервера, Россия, Москва, от 2000 рублей (HP Proliant G5, Intel Xeon E5430 (2.66GHz, Quad-Core, 12Mb), 8Gb RAM, 2x300Gb SAS HDD, P400i, 512Mb, BBU):
https://www.host-food.ru/tariffs/vydelennyi-server-ds/
Недорогие домены в популярных зонах: https://www.host-food.ru/domains/

[GhOsT_MZ]

Смарт винта можно?

[Гость]

Второй раз день добрый!

После 3х лет работы, на сервере разваливается зеркало.При попытке собрать:

gmirror forget gm0
gmirror insert gm0 /dev/ad6

Зеркало начинает собираться, при этом:

dmesg
...................................
ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=50944512
ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=52328704
ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=87725312
ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=136697088
ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=186122496
ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=231917568

и в конце концов:

ad6: TIMEOUT - WRITE_DMA48 retrying (1 retry left) LBA=278320128
ad6: TIMEOUT - WRITE_DMA48 retrying (0 retries left) LBA=278320128
ad6: FAILURE - WRITE_DMA48 timed out LBA=278320128
GEOM_MIRROR: Synchronization request failed (error=5). ad6[WRITE(offset=142499905536, length=131072)]
GEOM_MIRROR: Device gm0: provider ad6 disconnected.
GEOM_MIRROR: Device gm0: rebuilding provider ad6 stopped.

ad6 - живой, рабочий винт - проверено

З.Ы. Уже писал - но тема куда то пропала

[Гость]

Смарт винта можно?

smartools ??? машина "закрыта" для установки доп. прог. обеспечения

[manefesto]

WRITE_DMA говорит что винт мрет

[manefesto]

Смарт винта можно?

smartools ??? машина "закрыта" для установки доп. прог. обеспечения

тогда выведи винт из зеркала

[GhOsT_MZ]

Не факт, недавно было, что аналогичные ошикби (если память не изменяет) были при убитом шлейфе, вот и прошу СМАРТ

[Гость]

WRITE_DMA говорит что винт мрет

проверял MHDD - все ок

[Гость]

Не факт, недавно было, что аналогичные ошикби (если память не изменяет) были при убитом шлейфе, вот и прошу СМАРТ

т.е. надо установить смарттулс? машина закрыта для установки не прописанного в "документе" ПО. Есть другие варианты?

[GhOsT_MZ]

т.е. надо установить смарттулс? машина закрыта для установки не прописанного в "документе" ПО. Есть другие варианты?

Да можно и той же Victoria, не суть важно чем.
Интересно было бы посмотреть на этот "документ", который не предполагает софт для мониторинга состояния железа...

[Гость]

т.е. надо установить смарттулс? машина закрыта для установки не прописанного в "документе" ПО. Есть другие варианты?

Да можно и той же Victoria, не суть важно чем.
Интересно было бы посмотреть на этот "документ", который не предполагает софт для мониторинга состояния железа...

внутренний документ - сейчас пытаюсь получить разрешение...



такой вариант возможен?

1. Зеркало состоит из двух винтов по 500гигов.
2. покупаю два 1000гигов.
3. вывожу битый винт из зеркала
4. вставляю терабайтник
5. синхронизирую
6. вывожу 500-ик и удаляю его
7. вставляю 2ой терабайтник
8. синхронизирую

[GhOsT_MZ]

Насколько известно, главное, чтобы новый диск был не меньше, но наверняка сказать не могу, ибо не приходилось сталкиваться с такими ситуациями.

[Гость]

Не факт, недавно было, что аналогичные ошикби (если память не изменяет) были при убитом шлейфе, вот и прошу СМАРТ

smartctl -a /dev/ad6

smartctl 5.42 2011-10-20 r3458 [FreeBSD 7.0-RELEASE i386] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model: GB0500C8046
Serial Number: 9QM37N0W
LU WWN Device Id: 5 000c50 00cc1c99e
Firmware Version: HPG1
User Capacity: 500 107 862 016 bytes [500 GB]
Sector Size: 512 bytes logical/physical
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 7
ATA Standard is: ATA/ATAPI-7 T13 1532D revision 4a
Local Time is: Fri Mar 2 13:42:16 2012 YEKT
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: (0x82) Offline data collection activity
was completed without error.
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: ( 642) 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: ( 120) minutes.
Conveyance self-test routine
recommended polling time: ( 3) minutes.
SCT capabilities: (0x103f) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 082 063 044 Pre-fail Always - 170679072
3 Spin_Up_Time 0x0003 099 099 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 56
5 Reallocated_Sector_Ct 0x0033 080 080 036 Pre-fail Always - 412
7 Seek_Error_Rate 0x000f 079 060 030 Pre-fail Always - 21926914735
9 Power_On_Hours 0x0032 069 069 000 Old_age Always - 27807
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 56
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
188 Command_Timeout 0x0032 099 094 000 Old_age Always - 11993271
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 067 061 045 Old_age Always - 33 (Min/Max 27/38)
194 Temperature_Celsius 0x0022 033 040 000 Old_age Always - 33 (0 19 0 0 0)
195 Hardware_ECC_Recovered 0x001a 024 024 000 Old_age Always - 170679072
196 Reallocated_Event_Count 0x0033 080 080 036 Pre-fail Always - 412
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 17

SMART Error Log Version: 1
ATA Error Count: 1600 (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 1600 occurred at disk power-on lifetime: 2583 hours (107 days + 15 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
-- -- -- -- -- -- --
04 71 03 80 01 32 e0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
ec 00 00 00 00 00 e0 00 21d+14:50:25.278 IDENTIFY DEVICE
ec 00 00 00 00 00 e0 00 21d+14:50:25.277 IDENTIFY DEVICE
00 00 00 00 00 00 00 04 21d+14:50:14.083 NOP [Abort queued commands]
00 00 00 00 00 00 00 ff 21d+14:50:13.074 NOP [Abort queued commands]
08 00 aa 01 ff 00 a0 00 21d+14:49:44.620 DEVICE RESET

Error 1599 occurred at disk power-on lifetime: 2583 hours (107 days + 15 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
-- -- -- -- -- -- --
04 71 03 80 01 32 e0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
ec 00 00 00 00 00 e0 00 21d+14:50:25.277 IDENTIFY DEVICE
00 00 00 00 00 00 00 04 21d+14:50:14.083 NOP [Abort queued commands]
00 00 00 00 00 00 00 ff 21d+14:50:13.074 NOP [Abort queued commands]
08 00 aa 01 ff 00 a0 00 21d+14:49:44.620 DEVICE RESET
00 00 00 00 00 00 00 04 21d+14:49:43.912 NOP [Abort queued commands]

Error 1598 occurred at disk power-on lifetime: 2583 hours (107 days + 15 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
-- -- -- -- -- -- --
04 71 03 80 01 32 e0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
08 00 aa 01 ff 00 a0 00 21d+14:49:44.620 DEVICE RESET
00 00 00 00 00 00 00 04 21d+14:49:43.912 NOP [Abort queued commands]
08 00 aa 80 fe 32 a0 00 21d+14:49:34.699 DEVICE RESET
ec 00 aa 01 00 00 a0 00 21d+14:49:33.360 IDENTIFY DEVICE
00 00 00 00 00 00 00 ff 21d+14:48:55.639 NOP [Abort queued commands]

Error 1597 occurred at disk power-on lifetime: 2583 hours (107 days + 15 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
-- -- -- -- -- -- --
04 71 03 80 01 32 e0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
08 00 aa 80 fe 32 a0 00 21d+14:49:34.699 DEVICE RESET
ec 00 aa 01 00 00 a0 00 21d+14:49:33.360 IDENTIFY DEVICE
00 00 00 00 00 00 00 ff 21d+14:48:55.639 NOP [Abort queued commands]
ec 00 00 00 00 00 e0 00 21d+13:28:53.183 IDENTIFY DEVICE
ec 00 00 00 00 00 e0 00 21d+13:28:53.182 IDENTIFY DEVICE

Error 1596 occurred at disk power-on lifetime: 2583 hours (107 days + 15 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
-- -- -- -- -- -- --
04 71 03 80 01 32 e0

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
ec 00 aa 01 00 00 a0 00 21d+14:49:33.360 IDENTIFY DEVICE
00 00 00 00 00 00 00 ff 21d+14:48:55.639 NOP [Abort queued commands]
ec 00 00 00 00 00 e0 00 21d+13:28:53.183 IDENTIFY DEVICE
ec 00 00 00 00 00 e0 00 21d+13:28:53.182 IDENTIFY DEVICE
00 00 00 00 00 00 00 04 21d+13:28:41.977 NOP [Abort queued commands]

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Aborted by host 90% 16 -

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.

[GhOsT_MZ]

Смотрим смарт и понимаем, что винт действительно умирает...

Код: Выделить всё

1 Raw_Read_Error_Rate 0x000f 082 063 044 Pre-fail Always - 170679072
 5 Reallocated_Sector_Ct 0x0033 080 080 036 Pre-fail Always - 412
196 Reallocated_Event_Count 0x0033 080 080 036 Pre-fail Always - 412

Плюс ругань на саму передачу данных:

Код: Выделить всё

199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 17

ИМХО, я бы не доверял бы этому диску и заменил бы.

[Гость]

Смотрим смарт и понимаем, что винт действительно умирает...

Код: Выделить всё

1 Raw_Read_Error_Rate 0x000f 082 063 044 Pre-fail Always - 170679072
 5 Reallocated_Sector_Ct 0x0033 080 080 036 Pre-fail Always - 412
196 Reallocated_Event_Count 0x0033 080 080 036 Pre-fail Always - 412

Плюс ругань на саму передачу данных:

Код: Выделить всё

199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 17

ИМХО, я бы не доверял бы этому диску и заменил бы.

Огромное спасибо! Могу ли я для сравнения проверить /dev/ad4 - который в зеркале?

[GhOsT_MZ]

Ну никто не мешает посмотреть/показать его смарт для начала.

[Гость]

Ну никто не мешает посмотреть/показать его смарт для начала.

Я имею введу то что он в зеркале - ни как не повлияет?

[GhOsT_MZ]

Ну никто не мешает посмотреть/показать его смарт для начала.

Я имею введу то что он в зеркале - ни как не повлияет?

Да нет, не повлияет.

[Гость]

Ну никто не мешает посмотреть/показать его смарт для начала.

С этим тоже видимо не все гладко

smartctl 5.42 2011-10-20 r3458 [FreeBSD 7.0-RELEASE i386] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model: GB0500C8046
Serial Number: 9QM3ANJQ
LU WWN Device Id: 5 000c50 00cc344c1
Firmware Version: HPG1
User Capacity: 500 107 862 016 bytes [500 GB]
Sector Size: 512 bytes logical/physical
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 7
ATA Standard is: ATA/ATAPI-7 T13 1532D revision 4a
Local Time is: Fri Mar 2 14:02:11 2012 YEKT
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: (0x82) Offline data collection activity
was completed without error.
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: ( 634) 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: ( 118) minutes.
Conveyance self-test routine
recommended polling time: ( 3) minutes.
SCT capabilities: (0x103f) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 082 063 044 Pre-fail Always - 177969524
3 Spin_Up_Time 0x0003 099 099 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 57
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 074 060 030 Pre-fail Always - 82050013585
9 Power_On_Hours 0x0032 069 069 000 Old_age Always - 27820
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 57
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 094 094 000 Old_age Always - 6
188 Command_Timeout 0x0032 100 099 000 Old_age Always - 65537
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 065 060 045 Old_age Always - 35 (Min/Max 28/40)
194 Temperature_Celsius 0x0022 035 040 000 Old_age Always - 35 (0 18 0 0 0)
195 Hardware_ECC_Recovered 0x001a 049 027 000 Old_age Always - 177969524
196 Reallocated_Event_Count 0x0033 100 100 036 Pre-fail Always - 0
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0

SMART Error Log Version: 1
ATA Error Count: 6 (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 6 occurred at disk power-on lifetime: 22113 hours (921 days + 9 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 00 06 5f 13 00 Error: UNC at LBA = 0x00135f06 = 1269510

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 80 00 5f 13 e0 00 01:02:12.573 READ DMA
c8 00 10 10 00 00 e0 00 01:02:12.555 READ DMA
c8 00 80 80 5d 13 e0 00 01:02:12.552 READ DMA
c8 00 80 00 5d 13 e0 00 01:02:12.549 READ DMA
c8 00 10 80 00 00 e0 00 01:02:12.519 READ DMA

Error 5 occurred at disk power-on lifetime: 22112 hours (921 days + 8 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 00 06 5f 13 00 Error: UNC at LBA = 0x00135f06 = 1269510

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 80 00 5f 13 e0 00 00:55:14.243 READ DMA
c8 00 20 bf 20 00 e7 00 00:55:14.243 READ DMA
ca 00 20 9f 20 00 e7 00 00:55:14.242 WRITE DMA
c8 00 80 80 5e 13 e0 00 00:55:14.241 READ DMA
c8 00 80 00 5e 13 e0 00 00:55:14.241 READ DMA

Error 4 occurred at disk power-on lifetime: 22112 hours (921 days + 8 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 00 da 50 13 00 Error: UNC at LBA = 0x001350da = 1265882

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 80 80 50 13 e0 00 00:55:10.931 READ DMA
c8 00 80 00 50 13 e0 00 00:55:10.930 READ DMA
c8 00 20 9f 1e 00 e7 00 00:55:10.929 READ DMA
ca 00 20 7f 1e 00 e7 00 00:55:10.929 WRITE DMA
c8 00 80 80 4f 13 e0 00 00:55:10.928 READ DMA

Error 3 occurred at disk power-on lifetime: 22111 hours (921 days + 7 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 00 06 5f 13 00 Error: UNC at LBA = 0x00135f06 = 1269510

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 80 80 56 13 e0 00 00:01:17.101 READ DMA
c8 00 80 00 56 13 e0 00 00:01:17.096 READ DMA
35 00 01 ff ff ff 4f 00 00:01:17.094 WRITE DMA EXT
c8 00 01 00 00 00 e0 00 00:01:17.021 READ DMA
c8 00 01 80 00 00 e0 00 00:01:17.021 READ DMA

Error 2 occurred at disk power-on lifetime: 22111 hours (921 days + 7 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 00 06 5f 13 00 Error: UNC at LBA = 0x00135f06 = 1269510

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 80 00 5f 13 e0 00 05:08:40.289 READ DMA
c8 00 80 80 5e 13 e0 00 05:08:40.284 READ DMA
c8 00 80 00 5e 13 e0 00 05:08:40.284 READ DMA
c8 00 80 80 5d 13 e0 00 05:08:40.282 READ DMA
c8 00 80 00 5d 13 e0 00 05:08:40.281 READ DMA

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Aborted by host 90% 16 -

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.

[GhOsT_MZ]

Да нет, этот норм.

[Гость]

Да нет, этот норм.

спасибо.

смутило

1 Raw_Read_Error_Rate 0x000f 082 063 044 Pre-fail Always - 177969524

[GhOsT_MZ]

Это сигейт, а у них аттрибуты 1 и 195 имеют крупные значения и главное чтобы они были одинаковые.

[Гость]

Это сигейт, а у них аттрибуты 1 и 195 имеют крупные значения и главное чтобы они были одинаковые.

а сегодня с ad4 - совсем другая история:

1 Raw_Read_Error_Rate 0x000f 076 063 044 Pre-fail Always - 43613836
195 Hardware_ECC_Recovered 0x001a 050 027 000 Old_age Always - 43613836

ведь 03.03.12 совсем все по другому было..

1 Raw_Read_Error_Rate 0x000f 082 063 044 Pre-fail Always - 177969524
195 Hardware_ECC_Recovered 0x001a 049 027 000 Old_age Always - 177969524

это нормально?

[GhOsT_MZ]

Да, для сигейта это нормально

[Гость]

Люди - что дальше?
Заменил я винт на 1Тб, удалит 0,5Тб, вставил еще один 1Тб, синхронизировал, все ок - НО....

FS# gmirror list
Geom name: gm0
State: COMPLETE
Components: 2
Balance: round-robin
Slice: 4096
Flags: NONE
GenID: 6
SyncID: 10
ID: 2496644104
Providers:
1. Name: mirror/gm0
Mediasize: 500107861504 (466G)
Sectorsize: 512
Mode: r6w6e7
Consumers:
1. Name: ad4
Mediasize: 1000204886016 (932G)
Sectorsize: 512
Mode: r1w1e1
State: ACTIVE
Priority: 0
Flags: DIRTY
GenID: 6
SyncID: 10
ID: 314857996
2. Name: ad6
Mediasize: 1000204886016 (932G)
Sectorsize: 512
Mode: r1w1e1
State: ACTIVE
Priority: 0
Flags: DIRTY
GenID: 6
SyncID: 10
ID: 3246672515

По идее хотелось бы увеличить слайс FS. Как это сделать???

FS# df -H
Filesystem Size Used Avail Capacity Mounted on
/dev/mirror/gm0s1a 520M 321M 157M 67% /
devfs 1.0k 1.0k 0B 100% /dev
/dev/mirror/gm0s1g 458G 397G 25G 94% /fs
/dev/mirror/gm0s1e 520M 20k 478M 0% /tmp
/dev/mirror/gm0s1f 18G 2.8G 13G 17% /usr
/dev/mirror/gm0s1d 3.1G 374M 2.5G 13% /var