* unable to assemble (mostly?) clean array
@ 2013-12-08 23:32 Christopher Hoover
2013-12-08 23:55 ` NeilBrown
2013-12-09 0:02 ` Adam Goryachev
0 siblings, 2 replies; 9+ messages in thread
From: Christopher Hoover @ 2013-12-08 23:32 UTC (permalink / raw)
To: linux-raid
hi folks,
what's the safest way to get this array back into r/o mode?
thanks,
-ch
ch@murgatroid.com
ch@snaggle:~$ sudo mdadm --examine /dev/sd[defg]1 | egrep 'Event|^/dev/sd'
/dev/sdd1:
Events : 286024
/dev/sde1:
Events : 286011
/dev/sdf1:
Events : 286024
/dev/sdg1:
Events : 286024
ch@snaggle:~$ sudo mdadm --assemble --force /dev/md0 /dev/sdd1
/dev/sde1 /sdg1
mdadm: cannot open device /sdg1: No such file or directory
mdadm: /sdg1 has no superblock - assembly aborted
ch@snaggle:~$ sudo mdadm --assemble --force /dev/md0 /dev/sdd1 /dev/sde1
mdadm: ignoring /dev/sde1 as it reports /dev/sdd1 as failed
mdadm: /dev/md0 assembled from 0 drives and 1 spare - not enough to
start the array.
ch@snaggle:~$ sudo mdadm -E /dev/sd[defg]1
/dev/sdd1:
Magic : a92b4efc
Version : 0.90.00
UUID : 48af1ed4:8978e992:f8a6b934:875c877f (local to host snaggle)
Creation Time : Mon May 23 00:02:10 2011
Raid Level : raid6
Used Dev Size : 1465135936 (1397.26 GiB 1500.30 GB)
Array Size : 2930271872 (2794.53 GiB 3000.60 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 0
Update Time : Tue Dec 3 21:19:31 2013
State : clean
Active Devices : 1
Working Devices : 3
Failed Devices : 2
Spare Devices : 2
Checksum : f32d49b0 - correct
Events : 286024
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 4 8 33 4 spare
0 0 0 0 0 removed
1 1 0 0 1 faulty removed
2 2 8 65 2 active sync /dev/sde1
3 3 0 0 3 faulty removed
4 4 8 33 4 spare
5 5 8 81 5 spare /dev/sdf1
/dev/sde1:
Magic : a92b4efc
Version : 0.90.00
UUID : 48af1ed4:8978e992:f8a6b934:875c877f (local to host snaggle)
Creation Time : Mon May 23 00:02:10 2011
Raid Level : raid6
Used Dev Size : 1465135936 (1397.26 GiB 1500.30 GB)
Array Size : 2930271872 (2794.53 GiB 3000.60 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 0
Update Time : Sun Dec 1 18:03:17 2013
State : clean
Active Devices : 2
Working Devices : 4
Failed Devices : 1
Spare Devices : 2
Checksum : f32a7899 - correct
Events : 286011
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 1 8 49 1 active sync /dev/sdd1
0 0 0 0 0 removed
1 1 8 49 1 active sync /dev/sdd1
2 2 8 65 2 active sync /dev/sde1
3 3 0 0 3 faulty removed
4 4 8 33 4 spare
5 5 8 81 5 spare /dev/sdf1
/dev/sdf1:
Magic : a92b4efc
Version : 0.90.00
UUID : 48af1ed4:8978e992:f8a6b934:875c877f (local to host snaggle)
Creation Time : Mon May 23 00:02:10 2011
Raid Level : raid6
Used Dev Size : 1465135936 (1397.26 GiB 1500.30 GB)
Array Size : 2930271872 (2794.53 GiB 3000.60 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 0
Update Time : Tue Dec 3 21:19:31 2013
State : clean
Active Devices : 1
Working Devices : 3
Failed Devices : 2
Spare Devices : 2
Checksum : f32d49d2 - correct
Events : 286024
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 2 8 65 2 active sync /dev/sde1
0 0 0 0 0 removed
1 1 0 0 1 faulty removed
2 2 8 65 2 active sync /dev/sde1
3 3 0 0 3 faulty removed
4 4 8 33 4 spare
5 5 8 81 5 spare /dev/sdf1
/dev/sdg1:
Magic : a92b4efc
Version : 0.90.00
UUID : 48af1ed4:8978e992:f8a6b934:875c877f (local to host snaggle)
Creation Time : Mon May 23 00:02:10 2011
Raid Level : raid6
Used Dev Size : 1465135936 (1397.26 GiB 1500.30 GB)
Array Size : 2930271872 (2794.53 GiB 3000.60 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 0
Update Time : Tue Dec 3 21:19:31 2013
State : clean
Active Devices : 1
Working Devices : 3
Failed Devices : 2
Spare Devices : 2
Checksum : f32d49e2 - correct
Events : 286024
Layout : left-symmetric
Chunk Size : 64K
Number Major Minor RaidDevice State
this 5 8 81 5 spare /dev/sdf1
0 0 0 0 0 removed
1 1 0 0 1 faulty removed
2 2 8 65 2 active sync /dev/sde1
3 3 0 0 3 faulty removed
4 4 8 33 4 spare
5 5 8 81 5 spare /dev/sdf1
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: unable to assemble (mostly?) clean array
2013-12-08 23:32 unable to assemble (mostly?) clean array Christopher Hoover
@ 2013-12-08 23:55 ` NeilBrown
2013-12-09 0:02 ` Adam Goryachev
1 sibling, 0 replies; 9+ messages in thread
From: NeilBrown @ 2013-12-08 23:55 UTC (permalink / raw)
To: Christopher Hoover; +Cc: linux-raid
[-- Attachment #1: Type: text/plain, Size: 889 bytes --]
On Sun, 8 Dec 2013 15:32:42 -0800 Christopher Hoover <ch@murgatroid.com>
wrote:
> hi folks,
>
> what's the safest way to get this array back into r/o mode?
>
> thanks,
> -ch
> ch@murgatroid.com
>
>
> ch@snaggle:~$ sudo mdadm --examine /dev/sd[defg]1 | egrep 'Event|^/dev/sd'
>
> /dev/sdd1:
>
> Events : 286024
>
> /dev/sde1:
>
> Events : 286011
>
> /dev/sdf1:
>
> Events : 286024
>
> /dev/sdg1:
>
> Events : 286024
>
> ch@snaggle:~$ sudo mdadm --assemble --force /dev/md0 /dev/sdd1
> /dev/sde1 /sdg1
>
> mdadm: cannot open device /sdg1: No such file or directory
>
> mdadm: /sdg1 has no superblock - assembly aborted
You missed a "/dev" there!
Did you try just giving all the devices to mdadm and letting it pick the best?
mdadm --assemble --force /dev/md0 /dev/sd[defg]1
?
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: unable to assemble (mostly?) clean array
2013-12-08 23:32 unable to assemble (mostly?) clean array Christopher Hoover
2013-12-08 23:55 ` NeilBrown
@ 2013-12-09 0:02 ` Adam Goryachev
2013-12-09 0:32 ` Christopher Hoover
1 sibling, 1 reply; 9+ messages in thread
From: Adam Goryachev @ 2013-12-09 0:02 UTC (permalink / raw)
To: Christopher Hoover, linux-raid
On 09/12/13 10:32, Christopher Hoover wrote:
> hi folks,
>
> what's the safest way to get this array back into r/o mode?
>
> thanks,
> -ch
> ch@murgatroid.com
>
>
> ch@snaggle:~$ sudo mdadm --examine /dev/sd[defg]1 | egrep 'Event|^/dev/sd'
>
> /dev/sdd1:
>
> Events : 286024
>
> /dev/sde1:
>
> Events : 286011
>
> /dev/sdf1:
>
> Events : 286024
>
> /dev/sdg1:
>
> Events : 286024
>
> ch@snaggle:~$ sudo mdadm --assemble --force /dev/md0 /dev/sdd1
> /dev/sde1 /sdg1
>
> mdadm: cannot open device /sdg1: No such file or directory
>
> mdadm: /sdg1 has no superblock - assembly aborted
>
I'm no expert on this, but two questions:
Did you mean /dev/sdg1 ?
Why not use sdd1, sdf1 and sdg1 since they have the correct event counts?
Then add sde1 and allow to resync?
sudo mdadm --manage /dev/md0 --stop
sudo mdadm --assemble /dev/md0 /dev/sd[dfg]1
sudo mdadm --manage /dev/md0 --run
Try that, and provide any output
PS, it seems you would only need a minimum of 2 drives, and you have
three with matching event counts, so it should be fine.
Regards,
Adam
--
Adam Goryachev
Website Managers
P: +61 2 8304 0000 adam@websitemanagers.com.au
F: +61 2 8304 0001 www.websitemanagers.com.au
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: unable to assemble (mostly?) clean array
2013-12-09 0:02 ` Adam Goryachev
@ 2013-12-09 0:32 ` Christopher Hoover
2013-12-09 1:02 ` NeilBrown
0 siblings, 1 reply; 9+ messages in thread
From: Christopher Hoover @ 2013-12-09 0:32 UTC (permalink / raw)
To: Adam Goryachev; +Cc: linux-raid
yes, thanks, typo there. that was done hastily for the e-mail.
i had tried the right thing previously and here it is again. still no luck:
ch@snaggle:~$ sudo mdadm -E /dev/sd[defg]1 | egrep 'Events|^/dev/sd'
/dev/sdd1:
Events : 286024
/dev/sde1:
Events : 286011
/dev/sdf1:
Events : 286024
/dev/sdg1:
Events : 286024
ch@snaggle:~$ sudo mdadm --assemble --force /dev/md0 /dev/sd[dfg]1
mdadm: ignoring /dev/sdf1 as it reports /dev/sdd1 as failed
mdadm: /dev/md0 assembled from 0 drives and 2 spares - not enough to
start the array.
ch@snaggle:~$
On Sun, Dec 8, 2013 at 4:02 PM, Adam Goryachev
<adam@websitemanagers.com.au> wrote:
> On 09/12/13 10:32, Christopher Hoover wrote:
>>
>> hi folks,
>>
>> what's the safest way to get this array back into r/o mode?
>>
>> thanks,
>> -ch
>> ch@murgatroid.com
>>
>>
>> ch@snaggle:~$ sudo mdadm --examine /dev/sd[defg]1 | egrep 'Event|^/dev/sd'
>>
>> /dev/sdd1:
>>
>> Events : 286024
>>
>> /dev/sde1:
>>
>> Events : 286011
>>
>> /dev/sdf1:
>>
>> Events : 286024
>>
>> /dev/sdg1:
>>
>> Events : 286024
>>
>> ch@snaggle:~$ sudo mdadm --assemble --force /dev/md0 /dev/sdd1
>> /dev/sde1 /sdg1
>>
>> mdadm: cannot open device /sdg1: No such file or directory
>>
>> mdadm: /sdg1 has no superblock - assembly aborted
>>
>
> I'm no expert on this, but two questions:
> Did you mean /dev/sdg1 ?
>
> Why not use sdd1, sdf1 and sdg1 since they have the correct event counts?
> Then add sde1 and allow to resync?
>
> sudo mdadm --manage /dev/md0 --stop
> sudo mdadm --assemble /dev/md0 /dev/sd[dfg]1
> sudo mdadm --manage /dev/md0 --run
>
> Try that, and provide any output
>
>
> PS, it seems you would only need a minimum of 2 drives, and you have three
> with matching event counts, so it should be fine.
>
> Regards,
> Adam
>
> --
> Adam Goryachev
> Website Managers
> P: +61 2 8304 0000 adam@websitemanagers.com.au
> F: +61 2 8304 0001 www.websitemanagers.com.au
>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: unable to assemble (mostly?) clean array
2013-12-09 0:32 ` Christopher Hoover
@ 2013-12-09 1:02 ` NeilBrown
2013-12-09 1:08 ` Christopher Hoover
0 siblings, 1 reply; 9+ messages in thread
From: NeilBrown @ 2013-12-09 1:02 UTC (permalink / raw)
To: Christopher Hoover; +Cc: Adam Goryachev, linux-raid
[-- Attachment #1: Type: text/plain, Size: 814 bytes --]
On Sun, 8 Dec 2013 16:32:22 -0800 Christopher Hoover <ch@murgatroid.com>
wrote:
> yes, thanks, typo there. that was done hastily for the e-mail.
>
> i had tried the right thing previously and here it is again. still no luck:
>
>
> ch@snaggle:~$ sudo mdadm -E /dev/sd[defg]1 | egrep 'Events|^/dev/sd'
> /dev/sdd1:
> Events : 286024
> /dev/sde1:
> Events : 286011
> /dev/sdf1:
> Events : 286024
> /dev/sdg1:
> Events : 286024
> ch@snaggle:~$ sudo mdadm --assemble --force /dev/md0 /dev/sd[dfg]1
> mdadm: ignoring /dev/sdf1 as it reports /dev/sdd1 as failed
> mdadm: /dev/md0 assembled from 0 drives and 2 spares - not enough to
> start the array.
> ch@snaggle:~$
Please try listing *all* of the devices, and add "-v" for extra output.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: unable to assemble (mostly?) clean array
2013-12-09 1:02 ` NeilBrown
@ 2013-12-09 1:08 ` Christopher Hoover
2013-12-09 1:33 ` NeilBrown
0 siblings, 1 reply; 9+ messages in thread
From: Christopher Hoover @ 2013-12-09 1:08 UTC (permalink / raw)
To: NeilBrown; +Cc: Adam Goryachev, linux-raid
ch@snaggle:~$ sudo mdadm --assemble --verbose --force /dev/md0 /dev/sd[defg]1
mdadm: looking for devices for /dev/md0
mdadm: /dev/sdd1 is identified as a member of /dev/md0, slot 4.
mdadm: /dev/sde1 is identified as a member of /dev/md0, slot 1.
mdadm: /dev/sdf1 is identified as a member of /dev/md0, slot 2.
mdadm: /dev/sdg1 is identified as a member of /dev/md0, slot 5.
mdadm: ignoring /dev/sde1 as it reports /dev/sdd1 as failed
mdadm: ignoring /dev/sdf1 as it reports /dev/sdd1 as failed
mdadm: no uptodate device for slot 0 of /dev/md0
mdadm: no uptodate device for slot 1 of /dev/md0
mdadm: no uptodate device for slot 2 of /dev/md0
mdadm: no uptodate device for slot 3 of /dev/md0
mdadm: added /dev/sdg1 to /dev/md0 as 5
mdadm: added /dev/sdd1 to /dev/md0 as 4
mdadm: /dev/md0 assembled from 0 drives and 2 spares - not enough to
start the array.
ch@snaggle:~$
On Sun, Dec 8, 2013 at 5:02 PM, NeilBrown <neilb@suse.de> wrote:
> On Sun, 8 Dec 2013 16:32:22 -0800 Christopher Hoover <ch@murgatroid.com>
> wrote:
>
>> yes, thanks, typo there. that was done hastily for the e-mail.
>>
>> i had tried the right thing previously and here it is again. still no luck:
>>
>>
>> ch@snaggle:~$ sudo mdadm -E /dev/sd[defg]1 | egrep 'Events|^/dev/sd'
>> /dev/sdd1:
>> Events : 286024
>> /dev/sde1:
>> Events : 286011
>> /dev/sdf1:
>> Events : 286024
>> /dev/sdg1:
>> Events : 286024
>> ch@snaggle:~$ sudo mdadm --assemble --force /dev/md0 /dev/sd[dfg]1
>> mdadm: ignoring /dev/sdf1 as it reports /dev/sdd1 as failed
>> mdadm: /dev/md0 assembled from 0 drives and 2 spares - not enough to
>> start the array.
>> ch@snaggle:~$
>
> Please try listing *all* of the devices, and add "-v" for extra output.
>
> NeilBrown
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: unable to assemble (mostly?) clean array
2013-12-09 1:08 ` Christopher Hoover
@ 2013-12-09 1:33 ` NeilBrown
2013-12-09 3:00 ` Christopher Hoover
0 siblings, 1 reply; 9+ messages in thread
From: NeilBrown @ 2013-12-09 1:33 UTC (permalink / raw)
To: Christopher Hoover; +Cc: Adam Goryachev, linux-raid
[-- Attachment #1: Type: text/plain, Size: 2225 bytes --]
On Sun, 8 Dec 2013 17:08:19 -0800 Christopher Hoover <ch@murgatroid.com>
wrote:
> ch@snaggle:~$ sudo mdadm --assemble --verbose --force /dev/md0 /dev/sd[defg]1
> mdadm: looking for devices for /dev/md0
> mdadm: /dev/sdd1 is identified as a member of /dev/md0, slot 4.
> mdadm: /dev/sde1 is identified as a member of /dev/md0, slot 1.
> mdadm: /dev/sdf1 is identified as a member of /dev/md0, slot 2.
> mdadm: /dev/sdg1 is identified as a member of /dev/md0, slot 5.
> mdadm: ignoring /dev/sde1 as it reports /dev/sdd1 as failed
> mdadm: ignoring /dev/sdf1 as it reports /dev/sdd1 as failed
> mdadm: no uptodate device for slot 0 of /dev/md0
> mdadm: no uptodate device for slot 1 of /dev/md0
> mdadm: no uptodate device for slot 2 of /dev/md0
> mdadm: no uptodate device for slot 3 of /dev/md0
> mdadm: added /dev/sdg1 to /dev/md0 as 5
> mdadm: added /dev/sdd1 to /dev/md0 as 4
> mdadm: /dev/md0 assembled from 0 drives and 2 spares - not enough to
> start the array.
> ch@snaggle:~$
Thanks.
I recognise this bug now. You are running mdadm-3.2.something - correct?
You need 3.3.
Just grab the latest:
cd /tmp;git clone git://neil.brown.name/mdadm ; cd mdadm ; make ; ./mdadm -Avf /dev/md0 /dev/sd[defg]1
NeilBrown
>
> On Sun, Dec 8, 2013 at 5:02 PM, NeilBrown <neilb@suse.de> wrote:
> > On Sun, 8 Dec 2013 16:32:22 -0800 Christopher Hoover <ch@murgatroid.com>
> > wrote:
> >
> >> yes, thanks, typo there. that was done hastily for the e-mail.
> >>
> >> i had tried the right thing previously and here it is again. still no luck:
> >>
> >>
> >> ch@snaggle:~$ sudo mdadm -E /dev/sd[defg]1 | egrep 'Events|^/dev/sd'
> >> /dev/sdd1:
> >> Events : 286024
> >> /dev/sde1:
> >> Events : 286011
> >> /dev/sdf1:
> >> Events : 286024
> >> /dev/sdg1:
> >> Events : 286024
> >> ch@snaggle:~$ sudo mdadm --assemble --force /dev/md0 /dev/sd[dfg]1
> >> mdadm: ignoring /dev/sdf1 as it reports /dev/sdd1 as failed
> >> mdadm: /dev/md0 assembled from 0 drives and 2 spares - not enough to
> >> start the array.
> >> ch@snaggle:~$
> >
> > Please try listing *all* of the devices, and add "-v" for extra output.
> >
> > NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: unable to assemble (mostly?) clean array
2013-12-09 1:33 ` NeilBrown
@ 2013-12-09 3:00 ` Christopher Hoover
2013-12-09 3:41 ` NeilBrown
0 siblings, 1 reply; 9+ messages in thread
From: Christopher Hoover @ 2013-12-09 3:00 UTC (permalink / raw)
To: NeilBrown; +Cc: Adam Goryachev, linux-raid
OK, seems to be back to doing "something". See below.
I'm a little concerned that it "promoted" sde1 rather than relying on
the other three drives with the same event count.
Very much thank you for your help!
-ch
p.s. is there anyway to assemble a container from components in read
only mode? I have a feeling i'm going to loved sde1 again before the
recovery.
ch@snaggle:~/src/mdadm$ sudo ./mdadm -Avf /dev/md0 /dev/sd[efdg]1
mdadm: looking for devices for /dev/md0
mdadm: /dev/sdd1 is identified as a member of /dev/md0, slot 4.
mdadm: /dev/sde1 is identified as a member of /dev/md0, slot 1.
mdadm: /dev/sdf1 is identified as a member of /dev/md0, slot 2.
mdadm: /dev/sdg1 is identified as a member of /dev/md0, slot 5.
mdadm: forcing event count in /dev/sde1(1) from 286011 upto 286024
mdadm: no uptodate device for slot 0 of /dev/md0
mdadm: added /dev/sdf1 to /dev/md0 as 2
mdadm: no uptodate device for slot 6 of /dev/md0
mdadm: added /dev/sdd1 to /dev/md0 as 4
mdadm: added /dev/sdg1 to /dev/md0 as 5
mdadm: added /dev/sde1 to /dev/md0 as 1
mdadm: /dev/md0 has been started with 2 drives (out of 4) and 2 spares.
ch@snaggle:~/src/mdadm$ sudo mdadm -D /dev/md0
/dev/md0:
Version : 0.90
Creation Time : Mon May 23 00:02:10 2011
Raid Level : raid6
Array Size : 2930271872 (2794.53 GiB 3000.60 GB)
Used Dev Size : 1465135936 (1397.26 GiB 1500.30 GB)
Raid Devices : 4
Total Devices : 4
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Sun Dec 8 18:53:29 2013
State : clean, degraded, recovering
Active Devices : 2
Working Devices : 4
Failed Devices : 0
Spare Devices : 2
Layout : left-symmetric
Chunk Size : 64K
Rebuild Status : 0% complete
UUID : 48af1ed4:8978e992:f8a6b934:875c877f (local to host snaggle)
Events : 0.286025
Number Major Minor RaidDevice State
4 8 97 0 spare rebuilding /dev/sdg1
1 8 65 1 active sync /dev/sde1
2 8 81 2 active sync /dev/sdf1
5 8 49 3 spare rebuilding /dev/sdd1
ch@snaggle:~/src/mdadm$
On Sun, Dec 8, 2013 at 5:33 PM, NeilBrown <neilb@suse.de> wrote:
> On Sun, 8 Dec 2013 17:08:19 -0800 Christopher Hoover <ch@murgatroid.com>
> wrote:
>
>> ch@snaggle:~$ sudo mdadm --assemble --verbose --force /dev/md0 /dev/sd[defg]1
>> mdadm: looking for devices for /dev/md0
>> mdadm: /dev/sdd1 is identified as a member of /dev/md0, slot 4.
>> mdadm: /dev/sde1 is identified as a member of /dev/md0, slot 1.
>> mdadm: /dev/sdf1 is identified as a member of /dev/md0, slot 2.
>> mdadm: /dev/sdg1 is identified as a member of /dev/md0, slot 5.
>> mdadm: ignoring /dev/sde1 as it reports /dev/sdd1 as failed
>> mdadm: ignoring /dev/sdf1 as it reports /dev/sdd1 as failed
>> mdadm: no uptodate device for slot 0 of /dev/md0
>> mdadm: no uptodate device for slot 1 of /dev/md0
>> mdadm: no uptodate device for slot 2 of /dev/md0
>> mdadm: no uptodate device for slot 3 of /dev/md0
>> mdadm: added /dev/sdg1 to /dev/md0 as 5
>> mdadm: added /dev/sdd1 to /dev/md0 as 4
>> mdadm: /dev/md0 assembled from 0 drives and 2 spares - not enough to
>> start the array.
>> ch@snaggle:~$
>
> Thanks.
>
> I recognise this bug now. You are running mdadm-3.2.something - correct?
> You need 3.3.
> Just grab the latest:
>
> cd /tmp;git clone git://neil.brown.name/mdadm ; cd mdadm ; make ; ./mdadm -Avf /dev/md0 /dev/sd[defg]1
>
> NeilBrown
>
>
>>
>> On Sun, Dec 8, 2013 at 5:02 PM, NeilBrown <neilb@suse.de> wrote:
>> > On Sun, 8 Dec 2013 16:32:22 -0800 Christopher Hoover <ch@murgatroid.com>
>> > wrote:
>> >
>> >> yes, thanks, typo there. that was done hastily for the e-mail.
>> >>
>> >> i had tried the right thing previously and here it is again. still no luck:
>> >>
>> >>
>> >> ch@snaggle:~$ sudo mdadm -E /dev/sd[defg]1 | egrep 'Events|^/dev/sd'
>> >> /dev/sdd1:
>> >> Events : 286024
>> >> /dev/sde1:
>> >> Events : 286011
>> >> /dev/sdf1:
>> >> Events : 286024
>> >> /dev/sdg1:
>> >> Events : 286024
>> >> ch@snaggle:~$ sudo mdadm --assemble --force /dev/md0 /dev/sd[dfg]1
>> >> mdadm: ignoring /dev/sdf1 as it reports /dev/sdd1 as failed
>> >> mdadm: /dev/md0 assembled from 0 drives and 2 spares - not enough to
>> >> start the array.
>> >> ch@snaggle:~$
>> >
>> > Please try listing *all* of the devices, and add "-v" for extra output.
>> >
>> > NeilBrown
>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: unable to assemble (mostly?) clean array
2013-12-09 3:00 ` Christopher Hoover
@ 2013-12-09 3:41 ` NeilBrown
0 siblings, 0 replies; 9+ messages in thread
From: NeilBrown @ 2013-12-09 3:41 UTC (permalink / raw)
To: Christopher Hoover; +Cc: Adam Goryachev, linux-raid
[-- Attachment #1: Type: text/plain, Size: 5133 bytes --]
On Sun, 8 Dec 2013 19:00:02 -0800 Christopher Hoover <ch@murgatroid.com>
wrote:
> OK, seems to be back to doing "something". See below.
>
> I'm a little concerned that it "promoted" sde1 rather than relying on
> the other three drives with the same event count.
Two of those three devices considered themselves to be 'spares' - so there is
no reason to believe there was useful data on them.
>
> Very much thank you for your help!
>
> -ch
>
> p.s. is there anyway to assemble a container from components in read
> only mode? I have a feeling i'm going to loved sde1 again before the
> recovery.
Not really, no.
NeilBrown
>
>
>
> ch@snaggle:~/src/mdadm$ sudo ./mdadm -Avf /dev/md0 /dev/sd[efdg]1
> mdadm: looking for devices for /dev/md0
> mdadm: /dev/sdd1 is identified as a member of /dev/md0, slot 4.
> mdadm: /dev/sde1 is identified as a member of /dev/md0, slot 1.
> mdadm: /dev/sdf1 is identified as a member of /dev/md0, slot 2.
> mdadm: /dev/sdg1 is identified as a member of /dev/md0, slot 5.
> mdadm: forcing event count in /dev/sde1(1) from 286011 upto 286024
> mdadm: no uptodate device for slot 0 of /dev/md0
> mdadm: added /dev/sdf1 to /dev/md0 as 2
> mdadm: no uptodate device for slot 6 of /dev/md0
> mdadm: added /dev/sdd1 to /dev/md0 as 4
> mdadm: added /dev/sdg1 to /dev/md0 as 5
> mdadm: added /dev/sde1 to /dev/md0 as 1
> mdadm: /dev/md0 has been started with 2 drives (out of 4) and 2 spares.
>
> ch@snaggle:~/src/mdadm$ sudo mdadm -D /dev/md0
> /dev/md0:
> Version : 0.90
> Creation Time : Mon May 23 00:02:10 2011
> Raid Level : raid6
> Array Size : 2930271872 (2794.53 GiB 3000.60 GB)
> Used Dev Size : 1465135936 (1397.26 GiB 1500.30 GB)
> Raid Devices : 4
> Total Devices : 4
> Preferred Minor : 0
> Persistence : Superblock is persistent
>
> Update Time : Sun Dec 8 18:53:29 2013
> State : clean, degraded, recovering
> Active Devices : 2
> Working Devices : 4
> Failed Devices : 0
> Spare Devices : 2
>
> Layout : left-symmetric
> Chunk Size : 64K
>
> Rebuild Status : 0% complete
>
> UUID : 48af1ed4:8978e992:f8a6b934:875c877f (local to host snaggle)
> Events : 0.286025
>
> Number Major Minor RaidDevice State
> 4 8 97 0 spare rebuilding /dev/sdg1
> 1 8 65 1 active sync /dev/sde1
> 2 8 81 2 active sync /dev/sdf1
> 5 8 49 3 spare rebuilding /dev/sdd1
> ch@snaggle:~/src/mdadm$
>
>
> On Sun, Dec 8, 2013 at 5:33 PM, NeilBrown <neilb@suse.de> wrote:
> > On Sun, 8 Dec 2013 17:08:19 -0800 Christopher Hoover <ch@murgatroid.com>
> > wrote:
> >
> >> ch@snaggle:~$ sudo mdadm --assemble --verbose --force /dev/md0 /dev/sd[defg]1
> >> mdadm: looking for devices for /dev/md0
> >> mdadm: /dev/sdd1 is identified as a member of /dev/md0, slot 4.
> >> mdadm: /dev/sde1 is identified as a member of /dev/md0, slot 1.
> >> mdadm: /dev/sdf1 is identified as a member of /dev/md0, slot 2.
> >> mdadm: /dev/sdg1 is identified as a member of /dev/md0, slot 5.
> >> mdadm: ignoring /dev/sde1 as it reports /dev/sdd1 as failed
> >> mdadm: ignoring /dev/sdf1 as it reports /dev/sdd1 as failed
> >> mdadm: no uptodate device for slot 0 of /dev/md0
> >> mdadm: no uptodate device for slot 1 of /dev/md0
> >> mdadm: no uptodate device for slot 2 of /dev/md0
> >> mdadm: no uptodate device for slot 3 of /dev/md0
> >> mdadm: added /dev/sdg1 to /dev/md0 as 5
> >> mdadm: added /dev/sdd1 to /dev/md0 as 4
> >> mdadm: /dev/md0 assembled from 0 drives and 2 spares - not enough to
> >> start the array.
> >> ch@snaggle:~$
> >
> > Thanks.
> >
> > I recognise this bug now. You are running mdadm-3.2.something - correct?
> > You need 3.3.
> > Just grab the latest:
> >
> > cd /tmp;git clone git://neil.brown.name/mdadm ; cd mdadm ; make ; ./mdadm -Avf /dev/md0 /dev/sd[defg]1
> >
> > NeilBrown
> >
> >
> >>
> >> On Sun, Dec 8, 2013 at 5:02 PM, NeilBrown <neilb@suse.de> wrote:
> >> > On Sun, 8 Dec 2013 16:32:22 -0800 Christopher Hoover <ch@murgatroid.com>
> >> > wrote:
> >> >
> >> >> yes, thanks, typo there. that was done hastily for the e-mail.
> >> >>
> >> >> i had tried the right thing previously and here it is again. still no luck:
> >> >>
> >> >>
> >> >> ch@snaggle:~$ sudo mdadm -E /dev/sd[defg]1 | egrep 'Events|^/dev/sd'
> >> >> /dev/sdd1:
> >> >> Events : 286024
> >> >> /dev/sde1:
> >> >> Events : 286011
> >> >> /dev/sdf1:
> >> >> Events : 286024
> >> >> /dev/sdg1:
> >> >> Events : 286024
> >> >> ch@snaggle:~$ sudo mdadm --assemble --force /dev/md0 /dev/sd[dfg]1
> >> >> mdadm: ignoring /dev/sdf1 as it reports /dev/sdd1 as failed
> >> >> mdadm: /dev/md0 assembled from 0 drives and 2 spares - not enough to
> >> >> start the array.
> >> >> ch@snaggle:~$
> >> >
> >> > Please try listing *all* of the devices, and add "-v" for extra output.
> >> >
> >> > NeilBrown
> >
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2013-12-09 3:41 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-12-08 23:32 unable to assemble (mostly?) clean array Christopher Hoover
2013-12-08 23:55 ` NeilBrown
2013-12-09 0:02 ` Adam Goryachev
2013-12-09 0:32 ` Christopher Hoover
2013-12-09 1:02 ` NeilBrown
2013-12-09 1:08 ` Christopher Hoover
2013-12-09 1:33 ` NeilBrown
2013-12-09 3:00 ` Christopher Hoover
2013-12-09 3:41 ` NeilBrown
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).