Multipath Raid 6 - MDADM can't find superblocks - 18.04












0















I am running a server that connects to a multi-drive disk array, It is connected in a dual path configuration. Because of this, all of the drives show up twice.



I suffered a power outage and now the array is not assembling. I do however have the original commands I use. When I have attempted to assemble it says that there is no superblock.



mdadm: No super block found on /dev/mapper/35000c500415cbb87 (Expected magic a92b4efc, got 00000000)
mdadm: no RAID superblock on /dev/mapper/35000c500415cbb87


I have two questions:




  1. Is it possible to reassemble the array at this point or is any data lost?

  2. How should I do this properly to avoid this in the future.


Initial commands run:



-Attempted to setup array, realized that I had twice as many drives.
-Learned about multipath
-Built a config that included the excluded the non-multipath drivers (see below)
- Created a Raid6 array using the /dev/mapper/drives.
Commands:



sudo mdadm --create --verbose /dev/md0 --level=6 --raid-devices=12 dev/mapper/35000c500415cbb87 /dev/mapper/35000c500415cbbef /dev/mapper/35000c500415cfea3 /dev/mapper/35000c500415d0e3b /dev/mapper/35000c500415d6e3b /dev/mapper/35000c500415e456b /dev/mapper/35000c500415e4e5f /dev/mapper/35000c500415e8223 /dev/mapper/35000c500415ee867 /dev/mapper/35000c5004160b2df /dev/mapper/35000c5004160b6bb /dev/mapper/35000c50041611daf 

sudo mdadm -A /dev/mapper/35000c500415cbb87 /dev/mapper/35000c500415cbbef /dev/mapper/35000c500415cfea3 /dev/mapper/35000c500415d0e3b /dev/mapper/35000c500415d6e3b /dev/mapper/35000c500415e456b /dev/mapper/35000c500415e4e5f /dev/mapper/35000c500415e8223 /dev/mapper/35000c500415ee867 /dev/mapper/35000c5004160b2df /dev/mapper/35000c5004160b6bb /dev/mapper/35000c50041611daf

sudo mkfs.ext4 -F /dev/md0
sudo mkdir -p /mnt/md0
sudo mount /dev/md0 /mnt/md0
sudo mdadm --detail --scan | sudo tee -a /etc/mdadm/mdadm.conf
sudo update-initramfs -u


At that point, I setup folders and started using the drive, until the power outage shut it down. Upon restart, I cannot get it to reassemble.



/etc/multipath.conf



defaults {
user_friendly_names no
}
blacklist {
wwid "600508e000000000997d2e0655fb5108"
wwid "5002538d408c9715"
device {
vendor "Dell "
product "Virtual Disk "
}
}


/etc/mdadm/mdadm.conf



# wildcards if desired.
#DEVICE partitions containers

DEVICE /dev/mapper/35000c500415cbb87
DEVICE /dev/mapper/35000c500415cbbef
DEVICE /dev/mapper/35000c500415cfea3
DEVICE /dev/mapper/35000c500415d0e3b
DEVICE /dev/mapper/35000c500415d6e3b
DEVICE /dev/mapper/35000c500415e456b
DEVICE /dev/mapper/35000c500415e4e5f
DEVICE /dev/mapper/35000c500415e8223
DEVICE /dev/mapper/35000c500415ee867
DEVICE /dev/mapper/35000c5004160b2df
DEVICE /dev/mapper/35000c5004160b6bb
DEVICE /dev/mapper/35000c50041611daf


# automatically tag new arrays as belonging to the local system
HOMEHOST <system>

# instruct the monitoring daemon where to send mail alerts
#MAILADDR root

# definitions of existing MD arrays

# This configuration was auto-generated on Wed, 25 Jul 2018 23:01:52 +0000 by mkconf
ARRAY /dev/md0 metadata=1.2 name=media:0 UUID=5cfbe80c:d11c6b57:4beaff64:ed3bc6dd









share|improve this question







New contributor




Patch is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

























    0















    I am running a server that connects to a multi-drive disk array, It is connected in a dual path configuration. Because of this, all of the drives show up twice.



    I suffered a power outage and now the array is not assembling. I do however have the original commands I use. When I have attempted to assemble it says that there is no superblock.



    mdadm: No super block found on /dev/mapper/35000c500415cbb87 (Expected magic a92b4efc, got 00000000)
    mdadm: no RAID superblock on /dev/mapper/35000c500415cbb87


    I have two questions:




    1. Is it possible to reassemble the array at this point or is any data lost?

    2. How should I do this properly to avoid this in the future.


    Initial commands run:



    -Attempted to setup array, realized that I had twice as many drives.
    -Learned about multipath
    -Built a config that included the excluded the non-multipath drivers (see below)
    - Created a Raid6 array using the /dev/mapper/drives.
    Commands:



    sudo mdadm --create --verbose /dev/md0 --level=6 --raid-devices=12 dev/mapper/35000c500415cbb87 /dev/mapper/35000c500415cbbef /dev/mapper/35000c500415cfea3 /dev/mapper/35000c500415d0e3b /dev/mapper/35000c500415d6e3b /dev/mapper/35000c500415e456b /dev/mapper/35000c500415e4e5f /dev/mapper/35000c500415e8223 /dev/mapper/35000c500415ee867 /dev/mapper/35000c5004160b2df /dev/mapper/35000c5004160b6bb /dev/mapper/35000c50041611daf 

    sudo mdadm -A /dev/mapper/35000c500415cbb87 /dev/mapper/35000c500415cbbef /dev/mapper/35000c500415cfea3 /dev/mapper/35000c500415d0e3b /dev/mapper/35000c500415d6e3b /dev/mapper/35000c500415e456b /dev/mapper/35000c500415e4e5f /dev/mapper/35000c500415e8223 /dev/mapper/35000c500415ee867 /dev/mapper/35000c5004160b2df /dev/mapper/35000c5004160b6bb /dev/mapper/35000c50041611daf

    sudo mkfs.ext4 -F /dev/md0
    sudo mkdir -p /mnt/md0
    sudo mount /dev/md0 /mnt/md0
    sudo mdadm --detail --scan | sudo tee -a /etc/mdadm/mdadm.conf
    sudo update-initramfs -u


    At that point, I setup folders and started using the drive, until the power outage shut it down. Upon restart, I cannot get it to reassemble.



    /etc/multipath.conf



    defaults {
    user_friendly_names no
    }
    blacklist {
    wwid "600508e000000000997d2e0655fb5108"
    wwid "5002538d408c9715"
    device {
    vendor "Dell "
    product "Virtual Disk "
    }
    }


    /etc/mdadm/mdadm.conf



    # wildcards if desired.
    #DEVICE partitions containers

    DEVICE /dev/mapper/35000c500415cbb87
    DEVICE /dev/mapper/35000c500415cbbef
    DEVICE /dev/mapper/35000c500415cfea3
    DEVICE /dev/mapper/35000c500415d0e3b
    DEVICE /dev/mapper/35000c500415d6e3b
    DEVICE /dev/mapper/35000c500415e456b
    DEVICE /dev/mapper/35000c500415e4e5f
    DEVICE /dev/mapper/35000c500415e8223
    DEVICE /dev/mapper/35000c500415ee867
    DEVICE /dev/mapper/35000c5004160b2df
    DEVICE /dev/mapper/35000c5004160b6bb
    DEVICE /dev/mapper/35000c50041611daf


    # automatically tag new arrays as belonging to the local system
    HOMEHOST <system>

    # instruct the monitoring daemon where to send mail alerts
    #MAILADDR root

    # definitions of existing MD arrays

    # This configuration was auto-generated on Wed, 25 Jul 2018 23:01:52 +0000 by mkconf
    ARRAY /dev/md0 metadata=1.2 name=media:0 UUID=5cfbe80c:d11c6b57:4beaff64:ed3bc6dd









    share|improve this question







    New contributor




    Patch is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.























      0












      0








      0








      I am running a server that connects to a multi-drive disk array, It is connected in a dual path configuration. Because of this, all of the drives show up twice.



      I suffered a power outage and now the array is not assembling. I do however have the original commands I use. When I have attempted to assemble it says that there is no superblock.



      mdadm: No super block found on /dev/mapper/35000c500415cbb87 (Expected magic a92b4efc, got 00000000)
      mdadm: no RAID superblock on /dev/mapper/35000c500415cbb87


      I have two questions:




      1. Is it possible to reassemble the array at this point or is any data lost?

      2. How should I do this properly to avoid this in the future.


      Initial commands run:



      -Attempted to setup array, realized that I had twice as many drives.
      -Learned about multipath
      -Built a config that included the excluded the non-multipath drivers (see below)
      - Created a Raid6 array using the /dev/mapper/drives.
      Commands:



      sudo mdadm --create --verbose /dev/md0 --level=6 --raid-devices=12 dev/mapper/35000c500415cbb87 /dev/mapper/35000c500415cbbef /dev/mapper/35000c500415cfea3 /dev/mapper/35000c500415d0e3b /dev/mapper/35000c500415d6e3b /dev/mapper/35000c500415e456b /dev/mapper/35000c500415e4e5f /dev/mapper/35000c500415e8223 /dev/mapper/35000c500415ee867 /dev/mapper/35000c5004160b2df /dev/mapper/35000c5004160b6bb /dev/mapper/35000c50041611daf 

      sudo mdadm -A /dev/mapper/35000c500415cbb87 /dev/mapper/35000c500415cbbef /dev/mapper/35000c500415cfea3 /dev/mapper/35000c500415d0e3b /dev/mapper/35000c500415d6e3b /dev/mapper/35000c500415e456b /dev/mapper/35000c500415e4e5f /dev/mapper/35000c500415e8223 /dev/mapper/35000c500415ee867 /dev/mapper/35000c5004160b2df /dev/mapper/35000c5004160b6bb /dev/mapper/35000c50041611daf

      sudo mkfs.ext4 -F /dev/md0
      sudo mkdir -p /mnt/md0
      sudo mount /dev/md0 /mnt/md0
      sudo mdadm --detail --scan | sudo tee -a /etc/mdadm/mdadm.conf
      sudo update-initramfs -u


      At that point, I setup folders and started using the drive, until the power outage shut it down. Upon restart, I cannot get it to reassemble.



      /etc/multipath.conf



      defaults {
      user_friendly_names no
      }
      blacklist {
      wwid "600508e000000000997d2e0655fb5108"
      wwid "5002538d408c9715"
      device {
      vendor "Dell "
      product "Virtual Disk "
      }
      }


      /etc/mdadm/mdadm.conf



      # wildcards if desired.
      #DEVICE partitions containers

      DEVICE /dev/mapper/35000c500415cbb87
      DEVICE /dev/mapper/35000c500415cbbef
      DEVICE /dev/mapper/35000c500415cfea3
      DEVICE /dev/mapper/35000c500415d0e3b
      DEVICE /dev/mapper/35000c500415d6e3b
      DEVICE /dev/mapper/35000c500415e456b
      DEVICE /dev/mapper/35000c500415e4e5f
      DEVICE /dev/mapper/35000c500415e8223
      DEVICE /dev/mapper/35000c500415ee867
      DEVICE /dev/mapper/35000c5004160b2df
      DEVICE /dev/mapper/35000c5004160b6bb
      DEVICE /dev/mapper/35000c50041611daf


      # automatically tag new arrays as belonging to the local system
      HOMEHOST <system>

      # instruct the monitoring daemon where to send mail alerts
      #MAILADDR root

      # definitions of existing MD arrays

      # This configuration was auto-generated on Wed, 25 Jul 2018 23:01:52 +0000 by mkconf
      ARRAY /dev/md0 metadata=1.2 name=media:0 UUID=5cfbe80c:d11c6b57:4beaff64:ed3bc6dd









      share|improve this question







      New contributor




      Patch is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.












      I am running a server that connects to a multi-drive disk array, It is connected in a dual path configuration. Because of this, all of the drives show up twice.



      I suffered a power outage and now the array is not assembling. I do however have the original commands I use. When I have attempted to assemble it says that there is no superblock.



      mdadm: No super block found on /dev/mapper/35000c500415cbb87 (Expected magic a92b4efc, got 00000000)
      mdadm: no RAID superblock on /dev/mapper/35000c500415cbb87


      I have two questions:




      1. Is it possible to reassemble the array at this point or is any data lost?

      2. How should I do this properly to avoid this in the future.


      Initial commands run:



      -Attempted to setup array, realized that I had twice as many drives.
      -Learned about multipath
      -Built a config that included the excluded the non-multipath drivers (see below)
      - Created a Raid6 array using the /dev/mapper/drives.
      Commands:



      sudo mdadm --create --verbose /dev/md0 --level=6 --raid-devices=12 dev/mapper/35000c500415cbb87 /dev/mapper/35000c500415cbbef /dev/mapper/35000c500415cfea3 /dev/mapper/35000c500415d0e3b /dev/mapper/35000c500415d6e3b /dev/mapper/35000c500415e456b /dev/mapper/35000c500415e4e5f /dev/mapper/35000c500415e8223 /dev/mapper/35000c500415ee867 /dev/mapper/35000c5004160b2df /dev/mapper/35000c5004160b6bb /dev/mapper/35000c50041611daf 

      sudo mdadm -A /dev/mapper/35000c500415cbb87 /dev/mapper/35000c500415cbbef /dev/mapper/35000c500415cfea3 /dev/mapper/35000c500415d0e3b /dev/mapper/35000c500415d6e3b /dev/mapper/35000c500415e456b /dev/mapper/35000c500415e4e5f /dev/mapper/35000c500415e8223 /dev/mapper/35000c500415ee867 /dev/mapper/35000c5004160b2df /dev/mapper/35000c5004160b6bb /dev/mapper/35000c50041611daf

      sudo mkfs.ext4 -F /dev/md0
      sudo mkdir -p /mnt/md0
      sudo mount /dev/md0 /mnt/md0
      sudo mdadm --detail --scan | sudo tee -a /etc/mdadm/mdadm.conf
      sudo update-initramfs -u


      At that point, I setup folders and started using the drive, until the power outage shut it down. Upon restart, I cannot get it to reassemble.



      /etc/multipath.conf



      defaults {
      user_friendly_names no
      }
      blacklist {
      wwid "600508e000000000997d2e0655fb5108"
      wwid "5002538d408c9715"
      device {
      vendor "Dell "
      product "Virtual Disk "
      }
      }


      /etc/mdadm/mdadm.conf



      # wildcards if desired.
      #DEVICE partitions containers

      DEVICE /dev/mapper/35000c500415cbb87
      DEVICE /dev/mapper/35000c500415cbbef
      DEVICE /dev/mapper/35000c500415cfea3
      DEVICE /dev/mapper/35000c500415d0e3b
      DEVICE /dev/mapper/35000c500415d6e3b
      DEVICE /dev/mapper/35000c500415e456b
      DEVICE /dev/mapper/35000c500415e4e5f
      DEVICE /dev/mapper/35000c500415e8223
      DEVICE /dev/mapper/35000c500415ee867
      DEVICE /dev/mapper/35000c5004160b2df
      DEVICE /dev/mapper/35000c5004160b6bb
      DEVICE /dev/mapper/35000c50041611daf


      # automatically tag new arrays as belonging to the local system
      HOMEHOST <system>

      # instruct the monitoring daemon where to send mail alerts
      #MAILADDR root

      # definitions of existing MD arrays

      # This configuration was auto-generated on Wed, 25 Jul 2018 23:01:52 +0000 by mkconf
      ARRAY /dev/md0 metadata=1.2 name=media:0 UUID=5cfbe80c:d11c6b57:4beaff64:ed3bc6dd






      raid mdadm multipath






      share|improve this question







      New contributor




      Patch is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      share|improve this question







      New contributor




      Patch is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      share|improve this question




      share|improve this question






      New contributor




      Patch is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked 4 hours ago









      PatchPatch

      1




      1




      New contributor




      Patch is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      Patch is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      Patch is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






















          0






          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "89"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });






          Patch is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1110761%2fmultipath-raid-6-mdadm-cant-find-superblocks-18-04%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          Patch is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          Patch is a new contributor. Be nice, and check out our Code of Conduct.













          Patch is a new contributor. Be nice, and check out our Code of Conduct.












          Patch is a new contributor. Be nice, and check out our Code of Conduct.
















          Thanks for contributing an answer to Ask Ubuntu!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1110761%2fmultipath-raid-6-mdadm-cant-find-superblocks-18-04%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          GameSpot

          connect to host localhost port 22: Connection refused

          Getting a Wifi WPA2 wifi connection