* request help with RAID1 array that endlessly attempts to sync
@ 2013-12-17 6:50 Julie Ashworth
2013-12-17 16:53 ` Julie Ashworth
0 siblings, 1 reply; 12+ messages in thread
From: Julie Ashworth @ 2013-12-17 6:50 UTC (permalink / raw)
To: linux-raid
[-- Attachment #1: Type: text/plain, Size: 1516 bytes --]
hi,
I have a RAID1 array (md1) with two partitions (/dev/sda1 and /dev/sdb1).
Earlier today, I replaced /dev/sda because it had errors (reported by smartd/smartctl)
# mdadm /dev/md0 -f /dev/sda1 -r /dev/sda1
# mdadm /dev/md1 -f /dev/sda2 -r /dev/sda2
I replaced and formatted the drive and added it to the RAID1 arrays:
# mdadm /dev/md0 -a /dev/sda1
# mdadm /dev/md1 -a /dev/sda2
Everything looked great at first:
# cat /proc/mdstat
Personalities : [raid1]
md0 : active raid1 sda1[0] sdb1[1]
521984 blocks [2/2] [UU]
md1 : active raid1 sda2[2] sdb2[1]
976237824 blocks [2/1] [_U]
[====>................] recovery = 22.4% (219600512/976237824) finish=131.5min speed=95860K/sec
unused devices: <none>
But the sync restarted w/o error.
So, I ran:
# smartctl -a /dev/sdb
... which returned 3 errors.
After the second time the sync restarted, smartctl reported 24 errors on /dev/sdb. It has restarted a few times since then, but smartctl reports the same number of errors (24).
I'm enclosing the output from 'smartctl -a /dev/sdb'.
I tried to run a short selftest, but aborted it after 10 minutes. I was concerned that I shouldn't run a selftest at the same time it's rebuilding.
For what it's worth, I can't pause the sync. The command:
# echo idle > /sys/block/md1/md/sync_action
... has apparently no effect.
Can anybody make a recommendation? I'd rather not reboot, but I have a planned outage scheduled Friday.
Thanks in advance for any help,
Julie
-----------
[-- Attachment #2: smartctl.out --]
[-- Type: text/plain, Size: 9201 bytes --]
smartctl version 5.38 [x86_64-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Device Model: ST31000340NS
Serial Number: 9QJ6Y79S
Firmware Version: SN06
User Capacity: 1,000,204,886,016 bytes
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Mon Dec 16 22:27:54 2013 PST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 22) The self-test routine was aborted by
the host.
Total time to complete Offline
data collection: ( 625) 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: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 220) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x103d) SCT Status 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 UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 079 062 044 Pre-fail Always - 94946845
3 Spin_Up_Time 0x0003 099 099 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 29
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 3
7 Seek_Error_Rate 0x000f 081 060 030 Pre-fail Always - 131642238
9 Power_On_Hours 0x0032 067 067 000 Old_age Always - 29562
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 037 020 Old_age Always - 29
184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 098 098 000 Old_age Always - 2
188 Unknown_Attribute 0x0032 100 096 000 Old_age Always - 42950328381
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 078 060 045 Old_age Always - 22 (Lifetime Min/Max 18/40)
194 Temperature_Celsius 0x0022 022 040 000 Old_age Always - 22 (0 15 0 0)
195 Hardware_ECC_Recovered 0x001a 064 048 000 Old_age Always - 94946845
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 1
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 1
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 24 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 24 occurred at disk power-on lifetime: 29559 hours (1231 days + 15 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 08 ff ff ff 4f 00 23d+11:18:28.172 READ FPDMA QUEUED
27 00 00 00 00 00 e0 00 23d+11:18:28.145 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 23d+11:18:28.143 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 23d+11:18:28.130 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 00 23d+11:18:28.102 READ NATIVE MAX ADDRESS EXT
Error 23 occurred at disk power-on lifetime: 29559 hours (1231 days + 15 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 08 ff ff ff 4f 00 23d+11:18:25.024 READ FPDMA QUEUED
27 00 00 00 00 00 e0 00 23d+11:18:24.996 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 23d+11:18:24.995 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 23d+11:18:24.982 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 00 23d+11:18:24.954 READ NATIVE MAX ADDRESS EXT
Error 22 occurred at disk power-on lifetime: 29559 hours (1231 days + 15 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 08 ff ff ff 4f 00 23d+11:18:21.884 READ FPDMA QUEUED
27 00 00 00 00 00 e0 00 23d+11:18:21.856 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 23d+11:18:21.855 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 23d+11:18:21.841 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 00 23d+11:18:21.814 READ NATIVE MAX ADDRESS EXT
Error 21 occurred at disk power-on lifetime: 29559 hours (1231 days + 15 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 08 ff ff ff 4f 00 23d+11:18:18.752 READ FPDMA QUEUED
27 00 00 00 00 00 e0 00 23d+11:18:18.724 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 23d+11:18:18.723 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 23d+11:18:18.710 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 00 23d+11:18:18.682 READ NATIVE MAX ADDRESS EXT
Error 20 occurred at disk power-on lifetime: 29559 hours (1231 days + 15 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 08 ff ff ff 4f 00 23d+11:18:15.645 READ FPDMA QUEUED
27 00 00 00 00 00 e0 00 23d+11:18:15.617 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 23d+11:18:15.616 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 23d+11:18:15.603 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 00 23d+11:18:15.575 READ NATIVE MAX ADDRESS EXT
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Aborted by host 60% 29560 -
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] 12+ messages in thread
* Re: request help with RAID1 array that endlessly attempts to sync
2013-12-17 6:50 request help with RAID1 array that endlessly attempts to sync Julie Ashworth
@ 2013-12-17 16:53 ` Julie Ashworth
2013-12-17 17:55 ` Phil Turmel
2013-12-17 18:12 ` Wilson Jonathan
0 siblings, 2 replies; 12+ messages in thread
From: Julie Ashworth @ 2013-12-17 16:53 UTC (permalink / raw)
To: linux-raid
hi all,
The sync ran overnight, and smartctl reports 60 errors on /dev/sdb this morning. So, it seems like the drive is doomed.
It's frustrating, because this has happened twice in the last month, where a disk failed in a RAID1, I replaced the drive, and the 'good' drive failed during the sync. Last time I rebuilt from scratch. I presume that is my fate this time.
I plan to use RAID6 in the future, but I still have important servers with RAID1 arrays. Do you folks recommend replacing HDDs before they report errors? The drives are all ~3 years old - Seagate.
I should probably stop the sync. I presume the best way to do this is to fail/remove /dev/sda (the new disk).
Thanks again!
best,
Julie
On 16-12-2013 22.50 -0800, Julie Ashworth wrote:
> hi,
> I have a RAID1 array (md1) with two partitions (/dev/sda1 and /dev/sdb1).
>
> Earlier today, I replaced /dev/sda because it had errors (reported by smartd/smartctl)
> # mdadm /dev/md0 -f /dev/sda1 -r /dev/sda1
> # mdadm /dev/md1 -f /dev/sda2 -r /dev/sda2
>
> I replaced and formatted the drive and added it to the RAID1 arrays:
>
> # mdadm /dev/md0 -a /dev/sda1
> # mdadm /dev/md1 -a /dev/sda2
>
> Everything looked great at first:
> # cat /proc/mdstat
> Personalities : [raid1]
> md0 : active raid1 sda1[0] sdb1[1]
> 521984 blocks [2/2] [UU]
>
> md1 : active raid1 sda2[2] sdb2[1]
> 976237824 blocks [2/1] [_U]
> [====>................] recovery = 22.4% (219600512/976237824) finish=131.5min speed=95860K/sec
>
> unused devices: <none>
>
>
> But the sync restarted w/o error.
>
> So, I ran:
> # smartctl -a /dev/sdb
>
> ... which returned 3 errors.
>
> After the second time the sync restarted, smartctl reported 24 errors on /dev/sdb. It has restarted a few times since then, but smartctl reports the same number of errors (24).
>
> I'm enclosing the output from 'smartctl -a /dev/sdb'.
> I tried to run a short selftest, but aborted it after 10 minutes. I was concerned that I shouldn't run a selftest at the same time it's rebuilding.
>
> For what it's worth, I can't pause the sync. The command:
>
> # echo idle > /sys/block/md1/md/sync_action
>
> ... has apparently no effect.
>
> Can anybody make a recommendation? I'd rather not reboot, but I have a planned outage scheduled Friday.
>
> Thanks in advance for any help,
> Julie
> -----------
>
>
>
> smartctl version 5.38 [x86_64-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen
> Home page is http://smartmontools.sourceforge.net/
>
> === START OF INFORMATION SECTION ===
> Device Model: ST31000340NS
> Serial Number: 9QJ6Y79S
> Firmware Version: SN06
> User Capacity: 1,000,204,886,016 bytes
> Device is: Not in smartctl database [for details use: -P showall]
> ATA Version is: 8
> ATA Standard is: ATA-8-ACS revision 4
> Local Time is: Mon Dec 16 22:27:54 2013 PST
> SMART support is: Available - device has SMART capability.
> SMART support is: Enabled
>
> === START OF READ SMART DATA SECTION ===
> SMART overall-health self-assessment test result: PASSED
>
> General SMART Values:
> Offline data collection status: (0x82) Offline data collection activity
> was completed without error.
> Auto Offline Data Collection: Enabled.
> Self-test execution status: ( 22) The self-test routine was aborted by
> the host.
> Total time to complete Offline
> data collection: ( 625) 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: ( 1) minutes.
> Extended self-test routine
> recommended polling time: ( 220) minutes.
> Conveyance self-test routine
> recommended polling time: ( 2) minutes.
> SCT capabilities: (0x103d) SCT Status 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 UPDATED WHEN_FAILED RAW_VALUE
> 1 Raw_Read_Error_Rate 0x000f 079 062 044 Pre-fail Always - 94946845
> 3 Spin_Up_Time 0x0003 099 099 000 Pre-fail Always - 0
> 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 29
> 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 3
> 7 Seek_Error_Rate 0x000f 081 060 030 Pre-fail Always - 131642238
> 9 Power_On_Hours 0x0032 067 067 000 Old_age Always - 29562
> 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
> 12 Power_Cycle_Count 0x0032 100 037 020 Old_age Always - 29
> 184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0
> 187 Reported_Uncorrect 0x0032 098 098 000 Old_age Always - 2
> 188 Unknown_Attribute 0x0032 100 096 000 Old_age Always - 42950328381
> 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
> 190 Airflow_Temperature_Cel 0x0022 078 060 045 Old_age Always - 22 (Lifetime Min/Max 18/40)
> 194 Temperature_Celsius 0x0022 022 040 000 Old_age Always - 22 (0 15 0 0)
> 195 Hardware_ECC_Recovered 0x001a 064 048 000 Old_age Always - 94946845
> 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 1
> 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 1
> 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
>
> SMART Error Log Version: 1
> ATA Error Count: 24 (device log contains only the most recent five errors)
> CR = Command Register [HEX]
> FR = Features Register [HEX]
> SC = Sector Count Register [HEX]
> SN = Sector Number Register [HEX]
> CL = Cylinder Low Register [HEX]
> CH = Cylinder High Register [HEX]
> DH = Device/Head Register [HEX]
> DC = Device Command Register [HEX]
> ER = Error register [HEX]
> ST = Status register [HEX]
> Powered_Up_Time is measured from power on, and printed as
> DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
> SS=sec, and sss=millisec. It "wraps" after 49.710 days.
>
> Error 24 occurred at disk power-on lifetime: 29559 hours (1231 days + 15 hours)
> When the command that caused the error occurred, the device was active or idle.
>
> After command completion occurred, registers were:
> ER ST SC SN CL CH DH
> -- -- -- -- -- -- --
> 40 51 00 ff ff ff 0f
>
> Commands leading to the command that caused the error were:
> CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
> -- -- -- -- -- -- -- -- ---------------- --------------------
> 60 00 08 ff ff ff 4f 00 23d+11:18:28.172 READ FPDMA QUEUED
> 27 00 00 00 00 00 e0 00 23d+11:18:28.145 READ NATIVE MAX ADDRESS EXT
> ec 00 00 00 00 00 a0 00 23d+11:18:28.143 IDENTIFY DEVICE
> ef 03 46 00 00 00 a0 00 23d+11:18:28.130 SET FEATURES [Set transfer mode]
> 27 00 00 00 00 00 e0 00 23d+11:18:28.102 READ NATIVE MAX ADDRESS EXT
>
> Error 23 occurred at disk power-on lifetime: 29559 hours (1231 days + 15 hours)
> When the command that caused the error occurred, the device was active or idle.
>
> After command completion occurred, registers were:
> ER ST SC SN CL CH DH
> -- -- -- -- -- -- --
> 40 51 00 ff ff ff 0f
>
> Commands leading to the command that caused the error were:
> CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
> -- -- -- -- -- -- -- -- ---------------- --------------------
> 60 00 08 ff ff ff 4f 00 23d+11:18:25.024 READ FPDMA QUEUED
> 27 00 00 00 00 00 e0 00 23d+11:18:24.996 READ NATIVE MAX ADDRESS EXT
> ec 00 00 00 00 00 a0 00 23d+11:18:24.995 IDENTIFY DEVICE
> ef 03 46 00 00 00 a0 00 23d+11:18:24.982 SET FEATURES [Set transfer mode]
> 27 00 00 00 00 00 e0 00 23d+11:18:24.954 READ NATIVE MAX ADDRESS EXT
>
> Error 22 occurred at disk power-on lifetime: 29559 hours (1231 days + 15 hours)
> When the command that caused the error occurred, the device was active or idle.
>
> After command completion occurred, registers were:
> ER ST SC SN CL CH DH
> -- -- -- -- -- -- --
> 40 51 00 ff ff ff 0f
>
> Commands leading to the command that caused the error were:
> CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
> -- -- -- -- -- -- -- -- ---------------- --------------------
> 60 00 08 ff ff ff 4f 00 23d+11:18:21.884 READ FPDMA QUEUED
> 27 00 00 00 00 00 e0 00 23d+11:18:21.856 READ NATIVE MAX ADDRESS EXT
> ec 00 00 00 00 00 a0 00 23d+11:18:21.855 IDENTIFY DEVICE
> ef 03 46 00 00 00 a0 00 23d+11:18:21.841 SET FEATURES [Set transfer mode]
> 27 00 00 00 00 00 e0 00 23d+11:18:21.814 READ NATIVE MAX ADDRESS EXT
>
> Error 21 occurred at disk power-on lifetime: 29559 hours (1231 days + 15 hours)
> When the command that caused the error occurred, the device was active or idle.
>
> After command completion occurred, registers were:
> ER ST SC SN CL CH DH
> -- -- -- -- -- -- --
> 40 51 00 ff ff ff 0f
>
> Commands leading to the command that caused the error were:
> CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
> -- -- -- -- -- -- -- -- ---------------- --------------------
> 60 00 08 ff ff ff 4f 00 23d+11:18:18.752 READ FPDMA QUEUED
> 27 00 00 00 00 00 e0 00 23d+11:18:18.724 READ NATIVE MAX ADDRESS EXT
> ec 00 00 00 00 00 a0 00 23d+11:18:18.723 IDENTIFY DEVICE
> ef 03 46 00 00 00 a0 00 23d+11:18:18.710 SET FEATURES [Set transfer mode]
> 27 00 00 00 00 00 e0 00 23d+11:18:18.682 READ NATIVE MAX ADDRESS EXT
>
> Error 20 occurred at disk power-on lifetime: 29559 hours (1231 days + 15 hours)
> When the command that caused the error occurred, the device was active or idle.
>
> After command completion occurred, registers were:
> ER ST SC SN CL CH DH
> -- -- -- -- -- -- --
> 40 51 00 ff ff ff 0f
>
> Commands leading to the command that caused the error were:
> CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
> -- -- -- -- -- -- -- -- ---------------- --------------------
> 60 00 08 ff ff ff 4f 00 23d+11:18:15.645 READ FPDMA QUEUED
> 27 00 00 00 00 00 e0 00 23d+11:18:15.617 READ NATIVE MAX ADDRESS EXT
> ec 00 00 00 00 00 a0 00 23d+11:18:15.616 IDENTIFY DEVICE
> ef 03 46 00 00 00 a0 00 23d+11:18:15.603 SET FEATURES [Set transfer mode]
> 27 00 00 00 00 00 e0 00 23d+11:18:15.575 READ NATIVE MAX ADDRESS EXT
>
> SMART Self-test log structure revision number 1
> Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
> # 1 Short offline Aborted by host 60% 29560 -
>
> 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.
>
---end quoted text---
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: request help with RAID1 array that endlessly attempts to sync
2013-12-17 16:53 ` Julie Ashworth
@ 2013-12-17 17:55 ` Phil Turmel
2013-12-17 19:26 ` Julie Ashworth
2013-12-17 18:12 ` Wilson Jonathan
1 sibling, 1 reply; 12+ messages in thread
From: Phil Turmel @ 2013-12-17 17:55 UTC (permalink / raw)
To: Julie Ashworth, linux-raid
Hi Julie,
On 12/17/2013 11:53 AM, Julie Ashworth wrote:
> hi all, The sync ran overnight, and smartctl reports 60 errors on
> /dev/sdb this morning. So, it seems like the drive is doomed.
You haven't actually posted enough data from smartctl to say that,
though failures in the vicinity of three years is not surprising.
Please post the output of "smartctl -x" for both of these drives.
> It's frustrating, because this has happened twice in the last month,
> where a disk failed in a RAID1, I replaced the drive, and the 'good'
> drive failed during the sync. Last time I rebuilt from scratch. I
> presume that is my fate this time.
"Good drives failing during rebuild" is a big red flag suggesting
timeout mismatches combined with lack of scrubbing.
> I plan to use RAID6 in the future, but I still have important servers
> with RAID1 arrays. Do you folks recommend replacing HDDs before they
> report errors? The drives are all ~3 years old - Seagate.
I replace drives when they reach 10 relocations, given weekly scrubs.
> I should probably stop the sync. I presume the best way to do this is
> to fail/remove /dev/sda (the new disk).
Maybe not. Please tell us you know all about error recovery timeouts
and the timeout mismatch problem commonly encountered with
consumer-grade hard drives. Otherwise, you might want search the list
archives for various combinations of the keywords "scterc", "error
recovery", "timeout mismatch", "URE", and/or "bit error rate".
Phil
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: request help with RAID1 array that endlessly attempts to sync
2013-12-17 16:53 ` Julie Ashworth
2013-12-17 17:55 ` Phil Turmel
@ 2013-12-17 18:12 ` Wilson Jonathan
1 sibling, 0 replies; 12+ messages in thread
From: Wilson Jonathan @ 2013-12-17 18:12 UTC (permalink / raw)
To: Julie Ashworth; +Cc: linux-raid
On Tue, 2013-12-17 at 08:53 -0800, Julie Ashworth wrote:
> hi all,
> The sync ran overnight, and smartctl reports 60 errors on /dev/sdb this morning. So, it seems like the drive is doomed.
>
> It's frustrating, because this has happened twice in the last month, where a disk failed in a RAID1, I replaced the drive, and the 'good' drive failed during the sync. Last time I rebuilt from scratch. I presume that is my fate this time.
>
> I plan to use RAID6 in the future, but I still have important servers with RAID1 arrays. Do you folks recommend replacing HDDs before they report errors? The drives are all ~3 years old - Seagate.
>
> I should probably stop the sync. I presume the best way to do this is to fail/remove /dev/sda (the new disk).
>
> Thanks again!
> best,
> Julie
I'm beginning to think that some kind of pro-active disk replacement is
not a bad thing, especially after degrading a 6 drive raid 6 (managed to
pull 3 drives by mistake, eventually recovered it) when replacing 3
drives (in theory one at a time was my plan) and as I was lacking a
backup re-used 2 of the drives as a temp back up media and had one of
them go wonky with bad writes (reallocated) that had been working
flawlessly... for nearly 4 years!!
I also managed to pull one of my "os" raid1 disks, which also included a
large static data set of raw photo files, and the recovery was painful
as the still working drive started reporting an increase in "195 crc
recovered" errors in s.m.a.r.t which I had never noticed before.
As I'm a "home user" I think my best option is to 1, have at least one
"spare" drive on my raid6 (just in case) and over time purchase
additional replacements and every so often (about 2 years in rotation, 1
a year) fail the oldest, remove it, sync a brand new drive. Test the
removed drive and use it as a "last chance, maybe" backup. (or if I can
get the funds together over a year build a whole new "rsync style"
system that is only powered on for backups, I have some bits already
from older systems)
For my Raid1 disks I think I will get a new drive, add it, increase the
raid to 3 disks, let it sync, fail the "danger drive" and then drop the
count back to 2 disks... then set up a spare... again I think that I'll
start to replace a disk every 2 years in rotation.
Saving up for 2 disks a year is a negligable amount each month, having
the worry of a raid with part missing while I scrable to get the cash
together for a week or so is more than my rapidly greying hair will
stand; its bad enough when the family starts moaning because the server
is being re-booted ;-)
I would love to have some kind of genuine tape backup (I'm from IBM
AS/400 background originally) but a tape system for TB's of data is way
out of reach for a home user (circa 4K+ as far as I can tell) as
"backup" has not kept pace, or price, with raw disk storage and the ease
at which any home user can "simply" set up massive raid storage.
>
>
>
> On 16-12-2013 22.50 -0800, Julie Ashworth wrote:
> > hi,
> > I have a RAID1 array (md1) with two partitions (/dev/sda1 and /dev/sdb1).
> >
> > Earlier today, I replaced /dev/sda because it had errors (reported by smartd/smartctl)
> > # mdadm /dev/md0 -f /dev/sda1 -r /dev/sda1
> > # mdadm /dev/md1 -f /dev/sda2 -r /dev/sda2
> >
> > I replaced and formatted the drive and added it to the RAID1 arrays:
> >
> > # mdadm /dev/md0 -a /dev/sda1
> > # mdadm /dev/md1 -a /dev/sda2
> >
> > Everything looked great at first:
> > # cat /proc/mdstat
> > Personalities : [raid1]
> > md0 : active raid1 sda1[0] sdb1[1]
> > 521984 blocks [2/2] [UU]
> >
> > md1 : active raid1 sda2[2] sdb2[1]
> > 976237824 blocks [2/1] [_U]
> > [====>................] recovery = 22.4% (219600512/976237824) finish=131.5min speed=95860K/sec
> >
> > unused devices: <none>
> >
> >
> > But the sync restarted w/o error.
> >
> > So, I ran:
> > # smartctl -a /dev/sdb
> >
> > ... which returned 3 errors.
> >
> > After the second time the sync restarted, smartctl reported 24 errors on /dev/sdb. It has restarted a few times since then, but smartctl reports the same number of errors (24).
> >
> > I'm enclosing the output from 'smartctl -a /dev/sdb'.
> > I tried to run a short selftest, but aborted it after 10 minutes. I was concerned that I shouldn't run a selftest at the same time it's rebuilding.
> >
> > For what it's worth, I can't pause the sync. The command:
> >
> > # echo idle > /sys/block/md1/md/sync_action
> >
> > ... has apparently no effect.
> >
> > Can anybody make a recommendation? I'd rather not reboot, but I have a planned outage scheduled Friday.
> >
> > Thanks in advance for any help,
> > Julie
> > -----------
> >
> >
> >
>
> > smartctl version 5.38 [x86_64-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen
> > Home page is http://smartmontools.sourceforge.net/
> >
> > === START OF INFORMATION SECTION ===
> > Device Model: ST31000340NS
> > Serial Number: 9QJ6Y79S
> > Firmware Version: SN06
> > User Capacity: 1,000,204,886,016 bytes
> > Device is: Not in smartctl database [for details use: -P showall]
> > ATA Version is: 8
> > ATA Standard is: ATA-8-ACS revision 4
> > Local Time is: Mon Dec 16 22:27:54 2013 PST
> > SMART support is: Available - device has SMART capability.
> > SMART support is: Enabled
> >
> > === START OF READ SMART DATA SECTION ===
> > SMART overall-health self-assessment test result: PASSED
> >
> > General SMART Values:
> > Offline data collection status: (0x82) Offline data collection activity
> > was completed without error.
> > Auto Offline Data Collection: Enabled.
> > Self-test execution status: ( 22) The self-test routine was aborted by
> > the host.
> > Total time to complete Offline
> > data collection: ( 625) 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: ( 1) minutes.
> > Extended self-test routine
> > recommended polling time: ( 220) minutes.
> > Conveyance self-test routine
> > recommended polling time: ( 2) minutes.
> > SCT capabilities: (0x103d) SCT Status 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 UPDATED WHEN_FAILED RAW_VALUE
> > 1 Raw_Read_Error_Rate 0x000f 079 062 044 Pre-fail Always - 94946845
> > 3 Spin_Up_Time 0x0003 099 099 000 Pre-fail Always - 0
> > 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 29
> > 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 3
> > 7 Seek_Error_Rate 0x000f 081 060 030 Pre-fail Always - 131642238
> > 9 Power_On_Hours 0x0032 067 067 000 Old_age Always - 29562
> > 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
> > 12 Power_Cycle_Count 0x0032 100 037 020 Old_age Always - 29
> > 184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0
> > 187 Reported_Uncorrect 0x0032 098 098 000 Old_age Always - 2
> > 188 Unknown_Attribute 0x0032 100 096 000 Old_age Always - 42950328381
> > 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
> > 190 Airflow_Temperature_Cel 0x0022 078 060 045 Old_age Always - 22 (Lifetime Min/Max 18/40)
> > 194 Temperature_Celsius 0x0022 022 040 000 Old_age Always - 22 (0 15 0 0)
> > 195 Hardware_ECC_Recovered 0x001a 064 048 000 Old_age Always - 94946845
> > 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 1
> > 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 1
> > 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
> >
> > SMART Error Log Version: 1
> > ATA Error Count: 24 (device log contains only the most recent five errors)
> > CR = Command Register [HEX]
> > FR = Features Register [HEX]
> > SC = Sector Count Register [HEX]
> > SN = Sector Number Register [HEX]
> > CL = Cylinder Low Register [HEX]
> > CH = Cylinder High Register [HEX]
> > DH = Device/Head Register [HEX]
> > DC = Device Command Register [HEX]
> > ER = Error register [HEX]
> > ST = Status register [HEX]
> > Powered_Up_Time is measured from power on, and printed as
> > DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
> > SS=sec, and sss=millisec. It "wraps" after 49.710 days.
> >
> > Error 24 occurred at disk power-on lifetime: 29559 hours (1231 days + 15 hours)
> > When the command that caused the error occurred, the device was active or idle.
> >
> > After command completion occurred, registers were:
> > ER ST SC SN CL CH DH
> > -- -- -- -- -- -- --
> > 40 51 00 ff ff ff 0f
> >
> > Commands leading to the command that caused the error were:
> > CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
> > -- -- -- -- -- -- -- -- ---------------- --------------------
> > 60 00 08 ff ff ff 4f 00 23d+11:18:28.172 READ FPDMA QUEUED
> > 27 00 00 00 00 00 e0 00 23d+11:18:28.145 READ NATIVE MAX ADDRESS EXT
> > ec 00 00 00 00 00 a0 00 23d+11:18:28.143 IDENTIFY DEVICE
> > ef 03 46 00 00 00 a0 00 23d+11:18:28.130 SET FEATURES [Set transfer mode]
> > 27 00 00 00 00 00 e0 00 23d+11:18:28.102 READ NATIVE MAX ADDRESS EXT
> >
> > Error 23 occurred at disk power-on lifetime: 29559 hours (1231 days + 15 hours)
> > When the command that caused the error occurred, the device was active or idle.
> >
> > After command completion occurred, registers were:
> > ER ST SC SN CL CH DH
> > -- -- -- -- -- -- --
> > 40 51 00 ff ff ff 0f
> >
> > Commands leading to the command that caused the error were:
> > CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
> > -- -- -- -- -- -- -- -- ---------------- --------------------
> > 60 00 08 ff ff ff 4f 00 23d+11:18:25.024 READ FPDMA QUEUED
> > 27 00 00 00 00 00 e0 00 23d+11:18:24.996 READ NATIVE MAX ADDRESS EXT
> > ec 00 00 00 00 00 a0 00 23d+11:18:24.995 IDENTIFY DEVICE
> > ef 03 46 00 00 00 a0 00 23d+11:18:24.982 SET FEATURES [Set transfer mode]
> > 27 00 00 00 00 00 e0 00 23d+11:18:24.954 READ NATIVE MAX ADDRESS EXT
> >
> > Error 22 occurred at disk power-on lifetime: 29559 hours (1231 days + 15 hours)
> > When the command that caused the error occurred, the device was active or idle.
> >
> > After command completion occurred, registers were:
> > ER ST SC SN CL CH DH
> > -- -- -- -- -- -- --
> > 40 51 00 ff ff ff 0f
> >
> > Commands leading to the command that caused the error were:
> > CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
> > -- -- -- -- -- -- -- -- ---------------- --------------------
> > 60 00 08 ff ff ff 4f 00 23d+11:18:21.884 READ FPDMA QUEUED
> > 27 00 00 00 00 00 e0 00 23d+11:18:21.856 READ NATIVE MAX ADDRESS EXT
> > ec 00 00 00 00 00 a0 00 23d+11:18:21.855 IDENTIFY DEVICE
> > ef 03 46 00 00 00 a0 00 23d+11:18:21.841 SET FEATURES [Set transfer mode]
> > 27 00 00 00 00 00 e0 00 23d+11:18:21.814 READ NATIVE MAX ADDRESS EXT
> >
> > Error 21 occurred at disk power-on lifetime: 29559 hours (1231 days + 15 hours)
> > When the command that caused the error occurred, the device was active or idle.
> >
> > After command completion occurred, registers were:
> > ER ST SC SN CL CH DH
> > -- -- -- -- -- -- --
> > 40 51 00 ff ff ff 0f
> >
> > Commands leading to the command that caused the error were:
> > CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
> > -- -- -- -- -- -- -- -- ---------------- --------------------
> > 60 00 08 ff ff ff 4f 00 23d+11:18:18.752 READ FPDMA QUEUED
> > 27 00 00 00 00 00 e0 00 23d+11:18:18.724 READ NATIVE MAX ADDRESS EXT
> > ec 00 00 00 00 00 a0 00 23d+11:18:18.723 IDENTIFY DEVICE
> > ef 03 46 00 00 00 a0 00 23d+11:18:18.710 SET FEATURES [Set transfer mode]
> > 27 00 00 00 00 00 e0 00 23d+11:18:18.682 READ NATIVE MAX ADDRESS EXT
> >
> > Error 20 occurred at disk power-on lifetime: 29559 hours (1231 days + 15 hours)
> > When the command that caused the error occurred, the device was active or idle.
> >
> > After command completion occurred, registers were:
> > ER ST SC SN CL CH DH
> > -- -- -- -- -- -- --
> > 40 51 00 ff ff ff 0f
> >
> > Commands leading to the command that caused the error were:
> > CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
> > -- -- -- -- -- -- -- -- ---------------- --------------------
> > 60 00 08 ff ff ff 4f 00 23d+11:18:15.645 READ FPDMA QUEUED
> > 27 00 00 00 00 00 e0 00 23d+11:18:15.617 READ NATIVE MAX ADDRESS EXT
> > ec 00 00 00 00 00 a0 00 23d+11:18:15.616 IDENTIFY DEVICE
> > ef 03 46 00 00 00 a0 00 23d+11:18:15.603 SET FEATURES [Set transfer mode]
> > 27 00 00 00 00 00 e0 00 23d+11:18:15.575 READ NATIVE MAX ADDRESS EXT
> >
> > SMART Self-test log structure revision number 1
> > Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
> > # 1 Short offline Aborted by host 60% 29560 -
> >
> > 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.
> >
>
> ---end quoted text---
> --
> 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
>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: request help with RAID1 array that endlessly attempts to sync
2013-12-17 17:55 ` Phil Turmel
@ 2013-12-17 19:26 ` Julie Ashworth
2013-12-17 19:43 ` Phil Turmel
0 siblings, 1 reply; 12+ messages in thread
From: Julie Ashworth @ 2013-12-17 19:26 UTC (permalink / raw)
To: Phil Turmel; +Cc: linux-raid
[-- Attachment #1: Type: text/plain, Size: 1649 bytes --]
Thanks Phil,
I should note that the drives are labelled "enterprise", purchased from a hw RAID vendor (ACNC.com).
On 17-12-2013 12.55 -0500, Phil Turmel wrote:
> Please post the output of "smartctl -x" for both of these drives.
The Centos5 smartctl (from smartmontools rpm) doesn't support the -x option. However, it's apparently equivelent to:
smartctl -H -i -g all -c -A -f brief -l xerror,error -l xselftest,selftest -l selective -l directory -l scttemp -l scterc -l devstat -l sataphy
Centos5 smartctl supports the following:
smartctl -H -i -c -A -l error -l selftest -l selective -l directory -l scttemp -l scttempsts -l scttemphist
... and I enclosed the output for sda and sdb.
If you think it would be useful to have the additional options (provided by -x), then let me know, and I'll try to build it.
> timeout mismatches combined with lack of scrubbing.
I've read about mismatches, but not about scrubbing. I'll investigate this.
What program/options do your weekly scrub?
> Maybe not. Please tell us you know all about error recovery timeouts
Instead of stopping the sync, I decided to slow it down:
echo 1001 > /proc/sys/dev/raid/speed_limit_max
> and the timeout mismatch problem commonly encountered with
> consumer-grade hard drives. Otherwise, you might want search the list
> archives for various combinations of the keywords "scterc", "error
> recovery", "timeout mismatch", "URE", and/or "bit error rate".
I'm not a big fan of Seagate (enterprise or not). The drives I purchased before these (~2008) needed to have firmware updates to prevent bricking. Sigh.
Thanks for your help and search tips.
best,
Julie
----
[-- Attachment #2: smartctl.sda.out --]
[-- Type: text/plain, Size: 7817 bytes --]
smartctl version 5.38 [x86_64-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Device Model: Hitachi HUA722010CLA330
Serial Number: JPW9J0N12TGPJV
Firmware Version: JP4OA3EA
User Capacity: 1,000,204,886,016 bytes
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Tue Dec 17 11:14:24 2013 PST
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: (0x84) Offline data collection activity
was suspended by an interrupting command from host.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (9337) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 156) minutes.
SCT capabilities: (0x003d) 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 0x000b 100 100 016 Pre-fail Always - 0
2 Throughput_Performance 0x0005 137 137 054 Pre-fail Offline - 90
3 Spin_Up_Time 0x0007 100 100 024 Pre-fail Always - 249
4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 5
5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0
7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 142 142 020 Pre-fail Offline - 29
9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 46
10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 5
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 6
193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 6
194 Temperature_Celsius 0x0002 253 253 000 Old_age Always - 22 (Lifetime Min/Max 20/37)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0
Log Directory Supported
SMART Log Directory Logging Version 1 [multi-sector log support]
Log at address 0x00 has 001 sectors [Log Directory]
Log at address 0x01 has 001 sectors [Summary SMART error log]
Log at address 0x06 has 001 sectors [SMART self-test log]
Log at address 0x09 has 001 sectors [Selective self-test log]
Log at address 0x80 has 016 sectors [Host vendor specific log]
Log at address 0x81 has 016 sectors [Host vendor specific log]
Log at address 0x82 has 016 sectors [Host vendor specific log]
Log at address 0x83 has 016 sectors [Host vendor specific log]
Log at address 0x84 has 016 sectors [Host vendor specific log]
Log at address 0x85 has 016 sectors [Host vendor specific log]
Log at address 0x86 has 016 sectors [Host vendor specific log]
Log at address 0x87 has 016 sectors [Host vendor specific log]
Log at address 0x88 has 016 sectors [Host vendor specific log]
Log at address 0x89 has 016 sectors [Host vendor specific log]
Log at address 0x8a has 016 sectors [Host vendor specific log]
Log at address 0x8b has 016 sectors [Host vendor specific log]
Log at address 0x8c has 016 sectors [Host vendor specific log]
Log at address 0x8d has 016 sectors [Host vendor specific log]
Log at address 0x8e has 016 sectors [Host vendor specific log]
Log at address 0x8f has 016 sectors [Host vendor specific log]
Log at address 0x90 has 016 sectors [Host vendor specific log]
Log at address 0x91 has 016 sectors [Host vendor specific log]
Log at address 0x92 has 016 sectors [Host vendor specific log]
Log at address 0x93 has 016 sectors [Host vendor specific log]
Log at address 0x94 has 016 sectors [Host vendor specific log]
Log at address 0x95 has 016 sectors [Host vendor specific log]
Log at address 0x96 has 016 sectors [Host vendor specific log]
Log at address 0x97 has 016 sectors [Host vendor specific log]
Log at address 0x98 has 016 sectors [Host vendor specific log]
Log at address 0x99 has 016 sectors [Host vendor specific log]
Log at address 0x9a has 016 sectors [Host vendor specific log]
Log at address 0x9b has 016 sectors [Host vendor specific log]
Log at address 0x9c has 016 sectors [Host vendor specific log]
Log at address 0x9d has 016 sectors [Host vendor specific log]
Log at address 0x9e has 016 sectors [Host vendor specific log]
Log at address 0x9f has 016 sectors [Host vendor specific log]
Log at address 0xe0 has 001 sectors [Reserved log]
Log at address 0xe1 has 001 sectors [Reserved log]
SMART Error Log Version: 0
No Errors Logged
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
SCT Status Version: 3
SCT Version (vendor specific): 256 (0x0100)
SCT Support Level: 1
Device State: SMART Off-line Data Collection executing in background (4)
Current Temperature: 22 Celsius
Power Cycle Min/Max Temperature: 20/25 Celsius
Lifetime Min/Max Temperature: 20/37 Celsius
Under/Over Temperature Limit Count: 0/0
SCT Temperature History Version: 2
Temperature Sampling Period: 1 minute
Temperature Logging Interval: 1 minute
Min/Max recommended Temperature: 0/60 Celsius
Min/Max Temperature Limit: -40/70 Celsius
Temperature History Size (Index): 128 (110)
Index Estimated Time Temperature Celsius
111 2013-12-17 09:07 24 *****
... ..( 31 skipped). .. *****
15 2013-12-17 09:39 24 *****
16 2013-12-17 09:40 23 ****
... ..( 4 skipped). .. ****
21 2013-12-17 09:45 23 ****
22 2013-12-17 09:46 22 ***
... ..( 87 skipped). .. ***
110 2013-12-17 11:14 22 ***
[-- Attachment #3: smartctl.sdb.out --]
[-- Type: text/plain, Size: 14510 bytes --]
smartctl version 5.38 [x86_64-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/
=== START OF INFORMATION SECTION ===
Device Model: ST31000340NS
Serial Number: 9QJ6Y79S
Firmware Version: SN06
User Capacity: 1,000,204,886,016 bytes
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Tue Dec 17 11:14:32 2013 PST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 625) 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: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 220) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x103d) SCT Status 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 UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 081 062 044 Pre-fail Always - 142396197
3 Spin_Up_Time 0x0003 099 099 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 30
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 3
7 Seek_Error_Rate 0x000f 081 060 030 Pre-fail Always - 131721923
9 Power_On_Hours 0x0032 067 067 000 Old_age Always - 29575
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 037 020 Old_age Always - 30
184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 098 098 000 Old_age Always - 2
188 Unknown_Attribute 0x0032 100 096 000 Old_age Always - 42950328381
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 079 060 045 Old_age Always - 21 (Lifetime Min/Max 21/22)
194 Temperature_Celsius 0x0022 021 040 000 Old_age Always - 21 (0 15 0 0)
195 Hardware_ECC_Recovered 0x001a 061 048 000 Old_age Always - 142396197
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 1
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 1
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
Log Directory Supported
SMART Log Directory Logging Version 1 [multi-sector log support]
Log at address 0x00 has 001 sectors [Log Directory]
Log at address 0x01 has 001 sectors [Summary SMART error log]
Log at address 0x02 has 005 sectors [Comprehensive SMART error log]
Log at address 0x03 has 005 sectors [Extended Comprehensive SMART error log]
Log at address 0x06 has 001 sectors [SMART self-test log]
Log at address 0x07 has 001 sectors [Extended self-test log]
Log at address 0x09 has 001 sectors [Selective self-test log]
Log at address 0x10 has 001 sectors [Reserved log]
Log at address 0x11 has 001 sectors [Reserved log]
Log at address 0x21 has 001 sectors [Write stream error log]
Log at address 0x22 has 001 sectors [Read stream error log]
Log at address 0x80 has 016 sectors [Host vendor specific log]
Log at address 0x81 has 016 sectors [Host vendor specific log]
Log at address 0x82 has 016 sectors [Host vendor specific log]
Log at address 0x83 has 016 sectors [Host vendor specific log]
Log at address 0x84 has 016 sectors [Host vendor specific log]
Log at address 0x85 has 016 sectors [Host vendor specific log]
Log at address 0x86 has 016 sectors [Host vendor specific log]
Log at address 0x87 has 016 sectors [Host vendor specific log]
Log at address 0x88 has 016 sectors [Host vendor specific log]
Log at address 0x89 has 016 sectors [Host vendor specific log]
Log at address 0x8a has 016 sectors [Host vendor specific log]
Log at address 0x8b has 016 sectors [Host vendor specific log]
Log at address 0x8c has 016 sectors [Host vendor specific log]
Log at address 0x8d has 016 sectors [Host vendor specific log]
Log at address 0x8e has 016 sectors [Host vendor specific log]
Log at address 0x8f has 016 sectors [Host vendor specific log]
Log at address 0x90 has 016 sectors [Host vendor specific log]
Log at address 0x91 has 016 sectors [Host vendor specific log]
Log at address 0x92 has 016 sectors [Host vendor specific log]
Log at address 0x93 has 016 sectors [Host vendor specific log]
Log at address 0x94 has 016 sectors [Host vendor specific log]
Log at address 0x95 has 016 sectors [Host vendor specific log]
Log at address 0x96 has 016 sectors [Host vendor specific log]
Log at address 0x97 has 016 sectors [Host vendor specific log]
Log at address 0x98 has 016 sectors [Host vendor specific log]
Log at address 0x99 has 016 sectors [Host vendor specific log]
Log at address 0x9a has 016 sectors [Host vendor specific log]
Log at address 0x9b has 016 sectors [Host vendor specific log]
Log at address 0x9c has 016 sectors [Host vendor specific log]
Log at address 0x9d has 016 sectors [Host vendor specific log]
Log at address 0x9e has 016 sectors [Host vendor specific log]
Log at address 0x9f has 016 sectors [Host vendor specific log]
Log at address 0xa1 has 020 sectors [Device vendor specific log]
Log at address 0xa8 has 065 sectors [Device vendor specific log]
Log at address 0xa9 has 001 sectors [Device vendor specific log]
Log at address 0xe0 has 001 sectors [Reserved log]
Log at address 0xe1 has 001 sectors [Reserved log]
SMART Error Log Version: 1
ATA Error Count: 60 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 60 occurred at disk power-on lifetime: 29572 hours (1232 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 08 ff ff ff 4f 00 24d+00:14:08.396 READ FPDMA QUEUED
27 00 00 00 00 00 e0 00 24d+00:14:08.368 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 24d+00:14:08.367 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 24d+00:14:08.353 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 00 24d+00:14:08.326 READ NATIVE MAX ADDRESS EXT
Error 59 occurred at disk power-on lifetime: 29572 hours (1232 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 08 ff ff ff 4f 00 24d+00:14:05.247 READ FPDMA QUEUED
27 00 00 00 00 00 e0 00 24d+00:14:05.220 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 24d+00:14:05.218 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 24d+00:14:05.205 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 00 24d+00:14:05.177 READ NATIVE MAX ADDRESS EXT
Error 58 occurred at disk power-on lifetime: 29572 hours (1232 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 08 ff ff ff 4f 00 24d+00:14:02.124 READ FPDMA QUEUED
27 00 00 00 00 00 e0 00 24d+00:14:02.096 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 24d+00:14:02.095 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 24d+00:14:02.081 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 00 24d+00:14:02.054 READ NATIVE MAX ADDRESS EXT
Error 57 occurred at disk power-on lifetime: 29572 hours (1232 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 08 ff ff ff 4f 00 24d+00:13:58.992 READ FPDMA QUEUED
27 00 00 00 00 00 e0 00 24d+00:13:58.964 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 24d+00:13:58.963 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 24d+00:13:58.950 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 00 24d+00:13:58.922 READ NATIVE MAX ADDRESS EXT
Error 56 occurred at disk power-on lifetime: 29572 hours (1232 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 08 ff ff ff 4f 00 24d+00:13:55.835 READ FPDMA QUEUED
27 00 00 00 00 00 e0 00 24d+00:13:55.808 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 24d+00:13:55.806 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 24d+00:13:55.793 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 00 24d+00:13:55.765 READ NATIVE MAX ADDRESS EXT
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Aborted by host 60% 29560 -
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.
SCT Status Version: 3
SCT Version (vendor specific): 522 (0x020a)
SCT Support Level: 1
Device State: Active (0)
Current Temperature: 21 Celsius
Power Cycle Min/Max Temperature: 21/22 Celsius
Lifetime Min/Max Temperature: 15/40 Celsius
Under/Over Temperature Limit Count: 0/15
SCT Temperature History Version: 2
Temperature Sampling Period: 10 minutes
Temperature Logging Interval: 10 minutes
Min/Max recommended Temperature: 0/ 0 Celsius
Min/Max Temperature Limit: 0/ 0 Celsius
Temperature History Size (Index): 128 (20)
Index Estimated Time Temperature Celsius
21 2013-12-16 14:00 22 ***
... ..( 18 skipped). .. ***
40 2013-12-16 17:10 22 ***
41 2013-12-16 17:20 23 ****
42 2013-12-16 17:30 22 ***
... ..( 9 skipped). .. ***
52 2013-12-16 19:10 22 ***
53 2013-12-16 19:20 21 **
54 2013-12-16 19:30 22 ***
... ..( 25 skipped). .. ***
80 2013-12-16 23:50 22 ***
81 2013-12-17 00:00 21 **
82 2013-12-17 00:10 22 ***
83 2013-12-17 00:20 21 **
84 2013-12-17 00:30 22 ***
85 2013-12-17 00:40 21 **
... ..( 3 skipped). .. **
89 2013-12-17 01:20 21 **
90 2013-12-17 01:30 22 ***
... ..( 7 skipped). .. ***
98 2013-12-17 02:50 22 ***
99 2013-12-17 03:00 21 **
... ..( 9 skipped). .. **
109 2013-12-17 04:40 21 **
110 2013-12-17 04:50 22 ***
... ..( 7 skipped). .. ***
118 2013-12-17 06:10 22 ***
119 2013-12-17 06:20 21 **
... ..( 10 skipped). .. **
2 2013-12-17 08:10 21 **
3 2013-12-17 08:20 22 ***
4 2013-12-17 08:30 22 ***
5 2013-12-17 08:40 ? -
6 2013-12-17 08:50 22 ***
7 2013-12-17 09:00 22 ***
8 2013-12-17 09:10 22 ***
9 2013-12-17 09:20 21 **
10 2013-12-17 09:30 22 ***
11 2013-12-17 09:40 22 ***
12 2013-12-17 09:50 21 **
... ..( 7 skipped). .. **
20 2013-12-17 11:10 21 **
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: request help with RAID1 array that endlessly attempts to sync
2013-12-17 19:26 ` Julie Ashworth
@ 2013-12-17 19:43 ` Phil Turmel
2013-12-17 23:12 ` David C. Rankin
2013-12-18 3:45 ` Julie Ashworth
0 siblings, 2 replies; 12+ messages in thread
From: Phil Turmel @ 2013-12-17 19:43 UTC (permalink / raw)
To: Julie Ashworth; +Cc: linux-raid
On 12/17/2013 02:26 PM, Julie Ashworth wrote:
> Thanks Phil,
> I should note that the drives are labelled "enterprise", purchased from a hw RAID vendor (ACNC.com).
>
> On 17-12-2013 12.55 -0500, Phil Turmel wrote:
>> Please post the output of "smartctl -x" for both of these drives.
>
> The Centos5 smartctl (from smartmontools rpm) doesn't support the -x option. However, it's apparently equivelent to:
> smartctl -H -i -g all -c -A -f brief -l xerror,error -l xselftest,selftest -l selective -l directory -l scttemp -l scterc -l devstat -l sataphy
>
> Centos5 smartctl supports the following:
> smartctl -H -i -c -A -l error -l selftest -l selective -l directory -l scttemp -l scttempsts -l scttemphist
>
> ... and I enclosed the output for sda and sdb.
> If you think it would be useful to have the additional options (provided by -x), then let me know, and I'll try to build it.
I was interested in the reallocation counts, the current pending
sectors, and the scterc timeouts. The latter were not present, and are
important.
But /dev/sdb has three relocations and only one pending error. That's
an old drive, but not sick. I'd be concerned that there're other
hardware issues in your system if the timeout issue is not part of the
problem.
>> timeout mismatches combined with lack of scrubbing.
>
> I've read about mismatches, but not about scrubbing. I'll investigate this.
> What program/options do your weekly scrub?
Simple weekly cron job does "echo check >>/sys/block/mdX/md/sync_action"
for each array.
>> Maybe not. Please tell us you know all about error recovery timeouts
>
> Instead of stopping the sync, I decided to slow it down:
> echo 1001 > /proc/sys/dev/raid/speed_limit_max
>
>> and the timeout mismatch problem commonly encountered with
>> consumer-grade hard drives. Otherwise, you might want search the list
>> archives for various combinations of the keywords "scterc", "error
>> recovery", "timeout mismatch", "URE", and/or "bit error rate".
>
> I'm not a big fan of Seagate (enterprise or not). The drives I purchased before these (~2008) needed to have firmware updates to prevent bricking. Sigh.
That Seagate part number twigged an old memory... I didn't think it was
an enterprise drive. I have had good experiences with Hitachi, FWIW.
Recent purchases have all been WD Red just for this issue.
Phil
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: request help with RAID1 array that endlessly attempts to sync
2013-12-17 19:43 ` Phil Turmel
@ 2013-12-17 23:12 ` David C. Rankin
2013-12-18 3:45 ` Julie Ashworth
1 sibling, 0 replies; 12+ messages in thread
From: David C. Rankin @ 2013-12-17 23:12 UTC (permalink / raw)
To: mdraid
On 12/17/2013 01:43 PM, Phil Turmel wrote:
> That Seagate part number twigged an old memory... I didn't think it was
> an enterprise drive. I have had good experiences with Hitachi, FWIW.
> Recent purchases have all been WD Red just for this issue.
>
Good results with WD-Black as well.
--
David C. Rankin, J.D.,P.E.
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: request help with RAID1 array that endlessly attempts to sync
2013-12-17 19:43 ` Phil Turmel
2013-12-17 23:12 ` David C. Rankin
@ 2013-12-18 3:45 ` Julie Ashworth
2013-12-18 12:08 ` Phil Turmel
1 sibling, 1 reply; 12+ messages in thread
From: Julie Ashworth @ 2013-12-18 3:45 UTC (permalink / raw)
To: Phil Turmel; +Cc: linux-raid
[-- Attachment #1: Type: text/plain, Size: 1216 bytes --]
hi Phil,
thanks again for your help. It was surprisingly easy to install the latest smarmontools.
On 17-12-2013 14.43 -0500, Phil Turmel wrote:
> I was interested in the reallocation counts, the current pending
> sectors, and the scterc timeouts. The latter were not present, and are
> important.
ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
5 Reallocated_Sector_Ct PO--CK 100 100 036 - 3
197 Current_Pending_Sector -O--C- 100 100 000 - 1
SCT Error Recovery Control:
Read: 100 (10.0 seconds)
Write: 100 (10.0 seconds)
(I also attached the full output)
I verified that a weekly scrub is performed via cron (default with Centos5), and there were no errors detected prior to the sync. The output is included in syslog reports.
> But /dev/sdb has three relocations and only one pending error. That's
> an old drive, but not sick. I'd be concerned that there're other
> hardware issues in your system if the timeout issue is not part of the
> problem.
Should I run the sync (mdadm -a) in verbose mode? If so, what is the best way to terminate the current sync? By failing/removing /dev/sda?
Thanks in advance!
best,
Julie
----
[-- Attachment #2: smartctl-6.2-sdb.out --]
[-- Type: text/plain, Size: 17840 bytes --]
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-2.6.18-238.12.1.el5] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda ES.2
Device Model: ST31000340NS
Serial Number: 9QJ6Y79S
LU WWN Device Id: 5 000c50 01a89c17b
Firmware Version: SN06
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Size: 512 bytes logical/physical
Rotation Rate: 7200 rpm
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 2.6, 3.0 Gb/s
Local Time is: Tue Dec 17 19:41:28 2013 PST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is: Unavailable
APM feature is: Unavailable
Rd look-ahead is: Enabled
Write cache is: Enabled
ATA Security is: Disabled, NOT FROZEN [SEC1]
Wt Cache Reorder: Unknown
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 625) 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: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 220) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x103d) SCT Status supported.
SCT Error Recovery Control 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 FLAGS VALUE WORST THRESH FAIL RAW_VALUE
1 Raw_Read_Error_Rate POSR-- 083 062 044 - 208852444
3 Spin_Up_Time PO---- 099 099 000 - 0
4 Start_Stop_Count -O--CK 100 100 020 - 30
5 Reallocated_Sector_Ct PO--CK 100 100 036 - 3
7 Seek_Error_Rate POSR-- 081 060 030 - 131804707
9 Power_On_Hours -O--CK 067 067 000 - 29583
10 Spin_Retry_Count PO--C- 100 100 097 - 0
12 Power_Cycle_Count -O--CK 100 037 020 - 30
184 End-to-End_Error -O--CK 100 100 099 - 0
187 Reported_Uncorrect -O--CK 098 098 000 - 2
188 Command_Timeout -O--CK 100 096 000 - 42950328381
189 High_Fly_Writes -O-RCK 100 100 000 - 0
190 Airflow_Temperature_Cel -O---K 079 060 045 - 21 (Min/Max 21/22)
194 Temperature_Celsius -O---K 021 040 000 - 21 (0 15 0 0 0)
195 Hardware_ECC_Recovered -O-RC- 057 048 000 - 208852444
197 Current_Pending_Sector -O--C- 100 100 000 - 1
198 Offline_Uncorrectable ----C- 100 100 000 - 1
199 UDMA_CRC_Error_Count -OSRCK 200 200 000 - 0
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warning
General Purpose Log Directory Version 1
SMART Log Directory Version 1 [multi-sector log support]
Address Access R/W Size Description
0x00 GPL,SL R/O 1 Log Directory
0x01 GPL,SL R/O 1 Summary SMART error log
0x02 GPL,SL R/O 5 Comprehensive SMART error log
0x03 GPL,SL R/O 5 Ext. Comprehensive SMART error log
0x06 GPL,SL R/O 1 SMART self-test log
0x07 GPL,SL R/O 1 Extended self-test log
0x09 GPL,SL R/W 1 Selective self-test log
0x10 GPL,SL R/O 1 NCQ Command Error log
0x11 GPL,SL R/O 1 SATA Phy Event Counters
0x21 GPL,SL R/O 1 Write stream error log
0x22 GPL,SL R/O 1 Read stream error log
0x80-0x9f GPL,SL R/W 16 Host vendor specific log
0xa1 GPL,SL VS 20 Device vendor specific log
0xa2 GPL VS 2248 Device vendor specific log
0xa8 GPL,SL VS 65 Device vendor specific log
0xa9 GPL,SL VS 1 Device vendor specific log
0xb0 GPL VS 2864 Device vendor specific log
0xb6 GPL VS 1918 Device vendor specific log
0xbe-0xbf GPL VS 65535 Device vendor specific log
0xe0 GPL,SL R/W 1 SCT Command/Status
0xe1 GPL,SL R/W 1 SCT Data Transfer
SMART Extended Comprehensive Error Log Version: 1 (5 sectors)
Device Error Count: 60 (device log contains only the most recent 20 errors)
CR = Command Register
FEATR = Features Register
COUNT = Count (was: Sector Count) Register
LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8
LH = LBA High (was: Cylinder High) Register ] LBA
LM = LBA Mid (was: Cylinder Low) Register ] Register
LL = LBA Low (was: Sector Number) Register ]
DV = Device (was: Device/Head) Register
DC = Device Control Register
ER = Error register
ST = Status register
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 60 [19] occurred at disk power-on lifetime: 29572 hours (1232 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 74 5c d2 9b 00 00 Error: UNC at LBA = 0x745cd29b = 1952240283
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 08 00 00 74 5c d2 99 40 00 24d+00:14:08.396 READ FPDMA QUEUED
27 00 00 00 00 00 00 00 00 00 00 e0 00 24d+00:14:08.368 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 24d+00:14:08.367 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 24d+00:14:08.353 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 00 00 00 00 00 e0 00 24d+00:14:08.326 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 59 [18] occurred at disk power-on lifetime: 29572 hours (1232 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 74 5c d2 9b 00 00 Error: UNC at LBA = 0x745cd29b = 1952240283
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 08 00 00 74 5c d2 99 40 00 24d+00:14:05.247 READ FPDMA QUEUED
27 00 00 00 00 00 00 00 00 00 00 e0 00 24d+00:14:05.220 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 24d+00:14:05.218 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 24d+00:14:05.205 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 00 00 00 00 00 e0 00 24d+00:14:05.177 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 58 [17] occurred at disk power-on lifetime: 29572 hours (1232 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 74 5c d2 9b 00 00 Error: UNC at LBA = 0x745cd29b = 1952240283
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 08 00 00 74 5c d2 99 40 00 24d+00:14:02.124 READ FPDMA QUEUED
27 00 00 00 00 00 00 00 00 00 00 e0 00 24d+00:14:02.096 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 24d+00:14:02.095 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 24d+00:14:02.081 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 00 00 00 00 00 e0 00 24d+00:14:02.054 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 57 [16] occurred at disk power-on lifetime: 29572 hours (1232 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 74 5c d2 9b 00 00 Error: UNC at LBA = 0x745cd29b = 1952240283
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 08 00 00 74 5c d2 99 40 00 24d+00:13:58.992 READ FPDMA QUEUED
27 00 00 00 00 00 00 00 00 00 00 e0 00 24d+00:13:58.964 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 24d+00:13:58.963 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 24d+00:13:58.950 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 00 00 00 00 00 e0 00 24d+00:13:58.922 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 56 [15] occurred at disk power-on lifetime: 29572 hours (1232 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 74 5c d2 9b 00 00 Error: UNC at LBA = 0x745cd29b = 1952240283
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 08 00 00 74 5c d2 99 40 00 24d+00:13:55.835 READ FPDMA QUEUED
27 00 00 00 00 00 00 00 00 00 00 e0 00 24d+00:13:55.808 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 24d+00:13:55.806 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 24d+00:13:55.793 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 00 00 00 00 00 e0 00 24d+00:13:55.765 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 55 [14] occurred at disk power-on lifetime: 29572 hours (1232 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 74 5c d2 9b 00 00 Error: UNC at LBA = 0x745cd29b = 1952240283
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 08 00 00 74 5c d2 99 40 00 24d+00:13:52.680 READ FPDMA QUEUED
60 00 00 00 08 00 00 74 5c d2 89 40 00 24d+00:13:52.671 READ FPDMA QUEUED
60 00 00 00 08 00 00 74 5c d2 81 40 00 24d+00:13:52.664 READ FPDMA QUEUED
ea 00 00 00 00 00 00 00 00 00 00 a0 00 24d+00:13:52.657 FLUSH CACHE EXT
61 00 00 00 08 00 00 74 70 59 01 40 00 24d+00:13:52.657 WRITE FPDMA QUEUED
Error 54 [13] occurred at disk power-on lifetime: 29572 hours (1232 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 74 5c d2 9b 00 00 Error: UNC at LBA = 0x745cd29b = 1952240283
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 80 00 00 74 5c d2 81 40 00 24d+00:13:49.491 READ FPDMA QUEUED
60 00 00 00 80 00 00 74 5c d3 01 40 00 24d+00:13:49.490 READ FPDMA QUEUED
60 00 00 00 80 00 00 74 5c d3 81 40 00 24d+00:13:49.488 READ FPDMA QUEUED
27 00 00 00 00 00 00 00 00 00 00 e0 00 24d+00:13:49.461 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 24d+00:13:49.459 IDENTIFY DEVICE
Error 53 [12] occurred at disk power-on lifetime: 29572 hours (1232 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 74 5c d2 9b 00 00 Error: UNC at LBA = 0x745cd29b = 1952240283
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 80 00 00 74 5c d3 81 40 00 24d+00:13:46.341 READ FPDMA QUEUED
60 00 00 00 80 00 00 74 5c d3 01 40 00 24d+00:13:46.341 READ FPDMA QUEUED
60 00 00 00 80 00 00 74 5c d2 81 40 00 24d+00:13:46.340 READ FPDMA QUEUED
27 00 00 00 00 00 00 00 00 00 00 e0 00 24d+00:13:46.312 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 24d+00:13:46.311 IDENTIFY DEVICE
SMART Extended Self-test Log Version: 1 (1 sectors)
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Aborted by host 60% 29560 -
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.
SCT Status Version: 3
SCT Version (vendor specific): 522 (0x020a)
SCT Support Level: 1
Device State: Active (0)
Current Temperature: 21 Celsius
Power Cycle Min/Max Temperature: 21/22 Celsius
Lifetime Min/Max Temperature: 15/40 Celsius
Under/Over Temperature Limit Count: 0/66
SCT Temperature History Version: 2
Temperature Sampling Period: 10 minutes
Temperature Logging Interval: 10 minutes
Min/Max recommended Temperature: 0/ 0 Celsius
Min/Max Temperature Limit: 0/ 0 Celsius
Temperature History Size (Index): 128 (71)
Index Estimated Time Temperature Celsius
72 2013-12-16 22:30 22 ***
... ..( 7 skipped). .. ***
80 2013-12-16 23:50 22 ***
81 2013-12-17 00:00 21 **
82 2013-12-17 00:10 22 ***
83 2013-12-17 00:20 21 **
84 2013-12-17 00:30 22 ***
85 2013-12-17 00:40 21 **
... ..( 3 skipped). .. **
89 2013-12-17 01:20 21 **
90 2013-12-17 01:30 22 ***
... ..( 7 skipped). .. ***
98 2013-12-17 02:50 22 ***
99 2013-12-17 03:00 21 **
... ..( 9 skipped). .. **
109 2013-12-17 04:40 21 **
110 2013-12-17 04:50 22 ***
... ..( 7 skipped). .. ***
118 2013-12-17 06:10 22 ***
119 2013-12-17 06:20 21 **
... ..( 10 skipped). .. **
2 2013-12-17 08:10 21 **
3 2013-12-17 08:20 22 ***
4 2013-12-17 08:30 22 ***
5 2013-12-17 08:40 ? -
6 2013-12-17 08:50 22 ***
7 2013-12-17 09:00 22 ***
8 2013-12-17 09:10 22 ***
9 2013-12-17 09:20 21 **
10 2013-12-17 09:30 22 ***
11 2013-12-17 09:40 22 ***
12 2013-12-17 09:50 21 **
... ..( 42 skipped). .. **
55 2013-12-17 17:00 21 **
56 2013-12-17 17:10 22 ***
57 2013-12-17 17:20 21 **
... ..( 13 skipped). .. **
71 2013-12-17 19:40 21 **
SCT Error Recovery Control:
Read: 100 (10.0 seconds)
Write: 100 (10.0 seconds)
Device Statistics (GP Log 0x04) not supported
SATA Phy Event Counters (GP Log 0x11)
ID Size Value Description
0x000a 2 1 Device-to-host register FISes sent due to a COMRESET
0x0001 2 0 Command failed due to ICRC error
0x0003 2 0 R_ERR response for device-to-host data FIS
0x0004 2 0 R_ERR response for host-to-device data FIS
0x0006 2 0 R_ERR response for device-to-host non-data FIS
0x0007 2 0 R_ERR response for host-to-device non-data FIS
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: request help with RAID1 array that endlessly attempts to sync
2013-12-18 3:45 ` Julie Ashworth
@ 2013-12-18 12:08 ` Phil Turmel
2014-01-21 6:38 ` Julie Ashworth
0 siblings, 1 reply; 12+ messages in thread
From: Phil Turmel @ 2013-12-18 12:08 UTC (permalink / raw)
To: Julie Ashworth; +Cc: linux-raid
On 12/17/2013 10:45 PM, Julie Ashworth wrote:
> hi Phil,
> thanks again for your help. It was surprisingly easy to install the latest smarmontools.
>
> On 17-12-2013 14.43 -0500, Phil Turmel wrote:
>> I was interested in the reallocation counts, the current pending
>> sectors, and the scterc timeouts. The latter were not present, and are
>> important.
>
> ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
> 5 Reallocated_Sector_Ct PO--CK 100 100 036 - 3
> 197 Current_Pending_Sector -O--C- 100 100 000 - 1
> SCT Error Recovery Control:
> Read: 100 (10.0 seconds)
> Write: 100 (10.0 seconds)
>
> (I also attached the full output)
>
> I verified that a weekly scrub is performed via cron (default with Centos5), and there were no errors detected prior to the sync. The output is included in syslog reports.
Very good. You do not have a timeout mismatch problem. But the
behavior of /dev/sdb does not match its health. That suggests some
other problem is present, like a bad SATA cord or socket, a bad power
supply, bad cooling, et cetera.
>> But /dev/sdb has three relocations and only one pending error. That's
>> an old drive, but not sick. I'd be concerned that there're other
>> hardware issues in your system if the timeout issue is not part of the
>> problem.
>
> Should I run the sync (mdadm -a) in verbose mode? If so, what is the best way to terminate the current sync? By failing/removing /dev/sda?
I'd let the sync continue until it fails or completes. And if it
completes, exercise the array to see if it stays flaky. If it does not
complete, start swapping parts in the system.
Regards,
Phil
ps. I'll be offline all day today--I'm sure the list will chip in if
you need more help.
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: request help with RAID1 array that endlessly attempts to sync
2013-12-18 12:08 ` Phil Turmel
@ 2014-01-21 6:38 ` Julie Ashworth
2014-01-21 13:23 ` Phil Turmel
2014-02-25 0:16 ` Julie Ashworth
0 siblings, 2 replies; 12+ messages in thread
From: Julie Ashworth @ 2014-01-21 6:38 UTC (permalink / raw)
To: Phil Turmel; +Cc: linux-raid
[-- Attachment #1: Type: text/plain, Size: 1670 bytes --]
On 18-12-2013 07.08 -0500, Phil Turmel wrote:
> I'd let the sync continue until it fails or completes. And if it
> completes, exercise the array to see if it stays flaky. If it does not
> complete, start swapping parts in the system.
---end quoted text---
I'm responding to an old thread, but current problem. I started a RAID1 rebuild in mid-December, and it's still running - now with 2712 read errors - and counting. (I enclosed smartctl output).
# cat /proc/mdstat
Personalities : [raid1]
md0 : active raid1 sda1[0] sdb1[1]
521984 blocks [2/2] [UU]
md1 : active raid1 sda2[2] sdb2[1]
976237824 blocks [2/1] [_U]
[==============>......] recovery = 70.9% (692700480/976237824) finish=68.5min speed=68956K/sec
md0 is a boot partition, and md1 is the operating system.
I configured LVM on md1, and allocated 68GB (of 1TB):
# vgdisplay /dev/VolGroup00
VG Name VolGroup00
VG Size 931.00 GB
Alloc PE / Size 2176 / 68.00 GB
Free PE / Size 27616 / 863.00 GB
Currently, only ~5GB of the 1TB disk is used.
At this point, what is my best option for limiting downtime of the server (i.e. avoiding a rebuild)?
I added a drive (/dev/sdc) with identical geometry, and consider using dd, i.e.
# dd if=/dev/sdb of=/dev/sdc bs=4096 conv=sync,noerror
This may not be the most efficient method of transferring data, since .5% of the disk is used. But obviously, I'm not in a hurry.
Please excuse my ignorance, but after it's cloned, is it possible to add /dev/sdc2 to md1 while it's syncing (to /dev/sda2)? Or do I need to wait until /dev/sdb fails to replace it with /dev/sdc?
Thanks!
Julie
[-- Attachment #2: smartctl.20130120 --]
[-- Type: text/plain, Size: 17014 bytes --]
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-2.6.18-238.12.1.el5] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda ES.2
Device Model: ST31000340NS
Serial Number: 9QJ6Y79S
LU WWN Device Id: 5 000c50 01a89c17b
Firmware Version: SN06
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Size: 512 bytes logical/physical
Rotation Rate: 7200 rpm
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS T13/1699-D revision 4
SATA Version is: SATA 2.6, 3.0 Gb/s
Local Time is: Mon Jan 20 20:33:09 2014 PST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is: Unavailable
APM feature is: Unavailable
Rd look-ahead is: Enabled
Write cache is: Enabled
ATA Security is: Disabled, NOT FROZEN [SEC1]
Wt Cache Reorder: Unknown
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 625) 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: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 220) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x103d) SCT Status supported.
SCT Error Recovery Control 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 FLAGS VALUE WORST THRESH FAIL RAW_VALUE
1 Raw_Read_Error_Rate POSR-- 075 058 044 - 33516445
3 Spin_Up_Time PO---- 099 099 000 - 0
4 Start_Stop_Count -O--CK 100 100 020 - 36
5 Reallocated_Sector_Ct PO--CK 100 100 036 - 3
7 Seek_Error_Rate POSR-- 081 060 030 - 138049328
9 Power_On_Hours -O--CK 066 066 000 - 30400
10 Spin_Retry_Count PO--C- 100 100 097 - 0
12 Power_Cycle_Count -O--CK 100 037 020 - 36
184 End-to-End_Error -O--CK 100 100 099 - 0
187 Reported_Uncorrect -O--CK 092 092 000 - 8
188 Command_Timeout -O--CK 100 096 000 - 42950328381
189 High_Fly_Writes -O-RCK 100 100 000 - 0
190 Airflow_Temperature_Cel -O---K 079 060 045 - 21 (Min/Max 21/21)
194 Temperature_Celsius -O---K 021 040 000 - 21 (0 15 0 0 0)
195 Hardware_ECC_Recovered -O-RC- 064 048 000 - 33516445
197 Current_Pending_Sector -O--C- 100 100 000 - 1
198 Offline_Uncorrectable ----C- 100 100 000 - 1
199 UDMA_CRC_Error_Count -OSRCK 200 200 000 - 0
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warning
General Purpose Log Directory Version 1
SMART Log Directory Version 1 [multi-sector log support]
Address Access R/W Size Description
0x00 GPL,SL R/O 1 Log Directory
0x01 GPL,SL R/O 1 Summary SMART error log
0x02 GPL,SL R/O 5 Comprehensive SMART error log
0x03 GPL,SL R/O 5 Ext. Comprehensive SMART error log
0x06 GPL,SL R/O 1 SMART self-test log
0x07 GPL,SL R/O 1 Extended self-test log
0x09 GPL,SL R/W 1 Selective self-test log
0x10 GPL,SL R/O 1 NCQ Command Error log
0x11 GPL,SL R/O 1 SATA Phy Event Counters
0x21 GPL,SL R/O 1 Write stream error log
0x22 GPL,SL R/O 1 Read stream error log
0x80-0x9f GPL,SL R/W 16 Host vendor specific log
0xa1 GPL,SL VS 20 Device vendor specific log
0xa2 GPL VS 2248 Device vendor specific log
0xa8 GPL,SL VS 65 Device vendor specific log
0xa9 GPL,SL VS 1 Device vendor specific log
0xb0 GPL VS 2864 Device vendor specific log
0xb6 GPL VS 1918 Device vendor specific log
0xbe-0xbf GPL VS 65535 Device vendor specific log
0xe0 GPL,SL R/W 1 SCT Command/Status
0xe1 GPL,SL R/W 1 SCT Data Transfer
SMART Extended Comprehensive Error Log Version: 1 (5 sectors)
Device Error Count: 2712 (device log contains only the most recent 20 errors)
CR = Command Register
FEATR = Features Register
COUNT = Count (was: Sector Count) Register
LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8
LH = LBA High (was: Cylinder High) Register ] LBA
LM = LBA Mid (was: Cylinder Low) Register ] Register
LL = LBA Low (was: Sector Number) Register ]
DV = Device (was: Device/Head) Register
DC = Device Control Register
ER = Error register
ST = Status register
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 2712 [11] occurred at disk power-on lifetime: 30399 hours (1266 days + 15 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 74 5c d2 9b 00 00 Error: UNC at LBA = 0x745cd29b = 1952240283
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 08 00 00 74 5c d2 99 40 00 12d+15:29:19.453 READ FPDMA QUEUED
27 00 00 00 00 00 00 00 00 00 00 e0 00 12d+15:29:19.425 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 12d+15:29:19.424 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 12d+15:29:19.411 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 00 00 00 00 00 e0 00 12d+15:29:19.383 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 2711 [10] occurred at disk power-on lifetime: 30399 hours (1266 days + 15 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 74 5c d2 9b 00 00 Error: UNC at LBA = 0x745cd29b = 1952240283
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 08 00 00 74 5c d2 99 40 00 12d+15:29:16.279 READ FPDMA QUEUED
27 00 00 00 00 00 00 00 00 00 00 e0 00 12d+15:29:16.252 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 12d+15:29:16.250 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 12d+15:29:16.237 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 00 00 00 00 00 e0 00 12d+15:29:16.210 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 2710 [9] occurred at disk power-on lifetime: 30399 hours (1266 days + 15 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 74 5c d2 9b 00 00 Error: UNC at LBA = 0x745cd29b = 1952240283
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 08 00 00 74 5c d2 99 40 00 12d+15:29:13.115 READ FPDMA QUEUED
60 00 00 00 80 00 00 74 5c e2 01 40 00 12d+15:29:13.114 READ FPDMA QUEUED
27 00 00 00 00 00 00 00 00 00 00 e0 00 12d+15:29:13.087 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 12d+15:29:13.085 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 12d+15:29:13.072 SET FEATURES [Set transfer mode]
Error 2709 [8] occurred at disk power-on lifetime: 30399 hours (1266 days + 15 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 74 5c d2 9b 00 00 Error: UNC at LBA = 0x745cd29b = 1952240283
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 08 00 00 74 5c d2 99 40 00 12d+15:29:09.933 READ FPDMA QUEUED
27 00 00 00 00 00 00 00 00 00 00 e0 00 12d+15:29:09.905 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 12d+15:29:09.904 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 12d+15:29:09.890 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 00 00 00 00 00 e0 00 12d+15:29:09.863 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 2708 [7] occurred at disk power-on lifetime: 30399 hours (1266 days + 15 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 74 5c d2 9b 00 00 Error: UNC at LBA = 0x745cd29b = 1952240283
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 08 00 00 74 5c d2 99 40 00 12d+15:29:06.793 READ FPDMA QUEUED
27 00 00 00 00 00 00 00 00 00 00 e0 00 12d+15:29:06.765 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 00 00 00 00 00 a0 00 12d+15:29:06.763 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 00 12d+15:29:06.750 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 00 00 00 00 00 e0 00 12d+15:29:06.723 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 2707 [6] occurred at disk power-on lifetime: 30399 hours (1266 days + 15 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 74 5c d2 9b 00 00 Error: UNC at LBA = 0x745cd29b = 1952240283
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 08 00 00 74 5c d2 99 40 00 12d+15:29:03.653 READ FPDMA QUEUED
60 00 00 00 08 00 00 74 5c d2 89 40 00 12d+15:29:03.645 READ FPDMA QUEUED
60 00 00 00 08 00 00 74 5c d2 81 40 00 12d+15:29:03.638 READ FPDMA QUEUED
ea 00 00 00 00 00 00 00 00 00 00 a0 00 12d+15:29:03.629 FLUSH CACHE EXT
61 00 00 00 08 00 00 74 70 59 01 40 00 12d+15:29:03.628 WRITE FPDMA QUEUED
Error 2706 [5] occurred at disk power-on lifetime: 30399 hours (1266 days + 15 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 74 5c d2 9b 00 00 Error: UNC at LBA = 0x745cd29b = 1952240283
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 80 00 00 74 5c d2 81 40 00 12d+15:29:00.466 READ FPDMA QUEUED
60 00 00 00 80 00 00 74 5c d3 81 40 00 12d+15:29:00.465 READ FPDMA QUEUED
60 00 00 00 80 00 00 74 5c d4 01 40 00 12d+15:29:00.465 READ FPDMA QUEUED
60 00 00 00 80 00 00 74 5c d4 81 40 00 12d+15:29:00.464 READ FPDMA QUEUED
60 00 00 00 80 00 00 74 5c d5 01 40 00 12d+15:29:00.464 READ FPDMA QUEUED
Error 2705 [4] occurred at disk power-on lifetime: 30399 hours (1266 days + 15 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 74 5c d2 9b 00 00 Error: UNC at LBA = 0x745cd29b = 1952240283
Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name
-- == -- == -- == == == -- -- -- -- -- --------------- --------------------
60 00 00 00 80 00 00 74 5c d3 01 40 00 12d+15:28:57.308 READ FPDMA QUEUED
60 00 00 00 80 00 00 74 5c d5 01 40 00 12d+15:28:57.307 READ FPDMA QUEUED
60 00 00 00 80 00 00 74 5c d4 81 40 00 12d+15:28:57.307 READ FPDMA QUEUED
60 00 00 00 80 00 00 74 5c d4 01 40 00 12d+15:28:57.307 READ FPDMA QUEUED
60 00 00 00 80 00 00 74 5c d3 81 40 00 12d+15:28:57.307 READ FPDMA QUEUED
SMART Extended Self-test Log Version: 1 (1 sectors)
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Short offline Aborted by host 60% 29560 -
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.
SCT Status Version: 3
SCT Version (vendor specific): 522 (0x020a)
SCT Support Level: 1
Device State: Active (0)
Current Temperature: 21 Celsius
Power Cycle Min/Max Temperature: 21/21 Celsius
Lifetime Min/Max Temperature: 15/40 Celsius
Under/Over Temperature Limit Count: 0/1
SCT Temperature History Version: 2
Temperature Sampling Period: 10 minutes
Temperature Logging Interval: 10 minutes
Min/Max recommended Temperature: 0/ 0 Celsius
Min/Max Temperature Limit: 0/ 0 Celsius
Temperature History Size (Index): 128 (114)
Index Estimated Time Temperature Celsius
115 2014-01-19 23:20 21 **
... ..( 96 skipped). .. **
84 2014-01-20 15:30 21 **
85 2014-01-20 15:40 22 ***
... ..( 5 skipped). .. ***
91 2014-01-20 16:40 22 ***
92 2014-01-20 16:50 21 **
... ..( 14 skipped). .. **
107 2014-01-20 19:20 21 **
108 2014-01-20 19:30 22 ***
109 2014-01-20 19:40 22 ***
110 2014-01-20 19:50 22 ***
111 2014-01-20 20:00 21 **
112 2014-01-20 20:10 22 ***
113 2014-01-20 20:20 ? -
114 2014-01-20 20:30 21 **
SCT Error Recovery Control:
Read: 100 (10.0 seconds)
Write: 100 (10.0 seconds)
Device Statistics (GP Log 0x04) not supported
SATA Phy Event Counters (GP Log 0x11)
ID Size Value Description
0x000a 2 1 Device-to-host register FISes sent due to a COMRESET
0x0001 2 0 Command failed due to ICRC error
0x0003 2 0 R_ERR response for device-to-host data FIS
0x0004 2 0 R_ERR response for host-to-device data FIS
0x0006 2 0 R_ERR response for device-to-host non-data FIS
0x0007 2 0 R_ERR response for host-to-device non-data FIS
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: request help with RAID1 array that endlessly attempts to sync
2014-01-21 6:38 ` Julie Ashworth
@ 2014-01-21 13:23 ` Phil Turmel
2014-02-25 0:16 ` Julie Ashworth
1 sibling, 0 replies; 12+ messages in thread
From: Phil Turmel @ 2014-01-21 13:23 UTC (permalink / raw)
To: Julie Ashworth; +Cc: linux-raid
Good morning Julie,
On 01/21/2014 01:38 AM, Julie Ashworth wrote:
> On 18-12-2013 07.08 -0500, Phil Turmel wrote:
>> I'd let the sync continue until it fails or completes. And if it
>> completes, exercise the array to see if it stays flaky. If it does not
>> complete, start swapping parts in the system.
> ---end quoted text---
>
> I'm responding to an old thread, but current problem. I started a RAID1 rebuild in mid-December, and it's still running - now with 2712 read errors - and counting. (I enclosed smartctl output).
The smartctl report says the drive is relatively healthy (3 total
relocations after 30,000 hours of operation). That implies all of your
read errors are transient. Or it is the other drive? (Show the other
drive's smartctl output, too, perhaps.)
> # cat /proc/mdstat
> Personalities : [raid1]
> md0 : active raid1 sda1[0] sdb1[1]
> 521984 blocks [2/2] [UU]
>
> md1 : active raid1 sda2[2] sdb2[1]
> 976237824 blocks [2/1] [_U]
> [==============>......] recovery = 70.9% (692700480/976237824) finish=68.5min speed=68956K/sec
I would *not* disturb the rebuild (yet). You have a better option.
> md0 is a boot partition, and md1 is the operating system.
> I configured LVM on md1, and allocated 68GB (of 1TB):
>
> # vgdisplay /dev/VolGroup00
> VG Name VolGroup00
> VG Size 931.00 GB
> Alloc PE / Size 2176 / 68.00 GB
> Free PE / Size 27616 / 863.00 GB
>
> Currently, only ~5GB of the 1TB disk is used.
>
> At this point, what is my best option for limiting downtime of the server (i.e. avoiding a rebuild)?
> I added a drive (/dev/sdc) with identical geometry, and consider using dd, i.e.
>
> # dd if=/dev/sdb of=/dev/sdc bs=4096 conv=sync,noerror
No, this would also duplicate the raid metadata, confusing MD if you had
an unexpected reboot in the middle.
> This may not be the most efficient method of transferring data, since .5% of the disk is used. But obviously, I'm not in a hurry.
No hurry is good, as I suggest you take advantage of LVM to establish a
new raid under your volume group. This can be done on the fly, but
involves several steps.
> Please excuse my ignorance, but after it's cloned, is it possible to add /dev/sdc2 to md1 while it's syncing (to /dev/sda2)? Or do I need to wait until /dev/sdb fails to replace it with /dev/sdc?
Using LVM can achieve the equivalent.
Here's what I recommend:
1) Partition sdc to match the old drives
2) Expand /dev/md0 onto sdc1:
mdadm --add /dev/md0 /dev/sdc1
mdadm --grow /dev/md0 -n 3
3) Create a new, degraded raid1 on sdc2
mdadm --create --level=1 -n 2 /dev/md2 /dev/sdc2 missing
4) Update mdadm.conf and initramfs to include /dev/md2
5) Add the new array to your volume group
pvcreate /dev/md2
vgextend VolGroup00 /dev/md2
6) Convert your logical volume(s) into mirrors across both PVs
lvconvert -m1 --mirrorlog=mirrored /dev/VolGroup00/lvname
{wait for this background task to complete}
7) Fail the rebuilding drive out of /dev/md1 and add it to /dev/md2
mdadm /dev/md1 --fail /dev/sd?2
mdadm /dev/md1 --remove /dev/sd?2
mdadm /dev/md2 --add /dev/sd?2
{wait for the background rebuild to complete}
8) Unmirror your logical volume(s), dropping the /dev/md1 copy
lvconvert -m0 /dev/VolGroup00/lvname /dev/md1
9) Drop the empty /dev/md1 from the volume group
vgreduce -a VolGroup00
pvremove /dev/md1
10) Update mdadm.conf and initramfs to omit /dev/md1
11) Destroy /dev/md1 and add its device to the new array
mdadm --stop /dev/md1
mdadm --add /dev/md2 /dev/sd?2
mdadm --grow /dev/md2 -n 3
Enjoy your triple redundancy.
Phil
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: request help with RAID1 array that endlessly attempts to sync
2014-01-21 6:38 ` Julie Ashworth
2014-01-21 13:23 ` Phil Turmel
@ 2014-02-25 0:16 ` Julie Ashworth
1 sibling, 0 replies; 12+ messages in thread
From: Julie Ashworth @ 2014-02-25 0:16 UTC (permalink / raw)
To: Phil Turmel; +Cc: linux-raid
Thank you Phil!
I only had one glitch - my version of lvm2 (lvm2-2.02.74-5.el5_6.1) created mirrored extents on the same physical device. I reverted to linear LVs, upgraded lvm2, and it worked perfectly.
Words can't express my gratitude - you saved me so much time and stress. Do you like pizza? Dominos? Pizza Hut? ;)
best,
Julie
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2014-02-25 0:16 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-12-17 6:50 request help with RAID1 array that endlessly attempts to sync Julie Ashworth
2013-12-17 16:53 ` Julie Ashworth
2013-12-17 17:55 ` Phil Turmel
2013-12-17 19:26 ` Julie Ashworth
2013-12-17 19:43 ` Phil Turmel
2013-12-17 23:12 ` David C. Rankin
2013-12-18 3:45 ` Julie Ashworth
2013-12-18 12:08 ` Phil Turmel
2014-01-21 6:38 ` Julie Ashworth
2014-01-21 13:23 ` Phil Turmel
2014-02-25 0:16 ` Julie Ashworth
2013-12-17 18:12 ` Wilson Jonathan
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).