Страница 1 из 1
SETFEATURES SET TRANSFER MODE о как
Добавлено: 2008-12-17 10:20:04
Dron
седня пришел на работу, отвалился сенас ssh одного из сервов...
смотрю uptime ребутнулся часа в 4 ночи... лезу в логи...
Код: Выделить всё
Dec 17 03:52:40 andromeda kernel: ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly
Dec 17 03:52:40 andromeda kernel: ad4: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly
Dec 17 03:52:40 andromeda kernel: ad4: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly
Dec 17 03:52:40 andromeda kernel: ad4: WARNING - SET_MULTI taskqueue timeout - completing request directly
Dec 17 03:52:40 andromeda kernel: ad4: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=64673823
Dec 17 03:52:40 andromeda kernel: ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly
Dec 17 03:52:40 andromeda kernel: ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly
Dec 17 03:52:40 andromeda kernel: ad4: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly
Dec 17 03:52:40 andromeda kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 112, size: 4096
Dec 17 03:52:40 andromeda kernel: ad4: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly
Dec 17 03:52:40 andromeda kernel: ad4: WARNING - SET_MULTI taskqueue timeout - completing request directly
Dec 17 03:52:40 andromeda kernel: ad4: TIMEOUT - WRITE_DMA retrying (1 retry left) LBA=64673855
Dec 17 03:52:40 andromeda kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 99, size: 4096
Dec 17 03:52:40 andromeda kernel: ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly
Dec 17 03:52:40 andromeda kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 112, size: 4096
Dec 17 03:52:40 andromeda kernel: ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly
Dec 17 03:52:40 andromeda kernel: ad4: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly
Dec 17 03:52:40 andromeda kernel: ad4: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly
Dec 17 03:52:40 andromeda kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 99, size: 4096
Dec 17 03:52:40 andromeda kernel: ad4: WARNING - SET_MULTI taskqueue timeout - completing request directly
Dec 17 03:52:40 andromeda kernel: ad4: TIMEOUT - WRITE_DMA retrying (0 retries left) LBA=64673823
Dec 17 03:52:40 andromeda kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 112, size: 4096
Dec 17 03:52:40 andromeda kernel: ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly
Dec 17 03:52:40 andromeda kernel: ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly
Dec 17 03:52:40 andromeda kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 99, size: 4096
Dec 17 03:52:40 andromeda kernel: ad4: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly
Dec 17 03:52:40 andromeda kernel: ad4: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly
Dec 17 03:52:40 andromeda kernel: ad4: WARNING - SET_MULTI taskqueue timeout - completing request directly
Dec 17 03:52:40 andromeda kernel: ad4: TIMEOUT - WRITE_DMA retrying (0 retries left) LBA=64673855
Dec 17 03:52:40 andromeda kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 112, size: 4096
Dec 17 03:52:40 andromeda kernel: ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly
Dec 17 03:52:40 andromeda kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 99, size: 4096
Dec 17 03:52:40 andromeda kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 73, size: 4096
Dec 17 03:52:40 andromeda kernel: ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly
Dec 17 03:52:40 andromeda kernel: ad4: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly
Dec 17 03:52:40 andromeda kernel: ad4: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly
Dec 17 03:52:40 andromeda kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 112, size: 4096
Dec 17 03:52:40 andromeda kernel: ad4: WARNING - SET_MULTI taskqueue timeout - completing request directly
Dec 17 03:52:40 andromeda kernel: ad4: FAILURE - WRITE_DMA timed out LBA=64673823
Dec 17 03:52:40 andromeda kernel: g_vfs_done():ad4s1e[WRITE(offset=20228063232, length=16384)]error = 5
Dec 17 03:52:40 andromeda kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 99, size: 4096
Dec 17 03:52:40 andromeda kernel: swap_pager: indefinite wait buffer: bufobj: 0, blkno: 73, size: 4096
Dec 17 03:52:40 andromeda kernel: ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly
Dec 17 03:52:40 andromeda kernel: ad4: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly
Dec 17 03:52:40 andromeda kernel: ad4: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly
и т.д. Потом пошла загрузка системы...
Перед этим было несколько странных зависаний системы, но в логи ничего не сыпало...
Что это такое? Плохо винту или все серьезнее?
Re: SETFEATURES SET TRANSFER MODE о как
Добавлено: 2008-12-17 10:20:40
Alex Keda
смарт посмотрите
Re: SETFEATURES SET TRANSFER MODE о как
Добавлено: 2008-12-17 10:41:27
Dron
smart показал такое
Код: Выделить всё
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 0x000f 100 100 051 Pre-fail Always - 2
3 Spin_Up_Time 0x0007 253 253 025 Pre-fail Always - 4352
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 17
5 Reallocated_Sector_Ct 0x0033 253 253 010 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 253 253 051 Pre-fail Always - 0
8 Seek_Time_Performance 0x0025 253 253 015 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 7412
10 Spin_Retry_Count 0x0033 253 253 051 Pre-fail Always - 0
11 Calibration_Retry_Count 0x0012 253 253 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 17
13 Read_Soft_Error_Rate 0x000e 100 100 000 Old_age Always - 157824264
184 Unknown_Attribute 0x0033 253 253 099 Pre-fail Always - 0
187 Reported_Uncorrect 0x0032 253 253 000 Old_age Always - 0
188 Unknown_Attribute 0x0032 253 253 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 175 136 000 Old_age Always - 21 (Lifetime Min/Max 15/34)
194 Temperature_Celsius 0x0022 175 133 000 Old_age Always - 21 (Lifetime Min/Max 15/35)
195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 157824264
196 Reallocated_Event_Count 0x0032 253 253 000 Old_age Always - 0
197 Current_Pending_Sector 0x0012 253 253 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 253 253 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age Always - 0
201 Soft_Read_Error_Rate 0x000a 100 100 000 Old_age Always - 0
202 TA_Increase_Count 0x0032 253 253 000 Old_age Always - 0
т.е. есть 10 ремапов, есть ошибки чтения...
Re: SETFEATURES SET TRANSFER MODE о как
Добавлено: 2008-12-17 10:47:05
Alex Keda
меняй, пожалуй что...
Re: SETFEATURES SET TRANSFER MODE о как
Добавлено: 2008-12-17 11:50:58
Dron
Пообщался с ребятами, которые винты ремонтируют и инфу вытаскивают, смарт им отправил...
Говорят, что с винтом нормально, ему мол жить и жить...
Посоветовали поменять шлейф и посмотреть...
Вобщем дамплю пока разделы с винта, поменяю шлейф, а там понаблюдаем
Re: SETFEATURES SET TRANSFER MODE о как
Добавлено: 2008-12-18 5:36:45
zingel
это - убитый винт не причём тут шлейф
Re: SETFEATURES SET TRANSFER MODE о как
Добавлено: 2008-12-18 17:17:59
E-Wind
А разве кол-во ремапов выводится не в RAW_VALUE?
Код: Выделить всё
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
5 Reallocated_Sector_Ct 0x0033 253 253 010 Pre-fail Always - 0
194 Temperature_Celsius 0x0022 175 133 000 Old_age Always - 21 (Lifetime Min/Max 15/35)
У меня, например, в THRESH 36.. да та же температура для сравнения...
Для начала проверить сервисными программами и шлейф, а потом думать дальше....
Re: SETFEATURES SET TRANSFER MODE о как
Добавлено: 2008-12-24 23:08:24
Dron
неделя, полет нормальный, шлейф не менял...
Re: SETFEATURES SET TRANSFER MODE о как
Добавлено: 2009-09-15 13:13:26
E-Wind
неделя, полет нормальный, шлейф не менял...
И как сейчас?
Практически таже фигня в логах - много раз повторяется:
Код: Выделить всё
Sep 14 11:57:08 EWIS kernel: ad8: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly
Sep 14 11:57:12 EWIS kernel: ad8: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly
Sep 14 11:57:16 EWIS kernel: ad8: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly
Sep 14 11:57:20 EWIS kernel: ad8: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly
Sep 14 11:57:24 EWIS kernel: ad8: WARNING - SET_MULTI taskqueue timeout - completing request directly
Sep 14 11:57:24 EWIS kernel: ad8: FAILURE - SMART timed out LBA=12734214
Далее перестал читаться смарт и намертво завесился smartd
Код: Выделить всё
Sep 14 12:32:04 EWIS smartd[809]: Device: /dev/ad8, failed to read SMART Attribute Data
А после ребута винт не определился и вывалился из зеркала....
Интересно, что после второго ребута винт вернулся, с него стал читаться смарт и прочее.... вот сижу, думаю...
До этого на нем были найдены UNC (значения в полях Current_Pending_Sector и Offline_Uncorrectable выросли) секторы, но вроде спец. софтом исправлены...
Смарт:
Код: Выделить всё
smartctl version 5.38 [i386-portbld-freebsd7.1] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Device Model: ST31000340NS
Serial Number: 9QJ28JNW
Firmware Version: SN06
User Capacity: 1,000,204,886,016 bytes
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Tue Sep 15 10:02:03 2009 MSD
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: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 228) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x103d) SCT Status 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 079 064 044 Pre-fail Always - 182955282
3 Spin_Up_Time 0x0003 099 098 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 34
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 068 060 030 Pre-fail Always - 4301282890
9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 2234
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 037 020 Old_age Always - 34
184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 085 085 000 Old_age Always - 15
188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 073 053 045 Old_age Always - 27 (Lifetime Min/Max 21/27)
194 Temperature_Celsius 0x0022 027 047 000 Old_age Always - 27 (0 16 0 0)
195 Hardware_ECC_Recovered 0x001a 043 029 000 Old_age Always - 182955282
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: 14 (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 14 occurred at disk power-on lifetime: 2107 hours (87 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 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
42 d0 00 ff ff ff ef 00 02:05:47.539 READ VERIFY SECTOR(S) EXT
42 d0 00 ff ff ff ef 00 02:05:43.881 READ VERIFY SECTOR(S) EXT
42 d0 00 ff ff ff ef 00 02:05:41.533 READ VERIFY SECTOR(S) EXT
42 d0 00 ff ff ff ef 00 02:05:39.017 READ VERIFY SECTOR(S) EXT
42 d0 00 ff ff ff ef 00 02:05:36.469 READ VERIFY SECTOR(S) EXT
Error 13 occurred at disk power-on lifetime: 2107 hours (87 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 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
42 d0 00 ff ff ff ef 00 02:05:43.881 READ VERIFY SECTOR(S) EXT
42 d0 00 ff ff ff ef 00 02:05:41.533 READ VERIFY SECTOR(S) EXT
42 d0 00 ff ff ff ef 00 02:05:39.017 READ VERIFY SECTOR(S) EXT
42 d0 00 ff ff ff ef 00 02:05:36.469 READ VERIFY SECTOR(S) EXT
42 00 00 ff ff ff 4f 00 02:05:33.494 READ VERIFY SECTOR(S) EXT
Error 12 occurred at disk power-on lifetime: 2107 hours (87 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 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
42 d0 00 ff ff ff ef 00 02:05:41.533 READ VERIFY SECTOR(S) EXT
42 d0 00 ff ff ff ef 00 02:05:39.017 READ VERIFY SECTOR(S) EXT
42 d0 00 ff ff ff ef 00 02:05:36.469 READ VERIFY SECTOR(S) EXT
42 00 00 ff ff ff 4f 00 02:05:33.494 READ VERIFY SECTOR(S) EXT
42 d0 00 ff ff ff ef 00 02:05:31.623 READ VERIFY SECTOR(S) EXT
Error 11 occurred at disk power-on lifetime: 2107 hours (87 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 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
42 d0 00 ff ff ff ef 00 02:05:39.017 READ VERIFY SECTOR(S) EXT
42 d0 00 ff ff ff ef 00 02:05:36.469 READ VERIFY SECTOR(S) EXT
42 00 00 ff ff ff 4f 00 02:05:33.494 READ VERIFY SECTOR(S) EXT
42 d0 00 ff ff ff ef 00 02:05:31.623 READ VERIFY SECTOR(S) EXT
42 d0 00 ff ff ff ef 00 02:05:25.307 READ VERIFY SECTOR(S) EXT
Error 10 occurred at disk power-on lifetime: 2107 hours (87 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 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
42 d0 00 ff ff ff ef 00 02:05:36.469 READ VERIFY SECTOR(S) EXT
42 00 00 ff ff ff 4f 00 02:05:33.494 READ VERIFY SECTOR(S) EXT
42 d0 00 ff ff ff ef 00 02:05:31.623 READ VERIFY SECTOR(S) EXT
42 d0 00 ff ff ff ef 00 02:05:25.307 READ VERIFY SECTOR(S) EXT
42 d0 00 ff ff ff ef 00 02:05:19.025 READ VERIFY SECTOR(S) EXT
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% 2220 -
# 2 Extended offline Completed without error 00% 2201 -
# 3 Short offline Completed without error 00% 2197 -
# 4 Short offline Completed without error 00% 2173 -
# 5 Short offline Completed without error 00% 2149 -
# 6 Extended offline Completed without error 00% 2147 -
# 7 Short offline Completed without error 00% 2125 -
# 8 Short offline Completed without error 00% 2110 -
# 9 Short offline Completed without error 00% 2102 -
#10 Extended offline Completed: read failure 40% 2097 1329983860
#11 Short offline Completed without error 00% 2079 -
#12 Short offline Completed without error 00% 2055 -
#13 Short offline Completed without error 00% 2031 -
#14 Short offline Completed without error 00% 2007 -
#15 Short offline Completed without error 00% 1983 -
#16 Short offline Completed without error 00% 1959 -
#17 Extended offline Completed without error 00% 1939 -
#18 Short offline Completed without error 00% 1935 -
#19 Short offline Completed without error 00% 1911 -
#20 Short offline Completed without error 00% 1887 -
#21 Short offline Completed without error 00% 1863 -
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.
Re: SETFEATURES SET TRANSFER MODE о как
Добавлено: 2009-09-15 13:29:11
E-Wind
Хотя в этом
топике пишут что винты не при чем...
My personal experience makes me think that this issue is controller/driver related.
I'm using SATA 300 TX4 Controller from times of 6.1-Relaese on my fileserver (with 2 of 4 ports used) and I saw a lot of exactly the same errors in logs. Sometimes it was harmless, but sometimes as an effect of these one of disks magically disconnected from controller and only way to get it back and working was power down and up PC. That mostly happened while heavy I/O like while dumping filesystems.
Good thing is that starting from 7.0-release I saw such errors maybe 2-3 times and I didn't saw them at all from at least 6 months. Probably because I rebuild my system about once a month to keep up with stable branch and something was corrected in sources through that time.
So I also advice to upgrade to RELENG_7 and you probably get rid of these.
Good luck!
Re: SETFEATURES SET TRANSFER MODE о как
Добавлено: 2009-09-15 13:31:08
Dron
уменя винт так и живет, шлейф правда пришлось поменять, его по ходу и плющило...
Еще встречал ситуацию, когда такая-же фигня происходит из-за карманов, там по ходу тож контакты начинают гнать беса со временем...
Еще охлаждение может давать, ну и умирающий винт...
Re: SETFEATURES SET TRANSFER MODE о как
Добавлено: 2009-09-24 21:44:44
E-Wind
Дабы не создавать еще одну тему, тем более про тот же винт )
Сегодня пришло письмо
The following warning/error was logged by the smartd daemon:
Device: /dev/ad8, new Self-Test Log error at hour timestamp 0
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.
На сервере никаких изменений пока не заметил, сообщение появилось после автоматического запуска короткого self-теста, который прошел без ошибок.
Быстрый гуглинг пока не прояснил смысл ворнинга... хотя есть подозрение, что это может быть связано с заполнением журнала заново... и видимо что-то там пошло не так (более "старые" винты, той же серии (ES.2), меньшего объема - от них такого не приходило)
1.5.5. Self-test Log
Тип: Журнал результатов самоконтроля [SMART self-test]
Вид доступа: только чтение (RO)
Размер: 1 сектор (512 байт)
Примечание: поддерживается только 28-битная адресация секторов (28-bit LBA)
Данный журнал содержит информацию о результатах выполнения команд внутренней самодиагностики накопителя. Журнал может хранить до 21 записи. При превышении этого количества, журнал начинает заполняться заново, перезаписывая 1-ю запись 22-й, 2-ю - 23-ей и так далее. В каждой записи журнала сохраняется регистр с номером теста, код статуса выполнения теста, время на момент запуска/прерывания теста, номер текущей контрольной точки (или точки останова) теста, а также LBA-адрес сектора, на котором произошло прерывание/отмена теста.
Update: В общем разобрался, нашел в mail-lists:
This warning message normally appears when a new error entry appeared in
the log, but the total number of such entries did not increase.
The message also appears when the last error entry was removed from the
log. In this case, the message is actually misleading.
Christian
Если учесть что новые диски я тестирую сразу, то получается что результат последнего теста у меня записался поверх результата первого, который как раз и был сразу после первого запуска диска, т.е.
at hour timestamp 0