AHCI + ST3160023AS + NCQ problems

AHCI + ST3160023AS + NCQ problems

[Matheus Izvekov]

Seagate drive ST3160023AS is correctly detected as supporting NCQ, but
when its used with moderate loads, libata keeps throwing error
messages until it finally decides to disable NCQ on it.
this is the controller:

00:1f.2 SATA controller: Intel Corporation 82801GR/GH (ICH7 Family)
SATA AHCI Controller (rev 01) (prog-if 01 [AHCI 1.0])
        Subsystem: Intel Corporation Unknown device 5842
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium
>TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin B routed to IRQ 379
        Region 0: I/O ports at 30c8 [size=8]
        Region 1: I/O ports at 30e4 [size=4]
        Region 2: I/O ports at 30c0 [size=8]
        Region 3: I/O ports at 30e0 [size=4]
        Region 4: I/O ports at 30a0 [size=16]
        Region 5: Memory at 29304000 (32-bit, non-prefetchable) [size=1K]
        Capabilities: [80] Message Signalled Interrupts: Mask- 64bit-
Queue=0/0 Enable+
                Address: fee0f00c  Data: 4181
        Capabilities: [70] Power Management version 2
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot+,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-

relevant kmsg output:

ahci 0000:00:1f.2: version 2.3
ACPI: PCI Interrupt 0000:00:1f.2[B] -> GSI 19 (level, low) -> IRQ 19
ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 4 ports 3 Gbps 0xf impl SATA mode
ahci 0000:00:1f.2: flags: 64bit ncq led clo pio slum part
PCI: Setting latency timer of device 0000:00:1f.2 to 64
scsi0 : ahci
scsi1 : ahci
scsi2 : ahci
scsi3 : ahci
ata1: SATA max UDMA/133 cmd 0xffffc20000024100 ctl 0x0000000000000000
bmdma 0x0000000000000000 irq 379
ata2: SATA max UDMA/133 cmd 0xffffc20000024180 ctl 0x0000000000000000
bmdma 0x0000000000000000 irq 379
ata3: SATA max UDMA/133 cmd 0xffffc20000024200 ctl 0x0000000000000000
bmdma 0x0000000000000000 irq 379
ata4: SATA max UDMA/133 cmd 0xffffc20000024280 ctl 0x0000000000000000
bmdma 0x0000000000000000 irq 379
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: ATA-6: ST3120026AS, 3.18, max UDMA/133
ata1.00: 234441648 sectors, multi 16: LBA48
ata1.00: configured for UDMA/133
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: ATA-7: ST3320620AS, 3.AAK, max UDMA/133
ata2.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata2.00: configured for UDMA/133
ata3: SATA link down (SStatus 0 SControl 300)
ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata4.00: ATA-6: ST3160023AS, 3.42, max UDMA/133
ata4.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 31/32)
ata4.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access     ATA      ST3120026AS      3.18 PQ: 0 ANSI: 5
sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 MB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
 sda: sda1 sda2 sda3
sd 0:0:0:0: [sda] Attached SCSI disk
scsi 1:0:0:0: Direct-Access     ATA      ST3320620AS      3.AA PQ: 0 ANSI: 5
sd 1:0:0:0: [sdb] 625142448 512-byte hardware sectors (320073 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 1:0:0:0: [sdb] 625142448 512-byte hardware sectors (320073 MB)
sd 1:0:0:0: [sdb] Write Protect is off
sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
 sdb: unknown partition table
sd 1:0:0:0: [sdb] Attached SCSI disk
scsi 3:0:0:0: Direct-Access     ATA      ST3160023AS      3.42 PQ: 0 ANSI: 5
sd 3:0:0:0: [sdc] 312581808 512-byte hardware sectors (160042 MB)
sd 3:0:0:0: [sdc] Write Protect is off
sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
sd 3:0:0:0: [sdc] 312581808 512-byte hardware sectors (160042 MB)
sd 3:0:0:0: [sdc] Write Protect is off
sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
 sdc: unknown partition table
sd 3:0:0:0: [sdc] Attached SCSI disk

.....

ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x2 frozen
ata4.00: cmd 61/1f:00:f4:14:52/00:00:09:00:00/40 tag 0 cdb 0x0 data 15872 out
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata4: soft resetting port
ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata4.00: configured for UDMA/133
ata4: EH complete
sd 3:0:0:0: [sdc] 312581808 512-byte hardware sectors (160042 MB)
sd 3:0:0:0: [sdc] Write Protect is off
sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x2 frozen
ata4.00: cmd 61/40:00:e1:52:52/00:00:09:00:00/40 tag 0 cdb 0x0 data 32768 out
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata4: soft resetting port
ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata4.00: configured for UDMA/133
ata4: EH complete
sd 3:0:0:0: [sdc] 312581808 512-byte hardware sectors (160042 MB)
sd 3:0:0:0: [sdc] Write Protect is off
sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x2 frozen
ata4.00: cmd 61/19:00:4e:78:52/00:00:09:00:00/40 tag 0 cdb 0x0 data 12800 out
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata4: soft resetting port
ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata4.00: configured for UDMA/133
ata4: EH complete
sd 3:0:0:0: [sdc] 312581808 512-byte hardware sectors (160042 MB)
sd 3:0:0:0: [sdc] Write Protect is off
sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
ata4.00: NCQ disabled due to excessive errors
ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x2 frozen
ata4.00: cmd 61/35:00:27:a2:52/00:00:09:00:00/40 tag 0 cdb 0x0 data 27136 out
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
ata4: soft resetting port
ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata4.00: configured for UDMA/133
ata4: EH complete
sd 3:0:0:0: [sdc] 312581808 512-byte hardware sectors (160042 MB)
sd 3:0:0:0: [sdc] Write Protect is off
sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA

Also, ST3320620AS is SATA2 according to the manufacturer, but i only
see libata setting the link to 1.5gbps.

Re: AHCI + ST3160023AS + NCQ problems

[Michael Tokarev]

Matheus Izvekov wrote:
> Seagate drive ST3160023AS is correctly detected as supporting NCQ, but
> when its used with moderate loads, libata keeps throwing error
> messages until it finally decides to disable NCQ on it.
[]
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
> ata1.00: ATA-6: ST3120026AS, 3.18, max UDMA/133

By the way, did you forget to remove a jumper on the drive
(the only jumper installed by default) that limits drive
usage to SATAI?

[]
> ata4.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x2 frozen
> ata4.00: cmd 61/1f:00:f4:14:52/00:00:09:00:00/40 tag 0 cdb 0x0 data 15872 out
>          res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata4: soft resetting port
> ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)

..etc.   Try again without the jumper?  Note that NCQ is NOT supported
in SATAI mode, or there were some pre-standard implementations of it.
In SATAII, NCQ is standard (well... more or less anyway ;)

/mjt

Re: AHCI + ST3160023AS + NCQ problems

[Eric D. Mudama]

On 10/30/07, Michael Tokarev <mjt@tls.msk.ru> wrote:
> By the way, did you forget to remove a jumper on the drive
> (the only jumper installed by default) that limits drive
> usage to SATAI?
...
> ..etc.   Try again without the jumper?  Note that NCQ is NOT supported
> in SATAI mode, or there were some pre-standard implementations of it.
> In SATAII, NCQ is standard (well... more or less anyway ;)

Huh?

To my knowledge, the jumper should only limit the bus rate to
1.5Gbit/s, for compatibility with one or more chipsets.  It shouldn't
affect the command set supported by the device.

Re: AHCI + ST3160023AS + NCQ problems

[Michael Tokarev]

Eric D. Mudama wrote:
> On 10/30/07, Michael Tokarev <mjt@tls.msk.ru> wrote:
>> By the way, did you forget to remove a jumper on the drive
>> (the only jumper installed by default) that limits drive
>> usage to SATAI?
> ...
>> ..etc.   Try again without the jumper?  Note that NCQ is NOT supported
>> in SATAI mode, or there were some pre-standard implementations of it.
>> In SATAII, NCQ is standard (well... more or less anyway ;)
> 
> Huh?
> 
> To my knowledge, the jumper should only limit the bus rate to
> 1.5Gbit/s, for compatibility with one or more chipsets.  It shouldn't
> affect the command set supported by the device.

The thing is that I don't know.  I had some other probs with seagate
sata drives when the jumper was there.  So I learned a lesson -
always remove the jumper before using their drives.  I don't want
to test which other restrictions this and other drive families
apply when jumpered... ;)

/mjt

Re: AHCI + ST3160023AS + NCQ problems

[Matheus Izvekov]

On 10/30/07, Michael Tokarev <mjt@tls.msk.ru> wrote:
> Eric D. Mudama wrote:
> > On 10/30/07, Michael Tokarev <mjt@tls.msk.ru> wrote:
> >> By the way, did you forget to remove a jumper on the drive
> >> (the only jumper installed by default) that limits drive
> >> usage to SATAI?
> > ...
> >> ..etc.   Try again without the jumper?  Note that NCQ is NOT supported
> >> in SATAI mode, or there were some pre-standard implementations of it.
> >> In SATAII, NCQ is standard (well... more or less anyway ;)
> >
> > Huh?
> >
> > To my knowledge, the jumper should only limit the bus rate to
> > 1.5Gbit/s, for compatibility with one or more chipsets.  It shouldn't
> > affect the command set supported by the device.
>
> The thing is that I don't know.  I had some other probs with seagate
> sata drives when the jumper was there.  So I learned a lesson -
> always remove the jumper before using their drives.  I don't want
> to test which other restrictions this and other drive families
> apply when jumpered... ;)
>
> /mjt
>

Indeed removing the jumper of sdb made it be recognised as SATA2. But
sdc, what the problem is really about, is neither SATA2, not has any
jumper whatsoever. but both the manufacturer and libata claim it
supports NCQ.

Re: AHCI + ST3160023AS + NCQ problems

[Matheus Izvekov]

On 10/30/07, Matheus Izvekov <mizvekov@gmail.com> wrote:
> On 10/30/07, Michael Tokarev <mjt@tls.msk.ru> wrote:
> > Eric D. Mudama wrote:
> > > On 10/30/07, Michael Tokarev <mjt@tls.msk.ru> wrote:
> > >> By the way, did you forget to remove a jumper on the drive
> > >> (the only jumper installed by default) that limits drive
> > >> usage to SATAI?
> > > ...
> > >> ..etc.   Try again without the jumper?  Note that NCQ is NOT supported
> > >> in SATAI mode, or there were some pre-standard implementations of it.
> > >> In SATAII, NCQ is standard (well... more or less anyway ;)
> > >
> > > Huh?
> > >
> > > To my knowledge, the jumper should only limit the bus rate to
> > > 1.5Gbit/s, for compatibility with one or more chipsets.  It shouldn't
> > > affect the command set supported by the device.
> >
> > The thing is that I don't know.  I had some other probs with seagate
> > sata drives when the jumper was there.  So I learned a lesson -
> > always remove the jumper before using their drives.  I don't want
> > to test which other restrictions this and other drive families
> > apply when jumpered... ;)
> >
> > /mjt
> >
>
> Indeed removing the jumper of sdb made it be recognised as SATA2. But
> sdc, what the problem is really about, is neither SATA2, not has any
> jumper whatsoever. but both the manufacturer and libata claim it
> supports NCQ.
>

Anything i could do to help debug this? or perhaps it makes more sense
to just blacklist NCQ for this particular drive?

Re: AHCI + ST3160023AS + NCQ problems

[Tejun Heo]

Matheus Izvekov wrote:
>> Indeed removing the jumper of sdb made it be recognised as SATA2. But
>> sdc, what the problem is really about, is neither SATA2, not has any
>> jumper whatsoever. but both the manufacturer and libata claim it
>> supports NCQ.
>>
> 
> Anything i could do to help debug this? or perhaps it makes more sense
> to just blacklist NCQ for this particular drive?

Timeouts on modern SATA disks usually indicate hardware problem.

* unstable power supply (this is quite common)
* faulty cable or poorly seated connectors
* faulty drive or controller (seems rare)

Please apply common hardware debugging method - isolate problem by
changing configuration piece-by-piece and finding out to which component
the error actually belongs to.

-- 
tejun

Re: AHCI + ST3160023AS + NCQ problems

[Matheus Izvekov]

On Nov 12, 2007 1:04 AM, Tejun Heo <htejun@gmail.com> wrote:
> Matheus Izvekov wrote:
> >> Indeed removing the jumper of sdb made it be recognised as SATA2. But
> >> sdc, what the problem is really about, is neither SATA2, not has any
> >> jumper whatsoever. but both the manufacturer and libata claim it
> >> supports NCQ.
> >>
> >
> > Anything i could do to help debug this? or perhaps it makes more sense
> > to just blacklist NCQ for this particular drive?
>
> Timeouts on modern SATA disks usually indicate hardware problem.
>
> * unstable power supply (this is quite common)
> * faulty cable or poorly seated connectors
> * faulty drive or controller (seems rare)
>
> Please apply common hardware debugging method - isolate problem by
> changing configuration piece-by-piece and finding out to which component
> the error actually belongs to.
>
> --
> tejun
>

Tried everything, short of trying the hd on another controller, but
the problem persists.

Re: AHCI + ST3160023AS + NCQ problems

[Tejun Heo]

Matheus Izvekov wrote:
>> * unstable power supply (this is quite common)
>> * faulty cable or poorly seated connectors
>> * faulty drive or controller (seems rare)
> 
> Tried everything, short of trying the hd on another controller, but
> the problem persists.

Weird, ICH7 + 7200.7 combination is very widely tested.  Can you please
post the result of "hdparm -I /dev/sdX" and "smartctl -a /dev/sdX" where
sdX is the offending drive?  So, if you connect the drive to a different
port of the controller using a different cable, the problem follows the
drive, right?

Thanks.

-- 
tejun

Re: AHCI + ST3160023AS + NCQ problems

[Matheus Izvekov]

On Dec 7, 2007 9:51 PM, Tejun Heo <htejun@gmail.com> wrote:
> Matheus Izvekov wrote:
> >> * unstable power supply (this is quite common)
> >> * faulty cable or poorly seated connectors
> >> * faulty drive or controller (seems rare)
> >
> > Tried everything, short of trying the hd on another controller, but
> > the problem persists.
>
> Weird, ICH7 + 7200.7 combination is very widely tested.  Can you please
> post the result of "hdparm -I /dev/sdX" and "smartctl -a /dev/sdX" where
> sdX is the offending drive?  So, if you connect the drive to a different
> port of the controller using a different cable, the problem follows the
> drive, right?
>
> Thanks.
>
> --
> tejun
>

Yes it follows the drive. I have another drive which is quite similiar
to the offending one, but has no NCQ so the problem doesnt apply. i
have another that is sata2 (has ncq) and shows no problem.

/dev/sdb:

ATA device, with non-removable media
	Model Number:       ST3160023AS
	Serial Number:      5MT02XNY
	Firmware Revision:  3.42
Standards:
	Used: ATA/ATAPI-6 T13 1410D revision 2
	Supported: 6 5 4
Configuration:
	Logical		max	current
	cylinders	16383	16383
	heads		16	16
	sectors/track	63	63
	--
	CHS current addressable sectors:   16514064
	LBA    user addressable sectors:  268435455
	LBA48  user addressable sectors:  312581808
	device size with M = 1024*1024:      152627 MBytes
	device size with M = 1000*1000:      160041 MBytes (160 GB)
Capabilities:
	LBA, IORDY(can be disabled)
	Queue depth: 32
	Standby timer values: spec'd by Standard, no device specific minimum
	R/W multiple sector transfer: Max = 16	Current = 16
	Recommended acoustic management value: 254, current value: 0
	DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6
	     Cycle time: min=120ns recommended=120ns
	PIO: pio0 pio1 pio2 pio3 pio4
	     Cycle time: no flow control=240ns  IORDY flow control=120ns
Commands/features:
	Enabled	Supported:
	   *	SMART feature set
	    	Security Mode feature set
	   *	Power Management feature set
	   *	Write cache
	   *	Look-ahead
	   *	Host Protected Area feature set
	   *	WRITE_BUFFER command
	   *	READ_BUFFER command
	   *	DOWNLOAD_MICROCODE
	    	SET_MAX security extension
	   *	48-bit Address feature set
	   *	Device Configuration Overlay feature set
	   *	Mandatory FLUSH_CACHE
	   *	FLUSH_CACHE_EXT
	   *	SMART error logging
	   *	SMART self-test
	   *	SATA-I signaling speed (1.5Gb/s)
	   *	Native Command Queueing (NCQ)
Security:
	Master password revision code = 65534
		supported
	not	enabled
	not	locked
	not	frozen
	not	expired: security count
	not	supported: enhanced erase
Checksum: correct

smartctl version 5.37 [x86_64-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF INFORMATION SECTION ===
Model Family:     Seagate Barracuda 7200.7 and 7200.7 Plus family
Device Model:     ST3160023AS
Serial Number:    5MT02XNY
Firmware Version: 3.42
User Capacity:    160,041,885,696 bytes
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   6
ATA Standard is:  ATA/ATAPI-6 T13 1410D revision 2
Local Time is:    Fri Dec  7 22:36:15 2007 BRST
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:  (0x82)	Offline data collection activity
					was completed without error.
					Auto Offline Data Collection: Enabled.
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: 		 ( 430) 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.
					No General Purpose Logging support.
Short self-test routine
recommended polling time: 	 (   1) minutes.
Extended self-test routine
recommended polling time: 	 (  94) minutes.

SMART Attributes Data Structure revision number: 10
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   053   049   006    Pre-fail
Always       -       9124071
  3 Spin_Up_Time            0x0003   097   096   000    Pre-fail
Always       -       0
  4 Start_Stop_Count        0x0032   100   100   020    Old_age
Always       -       253
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail
Always       -       1
  7 Seek_Error_Rate         0x000f   087   060   030    Pre-fail
Always       -       576926517
  9 Power_On_Hours          0x0032   081   081   000    Old_age
Always       -       17263
 10 Spin_Retry_Count        0x0013   100   100   097    Pre-fail
Always       -       0
 12 Power_Cycle_Count       0x0032   100   100   020    Old_age
Always       -       329
194 Temperature_Celsius     0x0022   047   058   000    Old_age
Always       -       47 (Lifetime Min/Max 0/18)
195 Hardware_ECC_Recovered  0x001a   053   049   000    Old_age
Always       -       9124071
197 Current_Pending_Sector  0x0012   100   100   000    Old_age
Always       -       0
198 Offline_Uncorrectable   0x0010   100   100   000    Old_age
Offline      -       0
199 UDMA_CRC_Error_Count    0x003e   200   200   000    Old_age
Always       -       0
200 Multi_Zone_Error_Rate   0x0000   100   253   000    Old_age
Offline      -       0
202 TA_Increase_Count       0x0032   100   253   000    Old_age
Always       -       0

SMART Error Log Version: 1
No Errors Logged

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.

Re: AHCI + ST3160023AS + NCQ problems

[Tejun Heo]

Matheus Izvekov wrote:
> Yes it follows the drive. I have another drive which is quite similiar
> to the offending one, but has no NCQ so the problem doesnt apply. i
> have another that is sata2 (has ncq) and shows no problem.

Hmmm... Everything looks normal.  The problem is that there's currently
only one report and I can't tell whether your specific drive is faulty
or the model with the firmware version is faulty.

Ah... okay.  Another drive with the same firmware version is already
blacklisted, which makes the latter far more likely.  I'll create a
blacklist entry for your drive.

Thanks.

-- 
tejun