component device mismatches found: 9600

Looking through the logs, I found this in daemon.log.0. Is this a sign
of a problem? Below is the entire log:

Jul 3 00:57:01 x64VDR mdadm[2003]: RebuildStarted event detected on md
device /dev/md0
Jul 3 00:57:02 x64VDR mdadm[2003]: RebuildStarted event detected on md
device /dev/md3
Jul 3 01:02:10 x64VDR mdadm[2003]: RebuildStarted event detected on md
device /dev/md1
Jul 3 01:02:10 x64VDR mdadm[2003]: RebuildFinished event detected on md
device /dev/md0
Jul 3 01:03:01 x64VDR mdadm[2003]: RebuildStarted event detected on md
device /dev/md2
Jul 3 01:03:01 x64VDR mdadm[2003]: RebuildFinished event detected on md
device /dev/md1, component device mismatches found: 9600
Jul 3 01:19:41 x64VDR mdadm[2003]: Rebuild29 event detected on md
device /dev/md3
Jul 3 01:19:41 x64VDR mdadm[2003]: Rebuild21 event detected on md
device /dev/md2
Jul 3 01:36:21 x64VDR mdadm[2003]: Rebuild50 event detected on md
device /dev/md3
Jul 3 01:36:21 x64VDR mdadm[2003]: Rebuild41 event detected on md
device /dev/md2
Jul 3 01:53:01 x64VDR mdadm[2003]: Rebuild67 event detected on md
device /dev/md3
Jul 3 02:09:41 x64VDR mdadm[2003]: Rebuild83 event detected on md
device /dev/md3
Jul 3 02:09:41 x64VDR mdadm[2003]: Rebuild75 event detected on md
device /dev/md2
Jul 3 02:26:21 x64VDR mdadm[2003]: Rebuild88 event detected on md
device /dev/md2
Jul 3 02:32:20 x64VDR mdadm[2003]: RebuildFinished event detected on md
device /dev/md3
Jul 3 02:43:23 x64VDR mdadm[2003]: RebuildFinished event detected on md
device /dev/md2

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: component device mismatches found: 9600

On 31 July 2011 19:24, Timothy D. Lenz wrote:
> Looking through the logs, I found this in daemon.log.0. Is this a sig=
n of a
> problem? Below is the entire log:
>
> Jul  3 00:57:01 x64VDR mdadm[2003]: RebuildStarted event detecte=
d on md
> device /dev/md0
> Jul  3 00:57:02 x64VDR mdadm[2003]: RebuildStarted event detecte=
d on md
> device /dev/md3
> Jul  3 01:02:10 x64VDR mdadm[2003]: RebuildStarted event detecte=
d on md
> device /dev/md1
> Jul  3 01:02:10 x64VDR mdadm[2003]: RebuildFinished event detect=
ed on md
> device /dev/md0
> Jul  3 01:03:01 x64VDR mdadm[2003]: RebuildStarted event detecte=
d on md
> device /dev/md2
> Jul  3 01:03:01 x64VDR mdadm[2003]: RebuildFinished event detect=
ed on md
> device /dev/md1, component device  mismatches found: 9600
> Jul  3 01:19:41 x64VDR mdadm[2003]: Rebuild29 event detected on =
md device
> /dev/md3
> Jul  3 01:19:41 x64VDR mdadm[2003]: Rebuild21 event detected on =
md device
> /dev/md2
> Jul  3 01:36:21 x64VDR mdadm[2003]: Rebuild50 event detected on =
md device
> /dev/md3
> Jul  3 01:36:21 x64VDR mdadm[2003]: Rebuild41 event detected on =
md device
> /dev/md2
> Jul  3 01:53:01 x64VDR mdadm[2003]: Rebuild67 event detected on =
md device
> /dev/md3
> Jul  3 02:09:41 x64VDR mdadm[2003]: Rebuild83 event detected on =
md device
> /dev/md3
> Jul  3 02:09:41 x64VDR mdadm[2003]: Rebuild75 event detected on =
md device
> /dev/md2
> Jul  3 02:26:21 x64VDR mdadm[2003]: Rebuild88 event detected on =
md device
> /dev/md2
> Jul  3 02:32:20 x64VDR mdadm[2003]: RebuildFinished event detect=
ed on md
> device /dev/md3
> Jul  3 02:43:23 x64VDR mdadm[2003]: RebuildFinished event detect=
ed on md
> device /dev/md2
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-raid"=
in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.ht=
ml
>

Could you post the output of:

smartctl -a /dev/your_hdd (all HDDs used by the arrays)
cat /proc/mdstat
mdadm -D /dev/md(your arrays)

/Mathias
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" i=
n
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: component device mismatches found: 9600

On 7/31/2011 11:32 AM, Mathias Burén wrote:
> On 31 July 2011 19:24, Timothy D. Lenz wrote:
>> Looking through the logs, I found this in daemon.log.0. Is this a si=
gn of a
>> problem? Below is the entire log:
>>
>> Jul 3 00:57:01 x64VDR mdadm[2003]: RebuildStarted event detected on=
md
>> device /dev/md0
>> Jul 3 00:57:02 x64VDR mdadm[2003]: RebuildStarted event detected on=
md
>> device /dev/md3
>> Jul 3 01:02:10 x64VDR mdadm[2003]: RebuildStarted event detected on=
md
>> device /dev/md1
>> Jul 3 01:02:10 x64VDR mdadm[2003]: RebuildFinished event detected o=
n md
>> device /dev/md0
>> Jul 3 01:03:01 x64VDR mdadm[2003]: RebuildStarted event detected on=
md
>> device /dev/md2
>> Jul 3 01:03:01 x64VDR mdadm[2003]: RebuildFinished event detected o=
n md
>> device /dev/md1, component device mismatches found: 9600
>> Jul 3 01:19:41 x64VDR mdadm[2003]: Rebuild29 event detected on md d=
evice
>> /dev/md3
>> Jul 3 01:19:41 x64VDR mdadm[2003]: Rebuild21 event detected on md d=
evice
>> /dev/md2
>> Jul 3 01:36:21 x64VDR mdadm[2003]: Rebuild50 event detected on md d=
evice
>> /dev/md3
>> Jul 3 01:36:21 x64VDR mdadm[2003]: Rebuild41 event detected on md d=
evice
>> /dev/md2
>> Jul 3 01:53:01 x64VDR mdadm[2003]: Rebuild67 event detected on md d=
evice
>> /dev/md3
>> Jul 3 02:09:41 x64VDR mdadm[2003]: Rebuild83 event detected on md d=
evice
>> /dev/md3
>> Jul 3 02:09:41 x64VDR mdadm[2003]: Rebuild75 event detected on md d=
evice
>> /dev/md2
>> Jul 3 02:26:21 x64VDR mdadm[2003]: Rebuild88 event detected on md d=
evice
>> /dev/md2
>> Jul 3 02:32:20 x64VDR mdadm[2003]: RebuildFinished event detected o=
n md
>> device /dev/md3
>> Jul 3 02:43:23 x64VDR mdadm[2003]: RebuildFinished event detected o=
n md
>> device /dev/md2
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-raid=
" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
> Could you post the output of:
>
> smartctl -a /dev/your_hdd (all HDDs used by the arrays)
> cat /proc/mdstat
> mdadm -D /dev/md(your arrays)
>
> /Mathias
>

Don't think I have smartctl installed. Tried with/out sudo
vorg@x64VDR:~$ smartctl -a /dev/sda
-bash: smartctl: command not found

----------------------------------------------------------
vorg@x64VDR:~$ cat /proc/mdstat
Personalities : [raid1] [raid6] [raid5] [raid4] [multipath]
md1 : active raid1 sdb2[1] sda2[0]
4891712 blocks [2/2] [UU]

md2 : active raid1 sdb3[1] sda3[0]
459073344 blocks [2/2] [UU]

md3 : active raid1 sdd1[1] sdc1[0]
488383936 blocks [2/2] [UU]

md0 : active raid1 sdb1[1] sda1[0]
24418688 blocks [2/2] [UU]

unused devices:
------------------------------------------------------------ -
vorg@x64VDR:~$ sudo mdadm -D /dev/md0
/dev/md0:
Version : 0.90
Creation Time : Sat Oct 4 14:35:45 2008
Raid Level : raid1
Array Size : 24418688 (23.29 GiB 25.00 GB)
Used Dev Size : 24418688 (23.29 GiB 25.00 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Persistence : Superblock is persistent

Update Time : Mon Aug 1 12:37:59 2011
State : active
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0

UUID : e4926be6:8d6f08e5:0ab6b006:621c4ec0 (local to host=20
x64VDR)
Events : 0.648843

Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
1 8 17 1 active sync /dev/sdb1
------------------------------------------------------------ ---------
vorg@x64VDR:~$ sudo mdadm -D /dev/md1
/dev/md1:
Version : 0.90
Creation Time : Sat Oct 4 14:42:18 2008
Raid Level : raid1
Array Size : 4891712 (4.67 GiB 5.01 GB)
Used Dev Size : 4891712 (4.67 GiB 5.01 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 1
Persistence : Superblock is persistent

Update Time : Sun Jul 31 11:45:49 2011
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0

UUID : eac96451:66efa3ab:0ab6b006:621c4ec0 (local to host=20
x64VDR)
Events : 0.550

Number Major Minor RaidDevice State
0 8 2 0 active sync /dev/sda2
1 8 18 1 active sync /dev/sdb2
------------------------------------------------------------ ---------
vorg@x64VDR:~$ sudo mdadm -D /dev/md2
/dev/md2:
Version : 0.90
Creation Time : Fri Jun 4 23:03:23 2010
Raid Level : raid1
Array Size : 459073344 (437.81 GiB 470.09 GB)
Used Dev Size : 459073344 (437.81 GiB 470.09 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 2
Persistence : Superblock is persistent

Update Time : Sun Jul 31 14:46:45 2011
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0

UUID : 934b5d12:5f83677f:0ab6b006:621c4ec0 (local to host=20
x64VDR)
Events : 0.29054

Number Major Minor RaidDevice State
0 8 3 0 active sync /dev/sda3
1 8 19 1 active sync /dev/sdb3
------------------------------------------------------------ ---------
vorg@x64VDR:~$ sudo mdadm -D /dev/md3
/dev/md3:
Version : 0.90
Creation Time : Wed Jun 2 17:54:03 2010
Raid Level : raid1
Array Size : 488383936 (465.76 GiB 500.11 GB)
Used Dev Size : 488383936 (465.76 GiB 500.11 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 3
Persistence : Superblock is persistent

Update Time : Sun Jul 31 14:46:45 2011
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0

UUID : 47b3c905:5121e149:0ab6b006:621c4ec0 (local to host=20
x64VDR)
Events : 0.2406

Number Major Minor RaidDevice State
0 8 33 0 active sync /dev/sdc1
1 8 49 1 active sync /dev/sdd1
------------------------------------------------------------ ---------
I do have it setup for email reports and last time a drive failed, that=
=20
worked. I also have gotten emails about failed syncing which only=20
happened a couple of times and it's been awhile since I got one of=20
those. Likely fixed during an update somewhere along the way. It was=20
thought to be a false report.

Received: by vorgon.com (sSMTP sendmail emulation); Sun, 13 Jun 2010=20
00:57:02 -0700
Date: Sun, 13 Jun 2010 00:57:02 -0700
=46rom: root (Cron Daemon)
To: root
Subject: Cron [ -x /usr/share/mdadm/checkarray ] && [=20
$(date +%d) -le 7 ] && /usr/share/mdadm/checkarray --cron --all --quiet=
=20
(failed)
Content-Type: text/plain; charset=3DUTF-8
X-Cron-Env:
X-Cron-Env:
X-Cron-Env:
X-Cron-Env:
Message-Id: <0MRXn6-1OqP0O1vR2-00ShUl@mrelay.perfora.net>
X-Provags-ID: V01U2FsdGVkX1/bTJj+AQvAeW7xRwAd2EQ+S8duRn/uPMxwyFG
T6yf7bTnrgufCTUjkhnj4mQsIilzGEu+VDKrLyFu7t2itTaVgM
tshSGVhqbbiQbc1myOVEg==
Envelope-To: tlenz@vorgon.com
X-Antivirus: avast! (VPS 100602-1, 06/02/2010), Inbound message
X-Antivirus-Status: Clean

command failed with exit status 1

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" i=
n
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: component device mismatches found: 9600

On 1 August 2011 20:44, Timothy D. Lenz wrote:
>
> Don't think I have smartctl installed. Tried with/out sudo
>  vorg@x64VDR:~$ smartctl -a /dev/sda
>  -bash: smartctl: command not found

So install it, or compile it from source and run it (smartmontools).
It would be interesting to see if you have a problem with
HDDs/controllers/backplanes/cables.

/M
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" i=
n
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: component device mismatches found: 9600

vorg@x64VDR:~$ sudo smartctl -a /dev/sda
smartctl 5.41 2011-06-09 r3365 [x86_64-linux-2.6.34.20100610.1] (local=20
build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.=
net

===3D START OF INFORMATION SECTION ===3D
Model Family: Seagate Barracuda 7200.11
Device Model: ST3500320AS
Serial Number: 9QM7M86S
LU WWN Device Id: 5 000c50 01059c636
=46irmware Version: SD1A
User Capacity: 500,107,862,016 bytes [500 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Mon Aug 1 16:11:16 2011 MST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

===3D START OF READ SMART DATA SECTION ===3D
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x82) Offline data collection activit=
y
was completed without error.
Auto Offline Data Collection:=20
Enabled.
Self-test execution status: ( 0) The previous self-test routine=20
completed
without error or no self-test=20
has ever
been run.
Total time to complete Offline
data collection: ( 650) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate=

Auto Offline data collection=20
on/off support.
Suspend Offline collection upo=
n new
command.
Offline surface scan supported=

Self-test supported.
Conveyance Self-test supported=

Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before enterin=
g
power-saving mode.
Supports SMART auto save timer=

Error logging capability: (0x01) Error logging supported.
General Purpose Logging suppor=
ted.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 119) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x103b) SCT Status supported.
SCT Error Recovery Control=20
supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE=20
UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 114 100 006 Pre-fail=20
Always - 82804896
3 Spin_Up_Time 0x0003 094 094 000 Pre-fail=20
Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age=20
Always - 13
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail=20
Always - 0
7 Seek_Error_Rate 0x000f 070 060 030 Pre-fail=20
Always - 12546791
9 Power_On_Hours 0x0032 095 095 000 Old_age=20
Always - 4807
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail=20
Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age=20
Always - 13
184 End-to-End_Error 0x0032 100 100 099 Old_age Alway=
s=20
- 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Alway=
s=20
- 0
188 Command_Timeout 0x0032 100 100 000 Old_age Alway=
s=20
- 0
189 High_Fly_Writes 0x003a 100 100 000 Old_age Alway=
s=20
- 0
190 Airflow_Temperature_Cel 0x0022 067 065 045 Old_age Alway=
s=20
- 33 (Min/Max 30/34)
194 Temperature_Celsius 0x0022 033 040 000 Old_age Alway=
s=20
- 33 (0 21 0 0)
195 Hardware_ECC_Recovered 0x001a 054 033 000 Old_age Alway=
s=20
- 82804896
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Alway=
s=20
- 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age=20
Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Alway=
s=20
- 0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]


SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute de=
lay.
------------------------------------------------------------ -----------=
--------------------
vorg@x64VDR:~$ sudo smartctl -a /dev/sdb
smartctl 5.41 2011-06-09 r3365 [x86_64-linux-2.6.34.20100610.1] (local=20
build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.=
net

===3D START OF INFORMATION SECTION ===3D
Model Family: Seagate Barracuda 7200.11
Device Model: ST3500320AS
Serial Number: 9QM1P092
LU WWN Device Id: 5 000c50 0098f53ba
=46irmware Version: SD15
User Capacity: 500,107,862,016 bytes [500 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Mon Aug 1 16:12:14 2011 MST

==> WARNING: There are known problems with these drives,
AND THIS FIRMWARE VERSION IS AFFECTED,
see the following Seagate web pages:
http://seagate.custkb.com/seagate/crm/selfservice/search.jsp ?DocId=3D20=
7931
http://seagate.custkb.com/seagate/crm/selfservice/search.jsp ?DocId=3D20=
7951

SMART support is: Available - device has SMART capability.
SMART support is: Enabled

===3D START OF READ SMART DATA SECTION ===3D
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x82) Offline data collection activit=
y
was completed without error.
Auto Offline Data Collection:=20
Enabled.
Self-test execution status: ( 0) The previous self-test routine=20
completed
without error or no self-test=20
has ever
been run.
Total time to complete Offline
data collection: ( 625) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate=

Auto Offline data collection=20
on/off support.
Suspend Offline collection upo=
n new
command.
Offline surface scan supported=

Self-test supported.
Conveyance Self-test supported=

Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before enterin=
g
power-saving mode.
Supports SMART auto save timer=

Error logging capability: (0x01) Error logging supported.
General Purpose Logging suppor=
ted.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 113) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x103b) SCT Status supported.
SCT Error Recovery Control=20
supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE=20
UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 113 099 006 Pre-fail=20
Always - 52352187
3 Spin_Up_Time 0x0003 094 094 000 Pre-fail=20
Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age=20
Always - 39
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail=20
Always - 0
7 Seek_Error_Rate 0x000f 078 060 030 Pre-fail=20
Always - 64855982
9 Power_On_Hours 0x0032 072 072 000 Old_age=20
Always - 24685
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail=20
Always - 0
12 Power_Cycle_Count 0x0032 100 037 020 Old_age=20
Always - 39
184 End-to-End_Error 0x0032 100 100 099 Old_age Alway=
s=20
- 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Alway=
s=20
- 0
188 Command_Timeout 0x0032 100 098 000 Old_age Alway=
s=20
- 20
189 High_Fly_Writes 0x003a 100 100 000 Old_age Alway=
s=20
- 0
190 Airflow_Temperature_Cel 0x0022 066 062 045 Old_age Alway=
s=20
- 34 (Min/Max 30/35)
194 Temperature_Celsius 0x0022 034 040 000 Old_age Alway=
s=20
- 34 (0 22 0 0)
195 Hardware_ECC_Recovered 0x001a 029 023 000 Old_age Alway=
s=20
- 52352187
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Alway=
s=20
- 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age=20
Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Alway=
s=20
- 0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]


SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute de=
lay.
------------------------------------------------------------ -----------=
--------------------
vorg@x64VDR:~$ sudo smartctl -a /dev/sdc
smartctl 5.41 2011-06-09 r3365 [x86_64-linux-2.6.34.20100610.1] (local=20
build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.=
net

===3D START OF INFORMATION SECTION ===3D
Model Family: Seagate Barracuda 7200.11
Device Model: ST3500320AS
Serial Number: 9QM35MY5
LU WWN Device Id: 5 000c50 00b9fbd80
=46irmware Version: SD15
User Capacity: 500,107,862,016 bytes [500 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Mon Aug 1 16:13:15 2011 MST

==> WARNING: There are known problems with these drives,
AND THIS FIRMWARE VERSION IS AFFECTED,
see the following Seagate web pages:
http://seagate.custkb.com/seagate/crm/selfservice/search.jsp ?DocId=3D20=
7931
http://seagate.custkb.com/seagate/crm/selfservice/search.jsp ?DocId=3D20=
7951

SMART support is: Available - device has SMART capability.
SMART support is: Enabled

===3D START OF READ SMART DATA SECTION ===3D
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x82) Offline data collection activit=
y
was completed without error.
Auto Offline Data Collection:=20
Enabled.
Self-test execution status: ( 0) The previous self-test routine=20
completed
without error or no self-test=20
has ever
been run.
Total time to complete Offline
data collection: ( 634) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate=

Auto Offline data collection=20
on/off support.
Suspend Offline collection upo=
n new
command.
Offline surface scan supported=

Self-test supported.
Conveyance Self-test supported=

Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before enterin=
g
power-saving mode.
Supports SMART auto save timer=

Error logging capability: (0x01) Error logging supported.
General Purpose Logging suppor=
ted.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 113) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x103b) SCT Status supported.
SCT Error Recovery Control=20
supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE=20
UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 119 099 006 Pre-fail=20
Always - 220520828
3 Spin_Up_Time 0x0003 094 094 000 Pre-fail=20
Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age=20
Always - 39
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail=20
Always - 0
7 Seek_Error_Rate 0x000f 074 060 030 Pre-fail=20
Always - 8642691180
9 Power_On_Hours 0x0032 072 072 000 Old_age=20
Always - 24685
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail=20
Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age=20
Always - 39
184 End-to-End_Error 0x0032 100 100 099 Old_age Alway=
s=20
- 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Alway=
s=20
- 0
188 Command_Timeout 0x0032 100 100 000 Old_age Alway=
s=20
- 0
189 High_Fly_Writes 0x003a 100 100 000 Old_age Alway=
s=20
- 0
190 Airflow_Temperature_Cel 0x0022 066 061 045 Old_age Alway=
s=20
- 34 (Min/Max 30/36)
194 Temperature_Celsius 0x0022 034 040 000 Old_age Alway=
s=20
- 34 (0 22 0 0)
195 Hardware_ECC_Recovered 0x001a 028 021 000 Old_age Alway=
s=20
- 220520828
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Alway=
s=20
- 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age=20
Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Alway=
s=20
- 0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]


SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute de=
lay.
------------------------------------------------------------ -----------=
--------------------
vorg@x64VDR:~$ sudo smartctl -a /dev/sdd
smartctl 5.41 2011-06-09 r3365 [x86_64-linux-2.6.34.20100610.1] (local=20
build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.=
net

===3D START OF INFORMATION SECTION ===3D
Model Family: Seagate Barracuda 7200.11
Device Model: ST3500820AS
Serial Number: 9QM6V6JF
LU WWN Device Id: 5 000c50 009cb8c4c
=46irmware Version: SD1A
User Capacity: 500,107,862,016 bytes [500 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Mon Aug 1 16:14:04 2011 MST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

===3D START OF READ SMART DATA SECTION ===3D
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x82) Offline data collection activit=
y
was completed without error.
Auto Offline Data Collection:=20
Enabled.
Self-test execution status: ( 0) The previous self-test routine=20
completed
without error or no self-test=20
has ever
been run.
Total time to complete Offline
data collection: ( 634) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate=

Auto Offline data collection=20
on/off support.
Suspend Offline collection upo=
n new
command.
Offline surface scan supported=

Self-test supported.
Conveyance Self-test supported=

Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before enterin=
g
power-saving mode.
Supports SMART auto save timer=

Error logging capability: (0x01) Error logging supported.
General Purpose Logging suppor=
ted.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 114) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x103b) SCT Status supported.
SCT Error Recovery Control=20
supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE=20
UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 119 099 006 Pre-fail=20
Always - 205159952
3 Spin_Up_Time 0x0003 094 094 000 Pre-fail=20
Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age=20
Always - 34
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail=20
Always - 0
7 Seek_Error_Rate 0x000f 072 060 030 Pre-fail=20
Always - 15541587
9 Power_On_Hours 0x0032 088 088 000 Old_age=20
Always - 10726
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail=20
Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age=20
Always - 34
184 End-to-End_Error 0x0032 100 100 099 Old_age Alway=
s=20
- 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Alway=
s=20
- 0
188 Command_Timeout 0x0032 100 100 000 Old_age Alway=
s=20
- 0
189 High_Fly_Writes 0x003a 100 100 000 Old_age Alway=
s=20
- 0
190 Airflow_Temperature_Cel 0x0022 065 062 045 Old_age Alway=
s=20
- 35 (Min/Max 30/37)
194 Temperature_Celsius 0x0022 035 040 000 Old_age Alway=
s=20
- 35 (0 23 0 0)
195 Hardware_ECC_Recovered 0x001a 049 023 000 Old_age Alway=
s=20
- 205159952
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Alway=
s=20
- 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age=20
Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Alway=
s=20
- 0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]


SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute de=
lay.
------------------------------------------------------------ -----------=
--------------------


On 8/1/2011 12:49 PM, Mathias Burén wrote:
> On 1 August 2011 20:44, Timothy D. Lenz wrote:
>>
>> Don't think I have smartctl installed. Tried with/out sudo
>> vorg@x64VDR:~$ smartctl -a /dev/sda
>> -bash: smartctl: command not found
>
> So install it, or compile it from source and run it (smartmontools).
> It would be interesting to see if you have a problem with
> HDDs/controllers/backplanes/cables.
>
> /M
>
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" i=
n
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: component device mismatches found: 9600

On 01/08/2011 20:44, Timothy D. Lenz wrote:
> On 7/31/2011 11:32 AM, Mathias Burén wrote:
>> On 31 July 2011 19:24, Timothy D. Lenz wrote:
>>> Looking through the logs, I found this in daemon.log.0. Is this a
>>> sign of a
>>> problem? Below is the entire log:
[...]
>>> Jul 3 01:03:01 x64VDR mdadm[2003]: RebuildFinished event detected o=
n md
>>> device /dev/md1, component device mismatches found: 9600
[...]
> md1 : active raid1 sdb2[1] sda2[0]
> 4891712 blocks [2/2] [UU]

Hmm. Is this 5GB RAID-1 your swap partition? If so, don't worry about i=
t=20
- there is an oddity that mismatches can crop up on RAID-1 arrays when =
a=20
write is abandoned after one drive has been written but the other hasn'=
t=20
(I think that's the explanation), it's most often seen on swap, and it'=
s=20
harmless.

Red Hat disabled reporting mismatches on RAID-1 because of this.

Cheers,

John.

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" i=
n
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html