Comment 1: From Alan Cox:
================================================================================
Alan Cox <[email protected]>
> Error 1 occurred at disk power-on lifetime: 818 hours (34 days + 2 hours)
> When the command that caused the error occurred, the device was doing SMART
Offline or Self-test.
>
> After command completion occurred, registers were:
> ER ST SC SN CL CH DH
> -- -- -- -- -- -- --
> 04 51 00 34 cf f3 a3
So Error 0x04 (ABRT)
Status 0x51 (DRDY N/A ERR) Error occurred, and at the point data
transfer was expected
Which the spec says means the device errored the command because it does
not support it.
Seems odd that this then tripped a raid failover
================================================================================
Comment 1 Response: Should this have tripped a raid fail-over? I have
been having raid failures like this ever since I replaced all my
raptor150s with velociraptor300 disks, what can be done so this does not
occur? Is this a WD/firmware bug or a bug in the md/raid code?
================================================================================
Other questions I have:
Question 1: With a 3ware controller, it will 'remap' bad sectors, example:
20081114005455 - Controller 0
WARNING - Sector repair completed: port=11, LBA=0x73E3EAC
Question 2: How come the kernel does not do this? Does this not defeat
the purpose of raid, it should remap the bad sector and continue
processing, not drop the RAID/break it?
================================================================================
Logs from RAID1, smart info, etc, is SMART doing something bad on these
newer velociraptor disks?
================================================================================
Security Events for kernel
=-=-=-=-=-=-=-=-=-=-=-=-=-
Nov 21 01:04:17 p34 kernel: [490609.124770] end_request: I/O error, dev sda,
sector 309997925
^^^^^^^^^ Bad sector?? Is it really?
System Events
=-=-=-=-=-=-=
Nov 21 01:04:17 p34 kernel: [490609.089174] ata1.00: exception Emask 0x0 SAct
0x0 SErr 0x0 action 0x0
Nov 21 01:04:17 p34 kernel: [490609.089180] ata1.00: irq_stat 0x40000001
Nov 21 01:04:17 p34 kernel: [490609.089186] ata1.00: cmd
ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Nov 21 01:04:17 p34 kernel: [490609.089187] res
51/04:00:34:cf:f3/00:00:00:f3:40/a3 Emask 0x1 (device error)
Nov 21 01:04:17 p34 kernel: [490609.089192] ata1.00: status: { DRDY ERR }
Nov 21 01:04:17 p34 kernel: [490609.089195] ata1.00: error: { ABRT }
Nov 21 01:04:17 p34 kernel: [490609.113037] ata1.00: configured for UDMA/133
Nov 21 01:04:17 p34 kernel: [490609.124774] raid1: Disk failure on sda3,
disabling device.
Nov 21 01:04:17 p34 kernel: [490609.124775] raid1: Operation continuing on 1
devices.
Nov 21 01:04:17 p34 kernel: [490609.124802] sd 0:0:0:0: [sda] Write Protect is
off
Nov 21 01:04:17 p34 kernel: [490609.124803] sd 0:0:0:0: [sda] Mode Sense: 00 3a
00 00
Nov 21 01:04:17 p34 kernel: [490609.124820] sd 0:0:0:0: [sda] Write cache:
enabled, read cache: enabled, doesn't support DPO or FUA
Nov 21 01:04:17 p34 kernel: [490609.133725] RAID1 conf printout:
Nov 21 01:04:17 p34 kernel: [490609.133728] --- wd:1 rd:2
Nov 21 01:04:17 p34 kernel: [490609.133731] disk 0, wo:1, o:0, dev:sda3
Nov 21 01:04:17 p34 kernel: [490609.133733] disk 1, wo:0, o:1, dev:sdb3
Nov 21 01:04:17 p34 kernel: [490609.136170] RAID1 conf printout:
Nov 21 01:04:17 p34 kernel: [490609.136172] --- wd:1 rd:2
Nov 21 01:04:17 p34 kernel: [490609.136174] disk 1, wo:0, o:1, dev:sdb3
Nov 21 01:04:17 p34 mdadm[3285]: Fail event detected on md device /dev/md2,
component device /dev/sda3
Nov 21 01:34:02 p34 smartd[30574]: Device: /dev/sda, ATA error count increased
from 0 to 1
Nov 21 01:34:02 p34 smartd[30574]: Warning via mail to [email protected]:
successful
smart error:
Error 1 occurred at disk power-on lifetime: 818 hours (34 days + 2 hours)
When the command that caused the error occurred, the device was doing SMART Offline or Self-test.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 00 34 cf f3 a3
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
ea 00 00 00 00 00 00 08 8d+07:53:27.728 FLUSH CACHE EXIT
ea 00 00 00 00 00 00 08 8d+07:53:27.711 FLUSH CACHE EXIT
35 00 08 7b ac ee 22 08 8d+07:53:27.711 WRITE DMA EXT
ea 00 00 00 00 00 00 08 8d+07:53:24.980 FLUSH CACHE EXIT
b0 d4 00 01 4f c2 00 08 8d+07:53:19.871 SMART EXECUTE OFF-LINE IMMEDIATE
smartctl version 5.38 [x86_64-unknown-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Device Model: WDC WD3000HLFS-01G6U0
Serial Number: WD-*********
Firmware Version: 04.04V01
User Capacity: 300,069,052,416 bytes
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Fri Nov 21 04:06:58 2008 EST
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: (0x02) Offline data collection activity
was completed without error.
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: (4800) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 59) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x303f) SCT Status supported.
SCT Feature Control supported.
SCT Data Table supported.
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 200 200 051 Pre-fail Always - 0
3 Spin_Up_Time 0x0003 198 198 021 Pre-fail Always - 3083
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 22
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x000e 100 253 000 Old_age Always - 0
9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 821
10 Spin_Retry_Count 0x0012 100 253 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0012 100 253 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 22
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 13
193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 22
194 Temperature_Celsius 0x0022 121 115 000 Old_age Always - 26
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0012 200 200 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 200 200 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0
SMART Error Log Version: 1
ATA Error Count: 1
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 1 occurred at disk power-on lifetime: 818 hours (34 days + 2 hours)
When the command that caused the error occurred, the device was doing SMART Offline or Self-test.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
04 51 00 34 cf f3 a3
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
ea 00 00 00 00 00 00 08 8d+07:53:27.728 FLUSH CACHE EXIT
ea 00 00 00 00 00 00 08 8d+07:53:27.711 FLUSH CACHE EXIT
35 00 08 7b ac ee 22 08 8d+07:53:27.711 WRITE DMA EXT
ea 00 00 00 00 00 00 08 8d+07:53:24.980 FLUSH CACHE EXIT
b0 d4 00 01 4f c2 00 08 8d+07:53:19.871 SMART EXECUTE OFF-LINE IMMEDIATE
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% 818 -
# 2 Short offline Completed without error 00% 794 -
# 3 Short offline Completed without error 00% 771 -
# 4 Short offline Completed without error 00% 747 -
# 5 Short offline Completed without error 00% 723 -
# 6 Extended offline Completed without error 00% 701 -
# 7 Short offline Completed without error 00% 676 -
# 8 Short offline Completed without error 00% 652 -
# 9 Short offline Completed without error 00% 628 -
#10 Short offline Completed without error 00% 605 -
#11 Short offline Completed without error 00% 581 -
#12 Extended offline Completed without error 00% 535 -
#13 Short offline Completed without error 00% 510 -
#14 Short offline Completed without error 00% 486 -
#15 Short offline Completed without error 00% 462 -
#16 Short offline Completed without error 00% 438 -
#17 Short offline Completed without error 00% 414 -
#18 Short offline Completed without error 00% 406 -
#19 Short offline Completed without error 00% 391 -
#20 Extended offline Completed without error 00% 366 -
#21 Short offline Completed without error 00% 342 -
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.
I put it back into the RAID and then another bad sector caused it to error out
again:
[504864.661639] RAID1 conf printout:
[504864.661643] --- wd:2 rd:2
[504864.661646] disk 0, wo:0, o:1, dev:sda3
[504864.661649] disk 1, wo:0, o:1, dev:sdb3
[504915.503044] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[504915.503050] ata1.00: irq_stat 0x40000001
[504915.503055] ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[504915.503056] res 51/04:00:34:cf:f3/00:00:00:f3:40/a3 Emask 0x1 (device error)
[504915.503059] ata1.00: status: { DRDY ERR }
[504915.503061] ata1.00: error: { ABRT }
[504915.526980] ata1.00: configured for UDMA/133
[504915.526990] ata1: EH complete
[504915.527187] sd 0:0:0:0: [sda] 586072368 512-byte hardware sectors (300069 MB)
[504915.534181] end_request: I/O error, dev sda, sector 310069939
^^^^^^^^^ Another one.
[504915.534187] raid1: Disk failure on sda3, disabling device.
[504915.534188] raid1: Operation continuing on 1 devices.
[504915.534476] sd 0:0:0:0: [sda] Write Protect is off
[504915.534479] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[504915.534505] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[504915.545832] RAID1 conf printout:
[504915.545837] --- wd:1 rd:2
Try to write on those sectors, force remap?
p34:~# hdparm --write-sector 310069939 --yes-i-know-what-i-am-doing /dev/sda
/dev/sda:
re-writing sector 310069939: succeeded
p34:~#
p34:~# hdparm --write-sector 309997925 --yes-i-know-what-i-am-doing /dev/sda
/dev/sda:
re-writing sector 309997925: succeeded
p34:~#
p34:~# hdparm --repair-sector 310069939 --yes-i-know-what-i-am-doing /dev/sda
/dev/sda:
re-writing sector 310069939: succeeded
p34:~# hdparm --repair-sector 309997925 --yes-i-know-what-i-am-doing /dev/sda
/dev/sda:
re-writing sector 309997925: succeeded
p34:~#
-
Right now I am running a long smart test followed by an offline test to
see what happens next.
Adding [email protected] to the list incase that
is the root cause, sorry typo in first e-mail.
On Fri, 21 Nov 2008, Justin Piszcz wrote:
> Comment 1: From Alan Cox:
>
> ================================================================================
> Alan Cox <[email protected]>
>
>> Error 1 occurred at disk power-on lifetime: 818 hours (34 days + 2 hours)
>> When the command that caused the error occurred, the device was doing
>> SMART
> Offline or Self-test.
>>
>> After command completion occurred, registers were:
>> ER ST SC SN CL CH DH
>> -- -- -- -- -- -- --
>> 04 51 00 34 cf f3 a3
>
> So Error 0x04 (ABRT)
> Status 0x51 (DRDY N/A ERR) Error occurred, and at the point data
> transfer was expected
>
> Which the spec says means the device errored the command because it does
> not support it.
>
> Seems odd that this then tripped a raid failover
> ================================================================================
>
> Comment 1 Response: Should this have tripped a raid fail-over? I have been
> having raid failures like this ever since I replaced all my raptor150s with
> velociraptor300 disks, what can be done so this does not occur? Is this a
> WD/firmware bug or a bug in the md/raid code?
>
> ================================================================================
>
> Other questions I have:
>
> Question 1: With a 3ware controller, it will 'remap' bad sectors, example:
>
> 20081114005455 - Controller 0
> WARNING - Sector repair completed: port=11, LBA=0x73E3EAC
>
> Question 2: How come the kernel does not do this? Does this not defeat the
> purpose of raid, it should remap the bad sector and continue processing, not
> drop the RAID/break it?
>
> ================================================================================
>
> Logs from RAID1, smart info, etc, is SMART doing something bad on these newer
> velociraptor disks?
>
> ================================================================================
>
> Security Events for kernel
> =-=-=-=-=-=-=-=-=-=-=-=-=-
> Nov 21 01:04:17 p34 kernel: [490609.124770] end_request: I/O error, dev sda,
> sector 309997925
> ^^^^^^^^^ Bad sector?? Is it really?
>
> System Events
> =-=-=-=-=-=-=
> Nov 21 01:04:17 p34 kernel: [490609.089174] ata1.00: exception Emask 0x0 SAct
> 0x0 SErr 0x0 action 0x0
> Nov 21 01:04:17 p34 kernel: [490609.089180] ata1.00: irq_stat 0x40000001
> Nov 21 01:04:17 p34 kernel: [490609.089186] ata1.00: cmd
> ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
> Nov 21 01:04:17 p34 kernel: [490609.089187] res
> 51/04:00:34:cf:f3/00:00:00:f3:40/a3 Emask 0x1 (device error)
> Nov 21 01:04:17 p34 kernel: [490609.089192] ata1.00: status: { DRDY ERR }
> Nov 21 01:04:17 p34 kernel: [490609.089195] ata1.00: error: { ABRT }
> Nov 21 01:04:17 p34 kernel: [490609.113037] ata1.00: configured for UDMA/133
> Nov 21 01:04:17 p34 kernel: [490609.124774] raid1: Disk failure on sda3,
> disabling device.
> Nov 21 01:04:17 p34 kernel: [490609.124775] raid1: Operation continuing on 1
> devices.
> Nov 21 01:04:17 p34 kernel: [490609.124802] sd 0:0:0:0: [sda] Write Protect
> is
> off
> Nov 21 01:04:17 p34 kernel: [490609.124803] sd 0:0:0:0: [sda] Mode Sense: 00
> 3a
> 00 00
> Nov 21 01:04:17 p34 kernel: [490609.124820] sd 0:0:0:0: [sda] Write cache:
> enabled, read cache: enabled, doesn't support DPO or FUA
> Nov 21 01:04:17 p34 kernel: [490609.133725] RAID1 conf printout:
> Nov 21 01:04:17 p34 kernel: [490609.133728] --- wd:1 rd:2
> Nov 21 01:04:17 p34 kernel: [490609.133731] disk 0, wo:1, o:0, dev:sda3
> Nov 21 01:04:17 p34 kernel: [490609.133733] disk 1, wo:0, o:1, dev:sdb3
> Nov 21 01:04:17 p34 kernel: [490609.136170] RAID1 conf printout:
> Nov 21 01:04:17 p34 kernel: [490609.136172] --- wd:1 rd:2
> Nov 21 01:04:17 p34 kernel: [490609.136174] disk 1, wo:0, o:1, dev:sdb3
> Nov 21 01:04:17 p34 mdadm[3285]: Fail event detected on md device /dev/md2,
> component device /dev/sda3
> Nov 21 01:34:02 p34 smartd[30574]: Device: /dev/sda, ATA error count
> increased
> from 0 to 1
> Nov 21 01:34:02 p34 smartd[30574]: Warning via mail to [email protected]:
> successful
>
> smart error:
>
> Error 1 occurred at disk power-on lifetime: 818 hours (34 days + 2 hours)
> When the command that caused the error occurred, the device was doing SMART
> Offline or Self-test.
>
> After command completion occurred, registers were:
> ER ST SC SN CL CH DH
> -- -- -- -- -- -- --
> 04 51 00 34 cf f3 a3
>
> Commands leading to the command that caused the error were:
> CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
> -- -- -- -- -- -- -- -- ---------------- --------------------
> ea 00 00 00 00 00 00 08 8d+07:53:27.728 FLUSH CACHE EXIT
> ea 00 00 00 00 00 00 08 8d+07:53:27.711 FLUSH CACHE EXIT
> 35 00 08 7b ac ee 22 08 8d+07:53:27.711 WRITE DMA EXT
> ea 00 00 00 00 00 00 08 8d+07:53:24.980 FLUSH CACHE EXIT
> b0 d4 00 01 4f c2 00 08 8d+07:53:19.871 SMART EXECUTE OFF-LINE IMMEDIATE
>
> smartctl version 5.38 [x86_64-unknown-linux-gnu] Copyright (C) 2002-8 Bruce
> Allen
> Home page is http://smartmontools.sourceforge.net/
>
> === START OF INFORMATION SECTION ===
> Device Model: WDC WD3000HLFS-01G6U0
> Serial Number: WD-*********
> Firmware Version: 04.04V01
> User Capacity: 300,069,052,416 bytes
> Device is: Not in smartctl database [for details use: -P showall]
> ATA Version is: 8
> ATA Standard is: Exact ATA specification draft version not indicated
> Local Time is: Fri Nov 21 04:06:58 2008 EST
> 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: (0x02) Offline data collection activity
> was completed without error.
> 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: (4800)
> seconds.
> Offline data collection
> capabilities: (0x7b) SMART execute Offline immediate.
> Auto Offline data collection on/off
> support.
> Suspend Offline collection upon new
> command.
> Offline surface scan supported.
> Self-test supported.
> Conveyance Self-test supported.
> Selective Self-test supported.
> SMART capabilities: (0x0003) Saves SMART data before entering
> power-saving mode.
> Supports SMART auto save timer.
> Error logging capability: (0x01) Error logging supported.
> General Purpose Logging supported.
> Short self-test routine recommended polling time: ( 2) minutes.
> Extended self-test routine
> recommended polling time: ( 59) minutes.
> Conveyance self-test routine
> recommended polling time: ( 5) minutes.
> SCT capabilities: (0x303f) SCT Status supported.
> SCT Feature Control supported.
> SCT Data Table supported.
>
> 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 200 200 051 Pre-fail Always
> - 0
> 3 Spin_Up_Time 0x0003 198 198 021 Pre-fail Always
> - 3083
> 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always
> - 22
> 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always
> - 0
> 7 Seek_Error_Rate 0x000e 100 253 000 Old_age Always
> - 0
> 9 Power_On_Hours 0x0032 099 099 000 Old_age Always
> - 821
> 10 Spin_Retry_Count 0x0012 100 253 000 Old_age Always
> - 0
> 11 Calibration_Retry_Count 0x0012 100 253 000 Old_age Always
> - 0
> 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always
> - 22
> 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always
> - 13
> 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always
> - 22
> 194 Temperature_Celsius 0x0022 121 115 000 Old_age Always
> - 26
> 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always
> - 0
> 197 Current_Pending_Sector 0x0012 200 200 000 Old_age Always
> - 0
> 198 Offline_Uncorrectable 0x0010 200 200 000 Old_age Offline
> - 0
> 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always
> - 0
> 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline
> - 0
>
> SMART Error Log Version: 1
> ATA Error Count: 1
> 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 1 occurred at disk power-on lifetime: 818 hours (34 days + 2 hours)
> When the command that caused the error occurred, the device was doing SMART
> Offline or Self-test.
>
> After command completion occurred, registers were:
> ER ST SC SN CL CH DH
> -- -- -- -- -- -- --
> 04 51 00 34 cf f3 a3
>
> Commands leading to the command that caused the error were:
> CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
> -- -- -- -- -- -- -- -- ---------------- --------------------
> ea 00 00 00 00 00 00 08 8d+07:53:27.728 FLUSH CACHE EXIT
> ea 00 00 00 00 00 00 08 8d+07:53:27.711 FLUSH CACHE EXIT
> 35 00 08 7b ac ee 22 08 8d+07:53:27.711 WRITE DMA EXT
> ea 00 00 00 00 00 00 08 8d+07:53:24.980 FLUSH CACHE EXIT
> b0 d4 00 01 4f c2 00 08 8d+07:53:19.871 SMART EXECUTE OFF-LINE IMMEDIATE
>
> 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% 818
> -
> # 2 Short offline Completed without error 00% 794
> -
> # 3 Short offline Completed without error 00% 771
> -
> # 4 Short offline Completed without error 00% 747
> -
> # 5 Short offline Completed without error 00% 723
> -
> # 6 Extended offline Completed without error 00% 701
> -
> # 7 Short offline Completed without error 00% 676
> -
> # 8 Short offline Completed without error 00% 652
> -
> # 9 Short offline Completed without error 00% 628
> -
> #10 Short offline Completed without error 00% 605
> -
> #11 Short offline Completed without error 00% 581
> -
> #12 Extended offline Completed without error 00% 535
> -
> #13 Short offline Completed without error 00% 510
> -
> #14 Short offline Completed without error 00% 486
> -
> #15 Short offline Completed without error 00% 462
> -
> #16 Short offline Completed without error 00% 438
> -
> #17 Short offline Completed without error 00% 414
> -
> #18 Short offline Completed without error 00% 406
> -
> #19 Short offline Completed without error 00% 391
> -
> #20 Extended offline Completed without error 00% 366
> -
> #21 Short offline Completed without error 00% 342
> -
>
> 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.
>
> I put it back into the RAID and then another bad sector caused it to error
> out
> again:
>
> [504864.661639] RAID1 conf printout:
> [504864.661643] --- wd:2 rd:2
> [504864.661646] disk 0, wo:0, o:1, dev:sda3
> [504864.661649] disk 1, wo:0, o:1, dev:sdb3
> [504915.503044] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> [504915.503050] ata1.00: irq_stat 0x40000001
> [504915.503055] ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
> [504915.503056] res 51/04:00:34:cf:f3/00:00:00:f3:40/a3 Emask 0x1
> (device error)
> [504915.503059] ata1.00: status: { DRDY ERR }
> [504915.503061] ata1.00: error: { ABRT }
> [504915.526980] ata1.00: configured for UDMA/133
> [504915.526990] ata1: EH complete
> [504915.527187] sd 0:0:0:0: [sda] 586072368 512-byte hardware sectors (300069
> MB)
> [504915.534181] end_request: I/O error, dev sda, sector 310069939
> ^^^^^^^^^ Another
> one.
> [504915.534187] raid1: Disk failure on sda3, disabling device.
> [504915.534188] raid1: Operation continuing on 1 devices.
> [504915.534476] sd 0:0:0:0: [sda] Write Protect is off
> [504915.534479] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> [504915.534505] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled,
> doesn't support DPO or FUA
> [504915.545832] RAID1 conf printout:
> [504915.545837] --- wd:1 rd:2
>
>
> Try to write on those sectors, force remap?
>
> p34:~# hdparm --write-sector 310069939 --yes-i-know-what-i-am-doing /dev/sda
>
> /dev/sda:
> re-writing sector 310069939: succeeded
> p34:~#
>
> p34:~# hdparm --write-sector 309997925 --yes-i-know-what-i-am-doing /dev/sda
>
> /dev/sda:
> re-writing sector 309997925: succeeded
> p34:~#
>
> p34:~# hdparm --repair-sector 310069939 --yes-i-know-what-i-am-doing /dev/sda
>
> /dev/sda:
> re-writing sector 310069939: succeeded
>
> p34:~# hdparm --repair-sector 309997925 --yes-i-know-what-i-am-doing /dev/sda
>
> /dev/sda:
> re-writing sector 309997925: succeeded
> p34:~#
>
> -
>
> Right now I am running a long smart test followed by an offline test to see
> what happens next.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
On Fri, 21 Nov 2008, Peter Rabbitson wrote:
> It might very well be a WD bug. I had three (3) identical WDC
> WD2500AAJS-08B4A0 drives fail on me with the same _identical_ error
> (same sector number to the last digit):
>
> Oct 27 11:33:41 Arzamas kernel: ata6.00: exception Emask 0x10 SAct 0x0
> SErr 0x80000 action 0xe frozen
> Oct 27 11:33:41 Arzamas kernel: ata6.00: irq_stat 0x01100010, PHY RDY
> changed
> Oct 27 11:33:41 Arzamas kernel: ata6: SError: { 10B8B }
> Oct 27 11:33:41 Arzamas kernel: ata6.00: cmd
> ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
> Oct 27 11:33:41 Arzamas kernel: res 06/37:00:00:00:00/00:00:00:00:06/00
> Emask 0x12 (ATA bus error)
> Oct 27 11:33:41 Arzamas kernel: ata6.00: error: { IDNF ABRT }
> Oct 27 11:33:41 Arzamas kernel: ata6: hard resetting link
> Oct 27 11:33:46 Arzamas kernel: ata6: SATA link up 3.0 Gbps (SStatus 123
> SControl 0)
> Oct 27 11:33:46 Arzamas kernel: ata6.00: configured for UDMA/100
> Oct 27 11:33:46 Arzamas kernel: ata6: EH complete
> Oct 27 11:33:46 Arzamas kernel: sd 6:0:0:0: [sde] 488397168 512-byte
> hardware sectors (250059 MB)
> Oct 27 11:33:46 Arzamas kernel: sd 6:0:0:0: [sde] Write Protect is off
> Oct 27 11:33:46 Arzamas kernel: sd 6:0:0:0: [sde] Mode Sense: 00 3a 00 00
> Oct 27 11:33:46 Arzamas kernel: sd 6:0:0:0: [sde] Write cache: enabled,
> read cache: enabled, doesn't support DPO or FUA
> Oct 27 11:33:46 Arzamas kernel: end_request: I/O error, dev sde, sector
> 488166955
> Oct 27 11:33:46 Arzamas kernel: md: super_written gets error=-5, uptodate=0
>
>
> All 3 drives endured the same multiple rewriting of the sector in
> question, as they did multiple smart self-tests. I am currently in the
> process of replacing these two drives with Seagates, (the other 2 in the
> 4 member array are Maxtors). Will see what happens.
>
> Peter
>
> P.S. See threads http://marc.info/?l=linux-raid&m=122523835815697 and
> http://marc.info/?l=linux-raid&m=122669103213041 for more info on my
Pete,
Are these -new- 250GiB drives, recently purchased?
# hdparm -iv /dev/sda
Drive conforms to: Unspecified: ATA/ATAPI-1,2,3,4,5,6,7
What does yours conform to, just curious?
Justin.
On Fri, 21 Nov 2008, Justin Piszcz wrote:
>
>
> On Fri, 21 Nov 2008, Peter Rabbitson wrote:
>
>> It might very well be a WD bug. I had three (3) identical WDC
>> WD2500AAJS-08B4A0 drives fail on me with the same _identical_ error
>> (same sector number to the last digit):
>>
>> Oct 27 11:33:41 Arzamas kernel: ata6.00: exception Emask 0x10 SAct 0x0
>> SErr 0x80000 action 0xe frozen
>> Oct 27 11:33:41 Arzamas kernel: ata6.00: irq_stat 0x01100010, PHY RDY
>> changed
>> Oct 27 11:33:41 Arzamas kernel: ata6: SError: { 10B8B }
>> Oct 27 11:33:41 Arzamas kernel: ata6.00: cmd
>> ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
>> Oct 27 11:33:41 Arzamas kernel: res 06/37:00:00:00:00/00:00:00:00:06/00
>> Emask 0x12 (ATA bus error)
>> Oct 27 11:33:41 Arzamas kernel: ata6.00: error: { IDNF ABRT }
>> Oct 27 11:33:41 Arzamas kernel: ata6: hard resetting link
>> Oct 27 11:33:46 Arzamas kernel: ata6: SATA link up 3.0 Gbps (SStatus 123
>> SControl 0)
>> Oct 27 11:33:46 Arzamas kernel: ata6.00: configured for UDMA/100
>> Oct 27 11:33:46 Arzamas kernel: ata6: EH complete
>> Oct 27 11:33:46 Arzamas kernel: sd 6:0:0:0: [sde] 488397168 512-byte
>> hardware sectors (250059 MB)
>> Oct 27 11:33:46 Arzamas kernel: sd 6:0:0:0: [sde] Write Protect is off
>> Oct 27 11:33:46 Arzamas kernel: sd 6:0:0:0: [sde] Mode Sense: 00 3a 00 00
>> Oct 27 11:33:46 Arzamas kernel: sd 6:0:0:0: [sde] Write cache: enabled,
>> read cache: enabled, doesn't support DPO or FUA
>> Oct 27 11:33:46 Arzamas kernel: end_request: I/O error, dev sde, sector
>> 488166955
>> Oct 27 11:33:46 Arzamas kernel: md: super_written gets error=-5, uptodate=0
>>
>>
>> All 3 drives endured the same multiple rewriting of the sector in
>> question, as they did multiple smart self-tests. I am currently in the
>> process of replacing these two drives with Seagates, (the other 2 in the
>> 4 member array are Maxtors). Will see what happens.
>>
>> Peter
>>
>> P.S. See threads http://marc.info/?l=linux-raid&m=122523835815697 and
>> http://marc.info/?l=linux-raid&m=122669103213041 for more info on my
>
> Pete,
>
> Are these -new- 250GiB drives, recently purchased?
>
> # hdparm -iv /dev/sda
> Drive conforms to: Unspecified: ATA/ATAPI-1,2,3,4,5,6,7
>
> What does yours conform to, just curious?
Update, the extended offline test completed without any errors:
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% 823 -
# 2 Short offline Completed without error 00% 822 -
Running offline test now.
p34:~# smartctl -t offline /dev/sda
smartctl version 5.38 [x86_64-unknown-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION ===
Sending command: "Execute SMART off-line routine immediately in off-line mode".
Drive command "Execute SMART off-line routine immediately in off-line mode" successful.
Testing has begun.
Please wait 4800 seconds for test to complete.
Test will complete after Fri Nov 21 07:56:02 2008
Use smartctl -X to abort test.
p34:~#
We'll see what happens next..
Justin.
Justin Piszcz wrote:
>
>
> On Fri, 21 Nov 2008, Peter Rabbitson wrote:
>
>> It might very well be a WD bug. I had three (3) identical WDC
>> WD2500AAJS-08B4A0 drives fail on me with the same _identical_ error
>> (same sector number to the last digit):
>>
>> Oct 27 11:33:41 Arzamas kernel: ata6.00: exception Emask 0x10 SAct 0x0
>> SErr 0x80000 action 0xe frozen
>> Oct 27 11:33:41 Arzamas kernel: ata6.00: irq_stat 0x01100010, PHY RDY
>> changed
>> Oct 27 11:33:41 Arzamas kernel: ata6: SError: { 10B8B }
>> Oct 27 11:33:41 Arzamas kernel: ata6.00: cmd
>> ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
>> Oct 27 11:33:41 Arzamas kernel: res 06/37:00:00:00:00/00:00:00:00:06/00
>> Emask 0x12 (ATA bus error)
>> Oct 27 11:33:41 Arzamas kernel: ata6.00: error: { IDNF ABRT }
>> Oct 27 11:33:41 Arzamas kernel: ata6: hard resetting link
>> Oct 27 11:33:46 Arzamas kernel: ata6: SATA link up 3.0 Gbps (SStatus 123
>> SControl 0)
>> Oct 27 11:33:46 Arzamas kernel: ata6.00: configured for UDMA/100
>> Oct 27 11:33:46 Arzamas kernel: ata6: EH complete
>> Oct 27 11:33:46 Arzamas kernel: sd 6:0:0:0: [sde] 488397168 512-byte
>> hardware sectors (250059 MB)
>> Oct 27 11:33:46 Arzamas kernel: sd 6:0:0:0: [sde] Write Protect is off
>> Oct 27 11:33:46 Arzamas kernel: sd 6:0:0:0: [sde] Mode Sense: 00 3a 00 00
>> Oct 27 11:33:46 Arzamas kernel: sd 6:0:0:0: [sde] Write cache: enabled,
>> read cache: enabled, doesn't support DPO or FUA
>> Oct 27 11:33:46 Arzamas kernel: end_request: I/O error, dev sde, sector
>> 488166955
>> Oct 27 11:33:46 Arzamas kernel: md: super_written gets error=-5,
>> uptodate=0
>>
>>
>> All 3 drives endured the same multiple rewriting of the sector in
>> question, as they did multiple smart self-tests. I am currently in the
>> process of replacing these two drives with Seagates, (the other 2 in the
>> 4 member array are Maxtors). Will see what happens.
>>
>> Peter
>>
>> P.S. See threads http://marc.info/?l=linux-raid&m=122523835815697 and
>> http://marc.info/?l=linux-raid&m=122669103213041 for more info on my
>
> Pete,
>
> Are these -new- 250GiB drives, recently purchased?
>
> # hdparm -iv /dev/sda
> Drive conforms to: Unspecified: ATA/ATAPI-1,2,3,4,5,6,7
>
> What does yours conform to, just curious?
>
All 3 were new, bought from trusted channels as replacements (in 2 - 5
week intervals) for two of the Maxtors which went flaky after 4.5 years
of service. All showed usages hours starting from 1, confirming I am the
first user:
root@Arzamas:~# hdparm -iv /dev/sde
/dev/sde:
IO_support = 0 (default)
readonly = 0 (off)
readahead = 256 (on)
geometry = 30401/255/63, sectors = 488397168, start = 0
Model=WDC WD2500AAJS-08B4A0 , FwRev=01.03A01,
SerialNo= WD-WMAT14036837
Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=50
BuffType=unknown, BuffSize=8192kB, MaxMultSect=16, MultSect=?16?
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=488397168
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5
AdvancedPM=no WriteCache=enabled
Drive conforms to: Unspecified: ATA/ATAPI-1,2,3,4,5,6,7
* signifies the current active mode
root@Arzamas:~#
root@Arzamas:~# hdparm -iv /dev/sdc
/dev/sdc:
IO_support = 0 (default)
readonly = 0 (off)
readahead = 256 (on)
geometry = 30401/255/63, sectors = 488397168, start = 0
Model=WDC WD2500AAJS-00B4A0 , FwRev=01.03A01,
SerialNo= WD-WCAT11572764
Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=50
BuffType=unknown, BuffSize=8192kB, MaxMultSect=16, MultSect=?16?
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=488397168
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5 udma6
AdvancedPM=no WriteCache=enabled
Drive conforms to: Unspecified: ATA/ATAPI-1,2,3,4,5,6,7
* signifies the current active mode
root@Arzamas:~#
The 3rd drive is already gone back to MFG.
Peter
Justin Piszcz wrote:
> Comment 1: From Alan Cox:
>
> ================================================================================
>
> Alan Cox <[email protected]>
>
>> Error 1 occurred at disk power-on lifetime: 818 hours (34 days + 2 hours)
>> When the command that caused the error occurred, the device was
>> doing SMART
> Offline or Self-test.
>>
>> After command completion occurred, registers were:
>> ER ST SC SN CL CH DH
>> -- -- -- -- -- -- --
>> 04 51 00 34 cf f3 a3
>
> So Error 0x04 (ABRT)
> Status 0x51 (DRDY N/A ERR) Error occurred, and at the point data
> transfer was expected
>
> Which the spec says means the device errored the command because it does
> not support it.
>
> Seems odd that this then tripped a raid failover
> ================================================================================
>
>
> Comment 1 Response: Should this have tripped a raid fail-over? I have
> been having raid failures like this ever since I replaced all my
> raptor150s with velociraptor300 disks, what can be done so this does not
> occur? Is this a WD/firmware bug or a bug in the md/raid code?
>
> ================================================================================
>
It might very well be a WD bug. I had three (3) identical WDC
WD2500AAJS-08B4A0 drives fail on me with the same _identical_ error
(same sector number to the last digit):
Oct 27 11:33:41 Arzamas kernel: ata6.00: exception Emask 0x10 SAct 0x0
SErr 0x80000 action 0xe frozen
Oct 27 11:33:41 Arzamas kernel: ata6.00: irq_stat 0x01100010, PHY RDY
changed
Oct 27 11:33:41 Arzamas kernel: ata6: SError: { 10B8B }
Oct 27 11:33:41 Arzamas kernel: ata6.00: cmd
ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Oct 27 11:33:41 Arzamas kernel: res 06/37:00:00:00:00/00:00:00:00:06/00
Emask 0x12 (ATA bus error)
Oct 27 11:33:41 Arzamas kernel: ata6.00: error: { IDNF ABRT }
Oct 27 11:33:41 Arzamas kernel: ata6: hard resetting link
Oct 27 11:33:46 Arzamas kernel: ata6: SATA link up 3.0 Gbps (SStatus 123
SControl 0)
Oct 27 11:33:46 Arzamas kernel: ata6.00: configured for UDMA/100
Oct 27 11:33:46 Arzamas kernel: ata6: EH complete
Oct 27 11:33:46 Arzamas kernel: sd 6:0:0:0: [sde] 488397168 512-byte
hardware sectors (250059 MB)
Oct 27 11:33:46 Arzamas kernel: sd 6:0:0:0: [sde] Write Protect is off
Oct 27 11:33:46 Arzamas kernel: sd 6:0:0:0: [sde] Mode Sense: 00 3a 00 00
Oct 27 11:33:46 Arzamas kernel: sd 6:0:0:0: [sde] Write cache: enabled,
read cache: enabled, doesn't support DPO or FUA
Oct 27 11:33:46 Arzamas kernel: end_request: I/O error, dev sde, sector
488166955
Oct 27 11:33:46 Arzamas kernel: md: super_written gets error=-5, uptodate=0
All 3 drives endured the same multiple rewriting of the sector in
question, as they did multiple smart self-tests. I am currently in the
process of replacing these two drives with Seagates, (the other 2 in the
4 member array are Maxtors). Will see what happens.
Peter
P.S. See threads http://marc.info/?l=linux-raid&m=122523835815697 and
http://marc.info/?l=linux-raid&m=122669103213041 for more info on my
setup and hardware.
> Oct 27 11:33:41 Arzamas kernel: ata6.00: error: { IDNF ABRT }
Different error. IDNF -> ID not found
On Fri, 21 Nov 2008, Alan Cox wrote:
>> Oct 27 11:33:41 Arzamas kernel: ata6.00: error: { IDNF ABRT }
>
> Different error. IDNF -> ID not found
>
So the only thing in common is WD disks. I don't know at this point.. NCQ with
WD disks (at least raptor150s/300s) is completely broken and I have to disable
it to use the disks without NCQ errors and dropping out of arrays (on 3 diff)
systems with different chipsets, p35, 965.
This guy has the same errors I do when I enable NCQ. It seems like WD raptors
should be blacklisted from using NCQ in the kernel.
NCQ: http://lkml.org/lkml/2007/10/17/380
Concerning my error specifically:
How much time have you spent replacing and RMA'ing disks? Personally for me
I spent $3600 on new velociraptors but after having spend hours, days with
doing testing, replacing, I have spent much more in time than the drives are
worth. I am really getting sick and tired of it, every few days or every week
its another drive failure (or more). What are you plans, just keep RMA'ing
and hopefully they'll find the bug and fix it or just give up and build a new
system for production and the RMA'ing can be a hobby in another system?
What I meant when I asked did you buy them new, was, did you buy them recently,
because with the raptor150s I have in another system, all 1+ year old, bought
new but I wonder if they changed something in their firmware to cause this
problem, when I opened a case with WD about the issue and spoke with someone
in India they are only setup to answer basic questions and anything complicated
you will get canned answer: "RMA."
Time to dump WD raptor drives?
I will note I am using several 750GiB drives without any issue whether
NCQ is enabled or disabled in various raid and non-raid configurations.
Comments--buggy raptors?
Justin.
Justin Piszcz wrote:
>
>
> On Fri, 21 Nov 2008, Alan Cox wrote:
>
>>> Oct 27 11:33:41 Arzamas kernel: ata6.00: error: { IDNF ABRT }
>>
>> Different error. IDNF -> ID not found
>>
>
> So the only thing in common is WD disks. I don't know at this point..
> NCQ with
> WD disks (at least raptor150s/300s) is completely broken and I have to
> disable
> it to use the disks without NCQ errors and dropping out of arrays (on
> 3 diff)
> systems with different chipsets, p35, 965.
>
> This guy has the same errors I do when I enable NCQ. It seems like WD
> raptors
> should be blacklisted from using NCQ in the kernel.
>
> NCQ: http://lkml.org/lkml/2007/10/17/380
>
> Concerning my error specifically:
>
> How much time have you spent replacing and RMA'ing disks? Personally
> for me
> I spent $3600 on new velociraptors but after having spend hours, days
> with
> doing testing, replacing, I have spent much more in time than the
> drives are
> worth. I am really getting sick and tired of it, every few days or
> every week
> its another drive failure (or more). What are you plans, just keep
> RMA'ing and hopefully they'll find the bug and fix it or just give up
> and build a new system for production and the RMA'ing can be a hobby
> in another system?
>
> What I meant when I asked did you buy them new, was, did you buy them
> recently,
> because with the raptor150s I have in another system, all 1+ year old,
> bought
> new but I wonder if they changed something in their firmware to cause
> this
> problem, when I opened a case with WD about the issue and spoke with
> someone
> in India they are only setup to answer basic questions and anything
> complicated
> you will get canned answer: "RMA."
>
> Time to dump WD raptor drives?
>
> I will note I am using several 750GiB drives without any issue whether
> NCQ is enabled or disabled in various raid and non-raid configurations.
>
> Comments--buggy raptors?
Well I guess I will have some data points after the weekend... I just
got a new WD 1TB on sale from Newegg, and I'm going to be using it
raid10 with a raid0 of a pair of Seagate 500GB, and expect to beat it
somewhat severely moving data from place to place.
--
Bill Davidsen <[email protected]>
"Woe unto the statesman who makes war without a reason that will still
be valid when the war is over..." Otto von Bismark