Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #177502
| From | Marc Shapiro <marcnshap@gmail.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: How to fix I/O errors? |
| Date | 2017-02-06 22:20 +0100 |
| Message-ID | <t7YRB-1TU-47@gated-at.bofh.it> (permalink) |
| References | <t6wNI-No-25@gated-at.bofh.it> <t6FxD-6j7-5@gated-at.bofh.it> <t6TTX-7qD-9@gated-at.bofh.it> <t72NA-5vS-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 02/03/2017 11:13 PM, David Christensen wrote:
> On 02/03/17 13:47, Marc Shapiro wrote:
>> On 02/02/2017 10:23 PM, David Christensen wrote:
>>>
>>> Have you downloaded and run the manufacturer diagnostic utilities for
>>> all your drives? What do they say?
>>>
>> I have now downloaded and run Seagate's tools and it does show a does
>> show a disk error. Since it stops on the first error I do not know if
>> this is an isolated error, or a more systematic problem.
>>
>> Automatic Write Reallocation Enable (AWRE) is on by default, but
>> Automatic Read Reallocation Enable (ARRE) is off. If I set ARRE on and
>> then run the long test (which reads all sectors sequentially), will that
>> reallocate any bad sectors and mark them as such? Is this a safe thing
>> to do?
>
> Beware that failures have a way of escalating faster than you expect.
>
>
> Do you have a good backup of the drive?
>
>
> If not and the data has high value, do not power up the drive. Pack it
> properly and send it to a professional recovery service.
>
>
> >> http://www.seagate.com/support/downloads/seatools/
> > I see download links for DOS and Windows, nothiong for Linux
>
> It is common for Wintel-centric tools to only run on Windows. It's
> good to keep an operational Windows system drive around. Mobile docks
> make swapping drives easy.
>
>
> Sometimes you get lucky and the tool is a live CD:
>
> www.seagate.com/files/www-content/support-content/downloads/seatools/_shared/downloads/SeaToolsDOS223ALL.ISO
>
>
>
> > If I remember correctly, [SMART] is
> > only going to be useful if it was already installed so the daemon
> > could be capturing data when the problem occurred. Is that correct,
> > or am I thinking of a different package?
>
> https://en.wikipedia.org/wiki/S.M.A.R.T.
>
> SMART is built-in to the firmware of the HDD/SSD; the drive
> microcontroller does most of the work. Using the right tools, you can
> pull SMART information out of the microcontroller and/or adjust
> tunable SMART parameters. As the drive is failing, you especially
> want those reports. If you post them here, people can tell you all
> kinds of interesting things about your drive.
>
>
> > I have now downloaded and run Seagate's tools and it does show a does
> > show a disk error. Since it stops on the first error I do not know if
> > this is an isolated error, or a more systematic problem.
>
> Take a picture of the screen with a digital camera (or phone), and
> then type the exact screen contents into a reply.
>
>
> David
>
I am pasting the result of smartctl -x /dev/sda below as I have no real
clue what to do with the information, but I have a few questions first.
1) I have purchased a new, very similar, Seagate 1TB drive and I plan to
install it and copy the whole system to the new drive. What is the best
way to do this copy since I don't wangt to copy bad sectors?
2) Once I have verified that the new drive boots and everything is
running properly I am hoping to reformat the old drive. This should
reallocate the bad sectors IIRC. I then would like to set up a raid
with both drives (keeping a close eye on the old drive). The
feasibility of this, I would guess, depends on what the posted smartctl
information tells someone who knows what to look for.
3) As I understand it, the above mentioned raid should be safe since,
even if the old drive deteriorates further, the system can run on just
the new drive. Is that correct?
Here is the smafrtctl output:
$ sudo smartctl -x /dev/sda
smartctl 6.4 2014-10-07 r4002 [x86_64-linux-3.16.0-4-amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda 7200.12
Device Model: ST31000528AS
Serial Number: 5VP9QSWJ
LU WWN Device Id: 5 000c50 03e5ccb5c
Firmware Version: CC3E
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 4
SATA Version is: SATA 2.6, 3.0 Gb/s
Local Time is: Mon Feb 6 12:57:05 2017 PST
==> WARNING: A firmware update for this drive may be available,
see the following Seagate web pages:
http://knowledge.seagate.com/articles/en_US/FAQ/207931en
http://knowledge.seagate.com/articles/en_US/FAQ/213891en
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM level is: 0 (vendor specific), recommended: 254
APM feature is: Unavailable
Rd look-ahead is: Enabled
Write cache is: Enabled
ATA Security is: Disabled, NOT FROZEN [SEC1]
Wt Cache Reorder: Unknown
=== 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: ( 121) The previous self-test
completed having
the read element of the test failed.
Total time to complete Offline
data collection: ( 600) 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: ( 175) minutes.
Conveyance self-test routine
recommended polling time: ( 2) 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 FLAGS VALUE WORST THRESH FAIL RAW_VALUE
1 Raw_Read_Error_Rate POSR-- 117 095 006 - 165391146
3 Spin_Up_Time PO---- 095 093 000 - 0
4 Start_Stop_Count -O--CK 100 100 020 - 406
5 Reallocated_Sector_Ct PO--CK 072 072 036 - 1181
7 Seek_Error_Rate POSR-- 087 060 030 - 656506200
9 Power_On_Hours -O--CK 048 048 000 - 46195
10 Spin_Retry_Count PO--C- 100 100 097 - 0
12 Power_Cycle_Count -O--CK 100 100 020 - 203
183 Runtime_Bad_Block -O--CK 092 092 000 - 8
184 End-to-End_Error -O--CK 100 100 099 - 0
187 Reported_Uncorrect -O--CK 011 011 000 - 89
188 Command_Timeout -O--CK 100 097 000 - 51540394008
189 High_Fly_Writes -O-RCK 100 100 000 - 0
190 Airflow_Temperature_Cel -O---K 070 049 045 - 30 (Min/Max
27/32)
194 Temperature_Celsius -O---K 030 051 000 - 30 (0 20 0 0 0)
195 Hardware_ECC_Recovered -O-RC- 034 003 000 - 165391146
197 Current_Pending_Sector -O--C- 093 083 000 - 310
198 Offline_Uncorrectable ----C- 093 083 000 - 310
199 UDMA_CRC_Error_Count -OSRCK 200 200 000 - 26
240 Head_Flying_Hours ------ 100 253 000 - 46718 (49 76 0)
241 Total_LBAs_Written ------ 100 253 000 - 1725386978
242 Total_LBAs_Read ------ 100 253 000 - 265479204
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warning
General Purpose Log Directory Version 1
SMART Log Directory Version 1 [multi-sector log support]
Address Access R/W Size Description
0x00 GPL,SL R/O 1 Log Directory
0x01 GPL,SL R/O 1 Summary SMART error log
0x02 GPL,SL R/O 5 Comprehensive SMART error log
0x03 GPL R/O 5 Ext. Comprehensive SMART error log
0x06 GPL,SL R/O 1 SMART self-test log
0x07 GPL R/O 1 Extended self-test log
0x09 GPL,SL R/W 1 Selective self-test log
0x10 GPL R/O 1 SATA NCQ Queued Error log
0x11 GPL R/O 1 SATA Phy Event Counters log
0x21 GPL R/O 1 Write stream error log
0x22 GPL R/O 1 Read stream error log
0x80-0x9f GPL,SL R/W 16 Host vendor specific log
0xa1 GPL,SL VS 20 Device vendor specific log
0xa2 GPL VS 2248 Device vendor specific log
0xa8 GPL,SL VS 129 Device vendor specific log
0xa9 GPL,SL VS 1 Device vendor specific log
0xb0 GPL VS 2928 Device vendor specific log
0xbd GPL VS 252 Device vendor specific log
0xbe-0xbf GPL VS 65535 Device vendor specific log
0xc0 GPL,SL VS 1 Device vendor specific log
0xe0 GPL,SL R/W 1 SCT Command/Status
0xe1 GPL,SL R/W 1 SCT Data Transfer
SMART Extended Comprehensive Error Log Version: 1 (5 sectors)
Device Error Count: 89 (device log contains only the most recent 20 errors)
CR = Command Register
FEATR = Features Register
COUNT = Count (was: Sector Count) Register
LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8
LH = LBA High (was: Cylinder High) Register ] LBA
LM = LBA Mid (was: Cylinder Low) Register ] Register
LL = LBA Low (was: Sector Number) Register ]
DV = Device (was: Device/Head) Register
DC = Device Control Register
ER = Error register
ST = Status register
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 89 [8] occurred at disk power-on lifetime: 46170 hours (1923 days
+ 18 hours)
When the command that caused the error occurred, the device was
active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 0f 96 00 29 00 00 00 Error: UNC at LBA =
0xf96002900 = 66941102336
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time
Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- ---------------
--------------------
42 00 00 02 00 00 0f 96 00 29 00 40 00 09:03:21.547 READ VERIFY
SECTOR(S) EXT
42 00 00 02 00 00 0f 38 00 28 00 e0 00 09:03:21.123 READ VERIFY
SECTOR(S) EXT
42 00 00 02 00 00 0f 44 00 18 00 e0 00 09:03:16.898 READ VERIFY
SECTOR(S) EXT
42 00 00 02 00 00 0f 52 00 08 00 e0 00 09:03:12.615 READ VERIFY
SECTOR(S) EXT
42 00 00 02 00 00 0e 60 00 f8 00 e0 00 09:03:08.339 READ VERIFY
SECTOR(S) EXT
Error 88 [7] occurred at disk power-on lifetime: 46169 hours (1923 days
+ 17 hours)
When the command that caused the error occurred, the device was
active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 0f 96 00 29 00 00 00 Error: UNC at LBA =
0xf96002900 = 66941102336
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time
Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- ---------------
--------------------
42 00 00 02 00 00 0f 96 00 29 00 e0 00 08:31:35.660 READ VERIFY
SECTOR(S) EXT
42 00 00 02 00 00 0f 94 00 29 00 40 00 08:31:35.026 READ VERIFY
SECTOR(S) EXT
42 00 00 02 00 00 0f cc 00 21 00 e0 00 08:31:32.951 READ VERIFY
SECTOR(S) EXT
42 00 00 02 00 00 0f dc 00 11 00 e0 00 08:31:28.721 READ VERIFY
SECTOR(S) EXT
42 00 00 02 00 00 0f e8 00 01 00 e0 00 08:31:24.439 READ VERIFY
SECTOR(S) EXT
Error 87 [6] occurred at disk power-on lifetime: 46161 hours (1923 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 COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 0f a7 00 29 f8 00 00 Error: UNC at LBA =
0xfa70029f8 = 67226315256
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time
Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- ---------------
--------------------
60 00 00 00 08 00 0f a7 00 29 f8 40 00 2d+13:14:24.209 READ FPDMA
QUEUED
61 00 00 00 10 00 19 ed 00 45 9c 40 00 2d+13:14:24.209 WRITE FPDMA
QUEUED
61 00 00 00 10 00 19 96 00 45 1c 40 00 2d+13:14:24.209 WRITE FPDMA
QUEUED
61 00 00 00 10 00 19 f9 00 19 a4 40 00 2d+13:14:24.209 WRITE FPDMA
QUEUED
61 00 00 00 50 00 19 0c 00 43 2c 40 00 2d+13:14:24.209 WRITE FPDMA
QUEUED
Error 86 [5] occurred at disk power-on lifetime: 46161 hours (1923 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 COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 0f a7 00 29 f8 00 00 Error: UNC at LBA =
0xfa70029f8 = 67226315256
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time
Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- ---------------
--------------------
60 00 00 00 08 00 0f a7 00 29 f8 40 00 2d+13:14:20.983 READ FPDMA
QUEUED
60 00 00 00 08 00 0f a8 00 29 08 40 00 2d+13:14:20.982 READ FPDMA
QUEUED
60 00 00 00 08 00 0f a8 00 29 00 40 00 2d+13:14:20.975 READ FPDMA
QUEUED
60 00 00 00 08 00 0f a0 00 29 08 40 00 2d+13:14:20.974 READ FPDMA
QUEUED
60 00 00 00 08 00 0f 9f 00 29 f8 40 00 2d+13:14:20.965 READ FPDMA
QUEUED
Error 85 [4] occurred at disk power-on lifetime: 46161 hours (1923 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 COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 0f 98 00 29 84 00 00 Error: WP at LBA =
0xf98002984 = 66974656900
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time
Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- ---------------
--------------------
61 00 00 00 08 00 19 0c 00 43 24 40 00 2d+13:14:17.731 WRITE FPDMA
QUEUED
60 00 00 00 08 00 0f 98 00 29 80 40 00 2d+13:14:17.730 READ FPDMA
QUEUED
ea 00 00 00 00 00 00 00 00 00 00 a0 00 2d+13:14:17.730 FLUSH CACHE EXT
b0 00 da 00 00 00 00 4f 00 c2 00 00 00 2d+13:14:17.678 SMART RETURN
STATUS
60 00 00 00 08 00 0f 98 00 29 78 40 00 2d+13:14:17.650 READ FPDMA
QUEUED
Error 84 [3] occurred at disk power-on lifetime: 46161 hours (1923 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 COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 0f 98 00 29 4c 00 00 Error: UNC at LBA =
0xf9800294c = 66974656844
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time
Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- ---------------
--------------------
60 00 00 00 08 00 0f 98 00 29 48 40 00 2d+13:14:14.358 READ FPDMA
QUEUED
ea 00 00 00 00 00 00 00 00 00 00 a0 00 2d+13:14:14.358 FLUSH CACHE EXT
b0 00 d1 00 01 00 00 4f 00 c2 00 00 00 2d+13:14:14.351 SMART READ
ATTRIBUTE THRESHOLDS [OBS-4]
27 00 00 00 00 00 00 00 00 00 00 e0 00 2d+13:14:14.291 READ NATIVE
MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 2d+13:14:14.290 IDENTIFY DEVICE
Error 83 [2] occurred at disk power-on lifetime: 46161 hours (1923 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 COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 0f 98 00 29 3c 00 00 Error: WP at LBA =
0xf9800293c = 66974656828
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time
Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- ---------------
--------------------
61 00 00 00 08 00 19 0b 00 43 bc 40 00 2d+13:14:11.084 WRITE FPDMA
QUEUED
60 00 00 00 08 00 0f 98 00 29 38 40 00 2d+13:14:11.083 READ FPDMA
QUEUED
ea 00 00 00 00 00 00 00 00 00 00 a0 00 2d+13:14:11.083 FLUSH CACHE EXT
e5 00 00 00 00 00 00 00 00 00 00 00 00 2d+13:14:11.082 CHECK POWER MODE
27 00 00 00 00 00 00 00 00 00 00 e0 00 2d+13:14:11.022 READ NATIVE
MAX ADDRESS EXT [OBS-ACS-3]
Error 82 [1] occurred at disk power-on lifetime: 46161 hours (1923 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 COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 0f 98 00 29 10 00 00 Error: WP at LBA =
0xf98002910 = 66974656784
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time
Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- ---------------
--------------------
61 00 00 00 08 00 19 96 00 45 14 40 00 2d+13:14:07.755 WRITE FPDMA
QUEUED
61 00 00 00 50 00 19 0b 00 43 6c 40 00 2d+13:14:07.755 WRITE FPDMA
QUEUED
61 00 00 00 08 00 19 f9 00 19 9c 40 00 2d+13:14:07.754 WRITE FPDMA
QUEUED
61 00 00 00 08 00 19 c8 00 19 34 40 00 2d+13:14:07.754 WRITE FPDMA
QUEUED
61 00 00 00 08 00 19 a4 00 19 94 40 00 2d+13:14:07.754 WRITE FPDMA
QUEUED
SMART Extended Self-test Log Version: 1 (1 sectors)
Num Test_Description Status Remaining
LifeTime(hours) LBA_of_first_error
# 1 Short offline Completed: read failure 90% 46194
254384128
# 2 Short offline Completed without error 00% 8020 -
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.
SCT Status Version: 3
SCT Version (vendor specific): 522 (0x020a)
SCT Support Level: 1
Device State: Active (0)
Current Temperature: 31 Celsius
Power Cycle Min/Max Temperature: 27/32 Celsius
Lifetime Min/Max Temperature: 20/51 Celsius
Under/Over Temperature Limit Count: 0/0
SCT Temperature History Version: 2
Temperature Sampling Period: 1 minute
Temperature Logging Interval: 59 minutes
Min/Max recommended Temperature: 14/55 Celsius
Min/Max Temperature Limit: 10/60 Celsius
Temperature History Size (Index): 128 (116)
Index Estimated Time Temperature Celsius
117 2017-02-01 07:56 27 ********
118 2017-02-01 08:55 27 ********
119 2017-02-01 09:54 27 ********
120 2017-02-01 10:53 30 ***********
... ..( 7 skipped). .. ***********
0 2017-02-01 18:45 30 ***********
1 2017-02-01 19:44 28 *********
2 2017-02-01 20:43 28 *********
3 2017-02-01 21:42 28 *********
4 2017-02-01 22:41 29 **********
5 2017-02-01 23:40 28 *********
6 2017-02-02 00:39 29 **********
7 2017-02-02 01:38 29 **********
8 2017-02-02 02:37 31 ************
9 2017-02-02 03:36 31 ************
10 2017-02-02 04:35 28 *********
11 2017-02-02 05:34 28 *********
12 2017-02-02 06:33 ? -
13 2017-02-02 07:32 27 ********
... ..( 3 skipped). .. ********
17 2017-02-02 11:28 27 ********
18 2017-02-02 12:27 29 **********
19 2017-02-02 13:26 31 ************
20 2017-02-02 14:25 30 ***********
21 2017-02-02 15:24 31 ************
22 2017-02-02 16:23 30 ***********
23 2017-02-02 17:22 30 ***********
24 2017-02-02 18:21 30 ***********
25 2017-02-02 19:20 28 *********
26 2017-02-02 20:19 30 ***********
27 2017-02-02 21:18 30 ***********
28 2017-02-02 22:17 28 *********
29 2017-02-02 23:16 28 *********
30 2017-02-03 00:15 29 **********
31 2017-02-03 01:14 28 *********
32 2017-02-03 02:13 28 *********
33 2017-02-03 03:12 29 **********
34 2017-02-03 04:11 29 **********
35 2017-02-03 05:10 31 ************
36 2017-02-03 06:09 29 **********
37 2017-02-03 07:08 28 *********
38 2017-02-03 08:07 27 ********
... ..( 2 skipped). .. ********
41 2017-02-03 11:04 27 ********
42 2017-02-03 12:03 29 **********
43 2017-02-03 13:02 32 *************
44 2017-02-03 14:01 31 ************
45 2017-02-03 15:00 28 *********
46 2017-02-03 15:59 29 **********
47 2017-02-03 16:58 29 **********
48 2017-02-03 17:57 30 ***********
49 2017-02-03 18:56 29 **********
50 2017-02-03 19:55 30 ***********
51 2017-02-03 20:54 29 **********
52 2017-02-03 21:53 28 *********
53 2017-02-03 22:52 28 *********
54 2017-02-03 23:51 27 ********
55 2017-02-04 00:50 28 *********
... ..( 2 skipped). .. *********
58 2017-02-04 03:47 28 *********
59 2017-02-04 04:46 31 ************
60 2017-02-04 05:45 30 ***********
61 2017-02-04 06:44 29 **********
62 2017-02-04 07:43 28 *********
63 2017-02-04 08:42 28 *********
64 2017-02-04 09:41 28 *********
65 2017-02-04 10:40 30 ***********
66 2017-02-04 11:39 29 **********
67 2017-02-04 12:38 30 ***********
68 2017-02-04 13:37 29 **********
69 2017-02-04 14:36 31 ************
70 2017-02-04 15:35 30 ***********
71 2017-02-04 16:34 31 ************
72 2017-02-04 17:33 29 **********
73 2017-02-04 18:32 29 **********
74 2017-02-04 19:31 30 ***********
75 2017-02-04 20:30 ? -
76 2017-02-04 21:29 31 ************
77 2017-02-04 22:28 ? -
78 2017-02-04 23:27 31 ************
79 2017-02-05 00:26 31 ************
80 2017-02-05 01:25 30 ***********
81 2017-02-05 02:24 29 **********
... ..( 5 skipped). .. **********
87 2017-02-05 08:18 29 **********
88 2017-02-05 09:17 30 ***********
89 2017-02-05 10:16 30 ***********
90 2017-02-05 11:15 29 **********
91 2017-02-05 12:14 29 **********
92 2017-02-05 13:13 30 ***********
93 2017-02-05 14:12 32 *************
94 2017-02-05 15:11 32 *************
95 2017-02-05 16:10 31 ************
96 2017-02-05 17:09 31 ************
97 2017-02-05 18:08 ? -
98 2017-02-05 19:07 31 ************
99 2017-02-05 20:06 31 ************
100 2017-02-05 21:05 31 ************
101 2017-02-05 22:04 29 **********
102 2017-02-05 23:03 30 ***********
103 2017-02-06 00:02 30 ***********
104 2017-02-06 01:01 29 **********
105 2017-02-06 02:00 29 **********
106 2017-02-06 02:59 28 *********
107 2017-02-06 03:58 27 ********
108 2017-02-06 04:57 27 ********
109 2017-02-06 05:56 28 *********
110 2017-02-06 06:55 28 *********
111 2017-02-06 07:54 28 *********
112 2017-02-06 08:53 30 ***********
113 2017-02-06 09:52 29 **********
114 2017-02-06 10:51 27 ********
115 2017-02-06 11:50 27 ********
116 2017-02-06 12:49 31 ************
SCT Error Recovery Control:
Read: Disabled
Write: Disabled
Device Statistics (GP/SMART Log 0x04) not supported
SATA Phy Event Counters (GP Log 0x11)
ID Size Value Description
0x000a 2 3 Device-to-host register FISes sent due to a COMRESET
0x0001 2 0 Command failed due to ICRC error
0x0003 2 0 R_ERR response for device-to-host data FIS
0x0004 2 0 R_ERR response for host-to-device data FIS
0x0006 2 0 R_ERR response for device-to-host non-data FIS
0x0007 2 0 R_ERR response for host-to-device non-data FIS
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
How to fix I/O errors? Marc Shapiro <marcnshap@gmail.com> - 2017-02-02 22:10 +0100
Re: How to fix I/O errors? <tomas@tuxteam.de> - 2017-02-02 22:30 +0100
Re: How to fix I/O errors? Marc Shapiro <marcnshap@gmail.com> - 2017-02-02 22:50 +0100
Re: How to fix I/O errors? Marc Shapiro <marcnshap@gmail.com> - 2017-02-02 23:20 +0100
Re: How to fix I/O errors? David Christensen <dpchrist@holgerdanske.com> - 2017-02-03 07:30 +0100
Re: How to fix I/O errors? Marc Shapiro <marcnshap@gmail.com> - 2017-02-03 08:40 +0100
Re: How to fix I/O errors? Mark Fletcher <mark27q1@gmail.com> - 2017-02-03 16:00 +0100
Re: How to fix I/O errors? Marc Shapiro <marcnshap@gmail.com> - 2017-02-03 22:40 +0100
Re: How to fix I/O errors? Jonathan Dowland <jmtd@debian.org> - 2017-02-07 12:00 +0100
Re: How to fix I/O errors? Marc Shapiro <marcnshap@gmail.com> - 2017-02-03 22:50 +0100
Re: How to fix I/O errors? David Christensen <dpchrist@holgerdanske.com> - 2017-02-04 08:20 +0100
Re: How to fix I/O errors? Marc Shapiro <marcnshap@gmail.com> - 2017-02-06 22:20 +0100
Re: How to fix I/O errors? David Christensen <dpchrist@holgerdanske.com> - 2017-02-06 23:40 +0100
Re: How to fix I/O errors? Ric Moore <wayward4now@gmail.com> - 2017-02-04 16:20 +0100
Re: How to fix I/O errors? David Christensen <dpchrist@holgerdanske.com> - 2017-02-04 20:20 +0100
Re: How to fix I/O errors? Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2017-02-06 17:00 +0100
Re: How to fix I/O errors? Gene Heskett <gheskett@shentel.net> - 2017-02-06 18:30 +0100
Re: How to fix I/O errors? David Christensen <dpchrist@holgerdanske.com> - 2017-02-06 22:30 +0100
Re: How to fix I/O errors? Felix Miata <mrmazda@earthlink.net> - 2017-02-06 23:20 +0100
Re: How to fix I/O errors? David Christensen <dpchrist@holgerdanske.com> - 2017-02-06 22:30 +0100
csiph-web