brestows
8 лет, 7 месяцев назад
brestows avatar
Темы: 24
Сообщения: 189
Участник с: 06 апреля 2013
т.е. запускаю тест (sudo smartctl --test=long /dev/sdс) через 3 часа смотрю результаты по smartctl -Hc /dev/sdс ?
kdeneur: https://github.com/brestows/kdeNeur
awesome WM 3.5
brestows
8 лет, 7 месяцев назад
brestows avatar
Темы: 24
Сообщения: 189
Участник с: 06 апреля 2013
вот результат команды smartctl -Hc /dev/sdс:

smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.12.7-1-ARCH] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
=== 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:      (  40)	The self-test routine was interrupted
					by the host with a hard or soft reset.
Total time to complete Offline
data collection: 		( 9300) 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: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 155) minutes.
SCT capabilities: 	       (0x003f)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.
kdeneur: https://github.com/brestows/kdeNeur
awesome WM 3.5
brestows
8 лет, 7 месяцев назад
brestows avatar
Темы: 24
Сообщения: 189
Участник с: 06 апреля 2013
не прерывал, хотя могла кошка прервать :) меня не было за компом во время теста, она либит reset жать прыгая на системник :(
kdeneur: https://github.com/brestows/kdeNeur
awesome WM 3.5
brestows
8 лет, 7 месяцев назад
brestows avatar
Темы: 24
Сообщения: 189
Участник с: 06 апреля 2013
вот что мне показало:
=== START OF INFORMATION SECTION ===
Model Family:     SAMSUNG SpinPoint F3
Device Model:     SAMSUNG HD103SJ
Serial Number:    S246JDWSC34540
LU WWN Device Id: 5 0024e9 002a0580e
Firmware Version: 1AJ100E4
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    7200 rpm
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   ATA8-ACS T13/1699-D revision 6
SATA Version is:  SATA 2.6, 3.0 Gb/s
Local Time is:    Sat Jan 18 19:05:36 2014 FET
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:      (  40)	The self-test routine was interrupted
					by the host with a hard or soft reset.
Total time to complete Offline
data collection: 		( 9300) 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: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 155) minutes.
SCT capabilities: 	       (0x003f)	SCT Status supported.
					SCT Error Recovery Control 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   100   100   051    Pre-fail  Always       -       120
  2 Throughput_Performance  0x0026   252   252   000    Old_age   Always       -       0
  3 Spin_Up_Time            0x0023   073   071   025    Pre-fail  Always       -       8369
  4 Start_Stop_Count        0x0032   099   099   000    Old_age   Always       -       1286
  5 Reallocated_Sector_Ct   0x0033   252   252   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   252   252   051    Old_age   Always       -       0
  8 Seek_Time_Performance   0x0024   252   252   015    Old_age   Offline      -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       22191
 10 Spin_Retry_Count        0x0032   252   252   051    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   252   252   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       -       1260
191 G-Sense_Error_Rate      0x0022   100   100   000    Old_age   Always       -       75
192 Power-Off_Retract_Count 0x0022   252   252   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0002   058   052   000    Old_age   Always       -       42 (Min/Max 14/48)
195 Hardware_ECC_Recovered  0x003a   100   100   000    Old_age   Always       -       0
196 Reallocated_Event_Count 0x0032   252   252   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       3
198 Offline_Uncorrectable   0x0030   252   252   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0036   100   100   000    Old_age   Always       -       153
200 Multi_Zone_Error_Rate   0x002a   100   100   000    Old_age   Always       -       4
223 Load_Retry_Count        0x0032   252   252   000    Old_age   Always       -       0
225 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       1369
SMART Error Log Version: 1
ATA Error Count: 23 (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 23 occurred at disk power-on lifetime: 10766 hours (448 days + 14 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
  -- -- -- -- -- -- --
  84 51 00 00 00 00 a0
  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 a0 00      00:00:00.951  IDENTIFY DEVICE
  ef 03 42 00 00 00 a0 00      00:00:00.951  SET FEATURES [Set transfer mode]
  ef 10 02 00 00 00 a0 00      00:00:00.951  SET FEATURES [Enable SATA feature]
  27 00 00 00 00 00 e0 00      00:00:00.951  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00      00:00:00.951  IDENTIFY DEVICE
Error 22 occurred at disk power-on lifetime: 10766 hours (448 days + 14 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
  -- -- -- -- -- -- --
  84 51 00 00 00 00 a0
  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 a0 00      00:00:00.938  IDENTIFY DEVICE
  00 10 f0 1a 91 19 40 00      00:00:00.938  NOP [Reserved subcommand] [OBS-ACS-2]
  60 10 00 0a 91 19 40 00      00:00:00.938  READ FPDMA QUEUED
  ef 10 02 00 00 00 a0 00      00:00:00.938  SET FEATURES [Enable SATA feature]
  27 00 00 00 00 00 e0 00      00:00:00.938  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 21 occurred at disk power-on lifetime: 10766 hours (448 days + 14 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
  -- -- -- -- -- -- --
  84 51 00 00 00 00 a0
  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 a0 00      00:00:00.587  IDENTIFY DEVICE
  00 10 00 12 53 ec 40 00      00:00:00.587  NOP [Reserved subcommand] [OBS-ACS-2]
  00 10 00 12 52 ec 40 00      00:00:00.587  NOP [Reserved subcommand] [OBS-ACS-2]
  ec 00 00 00 00 00 a0 00      00:00:00.582  IDENTIFY DEVICE
  00 10 00 fa e4 ea 40 00      00:00:00.582  NOP [Reserved subcommand] [OBS-ACS-2]
Error 20 occurred at disk power-on lifetime: 10766 hours (448 days + 14 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
  -- -- -- -- -- -- --
  84 51 00 00 00 00 a0
  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 a0 00      00:00:00.421  IDENTIFY DEVICE
  ef 03 42 00 00 00 a0 00      00:00:00.421  SET FEATURES [Set transfer mode]
  ef 10 02 00 00 00 a0 00      00:00:00.421  SET FEATURES [Enable SATA feature]
  27 00 00 00 00 00 e0 00      00:00:00.421  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00      00:00:00.421  IDENTIFY DEVICE
Error 19 occurred at disk power-on lifetime: 10766 hours (448 days + 14 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
  -- -- -- -- -- -- --
  84 51 00 00 00 00 a0
  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 a0 00      00:00:00.406  IDENTIFY DEVICE
  ef 03 42 00 00 00 a0 00      00:00:00.406  SET FEATURES [Set transfer mode]
  ef 10 02 00 00 00 a0 00      00:00:00.406  SET FEATURES [Enable SATA feature]
  27 00 00 00 00 00 e0 00      00:00:00.406  READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
  ec 00 00 00 00 00 a0 00      00:00:00.406  IDENTIFY DEVICE
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Interrupted (host reset)      80%     22171         -
# 2  Short offline       Completed without error       00%     10892         -
SMART Selective self-test log data structure revision number 0
Note: revision number not 1 implies that no selective self-test has ever been run
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Interrupted [80% left] (0-65535)
    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.
kdeneur: https://github.com/brestows/kdeNeur
awesome WM 3.5
brestows
8 лет, 7 месяцев назад
brestows avatar
Темы: 24
Сообщения: 189
Участник с: 06 апреля 2013
За ссылку спасибо, буду читать.....

а как посмотреть результаты теста ?
kdeneur: https://github.com/brestows/kdeNeur
awesome WM 3.5
brestows
8 лет, 7 месяцев назад
brestows avatar
Темы: 24
Сообщения: 189
Участник с: 06 апреля 2013
Ок спасибо, буду проовать смотреть что и как, потом отпишусь
kdeneur: https://github.com/brestows/kdeNeur
awesome WM 3.5
brestows
8 лет, 7 месяцев назад
brestows avatar
Темы: 24
Сообщения: 189
Участник с: 06 апреля 2013
винт не один еще 3 винта сверху, которые работают нормально, бп хороший 550W должно хватать, ком нагружается редко даже очень максимум перехешировать торрент и откомпилить софт мой не более того :)
kdeneur: https://github.com/brestows/kdeNeur
awesome WM 3.5
brestows
8 лет, 7 месяцев назад
brestows avatar
Темы: 24
Сообщения: 189
Участник с: 06 апреля 2013
Добрый сегодня в логах нашел вот такое:

 TuxAdmin kernel: ata5.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x0
 TuxAdmin kernel: ata5.00: irq_stat 0x40000001
 TuxAdmin kernel: ata5.00: failed command: READ FPDMA QUEUED
 TuxAdmin kernel: ata5.00: cmd 60/00:00:67:8e:68/01:00:73:00:00/40 tag 0 ncq 131072 in
                                             res 41/00:1b:4c:8e:68/00:00:73:00:00/40 Emask 0x1 (device error)
 TuxAdmin kernel: ata5.00: status: { DRDY ERR }
 TuxAdmin kernel: ata5.00: failed command: READ FPDMA QUEUED
 TuxAdmin kernel: ata5.00: cmd 60/00:08:67:8d:68/01:00:73:00:00/40 tag 1 ncq 131072 in
                                             res 41/40:00:4c:8e:68/00:00:73:00:00/40 Emask 0x409 (media error) <F>
 TuxAdmin kernel: ata5.00: status: { DRDY ERR }
 TuxAdmin kernel: ata5.00: error: { UNC }
 TuxAdmin kernel: ata5.00: configured for UDMA/133
 TuxAdmin kernel: ata5: exception Emask 0x1 SAct 0x0 SErr 0x0 action 0x0 t4
 TuxAdmin kernel: ata5: irq_stat 0x40000008
 TuxAdmin kernel: sd 4:0:0:0: [sdc] Unhandled sense code
 TuxAdmin kernel: sd 4:0:0:0: [sdc]
 TuxAdmin kernel: Result: hostbyte=0x00 driverbyte=0x08
 TuxAdmin kernel: sd 4:0:0:0: [sdc]
 TuxAdmin kernel: Sense Key : 0x3 [current] [descriptor]
 TuxAdmin kernel: Descriptor sense data with sense descriptors (in hex):
 TuxAdmin kernel:         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
 TuxAdmin kernel:         73 68 8e 4c
 TuxAdmin kernel: sd 4:0:0:0: [sdc]
 TuxAdmin kernel: ASC=0x11 ASCQ=0x4
 TuxAdmin kernel: sd 4:0:0:0: [sdc] CDB:
 TuxAdmin kernel: cdb[0]=0x28: 28 00 73 68 8d 67 00 01 00 00
 TuxAdmin kernel: end_request: I/O error, dev sdc, sector 1936232012
 TuxAdmin kernel: ata5: EH complete
 TuxAdmin kernel: ata5.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
 TuxAdmin kernel: ata5.00: irq_stat 0x40000008
 TuxAdmin kernel: ata5.00: failed command: READ FPDMA QUEUED
 TuxAdmin kernel: ata5.00: cmd 60/08:00:47:8e:68/00:00:73:00:00/40 tag 0 ncq 4096 in
                                             res 41/40:00:4c:8e:68/00:00:73:00:00/40 Emask 0x409 (media error) <F>
 TuxAdmin kernel: ata5.00: status: { DRDY ERR }
TuxAdmin kernel: ata5.00: error: { UNC }

Полез смотреть S.M.A.R.T.

[[email protected]]>>sudo smartctl -A /dev/sdc                                                                                                                                            ~/ :(
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.12.6-1-ARCH] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF READ SMART DATA SECTION ===
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   100   100   051    Pre-fail  Always       -       120
  2 Throughput_Performance  0x0026   252   252   000    Old_age   Always       -       0
  3 Spin_Up_Time            0x0023   073   071   025    Pre-fail  Always       -       8369
  4 Start_Stop_Count        0x0032   099   099   000    Old_age   Always       -       1286
  5 Reallocated_Sector_Ct   0x0033   252   252   010    Pre-fail  Always       -       0
  7 Seek_Error_Rate         0x002e   252   252   051    Old_age   Always       -       0
  8 Seek_Time_Performance   0x0024   252   252   015    Old_age   Offline      -       0
  9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       22145
 10 Spin_Retry_Count        0x0032   252   252   051    Old_age   Always       -       0
 11 Calibration_Retry_Count 0x0032   252   252   000    Old_age   Always       -       0
 12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       -       1260
191 G-Sense_Error_Rate      0x0022   100   100   000    Old_age   Always       -       75
192 Power-Off_Retract_Count 0x0022   252   252   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0002   058   052   000    Old_age   Always       -       42 (Min/Max 14/48)
195 Hardware_ECC_Recovered  0x003a   100   100   000    Old_age   Always       -       0
196 Reallocated_Event_Count 0x0032   252   252   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   100   100   000    Old_age   Always       -       3
198 Offline_Uncorrectable   0x0030   252   252   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0036   100   100   000    Old_age   Always       -       153
200 Multi_Zone_Error_Rate   0x002a   100   100   000    Old_age   Always       -       4
223 Load_Retry_Count        0x0032   252   252   000    Old_age   Always       -       0
225 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       1369

Полагаю стоит задуматься о том что бы заменить его на что-то более здоровое ?
kdeneur: https://github.com/brestows/kdeNeur
awesome WM 3.5
brestows
8 лет, 8 месяцев назад
brestows avatar
Темы: 24
Сообщения: 189
Участник с: 06 апреля 2013
это я понял, но у тебя указанно конкретное приложение, а как сделать для любого приложения которое в плавающем виде отображает awesome?
kdeneur: https://github.com/brestows/kdeNeur
awesome WM 3.5
brestows
8 лет, 8 месяцев назад
brestows avatar
Темы: 24
Сообщения: 189
Участник с: 06 апреля 2013
Добрый вечер, возник вопрос, как в awesome прописать правила для окон у которых выставлено свойство floating в значение true, я хочу сделать так что бы плавающие окна, при открытии были размещены по центру экрана.
kdeneur: https://github.com/brestows/kdeNeur
awesome WM 3.5
 

© 2006-2022, Русскоязычное сообщество Arch Linux.
Название и логотип Arch Linux ™ являются признанными торговыми марками.
Linux ® — зарегистрированная торговая марка Linus Torvalds и LMI.