Find the answer to your Linux question:
Results 1 to 4 of 4
Hello All, Last night I found my software raid 5 to be down. It is on a Server that is running Debian Squeeze 6.0.9 using 4x 3tb drives. I am ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Aug 2014
    Posts
    2

    Software Raid Down / Inactive - Need help troubleshooting / Recovering


    Hello All,

    Last night I found my software raid 5 to be down. It is on a Server that is running Debian Squeeze 6.0.9 using 4x 3tb drives. I am new with these and could really use some help troubleshooting this to get it back up. I am a newer Linux user though I have used multiple distros over the years for basic servers I am still a amateur and this current server is a file store for my home windows network.

    Below is the info I gathered so far.

    Any help would be truly appreciated.


    Code:
    # lsb_release -a
    No LSB modules are available.
    Distributor ID: Debian
    Description:    Debian GNU/Linux 6.0.9 (squeeze)
    Release:        6.0.9
    Codename:       squeeze
    Code:
    # mdadm --query /dev/md0
    /dev/md0: is an md device which is not active
    Code:
    # cat /proc/mdstat
    Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid
    id10]
    md0 : inactive sdc[1](S) sde[3](S) sdd[2](S) sdb[0](S)
          11721062240 blocks super 1.2
    
    unused devices: <none>
    Code:
    # mdadm --stop /dev/md0
    mdadm: stopped /dev/md0
    Code:
    # mdadm --assemble /dev/md0
    mdadm: /dev/md0 assembled from 2 drives - not enough to start the array.
    Code:
    # mdadm -D /dev/md0
    mdadm: md device /dev/md0 does not appear to be active.


    Code:
    # mdadm -E /dev/sdb
    /dev/sdb:
              Magic : a92b4efc
            Version : 1.2
        Feature Map : 0x0
         Array UUID : d8cac9e1:9e2562d9:b4e7a873:eb4d9723
               Name : Vault:0  (local to host Vault)
      Creation Time : Fri May  2 10:09:10 2014
         Raid Level : raid5
       Raid Devices : 4
    
     Avail Dev Size : 5860531120 (2794.52 GiB 3000.59 GB)
         Array Size : 17581590528 (8383.56 GiB 9001.77 GB
      Used Dev Size : 5860530176 (2794.52 GiB 3000.59 GB)
        Data Offset : 2048 sectors
       Super Offset : 8 sectors
              State : active
        Device UUID : a9d206fc:80dcbdee:328cfee3:9da0cf31
    
        Update Time : Wed Aug  6 14:47:48 2014
           Checksum : e1d64d08 - correct
             Events : 54338
    
             Layout : left-symmetric
         Chunk Size : 512K
    
       Device Role : Active device 0
       Array State : AA.A ('A' == active, '.' == missing)

    Code:
    # mdadm -E /dev/sdc
    /dev/sdc:
              Magic : a92b4efc
            Version : 1.2
        Feature Map : 0x0
         Array UUID : d8cac9e1:9e2562d9:b4e7a873:eb4d9723
               Name : Vault:0  (local to host Vault)
      Creation Time : Fri May  2 10:09:10 2014
         Raid Level : raid5
       Raid Devices : 4
    
     Avail Dev Size : 5860531120 (2794.52 GiB 3000.59 GB)
         Array Size : 17581590528 (8383.56 GiB 9001.77 GB
      Used Dev Size : 5860530176 (2794.52 GiB 3000.59 GB)
        Data Offset : 2048 sectors
       Super Offset : 8 sectors
              State : clean
        Device UUID : 690e5854:549b2e26:94ffb847:d8c66bdf
    
        Update Time : Thu Aug  7 22:09:50 2014
           Checksum : 82f1a505 - correct
             Events : 54694
    
             Layout : left-symmetric
         Chunk Size : 512K
    
       Device Role : Active device 1
       Array State : .A.A ('A' == active, '.' == missing)

    Code:
    # mdadm -E /dev/sdd
    /dev/sdd:
              Magic : a92b4efc
            Version : 1.2
        Feature Map : 0x0
         Array UUID : d8cac9e1:9e2562d9:b4e7a873:eb4d9723
               Name : Vault:0  (local to host Vault)
      Creation Time : Fri May  2 10:09:10 2014
         Raid Level : raid5
       Raid Devices : 4
    
     Avail Dev Size : 5860531120 (2794.52 GiB 3000.59 GB)
         Array Size : 17581590528 (8383.56 GiB 9001.77 GB
      Used Dev Size : 5860530176 (2794.52 GiB 3000.59 GB)
        Data Offset : 2048 sectors
       Super Offset : 8 sectors
              State : clean
        Device UUID : 28925ebc:0abd12f5:c6fe2dff:a18b69b0
    
        Update Time : Sun Aug  3 17:07:13 2014
           Checksum : 4246bc40 - correct
             Events : 6565
    
             Layout : left-symmetric
         Chunk Size : 512K
    
       Device Role : Active device 2
       Array State : AAAA ('A' == active, '.' == missing)

    Code:
    # mdadm -E /dev/sde
    /dev/sde:
              Magic : a92b4efc
            Version : 1.2
        Feature Map : 0x0
         Array UUID : d8cac9e1:9e2562d9:b4e7a873:eb4d9723
               Name : Vault:0  (local to host Vault)
      Creation Time : Fri May  2 10:09:10 2014
         Raid Level : raid5
       Raid Devices : 4
    
     Avail Dev Size : 5860531120 (2794.52 GiB 3000.59 GB)
         Array Size : 17581590528 (8383.56 GiB 9001.77 GB
      Used Dev Size : 5860530176 (2794.52 GiB 3000.59 GB)
        Data Offset : 2048 sectors
       Super Offset : 8 sectors
              State : clean
        Device UUID : d88c823c:0f1990dd:6b0679a0:b3a43e5e
    
        Update Time : Thu Aug  7 22:09:50 2014
           Checksum : fa107c93 - correct
             Events : 54694
    
             Layout : left-symmetric
         Chunk Size : 512K
    
       Device Role : Active device 3
       Array State : .A.A ('A' == active, '.' == missing)

  2. #2
    Linux Guru Rubberman's Avatar
    Join Date
    Apr 2009
    Location
    I can be found either 40 miles west of Chicago, in Chicago, or in a galaxy far, far away.
    Posts
    11,753
    Does the server have a GUI? If so, go to Applications->System Tools->Disk Utility (or something like that). That will provide you with better diagnostics to see what is wrong with the array. I use this on my RedHat clones (Scientific Linux and CentOS). Command line tools are great, and provide all the data you need, but can be difficult to interpret.
    Sometimes, real fast is almost as good as real time.
    Just remember, Semper Gumbi - always be flexible!

  3. #3
    Just Joined!
    Join Date
    Aug 2014
    Posts
    2
    Quote Originally Posted by Rubberman View Post
    Does the server have a GUI? If so, go to Applications->System Tools->Disk Utility (or something like that). That will provide you with better diagnostics to see what is wrong with the array. I use this on my RedHat clones (Scientific Linux and CentOS). Command line tools are great, and provide all the data you need, but can be difficult to interpret.
    The only GUI is OpenMediaVault, which provides little information on the RAID. If their is one I can install that would help diagnose this just let me know I am willing to try anything.

  4. $spacer_open
    $spacer_close
  5. #4
    Just Joined!
    Join Date
    Jul 2008
    Posts
    1
    Hello,

    If you saved the array into the configuration file previously you may also use scan argument with the assemble:
    mdadm --assemble --scan

    I found that the gnome-disks can handle RAID arrays. I don't know if it is available on Debian.

Posting Permissions

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