mdadm mounting array no such file or directory error

Question

I'm Getting this Error when I try to integrate Crashlytics with my Project. I used the Crashlytics plugin to generate the code . But when I do a sync in Gradle it gives e the following error. I have also attavhed the build.gradle

Error:Unable to find method 'org.apache.http.conn.ssl.SSLConnectionSocketFactory.(Ljavax/net/ssl/SSLContext;Ljavax/net/ssl/HostnameVerifier;)V'. Possible causes for this unexpected error include:

• Gradle's dependency cache may be corrupt (this sometimes occurs after a network connection timeout.) Re-download dependencies and sync project (requires network)
• The state of a Gradle build process (daemon) may be corrupt. Stopping all Gradle daemons may solve this problem. Stop Gradle build processes (requires restart)
• Your project may be using a third-party plugin which is not compatible with the other plugins in the project or the version of Gradle requested by the project.

In the case of corrupt Gradle processes, you can also try closing the IDE and then killing all Java processes.

I have tried Invalidating the cache and also Redownload dependencies and also stoping the Gradle build and starting it.

I'm also connected to the Internet.

The Build works fine if I remove the crashlytics dependency.

Can anyone tell e how to fix this.

build.gradle

buildscript {
    repositories {
        mavenCentral()
        maven { url 'https://maven.fabric.io/public' }
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:2.2.2'
        classpath 'io.fabric.tools:gradle:1.+'
    }
}
apply plugin: 'com.android.application'
apply plugin: 'io.fabric'

repositories {
    mavenCentral()
    maven { url 'https://maven.fabric.io/public' }
}

android {
    compileSdkVersion 23
    buildToolsVersion "22.0.1"

    defaultConfig {
        minSdkVersion 16
        targetSdkVersion 22
    }
}

dependencies {
    compile 'com.android.support:support-v4:23.0.0'
    compile 'com.android.support:support-v13:23.0.0'
    compile 'com.android.support:appcompat-v7:23.0.0'
    compile 'com.android.support:palette-v7:23.0.0'
    compile 'com.android.support:recyclerview-v7:23.0.0'
    compile 'com.android.support:cardview-v7:23.0.0'
    compile 'com.squareup.okhttp3:okhttp:3.1.2'
    compile files('libs/volley.jar')
    compile('com.crashlytics.sdk.android:crashlytics:2.6.5@aar') {
        transitive = true;
    }
}

Solution

For the record, re-formatting my comments as an answer.

The first step is to look for raid devices status:

$ cat /proc/mdstat
...

OP output includes:

md1 : active raid6 sde2[0] sdd2[1]
      1046528 blocks super 1.2 level 6, 512k chunk, algorithm 2 [4/2] [UU__]

This indicates that two out of 4 devices from your /dev/md1 device are missing.

Now, since we can see that md0 is healthy, using 4 partitions: two of which on the same disks md1 uses, it is then fair to bet we can recover that array by re-adding partitions from the disks that are not listed as md1 devices:

mdadm --manage /dev/md1 add /dev/sdc2
mdadm --manage /dev/md1 add /dev/sdf2

Reboot, in doubt, ...

Now, it appears we're still missing a third raid device ... You might be able to find it back using:

mdadm --assemble --scan

Maybe:

mdadm --assemble /dev/md127 /dev/sdc3 /dev/sdd3 /dev/sde3 /dev/sdf3

Comments

[SYN]

look at cat /proc/mdstat to confirm your arrays availability, edit your post including output, ...

[whitebear]

I added /proc/mdstat data. there is no data-0 entry..... I remember that when my nas server worked properly there were md0 md1 md127.

[SYN]

Looks like your md1 is missing 2 out of 4 devices. No traces of data-0 or md127 though. Looks like md1 is a raid6: you should still be able to recover it, re-adding the missing disks (or adding replacement ones). Since your md0 is still healthy, and considering it share two disks with md1, ... Have you tried something like mdadm --manage /dev/md1 --add /dev/sdc2, then mdadm --manage /dev/md1 add /dev/sdf2?

[whitebear]

You are saving my life. I could add two disks to md1. it looks to work correctly. then... how can I mount this and reach the data???

[SYN]

Not being familiar with your hadware: maybe you will find entries in your /etc/fstab, referring to your /dev/md1. If so, just type mount /path/on/the/left/column to mount corresponding device. You might have to scan for logical volumes first (? unlikely, not impossible, vgscan then vgchange -a y VolName). In doubt: you should be able to reboot from there, and let boot process do whatever it used to

[whitebear]

Thank you for your help. You gave me one step forward, but I have found md1 block 1046528 is too small for my purpose md* I updated my article.

[whitebear]

Thanks for your help it is quit good advice for me and I could pointed out the problem.

[whitebear]

mdadm --assemble /dev/md127 /dev/sdc3 /dev/sdd3 /dev/sde3 /dev/sdf3 worked perfectly!!. The raid started with only 3 drives (maybe one drive was corrupted) thank you very much!!