* Damage when growing RAID 5 array
@ 2013-02-25 21:17 Kevin McAreavey
2013-02-26 3:24 ` Phil Turmel
0 siblings, 1 reply; 7+ messages in thread
From: Kevin McAreavey @ 2013-02-25 21:17 UTC (permalink / raw)
To: linux-raid
Hi everyone,
I'm really hoping someone can help me and that the array can be saved.
I was trying to grow a RAID 5 array from 3 to 4 drives (I've already successfully grown it once from 2 to 3 drives). However, after running the grow command it was stuck with 'resync=DELAYED'. I eventually rebooted but the array was then inactive and with whatever I've done since the array has now disappeared. Is it possible to salvage this before I make it any worse?
Thanks very much for any help!
Kevin
Some info:
----------
$ cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4] [linear] [multipath] [raid0] [raid1] [raid10]
unused devices: <none>
----------
$ sudo mdadm --assemble /dev/md1
mdadm: Failed to restore critical section for reshape, sorry.
Possibly you needed to specify the --backup-file
----------
$ sudo mdadm -Q /dev/sdc1
/dev/sdc1: is not an md array
/dev/sdc1: device 0 in 4 device undetected raid5 /dev/.tmp.md1. Use mdadm --examine for more detail.
----------
$ sudo mdadm --examine /dev/sd[acde]1
/dev/sda1:
Magic : a92b4efc
Version : 0.91.00
UUID : ec02c596:7c68f1da:7faca49f:4a711434 (local to host kevin-server)
Creation Time : Tue Jan 11 20:05:16 2011
Raid Level : raid5
Used Dev Size : 1953508352 (1863.01 GiB 2000.39 GB)
Array Size : 5860525056 (5589.03 GiB 6001.18 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 1
Reshape pos'n : 0
Delta Devices : 1 (3->4)
Update Time : Mon Feb 25 18:19:50 2013
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Checksum : ee7f7fa5 - correct
Events : 6108
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 3 8 1 3 active sync /dev/sda1
0 0 8 33 0 active sync /dev/sdc1
1 1 8 65 1 active sync /dev/sde1
2 2 8 49 2 active sync /dev/sdd1
3 3 8 1 3 active sync /dev/sda1
/dev/sdc1:
Magic : a92b4efc
Version : 0.91.00
UUID : ec02c596:7c68f1da:7faca49f:4a711434 (local to host kevin-server)
Creation Time : Tue Jan 11 20:05:16 2011
Raid Level : raid5
Used Dev Size : 1953508352 (1863.01 GiB 2000.39 GB)
Array Size : 5860525056 (5589.03 GiB 6001.18 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 1
Reshape pos'n : 0
Delta Devices : 1 (3->4)
Update Time : Mon Feb 25 18:19:50 2013
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Checksum : ee7f7fbf - correct
Events : 6108
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 0 8 33 0 active sync /dev/sdc1
0 0 8 33 0 active sync /dev/sdc1
1 1 8 65 1 active sync /dev/sde1
2 2 8 49 2 active sync /dev/sdd1
3 3 8 1 3 active sync /dev/sda1
/dev/sdd1:
Magic : a92b4efc
Version : 0.91.00
UUID : ec02c596:7c68f1da:7faca49f:4a711434 (local to host kevin-server)
Creation Time : Tue Jan 11 20:05:16 2011
Raid Level : raid5
Used Dev Size : 1953508352 (1863.01 GiB 2000.39 GB)
Array Size : 5860525056 (5589.03 GiB 6001.18 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 1
Reshape pos'n : 0
Delta Devices : 1 (3->4)
Update Time : Mon Feb 25 18:19:50 2013
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Checksum : ee7f7fd3 - correct
Events : 6108
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 2 8 49 2 active sync /dev/sdd1
0 0 8 33 0 active sync /dev/sdc1
1 1 8 65 1 active sync /dev/sde1
2 2 8 49 2 active sync /dev/sdd1
3 3 8 1 3 active sync /dev/sda1
/dev/sde1:
Magic : a92b4efc
Version : 0.91.00
UUID : ec02c596:7c68f1da:7faca49f:4a711434 (local to host kevin-server)
Creation Time : Tue Jan 11 20:05:16 2011
Raid Level : raid5
Used Dev Size : 1953508352 (1863.01 GiB 2000.39 GB)
Array Size : 5860525056 (5589.03 GiB 6001.18 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 1
Reshape pos'n : 0
Delta Devices : 1 (3->4)
Update Time : Mon Feb 25 18:19:50 2013
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Checksum : ee7f7fe1 - correct
Events : 6108
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 1 8 65 1 active sync /dev/sde1
0 0 8 33 0 active sync /dev/sdc1
1 1 8 65 1 active sync /dev/sde1
2 2 8 49 2 active sync /dev/sdd1
3 3 8 1 3 active sync /dev/sda1
----------
I also noticed that /dev/sda seems to have been added:
$ sudo mdadm --examine /dev/sd[acde]
/dev/sda:
Magic : a92b4efc
Version : 0.91.00
UUID : ec02c596:7c68f1da:7faca49f:4a711434 (local to host kevin-server)
Creation Time : Tue Jan 11 20:05:16 2011
Raid Level : raid5
Used Dev Size : 1953508352 (1863.01 GiB 2000.39 GB)
Array Size : 5860525056 (5589.03 GiB 6001.18 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 1
Reshape pos'n : 0
Delta Devices : 1 (3->4)
Update Time : Mon Feb 25 18:19:50 2013
State : clean
Active Devices : 4
Working Devices : 4
Failed Devices : 0
Spare Devices : 0
Checksum : ee7f7fa5 - correct
Events : 6108
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 3 8 1 3 active sync /dev/sda1
0 0 8 33 0 active sync /dev/sdc1
1 1 8 65 1 active sync /dev/sde1
2 2 8 49 2 active sync /dev/sdd1
3 3 8 1 3 active sync /dev/sda1
/dev/sdc:
MBR Magic : aa55
Partition[0] : 3907016904 sectors at 56 (type 83)
/dev/sdd:
MBR Magic : aa55
Partition[0] : 3907016904 sectors at 56 (type 83)
/dev/sde:
MBR Magic : aa55
Partition[0] : 3907016904 sectors at 56 (type 83)
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Damage when growing RAID 5 array
2013-02-25 21:17 Damage when growing RAID 5 array Kevin McAreavey
@ 2013-02-26 3:24 ` Phil Turmel
2013-02-26 9:47 ` Kevin McAreavey
0 siblings, 1 reply; 7+ messages in thread
From: Phil Turmel @ 2013-02-26 3:24 UTC (permalink / raw)
To: Kevin McAreavey; +Cc: linux-raid
On 02/25/2013 04:17 PM, Kevin McAreavey wrote:
> $ sudo mdadm --assemble /dev/md1
> mdadm: Failed to restore critical section for reshape, sorry.
> Possibly you needed to specify the --backup-file
Did you follow this advice? I doesn't look like it from the rest of
your report. (Reread that without the word "Possibly".)
Phil
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Damage when growing RAID 5 array
2013-02-26 3:24 ` Phil Turmel
@ 2013-02-26 9:47 ` Kevin McAreavey
2013-02-26 13:22 ` Phil Turmel
0 siblings, 1 reply; 7+ messages in thread
From: Kevin McAreavey @ 2013-02-26 9:47 UTC (permalink / raw)
To: Phil Turmel; +Cc: linux-raid
Hi Phil,
Unfortunately I didn't specify a backup-file when attempting to grow the array so I'm not able to run this.
Thanks,
Kevin
On 26 Feb 2013, at 03:24, Phil Turmel wrote:
> On 02/25/2013 04:17 PM, Kevin McAreavey wrote:
>
>> $ sudo mdadm --assemble /dev/md1
>> mdadm: Failed to restore critical section for reshape, sorry.
>> Possibly you needed to specify the --backup-file
>
> Did you follow this advice? I doesn't look like it from the rest of
> your report. (Reread that without the word "Possibly".)
>
> Phil
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Damage when growing RAID 5 array
2013-02-26 9:47 ` Kevin McAreavey
@ 2013-02-26 13:22 ` Phil Turmel
2013-02-26 13:41 ` Kevin McAreavey
0 siblings, 1 reply; 7+ messages in thread
From: Phil Turmel @ 2013-02-26 13:22 UTC (permalink / raw)
To: Kevin McAreavey; +Cc: linux-raid
On 02/26/2013 04:47 AM, Kevin McAreavey wrote:
> Hi Phil,
>
> Unfortunately I didn't specify a backup-file when attempting to grow the array so I'm not able to run this.
Hmmm. That sounds like a bug. It should have refused, I believe. What
kernel and mdadm versions are involved here?
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Damage when growing RAID 5 array
2013-02-26 13:22 ` Phil Turmel
@ 2013-02-26 13:41 ` Kevin McAreavey
2013-02-26 13:45 ` Phil Turmel
0 siblings, 1 reply; 7+ messages in thread
From: Kevin McAreavey @ 2013-02-26 13:41 UTC (permalink / raw)
To: Phil Turmel; +Cc: linux-raid
$ uname -srv
Linux 3.2.0-37-generic-pae #58-Ubuntu SMP Thu Jan 24 15:51:02 UTC 2013
$ mdadm --version
mdadm - v3.2.5 - 18th May 2012
On 26 Feb 2013, at 13:22, Phil Turmel wrote:
> On 02/26/2013 04:47 AM, Kevin McAreavey wrote:
>> Hi Phil,
>>
>> Unfortunately I didn't specify a backup-file when attempting to grow the array so I'm not able to run this.
>
> Hmmm. That sounds like a bug. It should have refused, I believe. What
> kernel and mdadm versions are involved here?
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Damage when growing RAID 5 array
2013-02-26 13:41 ` Kevin McAreavey
@ 2013-02-26 13:45 ` Phil Turmel
2013-02-26 14:18 ` Kevin McAreavey
0 siblings, 1 reply; 7+ messages in thread
From: Phil Turmel @ 2013-02-26 13:45 UTC (permalink / raw)
To: Kevin McAreavey; +Cc: linux-raid
Hi Kevin,
[top-posting repaired--please don't do that.]
On 02/26/2013 08:41 AM, Kevin McAreavey wrote:
> On 26 Feb 2013, at 13:22, Phil Turmel wrote:
>
>> On 02/26/2013 04:47 AM, Kevin McAreavey wrote:
>>> Hi Phil,
>>>
>>> Unfortunately I didn't specify a backup-file when attempting to grow the array so I'm not able to run this.
>>
>> Hmmm. That sounds like a bug. It should have refused, I believe. What
>> kernel and mdadm versions are involved here?
>
> $ uname -srv
> Linux 3.2.0-37-generic-pae #58-Ubuntu SMP Thu Jan 24 15:51:02 UTC 2013
>
> $ mdadm --version
> mdadm - v3.2.5 - 18th May 2012
>
Try the assemble with "--backup-file=... --invalid-backup"
The file must be outside the array, of course.
Phil
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Damage when growing RAID 5 array
2013-02-26 13:45 ` Phil Turmel
@ 2013-02-26 14:18 ` Kevin McAreavey
0 siblings, 0 replies; 7+ messages in thread
From: Kevin McAreavey @ 2013-02-26 14:18 UTC (permalink / raw)
To: Phil Turmel; +Cc: linux-raid
On 26 Feb 2013, at 13:45, Phil Turmel wrote:
> Hi Kevin,
>
> [top-posting repaired--please don't do that.]
>
> On 02/26/2013 08:41 AM, Kevin McAreavey wrote:
>> On 26 Feb 2013, at 13:22, Phil Turmel wrote:
>>
>>> On 02/26/2013 04:47 AM, Kevin McAreavey wrote:
>>>> Hi Phil,
>>>>
>>>> Unfortunately I didn't specify a backup-file when attempting to grow the array so I'm not able to run this.
>>>
>>> Hmmm. That sounds like a bug. It should have refused, I believe. What
>>> kernel and mdadm versions are involved here?
>>
>> $ uname -srv
>> Linux 3.2.0-37-generic-pae #58-Ubuntu SMP Thu Jan 24 15:51:02 UTC 2013
>>
>> $ mdadm --version
>> mdadm - v3.2.5 - 18th May 2012
>>
>
> Try the assemble with "--backup-file=... --invalid-backup"
> The file must be outside the array, of course.
>
> Phil
Hi Phil,
I ran that, it completed but didn't given me any message.
To be honest, I think I'm just going to cut my losses and start over. I don't really know what I'm doing at this point and I've probably just been making it worse.
Thanks for your help!
Kevin
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2013-02-26 14:18 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-02-25 21:17 Damage when growing RAID 5 array Kevin McAreavey
2013-02-26 3:24 ` Phil Turmel
2013-02-26 9:47 ` Kevin McAreavey
2013-02-26 13:22 ` Phil Turmel
2013-02-26 13:41 ` Kevin McAreavey
2013-02-26 13:45 ` Phil Turmel
2013-02-26 14:18 ` Kevin McAreavey
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.