problem with the inactive RAID 5












2














I have a server running ubuntu server, after a crash, I lost a Disc.
Here is the output:



cat /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10]
md0 : active raid1 cciss/c0d0p1[0] cciss/c0d1p1[1] cciss/c0d2p1[2]
489856 blocks [3/3] [UUU]

md2 : active raid1 cciss/c0d0p3[0] cciss/c0d1p3[1] cciss/c0d2p3[2]
138938048 blocks [3/3] [UUU]

md1 : active raid1 cciss/c0d0p2[0] cciss/c0d1p2[1] cciss/c0d2p2[2]
3903680 blocks [3/3] [UUU]

md3 : inactive cciss/c0d5p1[2](S) cciss/c0d3p1[0](S) cciss/c0d4p1[1](S) cciss/c0d6p1[3](S)
573327104 blocks

cat /etc/mdadm/mdadm.conf
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
DEVICE partitions

# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes

# 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
ARRAY /dev/md0 level=raid1 num-devices=3 UUID=e36f9237:d7a2a830:b3dedfb7:5e31bd86
ARRAY /dev/md1 level=raid1 num-devices=3 UUID=f1b3fc22:5cbadae9:c68d4e56:4c57b156
ARRAY /dev/md2 level=raid1 num-devices=3 UUID=58a9609b:3132051a:018fbdf9:bef9dca9
ARRAY /dev/md3 level=raid5 num-devices=5 UUID=459df1f2:70ea10af:40314e29:0652aa8c

# This file was auto-generated on Thu, 07 Aug 2008 03:22:07 +0000


Help










share|improve this question
























  • Could you also show us mdadm --detail /dev/md3?
    – rudimeier
    Sep 16 '16 at 9:47










  • Is this Software RAID using slices from the HP Smart Array controller or Hardware RAID mapped through into userspace? If it's the second won't you need to use the BIOS-level RAID configuration utility to fix the array?
    – roaima
    Sep 16 '16 at 9:48










  • thank you for your reply, i think that Hardware RAID mapped through into userspace, how i can have the confirmation ?because i have not been configured
    – olifa
    Sep 16 '16 at 11:16










  • output off :~# mdadm --detail /dev/md3 mdadm: md device /dev/md3 does not appear to be active.
    – olifa
    Sep 16 '16 at 11:16










  • mdadm --examine /dev/cciss/c0d?p1?
    – frostschutz
    Sep 16 '16 at 12:25
















2














I have a server running ubuntu server, after a crash, I lost a Disc.
Here is the output:



cat /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10]
md0 : active raid1 cciss/c0d0p1[0] cciss/c0d1p1[1] cciss/c0d2p1[2]
489856 blocks [3/3] [UUU]

md2 : active raid1 cciss/c0d0p3[0] cciss/c0d1p3[1] cciss/c0d2p3[2]
138938048 blocks [3/3] [UUU]

md1 : active raid1 cciss/c0d0p2[0] cciss/c0d1p2[1] cciss/c0d2p2[2]
3903680 blocks [3/3] [UUU]

md3 : inactive cciss/c0d5p1[2](S) cciss/c0d3p1[0](S) cciss/c0d4p1[1](S) cciss/c0d6p1[3](S)
573327104 blocks

cat /etc/mdadm/mdadm.conf
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
DEVICE partitions

# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes

# 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
ARRAY /dev/md0 level=raid1 num-devices=3 UUID=e36f9237:d7a2a830:b3dedfb7:5e31bd86
ARRAY /dev/md1 level=raid1 num-devices=3 UUID=f1b3fc22:5cbadae9:c68d4e56:4c57b156
ARRAY /dev/md2 level=raid1 num-devices=3 UUID=58a9609b:3132051a:018fbdf9:bef9dca9
ARRAY /dev/md3 level=raid5 num-devices=5 UUID=459df1f2:70ea10af:40314e29:0652aa8c

# This file was auto-generated on Thu, 07 Aug 2008 03:22:07 +0000


Help










share|improve this question
























  • Could you also show us mdadm --detail /dev/md3?
    – rudimeier
    Sep 16 '16 at 9:47










  • Is this Software RAID using slices from the HP Smart Array controller or Hardware RAID mapped through into userspace? If it's the second won't you need to use the BIOS-level RAID configuration utility to fix the array?
    – roaima
    Sep 16 '16 at 9:48










  • thank you for your reply, i think that Hardware RAID mapped through into userspace, how i can have the confirmation ?because i have not been configured
    – olifa
    Sep 16 '16 at 11:16










  • output off :~# mdadm --detail /dev/md3 mdadm: md device /dev/md3 does not appear to be active.
    – olifa
    Sep 16 '16 at 11:16










  • mdadm --examine /dev/cciss/c0d?p1?
    – frostschutz
    Sep 16 '16 at 12:25














2












2








2


1





I have a server running ubuntu server, after a crash, I lost a Disc.
Here is the output:



cat /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10]
md0 : active raid1 cciss/c0d0p1[0] cciss/c0d1p1[1] cciss/c0d2p1[2]
489856 blocks [3/3] [UUU]

md2 : active raid1 cciss/c0d0p3[0] cciss/c0d1p3[1] cciss/c0d2p3[2]
138938048 blocks [3/3] [UUU]

md1 : active raid1 cciss/c0d0p2[0] cciss/c0d1p2[1] cciss/c0d2p2[2]
3903680 blocks [3/3] [UUU]

md3 : inactive cciss/c0d5p1[2](S) cciss/c0d3p1[0](S) cciss/c0d4p1[1](S) cciss/c0d6p1[3](S)
573327104 blocks

cat /etc/mdadm/mdadm.conf
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
DEVICE partitions

# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes

# 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
ARRAY /dev/md0 level=raid1 num-devices=3 UUID=e36f9237:d7a2a830:b3dedfb7:5e31bd86
ARRAY /dev/md1 level=raid1 num-devices=3 UUID=f1b3fc22:5cbadae9:c68d4e56:4c57b156
ARRAY /dev/md2 level=raid1 num-devices=3 UUID=58a9609b:3132051a:018fbdf9:bef9dca9
ARRAY /dev/md3 level=raid5 num-devices=5 UUID=459df1f2:70ea10af:40314e29:0652aa8c

# This file was auto-generated on Thu, 07 Aug 2008 03:22:07 +0000


Help










share|improve this question















I have a server running ubuntu server, after a crash, I lost a Disc.
Here is the output:



cat /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10]
md0 : active raid1 cciss/c0d0p1[0] cciss/c0d1p1[1] cciss/c0d2p1[2]
489856 blocks [3/3] [UUU]

md2 : active raid1 cciss/c0d0p3[0] cciss/c0d1p3[1] cciss/c0d2p3[2]
138938048 blocks [3/3] [UUU]

md1 : active raid1 cciss/c0d0p2[0] cciss/c0d1p2[1] cciss/c0d2p2[2]
3903680 blocks [3/3] [UUU]

md3 : inactive cciss/c0d5p1[2](S) cciss/c0d3p1[0](S) cciss/c0d4p1[1](S) cciss/c0d6p1[3](S)
573327104 blocks

cat /etc/mdadm/mdadm.conf
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
DEVICE partitions

# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes

# 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
ARRAY /dev/md0 level=raid1 num-devices=3 UUID=e36f9237:d7a2a830:b3dedfb7:5e31bd86
ARRAY /dev/md1 level=raid1 num-devices=3 UUID=f1b3fc22:5cbadae9:c68d4e56:4c57b156
ARRAY /dev/md2 level=raid1 num-devices=3 UUID=58a9609b:3132051a:018fbdf9:bef9dca9
ARRAY /dev/md3 level=raid5 num-devices=5 UUID=459df1f2:70ea10af:40314e29:0652aa8c

# This file was auto-generated on Thu, 07 Aug 2008 03:22:07 +0000


Help







raid mdadm






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 16 at 15:48









Kusalananda

121k16229372




121k16229372










asked Sep 16 '16 at 8:55









olifa

114




114












  • Could you also show us mdadm --detail /dev/md3?
    – rudimeier
    Sep 16 '16 at 9:47










  • Is this Software RAID using slices from the HP Smart Array controller or Hardware RAID mapped through into userspace? If it's the second won't you need to use the BIOS-level RAID configuration utility to fix the array?
    – roaima
    Sep 16 '16 at 9:48










  • thank you for your reply, i think that Hardware RAID mapped through into userspace, how i can have the confirmation ?because i have not been configured
    – olifa
    Sep 16 '16 at 11:16










  • output off :~# mdadm --detail /dev/md3 mdadm: md device /dev/md3 does not appear to be active.
    – olifa
    Sep 16 '16 at 11:16










  • mdadm --examine /dev/cciss/c0d?p1?
    – frostschutz
    Sep 16 '16 at 12:25


















  • Could you also show us mdadm --detail /dev/md3?
    – rudimeier
    Sep 16 '16 at 9:47










  • Is this Software RAID using slices from the HP Smart Array controller or Hardware RAID mapped through into userspace? If it's the second won't you need to use the BIOS-level RAID configuration utility to fix the array?
    – roaima
    Sep 16 '16 at 9:48










  • thank you for your reply, i think that Hardware RAID mapped through into userspace, how i can have the confirmation ?because i have not been configured
    – olifa
    Sep 16 '16 at 11:16










  • output off :~# mdadm --detail /dev/md3 mdadm: md device /dev/md3 does not appear to be active.
    – olifa
    Sep 16 '16 at 11:16










  • mdadm --examine /dev/cciss/c0d?p1?
    – frostschutz
    Sep 16 '16 at 12:25
















Could you also show us mdadm --detail /dev/md3?
– rudimeier
Sep 16 '16 at 9:47




Could you also show us mdadm --detail /dev/md3?
– rudimeier
Sep 16 '16 at 9:47












Is this Software RAID using slices from the HP Smart Array controller or Hardware RAID mapped through into userspace? If it's the second won't you need to use the BIOS-level RAID configuration utility to fix the array?
– roaima
Sep 16 '16 at 9:48




Is this Software RAID using slices from the HP Smart Array controller or Hardware RAID mapped through into userspace? If it's the second won't you need to use the BIOS-level RAID configuration utility to fix the array?
– roaima
Sep 16 '16 at 9:48












thank you for your reply, i think that Hardware RAID mapped through into userspace, how i can have the confirmation ?because i have not been configured
– olifa
Sep 16 '16 at 11:16




thank you for your reply, i think that Hardware RAID mapped through into userspace, how i can have the confirmation ?because i have not been configured
– olifa
Sep 16 '16 at 11:16












output off :~# mdadm --detail /dev/md3 mdadm: md device /dev/md3 does not appear to be active.
– olifa
Sep 16 '16 at 11:16




output off :~# mdadm --detail /dev/md3 mdadm: md device /dev/md3 does not appear to be active.
– olifa
Sep 16 '16 at 11:16












mdadm --examine /dev/cciss/c0d?p1?
– frostschutz
Sep 16 '16 at 12:25




mdadm --examine /dev/cciss/c0d?p1?
– frostschutz
Sep 16 '16 at 12:25










1 Answer
1






active

oldest

votes


















0














Excuse me for the late reply, i found the solution by following this procedure



mdadm --stop /dev/md3 then
mdadm --assemble --force /dev/md3






share|improve this answer





















    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "106"
    };
    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: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    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
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f310296%2fproblem-with-the-inactive-raid-5%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    Excuse me for the late reply, i found the solution by following this procedure



    mdadm --stop /dev/md3 then
    mdadm --assemble --force /dev/md3






    share|improve this answer


























      0














      Excuse me for the late reply, i found the solution by following this procedure



      mdadm --stop /dev/md3 then
      mdadm --assemble --force /dev/md3






      share|improve this answer
























        0












        0








        0






        Excuse me for the late reply, i found the solution by following this procedure



        mdadm --stop /dev/md3 then
        mdadm --assemble --force /dev/md3






        share|improve this answer












        Excuse me for the late reply, i found the solution by following this procedure



        mdadm --stop /dev/md3 then
        mdadm --assemble --force /dev/md3







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Sep 22 '16 at 12:34









        olifa

        114




        114






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Unix & Linux Stack Exchange!


            • 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.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • 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%2funix.stackexchange.com%2fquestions%2f310296%2fproblem-with-the-inactive-raid-5%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

            Morgemoulin

            Scott Moir

            Souastre