You are not logged in.
Pages: 1
Hello,
I use archlinux since about a year and never had real big problems with it but since few weeks
I have a problematic issue. While I'm on Firefox or do nothing special, I can see that the load number of i3status (number of processes waiting for CPU time in the last 1, 5 and 15 minutes).
start to become very high and after few minutes I cannot open anything and most of the command in terminal respond with a "I/O error".
I don't know how to figure out from where the problem comes.
Do you know were can I search to see the problem source?
Thanks
Last edited by Nuocman (2015-01-17 22:37:28)
Offline
Anything in the journal? It sounds frightening like a disk drive failing.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
those are the lasts journal log that I have. I'm pretty sure that the system had to be shut down manually.
It may come from my HDD which is quite old.
Jan 08 19:39:34 ArchNuoc kernel: ata2.00: exception Emask 0x0 SAct 0xc0000 SErr 0x0 action 0x6 frozen
Jan 08 19:39:43 ArchNuoc kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Jan 08 19:39:43 ArchNuoc kernel: ata2.00: cmd 61/00:90:28:f7:a8/04:00:0a:00:00/40 tag 18 ncq 524288 out
res 40/00:08:e0:16:88/00:00:0b:00:00/40 Emask 0x4 (timeout)
Jan 08 19:39:43 ArchNuoc kernel: ata2.00: status: { DRDY }
Jan 08 19:39:43 ArchNuoc kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Jan 08 19:39:43 ArchNuoc kernel: ata2.00: cmd 61/d0:98:28:fb:a8/01:00:0a:00:00/40 tag 19 ncq 237568 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Jan 08 19:39:43 ArchNuoc kernel: ata2.00: status: { DRDY }
Jan 08 19:39:43 ArchNuoc kernel: ata2: hard resetting link
Jan 08 19:39:43 ArchNuoc kernel: ata2: link is slow to respond, please be patient (ready=0)
Jan 08 19:39:43 ArchNuoc kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Jan 08 19:39:43 ArchNuoc kernel: ata2.00: configured for UDMA/133
Jan 08 19:39:43 ArchNuoc kernel: ata2.00: device reported invalid CHS sector 0
Jan 08 19:39:43 ArchNuoc kernel: ata2: EH complete
Jan 08 19:40:20 ArchNuoc kernel: ata2.00: exception Emask 0x0 SAct 0x18000000 SErr 0x0 action 0x6 frozen
Jan 08 19:40:43 ArchNuoc kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Jan 08 19:40:43 ArchNuoc kernel: ata2.00: cmd 61/08:d8:d0:01:a9/02:00:0a:00:00/40 tag 27 ncq 266240 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Jan 08 19:40:43 ArchNuoc kernel: ata2.00: status: { DRDY }
Jan 08 19:40:43 ArchNuoc kernel: ata2.00: failed command: WRITE FPDMA QUEUED
Jan 08 19:40:43 ArchNuoc kernel: ata2.00: cmd 61/18:e0:30:66:87/00:00:01:00:00/40 tag 28 ncq 12288 out
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)Last edited by Nuocman (2015-01-15 21:40:24)
Offline
It appears you are indeed having problems with that drive.
Does it support S.M.A.R.T? If it does, install smartmontools and post the output of sudo smartctl -a /dev/sda
ewaller@odin ~ [96]1007 %pacman -Qs smartmontools
local/smartmontools 6.3-1
Control and monitor S.M.A.R.T. enabled ATA and SCSI Hard Drives
ewaller@odin ~ 1008 %sudo smartctl -a /dev/sda
smartctl 6.3 2014-07-26 r3976 [x86_64-linux-3.18.2-2-ARCH] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Western Digital Scorpio Blue Serial ATA
Device Model: WDC WD3200BEVT-60ZCT1
Serial Number: WD-WXH209349703
LU WWN Device Id: 5 0014ee 202a02add
Firmware Version: 13.01A13
User Capacity: 320,072,933,376 bytes [320 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: 5400 rpm
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS (minor revision not indicated)
SATA Version is: SATA 2.5, 3.0 Gb/s
Local Time is: Thu Jan 15 19:57:28 2015 PST
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
See vendor-specific Attribute list for marginal Attributes.
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: ( 9960) seconds.
Offline data collection
capabilities: (0x51) SMART execute Offline immediate.
No Auto Offline data collection support.
Suspend Offline collection upon new
command.
No 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: ( 118) minutes.
SCT capabilities: (0x303f) 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 200 200 051 Pre-fail Always - 17
3 Spin_Up_Time 0x0027 187 184 021 Pre-fail Always - 1641
4 Start_Stop_Count 0x0032 094 094 000 Old_age Always - 6948
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002f 100 253 051 Pre-fail Always - 0
9 Power_On_Hours 0x0032 038 038 000 Old_age Always - 45273
10 Spin_Retry_Count 0x0033 100 100 051 Pre-fail Always - 0
11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 099 099 000 Old_age Always - 1439
187 Reported_Uncorrect 0x0032 100 093 000 Old_age Always - 7
188 Command_Timeout 0x0032 100 089 000 Old_age Always - 21475164203
190 Airflow_Temperature_Cel 0x0022 043 022 040 Old_age Always In_the_past 57
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 345
193 Load_Cycle_Count 0x0032 054 054 000 Old_age Always - 438224
194 Temperature_Celsius 0x0022 090 069 000 Old_age Always - 57
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0009 100 253 051 Pre-fail Offline - 0
SMART Error Log Version: 1
ATA Error Count: 22 (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 22 occurred at disk power-on lifetime: 41854 hours (1743 days + 22 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 51 00 34 cf f3 a3
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
ea 00 00 00 00 00 00 08 5d+08:04:59.021 FLUSH CACHE EXT
61 30 b0 42 b3 61 19 08 5d+08:04:59.021 WRITE FPDMA QUEUED
61 28 a8 02 33 4e 19 08 5d+08:04:59.020 WRITE FPDMA QUEUED
ea 00 00 00 00 00 00 08 5d+08:04:54.920 FLUSH CACHE EXT
61 08 98 3a b3 61 19 08 5d+08:04:54.920 WRITE FPDMA QUEUED
Error 21 occurred at disk power-on lifetime: 41853 hours (1743 days + 21 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 51 00 34 cf f3 a3
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
ea 00 00 00 00 00 00 08 5d+07:03:16.250 FLUSH CACHE EXT
61 68 e0 1a 09 61 19 08 5d+07:03:16.249 WRITE FPDMA QUEUED
61 18 d8 c2 6f c4 18 08 5d+07:03:16.249 WRITE FPDMA QUEUED
61 20 d0 1a a3 6f 18 08 5d+07:03:16.248 WRITE FPDMA QUEUED
61 08 c8 52 90 6c 18 08 5d+07:03:16.248 WRITE FPDMA QUEUED
Error 20 occurred at disk power-on lifetime: 41853 hours (1743 days + 21 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 51 00 34 cf f3 a3
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
ea 00 00 00 00 00 00 08 5d+07:00:39.243 FLUSH CACHE EXT
61 10 68 42 04 61 19 08 5d+07:00:39.242 WRITE FPDMA QUEUED
ea 00 00 00 00 00 00 08 5d+07:00:36.338 FLUSH CACHE EXT
61 08 58 0a ea 9e 09 08 5d+07:00:36.338 WRITE FPDMA QUEUED
ea 00 00 00 00 00 00 08 5d+07:00:36.338 FLUSH CACHE EXT
Error 19 occurred at disk power-on lifetime: 25779 hours (1074 days + 3 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 ff eb b8 60 40 Error: UNC at LBA = 0x0060b8eb = 6338795
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 08 60 12 37 a5 1e 08 1d+00:13:27.967 READ FPDMA QUEUED
61 10 58 da ae 44 1b 08 1d+00:13:27.967 WRITE FPDMA QUEUED
61 00 50 8a ee c4 08 08 1d+00:13:27.946 WRITE FPDMA QUEUED
61 e8 48 8a 41 e0 08 08 1d+00:13:27.937 WRITE FPDMA QUEUED
61 00 40 8a fa c4 08 08 1d+00:13:27.906 WRITE FPDMA QUEUED
Error 18 occurred at disk power-on lifetime: 25779 hours (1074 days + 3 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
-- -- -- -- -- -- --
10 51 02 5a b1 e3 40 Error: IDNF at LBA = 0x00e3b15a = 14922074
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 48 c8 8a a2 e3 08 08 1d+00:13:17.256 WRITE FPDMA QUEUED
61 20 c0 da a5 e3 08 08 1d+00:13:17.212 WRITE FPDMA QUEUED
61 00 b8 8a f6 c4 08 08 1d+00:13:17.212 WRITE FPDMA QUEUED
61 00 b0 8a fa c4 08 08 1d+00:13:17.092 WRITE FPDMA QUEUED
61 e8 a8 8a 41 e0 08 08 1d+00:13:17.079 WRITE FPDMA QUEUED
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
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.
ewaller@odin ~ [96]1009 %And, this would be an excellent time to check your backups and ensure that anything you want on that drive is stored elsewhere.
Last edited by ewaller (2015-01-16 04:01:11)
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
Hi, here are the logs :
(nuocman@ArchNuoc)-(0)-(12:27 PM)(~)
--> sudo smartctl -a /dev/sda
smartctl 6.3 2014-07-26 r3976 [x86_64-linux-3.17.6-1-ARCH] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Hitachi Travelstar 5K250
Device Model: Hitachi HTS542516K9SA00
Serial Number: 071110BB0300WCH23EJC
LU WWN Device Id: 5 000cca 531cf0d25
Firmware Version: BBCOC33P
User Capacity: 160,041,885,696 bytes [160 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS T13/1699-D revision 3f
SATA Version is: SATA 2.5, 1.5 Gb/s
Local Time is: Fri Jan 16 12:27:25 2015 CET
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: ( 24) The self-test routine was aborted by
the host.
Total time to complete Offline
data collection: ( 645) 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: ( 75) minutes.
SCT capabilities: (0x003d) 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 0x000b 099 099 062 Pre-fail Always - 131073
2 Throughput_Performance 0x0005 100 100 040 Pre-fail Offline - 0
3 Spin_Up_Time 0x0007 232 232 033 Pre-fail Always - 1
4 Start_Stop_Count 0x0012 097 097 000 Old_age Always - 6005
5 Reallocated_Sector_Ct 0x0033 038 038 005 Pre-fail Always - 0
7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 040 Pre-fail Offline - 0
9 Power_On_Hours 0x0012 090 090 000 Old_age Always - 4503
10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 099 099 000 Old_age Always - 2459
191 G-Sense_Error_Rate 0x000a 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 099 099 000 Old_age Always - 274
193 Load_Cycle_Count 0x0012 093 093 000 Old_age Always - 76128
194 Temperature_Celsius 0x0002 152 152 000 Old_age Always - 36 (Min/Max 13/52)
196 Reallocated_Event_Count 0x0032 016 016 000 Old_age Always - 4205
197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 29
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 15
223 Load_Retry_Count 0x000a 100 100 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 18033 (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 18033 occurred at disk power-on lifetime: 3070 hours (127 days + 22 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 61 9f 05 93 e9 Error: UNC 97 sectors at LBA = 0x0993059f = 160630175
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 03 80 80 05 93 e0 00 00:04:21.500 READ DMA EXT
25 03 80 80 05 93 e0 00 00:04:17.400 READ DMA EXT
25 03 80 00 05 93 e0 00 00:04:17.400 READ DMA EXT
25 03 80 80 01 93 e0 00 00:04:17.400 READ DMA EXT
25 03 80 00 01 93 e0 00 00:04:17.400 READ DMA EXT
Error 18032 occurred at disk power-on lifetime: 3070 hours (127 days + 22 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 61 9f 05 93 e9 Error: UNC 97 sectors at LBA = 0x0993059f = 160630175
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 03 80 80 05 93 e0 00 00:04:17.400 READ DMA EXT
25 03 80 00 05 93 e0 00 00:04:17.400 READ DMA EXT
25 03 80 80 01 93 e0 00 00:04:17.400 READ DMA EXT
25 03 80 00 01 93 e0 00 00:04:17.400 READ DMA EXT
25 03 80 80 fd 92 e0 00 00:04:17.400 READ DMA EXT
Error 18031 occurred at disk power-on lifetime: 3070 hours (127 days + 22 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 5d 23 e5 92 e9 Error: UNC 93 sectors at LBA = 0x0992e523 = 160621859
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 03 80 00 e5 92 e0 00 00:04:13.200 READ DMA EXT
25 03 80 00 e5 92 e0 00 00:04:09.100 READ DMA EXT
25 03 80 00 e5 92 e0 00 00:04:05.000 READ DMA EXT
25 03 80 00 e5 92 e0 00 00:04:00.900 READ DMA EXT
25 03 80 00 e5 92 e0 00 00:03:56.800 READ DMA EXT
Error 18030 occurred at disk power-on lifetime: 3070 hours (127 days + 22 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 5d 23 e5 92 e9 Error: UNC 93 sectors at LBA = 0x0992e523 = 160621859
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 03 80 00 e5 92 e0 00 00:04:09.100 READ DMA EXT
25 03 80 00 e5 92 e0 00 00:04:05.000 READ DMA EXT
25 03 80 00 e5 92 e0 00 00:04:00.900 READ DMA EXT
25 03 80 00 e5 92 e0 00 00:03:56.800 READ DMA EXT
25 03 80 80 e1 92 e0 00 00:03:56.800 READ DMA EXT
Error 18029 occurred at disk power-on lifetime: 3070 hours (127 days + 22 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 5d 23 e5 92 e9 Error: UNC 93 sectors at LBA = 0x0992e523 = 160621859
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 03 80 00 e5 92 e0 00 00:04:05.000 READ DMA EXT
25 03 80 00 e5 92 e0 00 00:04:00.900 READ DMA EXT
25 03 80 00 e5 92 e0 00 00:03:56.800 READ DMA EXT
25 03 80 80 e1 92 e0 00 00:03:56.800 READ DMA EXT
25 03 80 00 e1 92 e0 00 00:03:56.800 READ DMA EXT
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 80% 4503 -
# 2 Short offline Completed: read failure 80% 4502 214555817
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.
(nuocman@ArchNuoc)-(0)-(12:27 PM)(~)
--> I can see that there are some unpleasant results but what can I understand about it ?
Thanks for helping
Offline
What I find striking there is that my drive has 10x the operating hours that your drive has (45273 h on y system versus 4503 h on your system). Your raw read error rate is four orders of magnitude higher than mine. (131073 for your drive versus 17 for mine). This is so bad that it might be a bad cable. What kind of system is this? Is this the only drive on that interface? Or, is this a laptop that does not use cables?
at 4500 hours on your system, I expect that it may be under warranty (depending on how much you leave the drive system running). You might look into that.
Off topic, I truly love your city and am deeply saddened by recent events. In my most recent visit, I had the pleasure of staying in the Vincennes area. People were friendly and took good care of my family and me. My thoughts are with all Parisians.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Offline
5 Reallocated_Sector_Ct 0x0033 038 038 005 Pre-fail Always - 0
196 Reallocated_Event_Count 0x0032 016 016 000 Old_age Always - 4205
197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 29The Reallocated_Event_Count is also disturbing. It indicates a lot of failed attempts to re-allocate the 29 pending sectors.
Also the ATA Error Count of 18033 is crazy. I've looked at smartctl output of hundreds of drives in various states of failure but never seen anything with over a few hundred.
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline
It's a laptop so no there is no cable problem.
I did not had many opportunities to use my own computer this year and that explain the low powered time of the hdd.
And if I can remember, I took this hddd from another random device when I was searching for one.
And ok, I clearly need to buy a new one.
I couldn't understand those numbers alone because I had no reference to compare with.
Thanks for all explanations.
And ewaller thank you for your support, since last week we only hear about it and other terrifying events, It's reconfort me to hear that
feel concerned about it. I only hope that all of this will stop soon. Thanks,
Offline
Pages: 1