* Velociraptor biting the dust (9th disk, continued to use it, and..)
@ 2008-11-22 21:45 Justin Piszcz
2008-11-22 21:55 ` Alan Cox
2008-11-23 1:38 ` Robert Hancock
0 siblings, 2 replies; 9+ messages in thread
From: Justin Piszcz @ 2008-11-22 21:45 UTC (permalink / raw)
To: linux-ide, linux-raid; +Cc: smartmontools-support, Alan Piszcz
I have several questions, to make things more clear I have segmented this
e-mail a bit-- any help with this issue would be greatly appreciated,
thank you.
================================================================================
So I continued to use the disk and it started failing again:
A Fail event had been detected on md device /dev/md2.
It could be related to component device /dev/sda3.
This is as it happened according to the kernel/dmesg:
================================================================================
[625188.381111] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[625188.381117] ata1.00: irq_stat 0x40000001
[625188.381124] ata1.00: cmd 25/00:a8:7b:57:8a/00:01:1c:00:00/e0 tag 0 dma 21708
8 in
[625188.381125] res 51/40:a8:7b:57:8a/00:01:1c:00:00/e0 Emask 0x9 (medi
a error)
[625188.381130] ata1.00: status: { DRDY ERR }
[625188.381133] ata1.00: error: { UNC }
[625188.402821] ata1.00: configured for UDMA/133
[625188.402831] ata1: EH complete
[625188.413645] sd 0:0:0:0: [sda] 586072368 512-byte hardware sectors (300069 MB
)
[625188.413665] sd 0:0:0:0: [sda] Write Protect is off
[625188.413668] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[625188.413692] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doe
sn't support DPO or FUA
[631340.401896] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[631340.401902] ata1.00: irq_stat 0x40000001
[631340.401907] ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[631340.401908] res 51/04:00:34:cf:f3/00:00:00:f3:40/a3 Emask 0x1 (devi
ce error)
[631340.401912] ata1.00: status: { DRDY ERR }
[631340.401914] ata1.00: error: { ABRT }
[631340.421630] ata1.00: configured for UDMA/133
[631340.421641] ata1: EH complete
[631340.421824] sd 0:0:0:0: [sda] 586072368 512-byte hardware sectors (300069 MB
)
================================================================================
[631340.433488] end_request: I/O error, dev sda, sector 586067067
^^^^^^^^^
sector in question
================================================================================
[631340.433493] md: super_written gets error=-5, uptodate=0
[631340.433497] raid1: Disk failure on sda3, disabling device.
[631340.433498] raid1: Operation continuing on 1 devices.
[631340.433571] sd 0:0:0:0: [sda] Write Protect is off
[631340.433575] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[631340.442957] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doe
sn't support DPO or FUA
[631340.444794] RAID1 conf printout:
[631340.444798] --- wd:1 rd:2
[631340.444800] disk 0, wo:1, o:0, dev:sda3
[631340.444802] disk 1, wo:0, o:1, dev:sdb3
[631340.448024] RAID1 conf printout:
[631340.448027] --- wd:1 rd:2
[631340.448030] disk 1, wo:0, o:1, dev:sdb3
================================================================================
Nov 22 14:34:02 p34 smartd[30574]: Device: /dev/sda, ATA error count increased from 2 to 3
Nov 22 16:09:49 p34 mdadm[3285]: Fail event detected on md device /dev/md2, component device /dev/sda3
================================================================================
p34:~# hdparm --read-sector 586067067 /dev/sda
/dev/sda:
reading sector 586067067: succeeded
<prints out a lot of data, snipped for e-mail>
[ .. snip .. ]
p34:~#
================================================================================
Does this mean the drive already remapped the bad sector?
[632350.116576] sd 0:0:0:0: [sda] 586072368 512-byte hardware sectors (300069 MB)
586067067 <- says this is the bad sector
586072368 <- total number of sectors
# for sector in $(seq 586067060 586072368); do hdparm --read-sector $sector /dev/sda > sector.$sector; done
All sectors could be read except the last one:
-rw-r--r-- 1 root root 1327 2008-11-22 16:30 sector.586072364
-rw-r--r-- 1 root root 1327 2008-11-22 16:30 sector.586072365
-rw-r--r-- 1 root root 1327 2008-11-22 16:30 sector.586072366
-rw-r--r-- 1 root root 1327 2008-11-22 16:30 sector.586072367
-rw-r--r-- 1 root root 37 2008-11-22 16:30 sector.586072368
================================================================================
p34:~/read# dmesg
p34:~/read# # empty
p34:~/read# hdparm --read-sector 586072368 /dev/sda
/dev/sda:
reading sector 586072368: FAILED: Input/output error
p34:~/read# dmesg
[632714.975824] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[632714.975831] ata1.00: irq_stat 0x40000001
[632714.975837] ata1.00: cmd 24/00:01:30:c1:ee/00:00:22:00:00/40 tag 0 pio 512 in
[632714.975838] res 51/10:01:30:c1:ee/00:00:22:00:00/40 Emask 0x81 (invalid argument)
[632714.975844] ata1.00: status: { DRDY ERR }
[632714.975847] ata1.00: error: { IDNF }
[632714.998757] ata1.00: configured for UDMA/133
[632714.998783] ata1: EH complete
[632714.998829] sd 0:0:0:0: [sda] 586072368 512-byte hardware sectors (300069 MB)
[632714.998842] sd 0:0:0:0: [sda] Write Protect is off
[632714.998844] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[632714.998860] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
p34:~/read#
Although its a different error IDNF, vs. that of above (UNC/ABRT).
================================================================================
In the smart logs on the disk; I see:
Error 3 occurred at disk power-on lifetime: 855 hours (35 days + 15 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
-- -- -- -- -- -- --
40 51 a8 7b 57 8a e0 Error: UNC 168 sectors at LBA = 0x008a577b = 9066363
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 a8 7b 57 8a 1c 08 9d+21:14:13.968 READ DMA EXT
25 00 00 33 64 db 19 08 9d+21:13:56.211 READ DMA EXT
25 00 00 a3 4c d6 19 08 9d+21:13:52.598 READ DMA EXT
25 00 00 a3 38 d6 19 08 9d+21:13:52.586 READ DMA EXT
25 00 00 a3 36 d6 19 08 9d+21:13:52.584 READ DMA EXT
================================================================================
However, the full smartctl output does not show any offline uncorrectable/etc
sectors yet?
================================================================================
BTW: I have already submitted an RMA for this disk (9th RMA!) I just cannot get
over how many of these are failing.
================================================================================
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: ***************
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: Sat Nov 22 16:33:29 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: (0x85) Offline data collection activity
was aborted by an interrupting command from host.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 247) Self-test routine in progress...
70% of test remaining.
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 200 200 000 Old_age Always - 0
9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 857
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 118 115 000 Old_age Always - 29
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: 4
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 4 occurred at disk power-on lifetime: 857 hours (35 days + 17 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 9d+22:56:39.886 FLUSH CACHE EXIT
ca 00 20 13 9b 04 06 08 9d+22:56:39.685 WRITE DMA
ca 00 08 2b 29 13 02 08 9d+22:56:39.685 WRITE DMA
ca 00 08 83 57 05 02 08 9d+22:56:39.685 WRITE DMA
ca 00 08 bb 54 05 02 08 9d+22:56:39.685 WRITE DMA
Error 3 occurred at disk power-on lifetime: 855 hours (35 days + 15 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
-- -- -- -- -- -- --
40 51 a8 7b 57 8a e0 Error: UNC 168 sectors at LBA = 0x008a577b = 9066363
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 a8 7b 57 8a 1c 08 9d+21:14:13.968 READ DMA EXT
25 00 00 33 64 db 19 08 9d+21:13:56.211 READ DMA EXT
25 00 00 a3 4c d6 19 08 9d+21:13:52.598 READ DMA EXT
25 00 00 a3 38 d6 19 08 9d+21:13:52.586 READ DMA EXT
25 00 00 a3 36 d6 19 08 9d+21:13:52.584 READ DMA EXT
Error 2 occurred at disk power-on lifetime: 822 hours (34 days + 6 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+11:51:40.026 FLUSH CACHE EXIT
ea 00 00 00 00 00 00 08 8d+11:51:40.008 FLUSH CACHE EXIT
35 00 08 7b ac ee 22 08 8d+11:51:40.008 WRITE DMA EXT
ea 00 00 00 00 00 00 08 8d+11:51:35.045 FLUSH CACHE EXIT
b0 d4 00 01 4f c2 00 08 8d+11:51:32.628 SMART EXECUTE OFF-LINE IMMEDIATE
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% 857 -
# 2 Short offline Completed without error 00% 842 -
# 3 Extended offline Completed without error 00% 823 -
# 4 Short offline Completed without error 00% 822 -
# 5 Short offline Completed without error 00% 822 -
# 6 Short offline Completed without error 00% 818 -
# 7 Short offline Completed without error 00% 794 -
# 8 Short offline Completed without error 00% 771 -
# 9 Short offline Completed without error 00% 747 -
#10 Short offline Completed without error 00% 723 -
#11 Extended offline Completed without error 00% 701 -
#12 Short offline Completed without error 00% 676 -
#13 Short offline Completed without error 00% 652 -
#14 Short offline Completed without error 00% 628 -
#15 Short offline Completed without error 00% 605 -
#16 Short offline Completed without error 00% 581 -
#17 Extended offline Completed without error 00% 535 -
#18 Short offline Completed without error 00% 510 -
#19 Short offline Completed without error 00% 486 -
#20 Short offline Completed without error 00% 462 -
#21 Short offline Completed without error 00% 438 -
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.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Velociraptor biting the dust (9th disk, continued to use it, and..)
2008-11-22 21:45 Velociraptor biting the dust (9th disk, continued to use it, and..) Justin Piszcz
@ 2008-11-22 21:55 ` Alan Cox
2008-12-16 12:31 ` [smartmontools-support] " Bruce Allen
2008-11-23 1:38 ` Robert Hancock
1 sibling, 1 reply; 9+ messages in thread
From: Alan Cox @ 2008-11-22 21:55 UTC (permalink / raw)
To: Justin Piszcz; +Cc: linux-ide, linux-raid, smartmontools-support, Alan Piszcz
> [625188.381125] res 51/40:a8:7b:57:8a/00:01:1c:00:00/e0 Emask 0x9 (medi
> a error)
> [625188.381130] ata1.00: status: { DRDY ERR }
> [625188.381133] ata1.00: error: { UNC }
UNC - uncorrectable error (eg a bad block)
> [631340.401912] ata1.00: status: { DRDY ERR }
> [631340.401914] ata1.00: error: { ABRT }
ABRT - usually unsupported command
> [632714.975844] ata1.00: status: { DRDY ERR }
> [632714.975847] ata1.00: error: { IDNF }
IDNF - ID not found, usually these days means 'asked for a sector out of
range'
Alan
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Velociraptor biting the dust (9th disk, continued to use it, and..)
2008-11-22 21:45 Velociraptor biting the dust (9th disk, continued to use it, and..) Justin Piszcz
2008-11-22 21:55 ` Alan Cox
@ 2008-11-23 1:38 ` Robert Hancock
2008-11-24 5:29 ` Tejun Heo
1 sibling, 1 reply; 9+ messages in thread
From: Robert Hancock @ 2008-11-23 1:38 UTC (permalink / raw)
To: linux-raid; +Cc: linux-ide, smartmontools-support
Justin Piszcz wrote:
> I have several questions, to make things more clear I have segmented this
> e-mail a bit-- any help with this issue would be greatly appreciated,
> thank you.
> ================================================================================
>
> So I continued to use the disk and it started failing again:
> A Fail event had been detected on md device /dev/md2.
> It could be related to component device /dev/sda3.
> This is as it happened according to the kernel/dmesg:
(snip)
> BTW: I have already submitted an RMA for this disk (9th RMA!) I just
> cannot get
> over how many of these are failing.
That many bad drives in a row seems unlikely. I would tend to suspect
some kind of other cause such as power issues, etc. though maybe it's
some kind of design flaw..
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: Velociraptor biting the dust (9th disk, continued to use it, and..)
2008-11-23 1:38 ` Robert Hancock
@ 2008-11-24 5:29 ` Tejun Heo
0 siblings, 0 replies; 9+ messages in thread
From: Tejun Heo @ 2008-11-24 5:29 UTC (permalink / raw)
To: Robert Hancock; +Cc: linux-ide, linux-raid, smartmontools-support
Robert Hancock wrote:
> Justin Piszcz wrote:
>> I have several questions, to make things more clear I have segmented this
>> e-mail a bit-- any help with this issue would be greatly appreciated,
>> thank you.
>> ================================================================================
>>
>> So I continued to use the disk and it started failing again:
>> A Fail event had been detected on md device /dev/md2.
>> It could be related to component device /dev/sda3.
>> This is as it happened according to the kernel/dmesg:
>
> (snip)
>
>> BTW: I have already submitted an RMA for this disk (9th RMA!) I just
>> cannot get
>> over how many of these are failing.
>
> That many bad drives in a row seems unlikely. I would tend to suspect
> some kind of other cause such as power issues, etc. though maybe it's
> some kind of design flaw..
Also, in many cases, simple resync is often enough to remove media
related errors as it makes the drive to rewrite and allows it to remap
if necessary but I admit I tend to have quite low standard regarding
hard drive quality.
Thanks.
--
tejun
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [smartmontools-support] Velociraptor biting the dust (9th disk, continued to use it, and..)
2008-11-22 21:55 ` Alan Cox
@ 2008-12-16 12:31 ` Bruce Allen
2008-12-16 13:07 ` Justin Piszcz
0 siblings, 1 reply; 9+ messages in thread
From: Bruce Allen @ 2008-12-16 12:31 UTC (permalink / raw)
To: Justin Piszcz, Alan Cox
Cc: linux-raid, linux-ide, Smartmontools Mailing List, Alan Piszcz
Hi Alan, Hi Justin,
Sorry, following up on old emails... I am behind as usual.
>> [632714.975844] ata1.00: status: { DRDY ERR }
>> [632714.975847] ata1.00: error: { IDNF }
> IDNF - ID not found, usually these days means 'asked for a sector out of
> range'
Justin, was this error provoked for example by you using a 'dd' command to
try and read stuff past the end of the disk? Because the md device driver
should not try and do something like that. The md device driver knows how
many LBAs are available on the disk and should never issue a read or write
past the end of the device.
Justin, I have the impression that this IDNF error was NOT due to you
issuing dd commands or similar, but was part of 'normal' md operation.
Alan, am I overlooking something? (One feature that might provide such
errors is the 'host reserved address' set of commands that allow you to
'clip' the disk capacity.)
Cheers,
Bruce
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [smartmontools-support] Velociraptor biting the dust (9th disk, continued to use it, and..)
2008-12-16 12:31 ` [smartmontools-support] " Bruce Allen
@ 2008-12-16 13:07 ` Justin Piszcz
2008-12-16 13:16 ` Bruce Allen
0 siblings, 1 reply; 9+ messages in thread
From: Justin Piszcz @ 2008-12-16 13:07 UTC (permalink / raw)
To: Bruce Allen
Cc: Alan Cox, linux-raid, linux-ide, Smartmontools Mailing List,
Alan Piszcz
On Tue, 16 Dec 2008, Bruce Allen wrote:
> Hi Alan, Hi Justin,
>
> Sorry, following up on old emails... I am behind as usual.
>
>>> [632714.975844] ata1.00: status: { DRDY ERR }
>>> [632714.975847] ata1.00: error: { IDNF }
>
>> IDNF - ID not found, usually these days means 'asked for a sector out of
>> range'
>
> Justin, was this error provoked for example by you using a 'dd' command to
> try and read stuff past the end of the disk? Because the md device driver
> should not try and do something like that. The md device driver knows how
> many LBAs are available on the disk and should never issue a read or write
> past the end of the device.
>
> Justin, I have the impression that this IDNF error was NOT due to you issuing
> dd commands or similar, but was part of 'normal' md operation.
>
> Alan, am I overlooking something? (One feature that might provide such
> errors is the 'host reserved address' set of commands that allow you to
> 'clip' the disk capacity.)
>
> Cheers,
> Bruce
>
Bruce,
Most of the errors were during normal md/Linux operation. However, I will
also note that with a 16-port 3ware controller, drives were also
having problems, different errors mind you but they were rather nasty.
The errors occured on RAID-1, RAID-5 and RAID-6 and even on a single disk,
no md/Linux, I kept running bonnie++ with different filesystems on one
disk, ext3 and XFS, both of which started erroring out.
I removed all of the Velociraptors and replaced them with good old
Raptor150s and tested with md/Linux and the 3ware card, no problems with
either configuration. I truly believe something is wrong with the
Velociraptors at this point since both md/Linux and 3ware both had problems
with the drives.
Justin.
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [smartmontools-support] Velociraptor biting the dust (9th disk, continued to use it, and..)
2008-12-16 13:07 ` Justin Piszcz
@ 2008-12-16 13:16 ` Bruce Allen
2008-12-16 22:49 ` Justin Piszcz
0 siblings, 1 reply; 9+ messages in thread
From: Bruce Allen @ 2008-12-16 13:16 UTC (permalink / raw)
To: Justin Piszcz
Cc: linux-raid, linux-ide, Smartmontools Mailing List, Alan Piszcz,
Alan Cox
>>>> [632714.975844] ata1.00: status: { DRDY ERR }
>>>> [632714.975847] ata1.00: error: { IDNF }
>>> IDNF - ID not found, usually these days means 'asked for a sector out of
>>> range'
>> Justin, was this error provoked for example by you using a 'dd' command to
>> try and read stuff past the end of the disk? Because the md device driver
>> should not try and do something like that. The md device driver knows how
>> many LBAs are available on the disk and should never issue a read or write
>> past the end of the device.
>>
>> Justin, I have the impression that this IDNF error was NOT due to you issuing
>> dd commands or similar, but was part of 'normal' md operation.
>>
>> Alan, am I overlooking something? (One feature that might provide such
>> errors is the 'host reserved address' set of commands that allow you to
>> 'clip' the disk capacity.)
> Most of the errors were during normal md/Linux operation. However, I will
> also note that with a 16-port 3ware controller, drives were also
> having problems, different errors mind you but they were rather nasty.
>
> The errors occured on RAID-1, RAID-5 and RAID-6 and even on a single disk,
> no md/Linux, I kept running bonnie++ with different filesystems on one
> disk, ext3 and XFS, both of which started erroring out.
When you say 'the errors occured' do you mean specifically the 'IDNF'
errors? Those are the onces I am talking about. I am NOT talking about
other types of errors like UNC or ABORT. I am ONLY talking about the IDNF
errors.
> I removed all of the Velociraptors and replaced them with good old
> Raptor150s and tested with md/Linux and the 3ware card, no problems with
> either configuration. I truly believe something is wrong with the
> Velociraptors at this point since both md/Linux and 3ware both had problems
> with the drives.
It is easy to check if the IDNF errors are from the disk firmware or
the Linux kernel.
The kernel error message for IDNF should report the LBA which provoked
that IDNF error. Please compare that with the maximum LBA on the disk,
which you can get either via hdparm or smartctl -i (divide total capacity
in bytes by 512).
If the LBA reported in the kernel error message is greater than the
maximum LBA on the disk, then the problem is in the Linux kernel. If the
LBA reported by the kernel is less than the maximum LBA on the disk, then
the problem is the disk firmware (or perhaps the disk has its capacity
'clipped' with the 'Host Protected Area' feature set. But the Linux
kernel should know about this, so that would be a kernel bug again, not a
disk firmware bug).
Cheers,
Bruce
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [smartmontools-support] Velociraptor biting the dust (9th disk, continued to use it, and..)
2008-12-16 13:16 ` Bruce Allen
@ 2008-12-16 22:49 ` Justin Piszcz
2008-12-17 3:52 ` Bruce Allen
0 siblings, 1 reply; 9+ messages in thread
From: Justin Piszcz @ 2008-12-16 22:49 UTC (permalink / raw)
To: Bruce Allen
Cc: linux-raid, linux-ide, Smartmontools Mailing List, Alan Piszcz,
Alan Cox
On Tue, 16 Dec 2008, Bruce Allen wrote:
>>>>> [632714.975844] ata1.00: status: { DRDY ERR }
>>>>> [632714.975847] ata1.00: error: { IDNF }
>
>>>> IDNF - ID not found, usually these days means 'asked for a sector out of
>>>> range'
>
>>> Justin, was this error provoked for example by you using a 'dd' command to
>>> try and read stuff past the end of the disk? Because the md device driver
>>> should not try and do something like that. The md device driver knows how
>>> many LBAs are available on the disk and should never issue a read or write
>>> past the end of the device.
>>>
>>> Justin, I have the impression that this IDNF error was NOT due to you
>>> issuing
>>> dd commands or similar, but was part of 'normal' md operation.
>>>
> When you say 'the errors occured' do you mean specifically the 'IDNF' errors?
> Those are the onces I am talking about. I am NOT talking about other types
> of errors like UNC or ABORT. I am ONLY talking about the IDNF errors.
>
> It is easy to check if the IDNF errors are from the disk firmware or the
> Linux kernel.
>
> The kernel error message for IDNF should report the LBA which provoked that
> IDNF error. Please compare that with the maximum LBA on the disk, which you
> can get either via hdparm or smartctl -i (divide total capacity in bytes by
> 512).
>
> If the LBA reported in the kernel error message is greater than the maximum
> LBA on the disk, then the problem is in the Linux kernel. If the LBA
> reported by the kernel is less than the maximum LBA on the disk, then the
> problem is the disk firmware (or perhaps the disk has its capacity 'clipped'
> with the 'Host Protected Area' feature set. But the Linux kernel should know
> about this, so that would be a kernel bug again, not a disk firmware bug).
>
Going to plug-in one of the disks to a test system, I dare not use them in
a real host anymore.. ok, plugged in:
syslog-Nov 25 02:53:25 p34 kernel: [842756.834250] end_request: I/O error, dev sda, sector 213221352
smartctl -i
# smartctl -i /dev/sdg
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 WD3000GLFS-01F8U0
Serial Number: [ .. ]
Firmware Version: 03.03V01
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: Tue Dec 16 17:44:53 2008 EST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
300069052416/512
586072368.000
213221352 <- error on sector (even though WD Diag Tools and smart shows the
disk as completely 100% ok)
hdparm -i
# hdparm -i /dev/sdg
/dev/sdg:
Model=WDC WD3000GLFS-01F8U0 , FwRev=03.03V01, SerialNo= [..]
Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=52
BuffType=unknown, BuffSize=16384kB, MaxMultSect=16, MultSect=?16?
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=586072368
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
hdparm -I
# hdparm -I /dev/sdg
/dev/sdg:
ATA device, with non-removable media
Model Number: WDC WD3000GLFS-01F8U0
Serial Number: [ .. ]
Firmware Revision: 03.03V01
Transport: Serial, SATA 1.0a, SATA II Extensions, SATA Rev 2.5
Standards:
Supported: 8 7 6 5
Likely used: 8
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: 586072368
device size with M = 1024*1024: 286168 MBytes
device size with M = 1000*1000: 300069 MBytes (300 GB)
Capabilities:
LBA, IORDY(can be disabled)
Queue depth: 32
Standby timer values: spec'd by Standard, with device specific minimum
R/W multiple sector transfer: Max = 16 Current = 16
Recommended acoustic management value: 128, current value: 254
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=120ns 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
* NOP cmd
* DOWNLOAD_MICROCODE
Power-Up In Standby feature set
* SET_FEATURES required to spinup after power up
SET_MAX security extension
* Automatic Acoustic Management feature set
* 48-bit Address feature set
* Device Configuration Overlay feature set
* Mandatory FLUSH_CACHE
* FLUSH_CACHE_EXT
* SMART error logging
* SMART self-test
* General Purpose Logging feature set
* WRITE_{DMA|MULTIPLE}_FUA_EXT
* 64-bit World wide name
* WRITE_UNCORRECTABLE_EXT command
* {READ,WRITE}_DMA_EXT_GPL commands
* Segmented DOWNLOAD_MICROCODE
* SATA-I signaling speed (1.5Gb/s)
* SATA-II signaling speed (3.0Gb/s)
* Native Command Queueing (NCQ)
* Phy event counters
DMA Setup Auto-Activate optimization
* Software settings preservation
* SMART Command Transport (SCT) feature set
* SCT Long Sector Access (AC1)
* SCT LBA Segment Access (AC2)
* SCT Error Recovery Control (AC3)
* SCT Features Control (AC4)
* SCT Data Tables (AC5)
unknown 206[12] (vendor specific)
unknown 206[13] (vendor specific)
Security:
Master password revision code = 65534
supported
not enabled
not locked
not frozen
not expired: security count
not supported: enhanced erase
48min for SECURITY ERASE UNIT.
Logical Unit WWN Device Identifier: 50014ee0ab4e9a45
NAA : 5
IEEE OUI : 14ee
Unique ID : 0ab4e9a45
Checksum: correct
Here is the information from older INDFs:
syslog-Nov 25 02:53:13 p34 kernel: [842744.785524] ata1: EH complete
syslog-Nov 25 02:53:13 p34 kernel: [842744.794100] sd 0:0:0:0: [sda] 586072368 512-byte hardware sectors (300069 MB)
syslog-Nov 25 02:53:13 p34 kernel: [842744.794573] sd 0:0:0:0: [sda] Write Protect is off
syslog-Nov 25 02:53:13 p34 kernel: [842744.794576] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
syslog-Nov 25 02:53:13 p34 kernel: [842744.795031] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
syslog-Nov 25 02:53:25 p34 kernel: [842756.811091] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
syslog-Nov 25 02:53:25 p34 kernel: [842756.811097] ata1.00: irq_stat 0x40000001
syslog-Nov 25 02:53:25 p34 kernel: [842756.811104] ata1.00: cmd 35/00:d0:e8:7f:b5/00:03:0c:00:00/e0 tag 0 dma 499712 out
syslog-Nov 25 02:53:25 p34 kernel: [842756.811106] res 51/10:d0:e8:7f:b5/00:03:0c:00:00/e0 Emask 0x81 (invalid argument)
syslog-Nov 25 02:53:25 p34 kernel: [842756.811110] ata1.00: status: { DRDY ERR }
syslog:Nov 25 02:53:25 p34 kernel: [842756.811113] ata1.00: error: { IDNF }
syslog-Nov 25 02:53:25 p34 kernel: [842756.834198] ata1.00: configured for UDMA/133
syslog-Nov 25 02:53:25 p34 kernel: [842756.834227] sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
syslog-Nov 25 02:53:25 p34 kernel: [842756.834231] sd 0:0:0:0: [sda] Sense Key : Aborted Command [current] [descriptor]
syslog-Nov 25 02:53:25 p34 kernel: [842756.834235] Descriptor sense data with sense descriptors (in hex):
syslog-Nov 25 02:53:25 p34 kernel: [842756.834237] 72 0b 14 00 00 00 00 0c 00 0a 80 00 00 00 00 00
syslog-Nov 25 02:53:25 p34 kernel: [842756.834243] 0c b5 7f e8
syslog-Nov 25 02:53:25 p34 kernel: [842756.834246] sd 0:0:0:0: [sda] Add. Sense: Recorded entity not found
syslog-Nov 25 02:53:25 p34 kernel: [842756.834250] end_request: I/O error, dev sda, sector 213221352
syslog-Nov 25 02:53:25 p34 kernel: [842756.834263] __ratelimit: 118 callbacks suppressed
syslog-Nov 25 02:53:25 p34 kernel: [842756.834265] Buffer I/O error on device sda, logical block 26652669
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [smartmontools-support] Velociraptor biting the dust (9th disk, continued to use it, and..)
2008-12-16 22:49 ` Justin Piszcz
@ 2008-12-17 3:52 ` Bruce Allen
0 siblings, 0 replies; 9+ messages in thread
From: Bruce Allen @ 2008-12-17 3:52 UTC (permalink / raw)
To: Justin Piszcz
Cc: linux-raid, linux-ide, Smartmontools Mailing List, Alan Piszcz,
Alan Cox
Hi Justin,
OK, this looks like a problem with the disk. The disk has 586 million
sectors, but is reporting IDNF and end-of-device errors at around sector
number 200 million.
Linux kernel jocks: ignore/delete this thread. Sorry for the noise.
Cheers,
Bruce
On Tue, 16 Dec 2008, Justin Piszcz wrote:
>
>
> On Tue, 16 Dec 2008, Bruce Allen wrote:
>
>>>>>> [632714.975844] ata1.00: status: { DRDY ERR }
>>>>>> [632714.975847] ata1.00: error: { IDNF }
>>
>>>>> IDNF - ID not found, usually these days means 'asked for a sector out of
>>>>> range'
>>
>>>> Justin, was this error provoked for example by you using a 'dd' command to
>>>> try and read stuff past the end of the disk? Because the md device driver
>>>> should not try and do something like that. The md device driver knows how
>>>> many LBAs are available on the disk and should never issue a read or write
>>>> past the end of the device.
>>>>
>>>> Justin, I have the impression that this IDNF error was NOT due to you
>>>> issuing
>>>> dd commands or similar, but was part of 'normal' md operation.
>>>>
>> When you say 'the errors occured' do you mean specifically the 'IDNF' errors?
>> Those are the onces I am talking about. I am NOT talking about other types
>> of errors like UNC or ABORT. I am ONLY talking about the IDNF errors.
>>
>> It is easy to check if the IDNF errors are from the disk firmware or the
>> Linux kernel.
>>
>> The kernel error message for IDNF should report the LBA which provoked that
>> IDNF error. Please compare that with the maximum LBA on the disk, which you
>> can get either via hdparm or smartctl -i (divide total capacity in bytes by
>> 512).
>>
>> If the LBA reported in the kernel error message is greater than the maximum
>> LBA on the disk, then the problem is in the Linux kernel. If the LBA
>> reported by the kernel is less than the maximum LBA on the disk, then the
>> problem is the disk firmware (or perhaps the disk has its capacity 'clipped'
>> with the 'Host Protected Area' feature set. But the Linux kernel should know
>> about this, so that would be a kernel bug again, not a disk firmware bug).
>>
>
> Going to plug-in one of the disks to a test system, I dare not use them in
> a real host anymore.. ok, plugged in:
>
> syslog-Nov 25 02:53:25 p34 kernel: [842756.834250] end_request: I/O error, dev sda, sector 213221352
>
> smartctl -i
>
> # smartctl -i /dev/sdg
> 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 WD3000GLFS-01F8U0
> Serial Number: [ .. ]
> Firmware Version: 03.03V01
> 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: Tue Dec 16 17:44:53 2008 EST
368> SMART support is: Available - device has SMART capability.
> SMART support is: Enabled
>
> 300069052416/512
> 586072368.000
> 213221352 <- error on sector (even though WD Diag Tools and smart shows the
> disk as completely 100% ok)
>
> hdparm -i
>
> # hdparm -i /dev/sdg
>
> /dev/sdg:
>
> Model=WDC WD3000GLFS-01F8U0 , FwRev=03.03V01, SerialNo= [..]
> Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq }
> RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=52
> BuffType=unknown, BuffSize=16384kB, MaxMultSect=16, MultSect=?16?
> CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=586072368
> 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
>
> hdparm -I
>
> # hdparm -I /dev/sdg
>
> /dev/sdg:
>
> ATA device, with non-removable media
> Model Number: WDC WD3000GLFS-01F8U0
> Serial Number: [ .. ]
> Firmware Revision: 03.03V01
> Transport: Serial, SATA 1.0a, SATA II Extensions, SATA Rev 2.5
> Standards:
> Supported: 8 7 6 5
> Likely used: 8
> 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: 586072368
> device size with M = 1024*1024: 286168 MBytes
> device size with M = 1000*1000: 300069 MBytes (300 GB)
> Capabilities:
> LBA, IORDY(can be disabled)
> Queue depth: 32
> Standby timer values: spec'd by Standard, with device specific minimum
> R/W multiple sector transfer: Max = 16 Current = 16
> Recommended acoustic management value: 128, current value: 254
> 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=120ns 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
> * NOP cmd
> * DOWNLOAD_MICROCODE
> Power-Up In Standby feature set
> * SET_FEATURES required to spinup after power up
> SET_MAX security extension
> * Automatic Acoustic Management feature set
> * 48-bit Address feature set
> * Device Configuration Overlay feature set
> * Mandatory FLUSH_CACHE
> * FLUSH_CACHE_EXT
> * SMART error logging
> * SMART self-test
> * General Purpose Logging feature set
> * WRITE_{DMA|MULTIPLE}_FUA_EXT
> * 64-bit World wide name
> * WRITE_UNCORRECTABLE_EXT command
> * {READ,WRITE}_DMA_EXT_GPL commands
> * Segmented DOWNLOAD_MICROCODE
> * SATA-I signaling speed (1.5Gb/s)
> * SATA-II signaling speed (3.0Gb/s)
> * Native Command Queueing (NCQ)
> * Phy event counters
> DMA Setup Auto-Activate optimization
> * Software settings preservation
> * SMART Command Transport (SCT) feature set
> * SCT Long Sector Access (AC1)
> * SCT LBA Segment Access (AC2)
> * SCT Error Recovery Control (AC3)
> * SCT Features Control (AC4)
> * SCT Data Tables (AC5)
> unknown 206[12] (vendor specific)
> unknown 206[13] (vendor specific)
> Security:
> Master password revision code = 65534
> supported
> not enabled
> not locked
> not frozen
> not expired: security count
> not supported: enhanced erase
> 48min for SECURITY ERASE UNIT.
> Logical Unit WWN Device Identifier: 50014ee0ab4e9a45
> NAA : 5
> IEEE OUI : 14ee
> Unique ID : 0ab4e9a45
> Checksum: correct
>
> Here is the information from older INDFs:
>
> syslog-Nov 25 02:53:13 p34 kernel: [842744.785524] ata1: EH complete
> syslog-Nov 25 02:53:13 p34 kernel: [842744.794100] sd 0:0:0:0: [sda] 586072368 512-byte hardware sectors (300069 MB)
> syslog-Nov 25 02:53:13 p34 kernel: [842744.794573] sd 0:0:0:0: [sda] Write Protect is off
> syslog-Nov 25 02:53:13 p34 kernel: [842744.794576] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> syslog-Nov 25 02:53:13 p34 kernel: [842744.795031] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
> syslog-Nov 25 02:53:25 p34 kernel: [842756.811091] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> syslog-Nov 25 02:53:25 p34 kernel: [842756.811097] ata1.00: irq_stat 0x40000001
> syslog-Nov 25 02:53:25 p34 kernel: [842756.811104] ata1.00: cmd 35/00:d0:e8:7f:b5/00:03:0c:00:00/e0 tag 0 dma 499712 out
> syslog-Nov 25 02:53:25 p34 kernel: [842756.811106] res 51/10:d0:e8:7f:b5/00:03:0c:00:00/e0 Emask 0x81 (invalid argument)
> syslog-Nov 25 02:53:25 p34 kernel: [842756.811110] ata1.00: status: { DRDY ERR }
> syslog:Nov 25 02:53:25 p34 kernel: [842756.811113] ata1.00: error: { IDNF }
> syslog-Nov 25 02:53:25 p34 kernel: [842756.834198] ata1.00: configured for UDMA/133
> syslog-Nov 25 02:53:25 p34 kernel: [842756.834227] sd 0:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
> syslog-Nov 25 02:53:25 p34 kernel: [842756.834231] sd 0:0:0:0: [sda] Sense Key : Aborted Command [current] [descriptor]
> syslog-Nov 25 02:53:25 p34 kernel: [842756.834235] Descriptor sense data with sense descriptors (in hex):
> syslog-Nov 25 02:53:25 p34 kernel: [842756.834237] 72 0b 14 00 00 00 00 0c 00 0a 80 00 00 00 00 00
> syslog-Nov 25 02:53:25 p34 kernel: [842756.834243] 0c b5 7f e8
> syslog-Nov 25 02:53:25 p34 kernel: [842756.834246] sd 0:0:0:0: [sda] Add. Sense: Recorded entity not found
> syslog-Nov 25 02:53:25 p34 kernel: [842756.834250] end_request: I/O error, dev sda, sector 213221352
> syslog-Nov 25 02:53:25 p34 kernel: [842756.834263] __ratelimit: 118 callbacks suppressed
> syslog-Nov 25 02:53:25 p34 kernel: [842756.834265] Buffer I/O error on device sda, logical block 26652669
>
>
>
> ------------------------------------------------------------------------------
> SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
> The future of the web can't happen without you. Join us at MIX09 to help
> pave the way to the Next Web now. Learn more and register at
> http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
> _______________________________________________
> Smartmontools-support mailing list
> Smartmontools-support@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/smartmontools-support
>
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2008-12-17 3:52 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-11-22 21:45 Velociraptor biting the dust (9th disk, continued to use it, and..) Justin Piszcz
2008-11-22 21:55 ` Alan Cox
2008-12-16 12:31 ` [smartmontools-support] " Bruce Allen
2008-12-16 13:07 ` Justin Piszcz
2008-12-16 13:16 ` Bruce Allen
2008-12-16 22:49 ` Justin Piszcz
2008-12-17 3:52 ` Bruce Allen
2008-11-23 1:38 ` Robert Hancock
2008-11-24 5:29 ` Tejun Heo
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).