* device error via SDB FIS
@ 2007-06-30 17:10 Daniel Schroeder
2007-06-30 17:12 ` Justin Piszcz
2007-06-30 21:22 ` Jeff Garzik
0 siblings, 2 replies; 8+ messages in thread
From: Daniel Schroeder @ 2007-06-30 17:10 UTC (permalink / raw)
To: linux-ide
hello list,
i do not know, what this could mean, but i have never seen it before.
System is 2.6.22-rc6, sil3132, samsung hd501lj (new hd under 10 power on
hours)
time line:
1: power on (single esata enclosure)
2: system recognizes and configures the disk
3: mount disk
4: use disk
5: device error via SDB FIS
6: mount is still there, everything looks good except of this entry in logs
<quote>
ata3: exception Emask 0x10 SAct 0x0 SErr 0x80000 action 0x2 frozen
ata3: (irq_stat 0x01140010, PHY RDY changed)
ata3: soft resetting port
ata3: SATA link down (SStatus 0 SControl 300)
ata3: EH complete
ata3: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0x2 frozen
ata3: (irq_stat 0x00b00090, PHY RDY changed)
ata3: soft resetting port
ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ata3.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168
ata3.00: ATA-8: SAMSUNG HD501LJ, CR100-10, max UDMA7
ata3.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
ata3.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168
ata3.00: configured for UDMA/100
ata3: EH complete
scsi 2:0:0:0: Direct-Access ATA SAMSUNG HD501LJ CR10 PQ: 0 ANSI: 5
sd 2:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB)
sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 2:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB)
sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sdc: sdc1
sd 2:0:0:0: [sdc] Attached SCSI disk
sd 2:0:0:0: Attached scsi generic sg2 type 0
kjournald starting. Commit interval 5 seconds
EXT3 FS on dm-4, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
ata3.00: exception Emask 0x0 SAct 0x2ef SErr 0x0 action 0x0
ata3.00: (irq_stat 0x00020002, device error via SDB FIS)
ata3.00: cmd 61/28:30:17:83:68/00:00:1f:00:00/40 tag 6 cdb 0x0 data
20480 out
res 51/04:30:17:83:68/50:04:1f:00:00/40 Emask 0x1 (device error)
ata3.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168
ata3.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168
ata3.00: configured for UDMA/100
ata3: EH complete
sd 2:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB)
sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
</quote>
daniel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: device error via SDB FIS
2007-06-30 17:10 device error via SDB FIS Daniel Schroeder
@ 2007-06-30 17:12 ` Justin Piszcz
2007-06-30 21:12 ` Daniel Schroeder
2007-06-30 21:22 ` Jeff Garzik
1 sibling, 1 reply; 8+ messages in thread
From: Justin Piszcz @ 2007-06-30 17:12 UTC (permalink / raw)
To: Daniel Schroeder; +Cc: linux-ide
Run smart tests yet?
1. smartctl -d ata -t short /dev/sda
2. smartctl -d ata -a /dev/sda (after few min)
also replace short with long
and then paste the output:
smartctl -d ata -a /dev/sda
There have been lots of reports on newegg concerning the HD501 DOA after
several hours.
Justin.
On Sat, 30 Jun 2007, Daniel Schroeder wrote:
> hello list,
>
> i do not know, what this could mean, but i have never seen it before.
> System is 2.6.22-rc6, sil3132, samsung hd501lj (new hd under 10 power on
> hours)
>
> time line:
> 1: power on (single esata enclosure)
> 2: system recognizes and configures the disk
> 3: mount disk
> 4: use disk
> 5: device error via SDB FIS
> 6: mount is still there, everything looks good except of this entry in logs
>
> <quote>
> ata3: exception Emask 0x10 SAct 0x0 SErr 0x80000 action 0x2 frozen
> ata3: (irq_stat 0x01140010, PHY RDY changed)
> ata3: soft resetting port
> ata3: SATA link down (SStatus 0 SControl 300)
> ata3: EH complete
> ata3: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata3: (irq_stat 0x00b00090, PHY RDY changed)
> ata3: soft resetting port
> ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168
> ata3.00: ATA-8: SAMSUNG HD501LJ, CR100-10, max UDMA7
> ata3.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
> ata3.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168
> ata3.00: configured for UDMA/100
> ata3: EH complete
> scsi 2:0:0:0: Direct-Access ATA SAMSUNG HD501LJ CR10 PQ: 0 ANSI: 5
> sd 2:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB)
> sd 2:0:0:0: [sdc] Write Protect is off
> sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
> sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support
> DPO or FUA
> sd 2:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB)
> sd 2:0:0:0: [sdc] Write Protect is off
> sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
> sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support
> DPO or FUA
> sdc: sdc1
> sd 2:0:0:0: [sdc] Attached SCSI disk
> sd 2:0:0:0: Attached scsi generic sg2 type 0
> kjournald starting. Commit interval 5 seconds
> EXT3 FS on dm-4, internal journal
> EXT3-fs: mounted filesystem with ordered data mode.
> ata3.00: exception Emask 0x0 SAct 0x2ef SErr 0x0 action 0x0
> ata3.00: (irq_stat 0x00020002, device error via SDB FIS)
> ata3.00: cmd 61/28:30:17:83:68/00:00:1f:00:00/40 tag 6 cdb 0x0 data 20480 out
> res 51/04:30:17:83:68/50:04:1f:00:00/40 Emask 0x1 (device error)
> ata3.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168
> ata3.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168
> ata3.00: configured for UDMA/100
> ata3: EH complete
> sd 2:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB)
> sd 2:0:0:0: [sdc] Write Protect is off
> sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
> sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support
> DPO or FUA
> </quote>
>
> daniel
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: device error via SDB FIS
2007-06-30 17:12 ` Justin Piszcz
@ 2007-06-30 21:12 ` Daniel Schroeder
2007-06-30 21:14 ` Justin Piszcz
0 siblings, 1 reply; 8+ messages in thread
From: Daniel Schroeder @ 2007-06-30 21:12 UTC (permalink / raw)
To: Justin Piszcz; +Cc: linux-ide
Justin Piszcz wrote:
> Run smart tests yet?
>
> 1. smartctl -d ata -t short /dev/sda
> 2. smartctl -d ata -a /dev/sda (after few min)
>
> also replace short with long
>
> and then paste the output:
>
> smartctl -d ata -a /dev/sda
>
<smartctl>
smartctl -a -d ata /dev/sdc
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 HD501LJ
Serial Number: S0MUJ1GP506675
Firmware Version: CR100-10
User Capacity: 500,107,862,016 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: Sat Jun 30 23:11:34 2007 CEST
==> 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: (8633) 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: ( 147) 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 - 7808
4 Start_Stop_Count 0x0032 100 100 000 Old_age
Always - 9
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 253 253 000 Old_age
Always - 8
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 - 6
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 060 055 000 Old_age Always
- 40
194 Temperature_Celsius 0x0022 118 103 000 Old_age Always
- 40
195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always
- 615567200
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 253 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
No Errors Logged
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining
LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed without error 00% 6
-
# 2 Short offline Completed without error 00% 4
-
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.
</smartctl>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: device error via SDB FIS
2007-06-30 21:12 ` Daniel Schroeder
@ 2007-06-30 21:14 ` Justin Piszcz
0 siblings, 0 replies; 8+ messages in thread
From: Justin Piszcz @ 2007-06-30 21:14 UTC (permalink / raw)
To: Daniel Schroeder; +Cc: linux-ide
On Sat, 30 Jun 2007, Daniel Schroeder wrote:
> Justin Piszcz wrote:
>> Run smart tests yet?
>>
>> 1. smartctl -d ata -t short /dev/sda
>> 2. smartctl -d ata -a /dev/sda (after few min)
>>
>> also replace short with long
>>
>> and then paste the output:
>>
>> smartctl -d ata -a /dev/sda
>>
>
> <smartctl>
> smartctl -a -d ata /dev/sdc
>
Your stats look fine, there have been _A LOT_ of SATA driver changes
lately, I would try different kernels, up to the latest 2.6.22-rcX also
try the drive on a different chipset as well.
Justin.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: device error via SDB FIS
2007-06-30 17:10 device error via SDB FIS Daniel Schroeder
2007-06-30 17:12 ` Justin Piszcz
@ 2007-06-30 21:22 ` Jeff Garzik
2007-06-30 21:33 ` Justin Piszcz
2007-06-30 21:42 ` Daniel Schroeder
1 sibling, 2 replies; 8+ messages in thread
From: Jeff Garzik @ 2007-06-30 21:22 UTC (permalink / raw)
To: Daniel Schroeder; +Cc: linux-ide
Daniel Schroeder wrote:
> hello list,
>
> i do not know, what this could mean, but i have never seen it before.
> System is 2.6.22-rc6, sil3132, samsung hd501lj (new hd under 10 power on
> hours)
>
> time line:
> 1: power on (single esata enclosure)
> 2: system recognizes and configures the disk
> 3: mount disk
> 4: use disk
> 5: device error via SDB FIS
> 6: mount is still there, everything looks good except of this entry in logs
>
> <quote>
> ata3: exception Emask 0x10 SAct 0x0 SErr 0x80000 action 0x2 frozen
> ata3: (irq_stat 0x01140010, PHY RDY changed)
> ata3: soft resetting port
> ata3: SATA link down (SStatus 0 SControl 300)
> ata3: EH complete
> ata3: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata3: (irq_stat 0x00b00090, PHY RDY changed)
> ata3: soft resetting port
> ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> ata3.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168
> ata3.00: ATA-8: SAMSUNG HD501LJ, CR100-10, max UDMA7
> ata3.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
> ata3.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168
> ata3.00: configured for UDMA/100
> ata3: EH complete
> scsi 2:0:0:0: Direct-Access ATA SAMSUNG HD501LJ CR10 PQ: 0
> ANSI: 5
> sd 2:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB)
> sd 2:0:0:0: [sdc] Write Protect is off
> sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
> sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA
> sd 2:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB)
> sd 2:0:0:0: [sdc] Write Protect is off
> sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
> sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't
> support DPO or FUA
> sdc: sdc1
> sd 2:0:0:0: [sdc] Attached SCSI disk
> sd 2:0:0:0: Attached scsi generic sg2 type 0
> kjournald starting. Commit interval 5 seconds
> EXT3 FS on dm-4, internal journal
> EXT3-fs: mounted filesystem with ordered data mode.
> ata3.00: exception Emask 0x0 SAct 0x2ef SErr 0x0 action 0x0
> ata3.00: (irq_stat 0x00020002, device error via SDB FIS)
> ata3.00: cmd 61/28:30:17:83:68/00:00:1f:00:00/40 tag 6 cdb 0x0 data
> 20480 out
> res 51/04:30:17:83:68/50:04:1f:00:00/40 Emask 0x1 (device error)
Command 0x61 is FPDMA WRITE (NCQ WRITE).
Error 0x04 is 'command aborted'.
Not much the driver can do but follow what the device is telling us...
If you disable NCQ, presumably this should go away.
Jeff
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: device error via SDB FIS
2007-06-30 21:22 ` Jeff Garzik
@ 2007-06-30 21:33 ` Justin Piszcz
2007-06-30 21:42 ` Daniel Schroeder
1 sibling, 0 replies; 8+ messages in thread
From: Justin Piszcz @ 2007-06-30 21:33 UTC (permalink / raw)
To: Jeff Garzik; +Cc: Daniel Schroeder, linux-ide
On Sat, 30 Jun 2007, Jeff Garzik wrote:
> Daniel Schroeder wrote:
>> hello list,
>>
>> i do not know, what this could mean, but i have never seen it before.
>> System is 2.6.22-rc6, sil3132, samsung hd501lj (new hd under 10 power on
>> hours)
>>
>> time line:
>> 1: power on (single esata enclosure)
>> 2: system recognizes and configures the disk
>> 3: mount disk
>> 4: use disk
>> 5: device error via SDB FIS
>> 6: mount is still there, everything looks good except of this entry in logs
>>
>> <quote>
>> ata3: exception Emask 0x10 SAct 0x0 SErr 0x80000 action 0x2 frozen
>> ata3: (irq_stat 0x01140010, PHY RDY changed)
>> ata3: soft resetting port
>> ata3: SATA link down (SStatus 0 SControl 300)
>> ata3: EH complete
>> ata3: exception Emask 0x10 SAct 0x0 SErr 0x0 action 0x2 frozen
>> ata3: (irq_stat 0x00b00090, PHY RDY changed)
>> ata3: soft resetting port
>> ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
>> ata3.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168
>> ata3.00: ATA-8: SAMSUNG HD501LJ, CR100-10, max UDMA7
>> ata3.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
>> ata3.00: ata_hpa_resize 1: sectors = 976773168, hpa_sectors = 976773168
>> ata3.00: configured for UDMA/100
>> ata3: EH complete
>> scsi 2:0:0:0: Direct-Access ATA SAMSUNG HD501LJ CR10 PQ: 0 ANSI:
>> 5
>> sd 2:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB)
>> sd 2:0:0:0: [sdc] Write Protect is off
>> sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
>> sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't
>> support DPO or FUA
>> sd 2:0:0:0: [sdc] 976773168 512-byte hardware sectors (500108 MB)
>> sd 2:0:0:0: [sdc] Write Protect is off
>> sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00
>> sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't
>> support DPO or FUA
>> sdc: sdc1
>> sd 2:0:0:0: [sdc] Attached SCSI disk
>> sd 2:0:0:0: Attached scsi generic sg2 type 0
>> kjournald starting. Commit interval 5 seconds
>> EXT3 FS on dm-4, internal journal
>> EXT3-fs: mounted filesystem with ordered data mode.
>> ata3.00: exception Emask 0x0 SAct 0x2ef SErr 0x0 action 0x0
>> ata3.00: (irq_stat 0x00020002, device error via SDB FIS)
>> ata3.00: cmd 61/28:30:17:83:68/00:00:1f:00:00/40 tag 6 cdb 0x0 data 20480
>> out
>> res 51/04:30:17:83:68/50:04:1f:00:00/40 Emask 0x1 (device error)
>
> Command 0x61 is FPDMA WRITE (NCQ WRITE).
>
> Error 0x04 is 'command aborted'.
>
> Not much the driver can do but follow what the device is telling us...
>
> If you disable NCQ, presumably this should go away.
>
> Jeff
>
To do that:
echo 1 > /sys/block/sda/device/queue_depth
Or jumper your HDD to turn off NCQ/3.0Gbps (limit to 1.5) s and see if
that fixes it.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: device error via SDB FIS
2007-06-30 21:22 ` Jeff Garzik
2007-06-30 21:33 ` Justin Piszcz
@ 2007-06-30 21:42 ` Daniel Schroeder
2007-06-30 21:46 ` Jeff Garzik
1 sibling, 1 reply; 8+ messages in thread
From: Daniel Schroeder @ 2007-06-30 21:42 UTC (permalink / raw)
To: Jeff Garzik; +Cc: linux-ide
>> ata3.00: exception Emask 0x0 SAct 0x2ef SErr 0x0 action 0x0
>> ata3.00: (irq_stat 0x00020002, device error via SDB FIS)
>> ata3.00: cmd 61/28:30:17:83:68/00:00:1f:00:00/40 tag 6 cdb 0x0 data
>> 20480 out
>> res 51/04:30:17:83:68/50:04:1f:00:00/40 Emask 0x1 (device error)
>
> Command 0x61 is FPDMA WRITE (NCQ WRITE).
>
> Error 0x04 is 'command aborted'.
>
> Not much the driver can do but follow what the device is telling us...
>
> If you disable NCQ, presumably this should go away.
>
> Jeff
>
>
>
thanks for your explanation, i will monitor this drive and disable ncq
if it happens again
daniel
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: device error via SDB FIS
2007-06-30 21:42 ` Daniel Schroeder
@ 2007-06-30 21:46 ` Jeff Garzik
0 siblings, 0 replies; 8+ messages in thread
From: Jeff Garzik @ 2007-06-30 21:46 UTC (permalink / raw)
To: Daniel Schroeder; +Cc: linux-ide
Daniel Schroeder wrote:
>
>>> ata3.00: exception Emask 0x0 SAct 0x2ef SErr 0x0 action 0x0
>>> ata3.00: (irq_stat 0x00020002, device error via SDB FIS)
>>> ata3.00: cmd 61/28:30:17:83:68/00:00:1f:00:00/40 tag 6 cdb 0x0 data
>>> 20480 out
>>> res 51/04:30:17:83:68/50:04:1f:00:00/40 Emask 0x1 (device error)
>>
>> Command 0x61 is FPDMA WRITE (NCQ WRITE).
>>
>> Error 0x04 is 'command aborted'.
>>
>> Not much the driver can do but follow what the device is telling us...
>>
>> If you disable NCQ, presumably this should go away.
> thanks for your explanation, i will monitor this drive and disable ncq
> if it happens again
I should have added: given your report, it sounds like the error
handling code took appropriate action for your error. It should
continue transferring data (though perhaps not in NCQ mode anymore).
HOPEFULLY all you see is a nasty message when the drive complains :)
If that is not the case, if you are seeing data transfer suddenly cease
(or worse, data corruption) please do speak up...
Jeff
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2007-06-30 21:46 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-06-30 17:10 device error via SDB FIS Daniel Schroeder
2007-06-30 17:12 ` Justin Piszcz
2007-06-30 21:12 ` Daniel Schroeder
2007-06-30 21:14 ` Justin Piszcz
2007-06-30 21:22 ` Jeff Garzik
2007-06-30 21:33 ` Justin Piszcz
2007-06-30 21:42 ` Daniel Schroeder
2007-06-30 21:46 ` Jeff Garzik
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).