From: Adam F. <a2...@du...> - 2008-01-18 14:45:41
|
Back in April I started a thread called "ATA error count increasing --- should I worry?" http://thread.gmane.org/gmane.linux.utilities.smartmontools/4528 I took the computer back the shop last summer with printouts of error messages and some of the information I got here. They did some tests for a few days and replaced the hard drive (with a larger Samsung model; I paid the difference to upgrade). I copied my data from the old one and wiped it without any problems and gave it back to them. At some point in the past few months the ata errors started appearing occasionally again in the syslog, and if I'm using the computer at the time, I can tell when it's happening: it freezes up for a few seconds and then something like [1] appears. In the past two weeks, the computer has also "lost" the hard drive connection a couple of times: it locked up completely; I pressed the reset button; the BIOS couldn't find the drive; I unplugged and replugged the SATA cable at the port (sometimes switching between the two ports); it started working again. This only happens when I'm not sitting at the machine. I've run the smartctl tests and to the best of my limited knowledge the results are OK: [2]. I think the problem must be in the SATA controller or nearby on the motherboard electronics (the SATA ports are built-in); can anyone advise on this? Thanks, Adam [1] Jan 15 21:53:54 bunsen kernel: [172805.880000] ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x3850000 action 0x2 frozen Jan 15 21:53:55 bunsen kernel: [172805.880000] ata1.00: cmd 25/00:00:0f:41:2b/00:01:2a:00:00/e0 tag 0 cdb 0x0 data 131072 in Jan 15 21:53:55 bunsen kernel: [172805.880000] ata1: hard resetting port Jan 15 21:53:55 bunsen kernel: [172806.916000] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jan 15 21:53:55 bunsen kernel: [172806.948000] ata1.00: configured for UDMA/133 Jan 15 21:53:55 bunsen kernel: [172806.948000] ata1: EH complete [2] smartctl version 5.37 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: SAMSUNG HD403LJ Serial Number: S0NFJ13P200885 Firmware Version: CT100-10 User Capacity: 400,088,457,216 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Not recognized. Minor revision code: 0x52 Local Time is: Fri Jan 18 14:32:47 2008 GMT ==> WARNING: May need -F samsung or -F samsung2 enabled; see manual for details. 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: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (8283) 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: ( 142) minutes. 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 - 1 3 Spin_Up_Time 0x0007 100 100 015 Pre-fail Always - 7424 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 32 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 - 3272 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 - 32 187 Unknown_Attribute 0x0032 253 253 000 Old_age Always - 0 188 Unknown_Attribute 0x0032 253 253 000 Old_age Always - 0 190 Temperature_Celsius 0x0022 065 058 000 Old_age Always - 35 194 Temperature_Celsius 0x0022 133 112 000 Old_age Always - 35 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 9636666 196 Reallocated_Event_Count 0x0032 253 253 000 Old_age Always - 0 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 1 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 SMART Error Log Version: 1 ATA Error Count: 52 (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 52 occurred at disk power-on lifetime: 1887 hours (78 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 -- -- -- -- -- -- -- 84 51 80 77 84 21 e7 Error: ICRC, ABRT 128 sectors at LBA = 0x07218477 = 119637111 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 77 84 21 e7 00 00:02:42.813 READ DMA c8 00 80 f7 83 21 e7 00 00:02:42.813 READ DMA c8 00 80 77 83 21 e7 00 00:02:42.813 READ DMA c8 00 80 f7 82 21 e7 00 00:02:42.813 READ DMA c8 00 80 77 82 21 e7 00 00:02:42.813 READ DMA Error 51 occurred at disk power-on lifetime: 1887 hours (78 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 -- -- -- -- -- -- -- 84 51 00 5f d8 6e ec Error: ICRC, ABRT at LBA = 0x0c6ed85f = 208590943 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 00 5f d8 6e ec 00 17d+14:39:23.329 READ DMA c8 00 d8 5f d6 6e ec 00 17d+14:39:23.329 READ DMA c8 00 00 5f d5 6e ec 00 17d+14:39:23.267 READ DMA c8 00 00 5f d4 6e ec 00 17d+14:39:23.267 READ DMA c8 00 00 5f d3 6e ec 00 17d+14:39:23.267 READ DMA Error 50 occurred at disk power-on lifetime: 1814 hours (75 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 80 57 76 86 eb Error: ICRC, ABRT 128 sectors at LBA = 0x0b867657 = 193361495 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 57 76 86 eb 00 14d+14:22:29.954 READ DMA c8 00 08 d7 04 0b ec 00 14d+14:22:29.892 READ DMA c8 00 08 2f 08 08 ec 00 14d+14:22:29.892 READ DMA c8 00 08 07 ff 0c ec 00 14d+14:22:29.892 READ DMA c8 00 08 3f 57 0c ec 00 14d+14:22:29.892 READ DMA Error 49 occurred at disk power-on lifetime: 1478 hours (61 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 cf 62 60 eb Error: ICRC, ABRT at LBA = 0x0b6062cf = 190866127 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 00 cf 62 60 eb 00 14:04:44.954 READ DMA c8 00 a0 df d7 6f eb 00 14:04:44.892 READ DMA c8 00 40 97 d7 6f eb 00 14:04:44.892 READ DMA ca 00 08 2f 01 f8 ed 00 14:04:44.829 WRITE DMA ca 00 08 17 05 f4 ed 00 14:04:44.829 WRITE DMA Error 48 occurred at disk power-on lifetime: 1478 hours (61 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 b8 37 a1 5a eb Error: ICRC, ABRT 184 sectors at LBA = 0x0b5aa137 = 190488887 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 b8 37 a1 5a eb 00 13:58:25.454 READ DMA c8 00 58 c7 a7 5a eb 00 13:58:25.329 READ DMA c8 00 18 9f a7 5a eb 00 13:58:25.329 READ DMA c8 00 20 77 a7 5a eb 00 13:58:25.329 READ DMA c8 00 08 5f a7 5a eb 00 13:58:25.329 READ DMA 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% 3269 - # 2 Extended offline Completed without error 00% 3199 - # 3 Short offline Completed without error 00% 3195 - # 4 Short offline Completed without error 00% 102 - SMART Selective Self-Test Log Data Structure Revision Number (0) should be 1 SMART Selective self-test log data structure revision number 0 Warning: ATA Specification requires 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. |
From: Justin P. <jp...@lu...> - 2008-01-18 17:27:41
|
On Fri, 18 Jan 2008, Adam Funk wrote: > Back in April I started a thread called "ATA error count increasing --- > should I worry?" > > http://thread.gmane.org/gmane.linux.utilities.smartmontools/4528 > That's usually not good, I got 1 disk out of 4 750GiB and one kept doing that resetting continuously, same thing with a raptor I bought once I rma'd them immediately. If it only does it spuriously, DISABLE NCQ on the drive, and the problem should go away. If it doesn't, it is either a: 1. cable issue 2. controller issue 3. drive electrical/issue 4. mobo/psu/issue (ulikley) Justin. |
From: Adam F. <a2...@du...> - 2008-01-31 15:15:41
|
On 2008-01-18, Justin Piszcz wrote: > > > On Fri, 18 Jan 2008, Adam Funk wrote: > >> Back in April I started a thread called "ATA error count increasing --- >> should I worry?" >> >> http://thread.gmane.org/gmane.linux.utilities.smartmontools/4528 This one now seems to have stopped putting the resets in the log. It just (rarely) loses the drive and I have to fiddle with it and hit reset a few times. I'm taking it back to the shop in a couple of days. > That's usually not good, I got 1 disk out of 4 750GiB and one kept doing that > resetting continuously, same thing with a raptor I bought once I rma'd them > immediately. > > If it only does it spuriously, DISABLE NCQ on the drive, What man page (for example) would tell me how to do that? |
From: Justin P. <jp...@lu...> - 2008-01-31 15:25:58
|
On Thu, 31 Jan 2008, Adam Funk wrote: > On 2008-01-18, Justin Piszcz wrote: > >> >> >> On Fri, 18 Jan 2008, Adam Funk wrote: >> >>> Back in April I started a thread called "ATA error count increasing --- >>> should I worry?" >>> >>> http://thread.gmane.org/gmane.linux.utilities.smartmontools/4528 > > This one now seems to have stopped putting the resets in the log. It > just (rarely) loses the drive and I have to fiddle with it and hit > reset a few times. I'm taking it back to the shop in a couple of days. > > >> That's usually not good, I got 1 disk out of 4 750GiB and one kept doing that >> resetting continuously, same thing with a raptor I bought once I rma'd them >> immediately. >> >> If it only does it spuriously, DISABLE NCQ on the drive, > > What man page (for example) would tell me how to do that? Setting the depth to 1 disables it. echo "Disabling NCQ on $i" echo 1 > /sys/block/"$i"/device/queue_depth Justin. |
From: Adam F. <a2...@du...> - 2008-01-31 21:00:54
|
On 2008-01-31, Justin Piszcz wrote: >>> If it only does it spuriously, DISABLE NCQ on the drive, >> >> What man page (for example) would tell me how to do that? > > Setting the depth to 1 disables it. > > echo "Disabling NCQ on $i" > echo 1 > /sys/block/"$i"/device/queue_depth I'd never have found it! I was looking in man hdparm and places like that. |
From: Bruce A. <ba...@gr...> - 2008-03-03 14:44:28
|
One other thing to check: the SATA cable and connections. On Fri, 18 Jan 2008, Adam Funk wrote: > Back in April I started a thread called "ATA error count increasing --- > should I worry?" > > http://thread.gmane.org/gmane.linux.utilities.smartmontools/4528 > > I took the computer back the shop last summer with printouts of error > messages and some of the information I got here. They did some tests > for a few days and replaced the hard drive (with a larger Samsung > model; I paid the difference to upgrade). I copied my data from the > old one and wiped it without any problems and gave it back to them. > > At some point in the past few months the ata errors started appearing > occasionally again in the syslog, and if I'm using the computer at the > time, I can tell when it's happening: it freezes up for a few seconds > and then something like [1] appears. > > In the past two weeks, the computer has also "lost" the hard drive > connection a couple of times: it locked up completely; I pressed the > reset button; the BIOS couldn't find the drive; I unplugged and > replugged the SATA cable at the port (sometimes switching between the > two ports); it started working again. This only happens when I'm not > sitting at the machine. > > I've run the smartctl tests and to the best of my limited knowledge > the results are OK: [2]. > > I think the problem must be in the SATA controller or nearby on the > motherboard electronics (the SATA ports are built-in); can anyone > advise on this? > > Thanks, > Adam > > > [1] > Jan 15 21:53:54 bunsen kernel: [172805.880000] ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x3850000 action 0x2 frozen > Jan 15 21:53:55 bunsen kernel: [172805.880000] ata1.00: cmd 25/00:00:0f:41:2b/00:01:2a:00:00/e0 tag 0 cdb 0x0 data 131072 in > Jan 15 21:53:55 bunsen kernel: [172805.880000] ata1: hard resetting port > Jan 15 21:53:55 bunsen kernel: [172806.916000] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > Jan 15 21:53:55 bunsen kernel: [172806.948000] ata1.00: configured for UDMA/133 > Jan 15 21:53:55 bunsen kernel: [172806.948000] ata1: EH complete > > > [2] > smartctl version 5.37 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen > Home page is http://smartmontools.sourceforge.net/ > > === START OF INFORMATION SECTION === > Device Model: SAMSUNG HD403LJ > Serial Number: S0NFJ13P200885 > Firmware Version: CT100-10 > User Capacity: 400,088,457,216 bytes > Device is: In smartctl database [for details use: -P show] > ATA Version is: 8 > ATA Standard is: Not recognized. Minor revision code: 0x52 > Local Time is: Fri Jan 18 14:32:47 2008 GMT > > ==> WARNING: May need -F samsung or -F samsung2 enabled; see manual for details. > > 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: ( 0) The previous self-test routine completed > without error or no self-test has ever > been run. > Total time to complete Offline > data collection: (8283) 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: ( 142) minutes. > > 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 - 1 > 3 Spin_Up_Time 0x0007 100 100 015 Pre-fail Always - 7424 > 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 32 > 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 - 3272 > 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 - 32 > 187 Unknown_Attribute 0x0032 253 253 000 Old_age Always - 0 > 188 Unknown_Attribute 0x0032 253 253 000 Old_age Always - 0 > 190 Temperature_Celsius 0x0022 065 058 000 Old_age Always - 35 > 194 Temperature_Celsius 0x0022 133 112 000 Old_age Always - 35 > 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 9636666 > 196 Reallocated_Event_Count 0x0032 253 253 000 Old_age Always - 0 > 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 1 > 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 > > SMART Error Log Version: 1 > ATA Error Count: 52 (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 52 occurred at disk power-on lifetime: 1887 hours (78 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 > -- -- -- -- -- -- -- > 84 51 80 77 84 21 e7 Error: ICRC, ABRT 128 sectors at LBA = 0x07218477 = 119637111 > > 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 77 84 21 e7 00 00:02:42.813 READ DMA > c8 00 80 f7 83 21 e7 00 00:02:42.813 READ DMA > c8 00 80 77 83 21 e7 00 00:02:42.813 READ DMA > c8 00 80 f7 82 21 e7 00 00:02:42.813 READ DMA > c8 00 80 77 82 21 e7 00 00:02:42.813 READ DMA > > Error 51 occurred at disk power-on lifetime: 1887 hours (78 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 > -- -- -- -- -- -- -- > 84 51 00 5f d8 6e ec Error: ICRC, ABRT at LBA = 0x0c6ed85f = 208590943 > > 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 00 5f d8 6e ec 00 17d+14:39:23.329 READ DMA > c8 00 d8 5f d6 6e ec 00 17d+14:39:23.329 READ DMA > c8 00 00 5f d5 6e ec 00 17d+14:39:23.267 READ DMA > c8 00 00 5f d4 6e ec 00 17d+14:39:23.267 READ DMA > c8 00 00 5f d3 6e ec 00 17d+14:39:23.267 READ DMA > > Error 50 occurred at disk power-on lifetime: 1814 hours (75 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 80 57 76 86 eb Error: ICRC, ABRT 128 sectors at LBA = 0x0b867657 = 193361495 > > 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 57 76 86 eb 00 14d+14:22:29.954 READ DMA > c8 00 08 d7 04 0b ec 00 14d+14:22:29.892 READ DMA > c8 00 08 2f 08 08 ec 00 14d+14:22:29.892 READ DMA > c8 00 08 07 ff 0c ec 00 14d+14:22:29.892 READ DMA > c8 00 08 3f 57 0c ec 00 14d+14:22:29.892 READ DMA > > Error 49 occurred at disk power-on lifetime: 1478 hours (61 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 cf 62 60 eb Error: ICRC, ABRT at LBA = 0x0b6062cf = 190866127 > > 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 00 cf 62 60 eb 00 14:04:44.954 READ DMA > c8 00 a0 df d7 6f eb 00 14:04:44.892 READ DMA > c8 00 40 97 d7 6f eb 00 14:04:44.892 READ DMA > ca 00 08 2f 01 f8 ed 00 14:04:44.829 WRITE DMA > ca 00 08 17 05 f4 ed 00 14:04:44.829 WRITE DMA > > Error 48 occurred at disk power-on lifetime: 1478 hours (61 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 b8 37 a1 5a eb Error: ICRC, ABRT 184 sectors at LBA = 0x0b5aa137 = 190488887 > > 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 b8 37 a1 5a eb 00 13:58:25.454 READ DMA > c8 00 58 c7 a7 5a eb 00 13:58:25.329 READ DMA > c8 00 18 9f a7 5a eb 00 13:58:25.329 READ DMA > c8 00 20 77 a7 5a eb 00 13:58:25.329 READ DMA > c8 00 08 5f a7 5a eb 00 13:58:25.329 READ DMA > > 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% 3269 - > # 2 Extended offline Completed without error 00% 3199 - > # 3 Short offline Completed without error 00% 3195 - > # 4 Short offline Completed without error 00% 102 - > > SMART Selective Self-Test Log Data Structure Revision Number (0) should be 1 > SMART Selective self-test log data structure revision number 0 > Warning: ATA Specification requires 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. > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Smartmontools-support mailing list > Sma...@li... > https://lists.sourceforge.net/lists/listinfo/smartmontools-support > |
From: Adam F. <a2...@du...> - 2008-03-04 20:45:43
|
On 2008-03-03, Bruce Allen wrote: > One other thing to check: the SATA cable and connections. I had already tried replacing the cable. The shop replaced the motherboard and I've had no further problems. Thanks for the advice. |