Sorry for starting a new thread, but I've deleted the messages from my
mail-box, and I'm sot sure it's the same problem as here:
http://lkml.org/lkml/2007/1/14/108
Today I've decided to try XFS... and just doing anything on it
(extracting a tarball, for example) make my SATA HD go crazy ;)
I don't remember to have seen this using Ext3.
[ 877.839920] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x2 frozen
[ 877.839929] ata1.00: cmd 61/02:00:64:98:98/00:00:00:00:00/40 tag 0 cdb 0x0 data 1024 out
[ 877.839931] res 40/00:00:00:4f:c2/00:00:00:4f:c2/00 Emask 0x4 (timeout)
[ 878.142367] ata1: soft resetting port
[ 878.351791] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 878.354384] ata1.00: configured for UDMA/133
[ 878.354392] ata1: EH complete
[ 878.355696] SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
[ 878.355716] sda: Write Protect is off
[ 878.355718] sda: Mode Sense: 00 3a 00 00
[ 878.355745] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
It takes nothing to reproduce it.
My hardware is:
00:00.0 Host bridge: Intel Corporation 82P965/G965 Memory Controller Hub (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82G965 Integrated Graphics Controller (rev 02)
00:03.0 Communication controller: Intel Corporation 82P965/G965 HECI Controller (rev 02)
00:19.0 Ethernet controller: Intel Corporation 82566DC Gigabit Network Connection (rev 02)
00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #4 (rev 02)
00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #5 (rev 02)
00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI #2 (rev 02)
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 3 (rev 02)
00:1c.3 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 4 (rev 02)
00:1c.4 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #3 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI #1 (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev f2)
00:1f.0 ISA bridge: Intel Corporation 82801HB/HR (ICH8/R) LPC Interface Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801HB (ICH8) 4 port SATA AHCI Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus Controller (rev 02)
02:00.0 IDE interface: Marvell Technology Group Ltd. Unknown device 6101 (rev b1)
06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
with a Seagate Barracurda 7200rpm 80GB HD
I've so far tested these kernels:
2.6.20-rc5 BAD
2.6.20-rc4 BAD
2.6.19 BAD
2.6.18 BAD
2.6.17 Good !
I'll start a git-bisection...
--
Paolo Ornati
Linux 2.6.20-rc5 on x86_64
On Sun, 21 Jan 2007 15:29:32 +0100
Paolo Ornati <[email protected]> wrote:
> Sorry for starting a new thread, but I've deleted the messages from my
> mail-box, and I'm sot sure it's the same problem as here:
> http://lkml.org/lkml/2007/1/14/108
>
> Today I've decided to try XFS... and just doing anything on it
> (extracting a tarball, for example) make my SATA HD go crazy ;)
>
> I don't remember to have seen this using Ext3.
>
> [ 877.839920] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action
> 0x2 frozen [ 877.839929] ata1.00: cmd
> 61/02:00:64:98:98/00:00:00:00:00/40 tag 0 cdb 0x0 data 1024 out
> [ 877.839931] res 40/00:00:00:4f:c2/00:00:00:4f:c2/00 Emask
> 0x4 (timeout) [ 878.142367] ata1: soft resetting port [ 878.351791]
> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 878.354384]
> ata1.00: configured for UDMA/133 [ 878.354392] ata1: EH complete
> [ 878.355696] SCSI device sda: 156301488 512-byte hdwr sectors
> (80026 MB) [ 878.355716] sda: Write Protect is off
> [ 878.355718] sda: Mode Sense: 00 3a 00 00
> [ 878.355745] SCSI device sda: write cache: enabled, read cache:
> enabled, doesn't support DPO or FUA
>
>
> It takes nothing to reproduce it.
>
> My hardware is:
>
> 00:00.0 Host bridge: Intel Corporation 82P965/G965 Memory Controller
> Hub (rev 02) 00:02.0 VGA compatible controller: Intel Corporation
> 82G965 Integrated Graphics Controller (rev 02) 00:03.0 Communication
> controller: Intel Corporation 82P965/G965 HECI Controller (rev 02)
> 00:19.0 Ethernet controller: Intel Corporation 82566DC Gigabit
> Network Connection (rev 02) 00:1a.0 USB Controller: Intel Corporation
> 82801H (ICH8 Family) USB UHCI #4 (rev 02) 00:1a.1 USB Controller:
> Intel Corporation 82801H (ICH8 Family) USB UHCI #5 (rev 02) 00:1a.7
> USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI #2
> (rev 02) 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family)
> HD Audio Controller (rev 02) 00:1c.0 PCI bridge: Intel Corporation
> 82801H (ICH8 Family) PCI Express Port 1 (rev 02) 00:1c.1 PCI bridge:
> Intel Corporation 82801H (ICH8 Family) PCI Express Port 2 (rev 02)
> 00:1c.2 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI
> Express Port 3 (rev 02) 00:1c.3 PCI bridge: Intel Corporation 82801H
> (ICH8 Family) PCI Express Port 4 (rev 02) 00:1c.4 PCI bridge: Intel
> Corporation 82801H (ICH8 Family) PCI Express Port 5 (rev 02) 00:1d.0
> USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI #1
> (rev 02) 00:1d.1 USB Controller: Intel Corporation 82801H (ICH8
> Family) USB UHCI #2 (rev 02) 00:1d.2 USB Controller: Intel
> Corporation 82801H (ICH8 Family) USB UHCI #3 (rev 02) 00:1d.7 USB
> Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI #1 (rev
> 02) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev f2)
> 00:1f.0 ISA bridge: Intel Corporation 82801HB/HR (ICH8/R) LPC
> Interface Controller (rev 02) 00:1f.2 SATA controller: Intel
> Corporation 82801HB (ICH8) 4 port SATA AHCI Controller (rev 02)
> 00:1f.3 SMBus: Intel Corporation 82801H (ICH8 Family) SMBus
> Controller (rev 02) 02:00.0 IDE interface: Marvell Technology Group
> Ltd. Unknown device 6101 (rev b1) 06:00.0 Ethernet controller:
> Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
>
>
> with a Seagate Barracurda 7200rpm 80GB HD
>
>
> I've so far tested these kernels:
> 2.6.20-rc5 BAD
> 2.6.20-rc4 BAD
> 2.6.19 BAD
> 2.6.18 BAD
> 2.6.17 Good !
>
> I'll start a git-bisection...
>
git-bisect points to this commit:
----------------------------------------------
12fad3f965830d71f6454f02b2af002a64cec4d3 is first bad commit
commit 12fad3f965830d71f6454f02b2af002a64cec4d3
Author: Tejun Heo <[email protected]>
Date: Mon May 15 21:03:55 2006 +0900
[PATCH] ahci: implement NCQ suppport
Implement NCQ support.
Original implementation is from Jens Axboe.
Signed-off-by: Tejun Heo <[email protected]>
:040000 040000 be681c4b21f34da5241e72c97c6695d735e90771
3557b2db9d7c3d48a0408137b455ce12931bb18d M drivers
----------------------------------------------
Problem just reproduced on 2.6.20-rc5:
[ 431.374421] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x2 frozen
[ 431.374430] ata1.00: cmd 61/40:00:fe:aa:98/00:00:00:00:00/40 tag 0 cdb 0x0 data 32768 out
[ 431.374432] res 40/00:00:9e:9c:bd/00:00:01:00:00/40 Emask 0x4 (timeout)
[ 431.677154] ata1: soft resetting port
[ 431.886700] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 431.889277] ata1.00: configured for UDMA/133
[ 431.889285] ata1: EH complete
[ 431.890781] SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
[ 431.890854] sda: Write Protect is off
[ 431.890858] sda: Mode Sense: 00 3a 00 00
[ 431.890903] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 450.800490] XFS mounting filesystem sda1
[ 450.853731] Ending clean XFS mount for filesystem: sda1
[ 481.131888] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x2 frozen
[ 481.131896] ata1.00: cmd 61/40:00:46:af:98/00:00:00:00:00/40 tag 0 cdb 0x0 data 32768 out
[ 481.131898] res 40/00:00:9e:9c:bd/00:00:01:00:00/40 Emask 0x4 (timeout)
[ 481.436015] ata1: soft resetting port
[ 481.645237] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[ 481.647825] ata1.00: configured for UDMA/133
[ 481.647834] ata1: EH complete
[ 481.649252] SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
[ 481.649295] sda: Write Protect is off
[ 481.649298] sda: Mode Sense: 00 3a 00 00
[ 481.649358] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Full dmesg attached.
If you need more info, just ask.
--
Paolo Ornati
Linux 2.6.20-rc5 on x86_64
Paolo Ornati wrote:
> On Sun, 21 Jan 2007 15:29:32 +0100
> Paolo Ornati <[email protected]> wrote:
>
>> Sorry for starting a new thread, but I've deleted the messages from my
>> mail-box, and I'm sot sure it's the same problem as here:
>> http://lkml.org/lkml/2007/1/14/108
>>
>> Today I've decided to try XFS... and just doing anything on it
>> (extracting a tarball, for example) make my SATA HD go crazy ;)
>>
>> I don't remember to have seen this using Ext3.
>>
>> [ 877.839920] ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action
>> 0x2 frozen [ 877.839929] ata1.00: cmd
>> 61/02:00:64:98:98/00:00:00:00:00/40 tag 0 cdb 0x0 data 1024 out
>> [ 877.839931] res 40/00:00:00:4f:c2/00:00:00:4f:c2/00 Emask
>> 0x4 (timeout) [ 878.142367] ata1: soft resetting port [ 878.351791]
>> ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 878.354384]
>> ata1.00: configured for UDMA/133 [ 878.354392] ata1: EH complete
>> [ 878.355696] SCSI device sda: 156301488 512-byte hdwr sectors
>> (80026 MB) [ 878.355716] sda: Write Protect is off
>> [ 878.355718] sda: Mode Sense: 00 3a 00 00
>> [ 878.355745] SCSI device sda: write cache: enabled, read cache:
>> enabled, doesn't support DPO or FUA
>>
>>
>> It takes nothing to reproduce it.
..
> git-bisect points to this commit:
>
> ----------------------------------------------
>
> 12fad3f965830d71f6454f02b2af002a64cec4d3 is first bad commit
> commit 12fad3f965830d71f6454f02b2af002a64cec4d3
> Author: Tejun Heo <[email protected]>
> Date: Mon May 15 21:03:55 2006 +0900
>
> [PATCH] ahci: implement NCQ suppport
>
> Implement NCQ support.
It looks like what you're getting is an actual NCQ write timing out.
That makes the bisect result not very interesting since obviously it
wouldn't have issued any NCQ writes before NCQ support was implemented.
Seeing as how it's also an entirely different driver I imagine it's a
different problem than what I've been looking at.
Maybe that drive just has some issues with NCQ? I would be surprised at
that with a Seagate though..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [email protected]
Home Page: http://www.roberthancock.com/
On Sun, 21 Jan 2007 11:32:02 -0600
Robert Hancock <[email protected]> wrote:
> It looks like what you're getting is an actual NCQ write timing out.
> That makes the bisect result not very interesting since obviously it
> wouldn't have issued any NCQ writes before NCQ support was
> implemented. Seeing as how it's also an entirely different driver I
> imagine it's a different problem than what I've been looking at.
>
> Maybe that drive just has some issues with NCQ? I would be surprised
> at that with a Seagate though..
I don't know. It's a two years old ST380817AS.
# smartctl -a -d ata /dev/sda
smartctl version 5.36 [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: ST380817AS
Serial Number: 4MR08EK8
Firmware Version: 3.42
User Capacity: 80,026,361,856 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: Sun Jan 21 20:15:40 2007 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (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: ( 47) 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 059 049 006 Pre-fail Always - 215927244
3 Spin_Up_Time 0x0003 098 098 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 098 098 020 Old_age Always - 2182
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 083 060 030 Pre-fail Always - 204305750
9 Power_On_Hours 0x0032 097 097 000 Old_age Always - 3494
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 098 098 020 Old_age Always - 2541
194 Temperature_Celsius 0x0022 024 040 000 Old_age Always - 24 (Lifetime Min/Max 0/15)
195 Hardware_ECC_Recovered 0x001a 059 049 000 Old_age Always - 215927244
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 1
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 1
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
ATA Error Count: 12 (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 12 occurred at disk power-on lifetime: 2516 hours (104 days + 20 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 0d 5b 9d 34 e1 Error: UNC 13 sectors at LBA = 0x01349d5b = 20225371
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 4e 9d 34 e1 00 00:03:03.851 READ DMA
c8 00 00 4e 9d 34 e1 00 00:03:03.848 READ DMA
c8 00 00 4e 9d 34 e1 00 00:03:03.846 READ DMA
c8 00 00 4e 9d 34 e1 00 00:03:03.843 READ DMA
c8 00 00 4e 9d 34 e1 00 00:03:03.839 READ DMA
Error 11 occurred at disk power-on lifetime: 2516 hours (104 days + 20 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 0d 5b 9d 34 e1 Error: UNC 13 sectors at LBA = 0x01349d5b = 20225371
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 4e 9d 34 e1 00 00:03:03.851 READ DMA
c8 00 00 4e 9d 34 e1 00 00:03:03.848 READ DMA
c8 00 00 4e 9d 34 e1 00 00:03:03.846 READ DMA
c8 00 00 4e 9d 34 e1 00 00:03:03.843 READ DMA
c8 00 00 4e 9d 34 e1 00 00:03:03.839 READ DMA
Error 10 occurred at disk power-on lifetime: 2516 hours (104 days + 20 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 0d 5b 9d 34 e1 Error: UNC 13 sectors at LBA = 0x01349d5b = 20225371
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 4e 9d 34 e1 00 00:03:03.851 READ DMA
c8 00 00 4e 9d 34 e1 00 00:03:03.848 READ DMA
c8 00 00 4e 9d 34 e1 00 00:03:03.846 READ DMA
c8 00 00 4e 9d 34 e1 00 00:03:03.843 READ DMA
c8 00 00 16 9c 34 e1 00 00:03:03.839 READ DMA
Error 9 occurred at disk power-on lifetime: 2516 hours (104 days + 20 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 0d 5b 9d 34 e1 Error: UNC 13 sectors at LBA = 0x01349d5b = 20225371
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 4e 9d 34 e1 00 00:03:03.851 READ DMA
c8 00 00 4e 9d 34 e1 00 00:03:03.848 READ DMA
c8 00 00 4e 9d 34 e1 00 00:03:03.846 READ DMA
c8 00 00 16 9c 34 e1 00 00:03:03.843 READ DMA
c8 00 00 0e 9b 34 e1 00 00:03:03.839 READ DMA
Error 8 occurred at disk power-on lifetime: 2516 hours (104 days + 20 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 0d 5b 9d 34 e1 Error: UNC 13 sectors at LBA = 0x01349d5b = 20225371
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 4e 9d 34 e1 00 00:03:03.851 READ DMA
c8 00 00 4e 9d 34 e1 00 00:03:03.848 READ DMA
c8 00 00 16 9c 34 e1 00 00:03:03.846 READ DMA
c8 00 00 0e 9b 34 e1 00 00:03:03.843 READ DMA
c8 00 00 8e 99 34 e1 00 00:03:03.839 READ DMA
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.
--
Paolo Ornati
Linux 2.6.20-rc5 on x86_64
On Sunday, 21. January 2007 20:25, Paolo Ornati wrote:
> On Sun, 21 Jan 2007 11:32:02 -0600
> Robert Hancock <[email protected]> wrote:
>
> > It looks like what you're getting is an actual NCQ write timing out.
> > That makes the bisect result not very interesting since obviously it
> > wouldn't have issued any NCQ writes before NCQ support was
> > implemented. Seeing as how it's also an entirely different driver I
> > imagine it's a different problem than what I've been looking at.
> >
> > Maybe that drive just has some issues with NCQ? I would be surprised
> > at that with a Seagate though..
>
> I don't know. It's a two years old ST380817AS.
>
>
> # smartctl -a -d ata /dev/sda
>
> smartctl version 5.36 [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: ST380817AS
> Serial Number: 4MR08EK8
> Firmware Version: 3.42
> User Capacity: 80,026,361,856 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: Sun Jan 21 20:15:40 2007 CET
> SMART support is: Available - device has SMART capability.
> SMART support is: Enabled
>
> === START OF READ SMART DATA SECTION ===
> SMART overall-health self-assessment test result: PASSED
>
> General SMART Values:
> Offline data collection status: (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: ( 47) 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 059 049 006 Pre-fail Always - 215927244
> 3 Spin_Up_Time 0x0003 098 098 000 Pre-fail Always - 0
> 4 Start_Stop_Count 0x0032 098 098 020 Old_age Always - 2182
> 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
> 7 Seek_Error_Rate 0x000f 083 060 030 Pre-fail Always - 204305750
> 9 Power_On_Hours 0x0032 097 097 000 Old_age Always - 3494
> 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
> 12 Power_Cycle_Count 0x0032 098 098 020 Old_age Always - 2541
> 194 Temperature_Celsius 0x0022 024 040 000 Old_age Always - 24 (Lifetime Min/Max 0/15)
> 195 Hardware_ECC_Recovered 0x001a 059 049 000 Old_age Always - 215927244
> 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 1
> 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 1
> 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
> ATA Error Count: 12 (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 12 occurred at disk power-on lifetime: 2516 hours (104 days + 20 hours)
> When the command that caused the error occurred, the device was active or idle.
>
> After command completion occurred, registers were:
> ER ST SC SN CL CH DH
> -- -- -- -- -- -- --
> 40 51 0d 5b 9d 34 e1 Error: UNC 13 sectors at LBA = 0x01349d5b = 20225371
>
> 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 4e 9d 34 e1 00 00:03:03.851 READ DMA
> c8 00 00 4e 9d 34 e1 00 00:03:03.848 READ DMA
> c8 00 00 4e 9d 34 e1 00 00:03:03.846 READ DMA
> c8 00 00 4e 9d 34 e1 00 00:03:03.843 READ DMA
> c8 00 00 4e 9d 34 e1 00 00:03:03.839 READ DMA
>
> Error 11 occurred at disk power-on lifetime: 2516 hours (104 days + 20 hours)
> When the command that caused the error occurred, the device was active or idle.
>
> After command completion occurred, registers were:
> ER ST SC SN CL CH DH
> -- -- -- -- -- -- --
> 40 51 0d 5b 9d 34 e1 Error: UNC 13 sectors at LBA = 0x01349d5b = 20225371
>
> 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 4e 9d 34 e1 00 00:03:03.851 READ DMA
> c8 00 00 4e 9d 34 e1 00 00:03:03.848 READ DMA
> c8 00 00 4e 9d 34 e1 00 00:03:03.846 READ DMA
> c8 00 00 4e 9d 34 e1 00 00:03:03.843 READ DMA
> c8 00 00 4e 9d 34 e1 00 00:03:03.839 READ DMA
>
> Error 10 occurred at disk power-on lifetime: 2516 hours (104 days + 20 hours)
> When the command that caused the error occurred, the device was active or idle.
>
> After command completion occurred, registers were:
> ER ST SC SN CL CH DH
> -- -- -- -- -- -- --
> 40 51 0d 5b 9d 34 e1 Error: UNC 13 sectors at LBA = 0x01349d5b = 20225371
>
> 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 4e 9d 34 e1 00 00:03:03.851 READ DMA
> c8 00 00 4e 9d 34 e1 00 00:03:03.848 READ DMA
> c8 00 00 4e 9d 34 e1 00 00:03:03.846 READ DMA
> c8 00 00 4e 9d 34 e1 00 00:03:03.843 READ DMA
> c8 00 00 16 9c 34 e1 00 00:03:03.839 READ DMA
>
> Error 9 occurred at disk power-on lifetime: 2516 hours (104 days + 20 hours)
> When the command that caused the error occurred, the device was active or idle.
>
> After command completion occurred, registers were:
> ER ST SC SN CL CH DH
> -- -- -- -- -- -- --
> 40 51 0d 5b 9d 34 e1 Error: UNC 13 sectors at LBA = 0x01349d5b = 20225371
>
> 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 4e 9d 34 e1 00 00:03:03.851 READ DMA
> c8 00 00 4e 9d 34 e1 00 00:03:03.848 READ DMA
> c8 00 00 4e 9d 34 e1 00 00:03:03.846 READ DMA
> c8 00 00 16 9c 34 e1 00 00:03:03.843 READ DMA
> c8 00 00 0e 9b 34 e1 00 00:03:03.839 READ DMA
>
> Error 8 occurred at disk power-on lifetime: 2516 hours (104 days + 20 hours)
> When the command that caused the error occurred, the device was active or idle.
>
> After command completion occurred, registers were:
> ER ST SC SN CL CH DH
> -- -- -- -- -- -- --
> 40 51 0d 5b 9d 34 e1 Error: UNC 13 sectors at LBA = 0x01349d5b = 20225371
>
> 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 4e 9d 34 e1 00 00:03:03.851 READ DMA
> c8 00 00 4e 9d 34 e1 00 00:03:03.848 READ DMA
> c8 00 00 16 9c 34 e1 00 00:03:03.846 READ DMA
> c8 00 00 0e 9b 34 e1 00 00:03:03.843 READ DMA
> c8 00 00 8e 99 34 e1 00 00:03:03.839 READ DMA
>
> 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.
>
(Added myself to CC.)
> 7 Seek_Error_Rate 0x000f 083 060 030 Pre-fail Always - 204305750
> 1 Raw_Read_Error_Rate 0x000f 059 049 006 Pre-fail Always - 215927244
> 195 Hardware_ECC_Recovered 0x001a 059 049 000 Old_age Always - 215927244
Wow! that HDD is really in a bad condition.
Thanks,
Chr.
Chr wrote:
>> 7 Seek_Error_Rate 0x000f 083 060 030 Pre-fail Always - 204305750
>> 1 Raw_Read_Error_Rate 0x000f 059 049 006 Pre-fail Always - 215927244
>> 195 Hardware_ECC_Recovered 0x001a 059 049 000 Old_age Always - 215927244
>
> Wow! that HDD is really in a bad condition.
I don't think so, this seems to be normal for Seagate drives...
regards,
--
http://www.fi.muni.cz/~xslaby/ Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8 22A0 32CC 55C3 39D4 7A7E
Paolo Ornati wrote:
> I don't know. It's a two years old ST380817AS.
>
> # smartctl -a -d ata /dev/sda
>
> smartctl version 5.36 [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: ST380817AS
I'll blacklist it. Thanks.
--
tejun
On Mon, 22 Jan 2007 01:53:21 +0059
Jiri Slaby <[email protected]> wrote:
> >> 7 Seek_Error_Rate 0x000f 083 060 030 Pre-fail Always - 204305750
> >> 1 Raw_Read_Error_Rate 0x000f 059 049 006 Pre-fail Always - 215927244
> >> 195 Hardware_ECC_Recovered 0x001a 059 049 000 Old_age Always - 215927244
> >
> > Wow! that HDD is really in a bad condition.
>
> I don't think so, this seems to be normal for Seagate drives...
I agree.
For Chr: I don't think these big raw-numbers are counters, look at the
normalized values instead, and see that they are greater than TRESH
values (so they are good).
The meaning of raw-numbers is vendor specific.
--
Paolo Ornati
Linux 2.6.20-rc5 on x86_64
On Mon, 22 Jan 2007 11:46:01 +0900
Tejun Heo <[email protected]> wrote:
> > I don't know. It's a two years old ST380817AS.
> >
> > # smartctl -a -d ata /dev/sda
> >
> > smartctl version 5.36 [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: ST380817AS
>
> I'll blacklist it. Thanks.
Ok. It will be better if someone else with the same HD could confirm.
It looks so strange that an HD that works fine, and should support NCQ,
have so big troubles that I can "freeze" it in less than a second by
using XFS (while with ext3 I cannot, or at least it's very hard).
--
Paolo Ornati
Linux 2.6.20-rc5 on x86_64
Paolo Ornati wrote:
>>> === START OF INFORMATION SECTION ===
>>> Model Family: Seagate Barracuda 7200.7 and 7200.7 Plus family
>>> Device Model: ST380817AS
>> I'll blacklist it. Thanks.
>
> Ok. It will be better if someone else with the same HD could confirm.
>
> It looks so strange that an HD that works fine, and should support NCQ,
> have so big troubles that I can "freeze" it in less than a second by
> using XFS (while with ext3 I cannot, or at least it's very hard).
Yeap, certainly. I'll ask people first before actually proceeding with
the blacklisting. I'm just getting a bit tired of tides of NCQ firmware
problems.
Anyways, for the time being, you can easily turn off NCQ using sysfs.
Please take a look at http://linux-ata.org/faq.html
--
tejun
On Mon, 22 Jan 2007 18:35:05 +0900
Tejun Heo <[email protected]> wrote:
> Yeap, certainly. I'll ask people first before actually proceeding with
> the blacklisting. I'm just getting a bit tired of tides of NCQ firmware
> problems.
>
> Anyways, for the time being, you can easily turn off NCQ using sysfs.
> Please take a look at http://linux-ata.org/faq.html
ok
--
Paolo Ornati
Linux 2.6.20-rc5 on x86_64
On Mon, 22 Jan 2007 18:35:05 +0900
Tejun Heo <[email protected]> wrote:
> Yeap, certainly. I'll ask people first before actually proceeding with
> the blacklisting. I'm just getting a bit tired of tides of NCQ firmware
> problems.
Another interesting thing: it seems that I'm unable to reproduce the
problem mounting XFS with "nobarrier" (using sda queue_depth = 31).
So it looks like a problem with NCQ combined with cache flush command...
--
Paolo Ornati
Linux 2.6.20-rc5 on x86_64