Find the answer to your Linux question:
Results 1 to 6 of 6
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1

    Failed RAID5 array grow after reboot interruption

    I used mdadm to create a RAID 5 array awhile ago (6 months) and I have 5 tb hard drives in it and wanted to grow it to 8 tb hard drives. It stated that it was going to take it 3 days to do, which is perfectly fine. It was going fine and then after about 2 days my electricity went out. So this completely interrupted the grow process obviously. So I started searching on google for a solution. I came up with this link: thread. At the sixth post it explains how he was able to correct his problem. All he had to do was get his version of mdadm to v2.6.4. The version of mdadm that I am usuing is v2.6.2. Well his problem is a little different. I can login into the desktop environment so I have easy access to everything. I don't want to loose any data that I have on the RAID 5 because it is very important and I should have backed it up but didn't. So anyways, I could try and update mdadm to v2.6.4 but not exactly sure how and didn't want to loose anything if i just tried to update it. I am pretty new with linux so please be easy with me and explain stuff in detail (it would just help me out a lot ). When i run this command
    mdadm --examine /dev/sdi1
    this is what I get:

    harold@server:~$ sudo mdadm --examine /dev/sdi1
              Magic : a92b4efc
            Version : 00.91.00
               UUID : 72fa18f5:bf5d1a62:31a05266:02bffc2c
      Creation Time : Mon Feb 11 16:48:31 2008
         Raid Level : raid5
      Used Dev Size : 976759936 (931.51 GiB 1000.20 GB)
         Array Size : 6837319552 (6520.58 GiB 7001.42 GB)
       Raid Devices : 8
      Total Devices : 8
    Preferred Minor : 0
      Reshape pos'n : 4642814400 (4427.73 GiB 4754.24 GB)
      Delta Devices : 3 (5->8)
        Update Time : Thu Jul 17 15:01:47 2008
              State : clean
     Active Devices : 8
    Working Devices : 8
     Failed Devices : 0
      Spare Devices : 0
           Checksum : 3d26208 - correct
             Events : 0.441232
             Layout : left-symmetric
         Chunk Size : 64K
          Number   Major   Minor   RaidDevice State
    this     4       8      129        4      active sync   /dev/sdi1
       0     0       8       49        0      active sync   /dev/sdd1
       1     1       8       81        1      active sync   /dev/sdf1
       2     2       8       97        2      active sync   /dev/sdg1
       3     3       8      113        3      active sync   /dev/sdh1
       4     4       8      129        4      active sync   /dev/sdi1
       5     5       8       65        5      active sync   /dev/sde1
       6     6       8       33        6      active sync   /dev/sdc1
       7     7       8       17        7      active sync   /dev/sdb1
    Any help at all would be great! Thanks!


  2. #2
    Linux Enthusiast likwid's Avatar
    Join Date
    Dec 2006
    And what is the error you get when you try to assemble the array? or how bout mdadm -E /dev/mdX where X is the md device.

  3. #3
    Here is what I get with some commands:

    harold@server:~$ sudo mdadm --assemble /dev/md0
    mdadm: no devices found for /dev/md0
    harold@server:~$ sudo mdadm --examine /dev/md0
    mdadm: No md superblock detected on /dev/md0.
    harold@server:~$ sudo mdadm --detail /dev/md0
    mdadm: md device /dev/md0 does not appear to be active.
    harold@server:~$ sudo mdadm --E /dev/md0
    mdadm: unrecognized option `--E'

  4. $spacer_open
  5. #4
    Can I just upgrade mdadm and not loose anything or will it affect it?

  6. #5
    According to this thread
    HTML Code:
    he has said that he was able to assemble his array back together but never said if he lost his data or not. I was just wondering if anybody knows if this would. I really don't want to try it if not sure because I don't wanna loose data

    In the last post he says this:

    It's been a long time coming, but I managed to work out the answer.
    The RAID array was intact, but needs to be assembled:
    mdadm --assemble /dev/md0 /dev/sdb1 /dev/sdc1 /dev/sdd1 /dev/sde1
    And then 
    cat /proc/mdstat
    will give the status of it building (it took my array 4 days!)
    But growing the array does not update the /etc/mdadm.conf file. To update:
    mdadm --detail --scan >> /etc/mdadm.conf
    and then 
    vi /etc/mdadm.conf 
    to get rid of the old entry.
    Now, you should be set to grow the file system on the array. It wasn't pretty, or fun, but I got there in the end.

  7. #6
    Any help at all would be great! I am not the greatest with linux and can't find anywhere what I should do.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts