> Von: "Phil Turmel" <philip@xxxxxxxxxx>
> An: "Alex Sommer" <alex@xxxxxxxxxxxxxxx>, "linux-raid maillist" <linux-raid@xxxxxxxxxxxxxxx>
> On 12/12/18 2:48 PM, Alex Sommer wrote:
> >
> > Hello,
>
> [trim /]
>
> > my idea is now to do:
> > mdadm --create --assume-clean --level=5 --raid-devices=5 /dev/md2 /dev/sdk1 /dev/sdj1 /dev/sdm1 /dev/sdl1 /dev/sdi1
>
> NO!
>
> > but all says it is better to ask here before do this.
>
> Because in many cases it destroys your data.
>
> I recommend:
>
> 1) Show/look at the output of "cat /proc/mdstat"
>
> 2) If your arrays shows up there as partially assembled, use mdadm
> --stop to release the drives.
device is stoped
> 3) retry "mdadm --assemble --force --verbose /dev/md2 /dev/sd[ijklm]1"
~ # mdadm --assemble --force --verbose /dev/md2 /dev/sd[ijklm]1
mdadm: looking for devices for /dev/md2
mdadm: /dev/sdi1 is identified as a member of /dev/md2, slot 4.
mdadm: /dev/sdj1 is identified as a member of /dev/md2, slot 1.
mdadm: /dev/sdk1 is identified as a member of /dev/md2, slot -1.
mdadm: /dev/sdl1 is identified as a member of /dev/md2, slot 3.
mdadm: /dev/sdm1 is identified as a member of /dev/md2, slot -1.
mdadm: no uptodate device for slot 0 of /dev/md2
mdadm: no uptodate device for slot 2 of /dev/md2
mdadm: added /dev/sdl1 to /dev/md2 as 3
mdadm: added /dev/sdi1 to /dev/md2 as 4
mdadm: added /dev/sdk1 to /dev/md2 as -1
mdadm: added /dev/sdm1 to /dev/md2 as -1
mdadm: added /dev/sdj1 to /dev/md2 as 1
mdadm: /dev/md2 assembled from 3 drives and 2 spares - not enough to start the array.
> 4) If that fails, show the output, then
>
> 5) mdadm --stop again, then retry the assemble leaving out the "m", like so:
>
> mdadm --assemble --force --verbose /dev/md2 /dev/sd[ijkl]1
~ # mdadm --stop /dev/md2
mdadm: stopped /dev/md2
~ # mdadm --assemble --force --verbose /dev/md2 /dev/sd[ijkl]1
mdadm: looking for devices for /dev/md2
mdadm: /dev/sdi1 is identified as a member of /dev/md2, slot 4.
mdadm: /dev/sdj1 is identified as a member of /dev/md2, slot 1.
mdadm: /dev/sdk1 is identified as a member of /dev/md2, slot -1.
mdadm: /dev/sdl1 is identified as a member of /dev/md2, slot 3.
mdadm: no uptodate device for slot 0 of /dev/md2
mdadm: no uptodate device for slot 2 of /dev/md2
mdadm: added /dev/sdl1 to /dev/md2 as 3
mdadm: added /dev/sdi1 to /dev/md2 as 4
mdadm: added /dev/sdk1 to /dev/md2 as -1
mdadm: added /dev/sdj1 to /dev/md2 as 1
mdadm: /dev/md2 assembled from 3 drives and 1 spare - not enough to start the array.
> And report its output.
~ # mdadm -D /dev/md2
/dev/md2:
Version : 1.2
Raid Level : raid0
Total Devices : 4
Persistence : Superblock is persistent
State : inactive
Working Devices : 4
Name : inet:2 (local to host inet)
UUID : 7c3e5def:31def6df:2ae53e66:e920a763
Events : 165464
Number Major Minor RaidDevice
- 8 177 - /dev/sdl1
- 8 161 - /dev/sdk1
- 8 145 - /dev/sdj1
- 8 129 - /dev/sdi1
~ # cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md2 : inactive sdj1[1](S) sdk1[0](S) sdl1[4](S) sdi1[5](S)
39048429568 blocks super 1.2
will not work, sorry
