Find the answer to your Linux question:
Results 1 to 3 of 3
I used to have a desktop working with 4 Disks in Raid 5 system but after some power failure the system crashed and now I have the 4 disks but ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Mar 2010
    Location
    Portugal
    Posts
    2

    Trouble to recover damaged RAID 5


    I used to have a desktop working with 4 Disks in Raid 5 system but after some power failure the system crashed and now I have the 4 disks but the RAID isn't working with all my files inside.
    I'm not expert in linux therefore any help is welcome.

    When I do the fdisk -l command this is what I get:

    ~# fdisk -l

    Disk /dev/sda: 60.0 GB, 60022480896 bytes
    255 heads, 63 sectors/track, 7297 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x09640963

    Device Boot Start End Blocks Id System
    /dev/sda1 * 1 7296 58605088+ 7 HPFS/NTFS

    Disk /dev/sdb: 250.1 GB, 250059350016 bytes
    255 heads, 63 sectors/track, 30401 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x0006f236

    Device Boot Start End Blocks Id System
    /dev/sdb1 * 1 13 104391 fd Linux raid autodetect
    /dev/sdb2 14 30401 244091610 fd Linux raid autodetect

    Disk /dev/sdc: 250.1 GB, 250059350016 bytes
    255 heads, 63 sectors/track, 30401 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x00071b11

    Device Boot Start End Blocks Id System
    /dev/sdc1 * 1 13 104391 fd Linux raid autodetect
    /dev/sdc2 14 30401 244091610 fd Linux raid autodetect

    Disk /dev/sdd: 250.1 GB, 250059350016 bytes
    255 heads, 63 sectors/track, 30401 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x00074429

    Device Boot Start End Blocks Id System
    /dev/sdd1 * 1 13 104391 fd Linux raid autodetect
    /dev/sdd2 14 30401 244091610 fd Linux raid autodetect

    Disk /dev/sde: 250.1 GB, 250059350016 bytes
    255 heads, 63 sectors/track, 30401 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x00076d0e

    Device Boot Start End Blocks Id System
    /dev/sde1 * 1 13 104391 fd Linux raid autodetect
    /dev/sde2 14 30401 244091610 fd Linux raid autodetect

    Disk /dev/md1: 106 MB, 106823680 bytes
    2 heads, 4 sectors/track, 26080 cylinders
    Units = cylinders of 8 * 512 = 4096 bytes
    Disk identifier: 0x291ac8f7

    Device Boot Start End Blocks Id System


    I can't run my /dev/md2 drive as it get's a error and when I try and see the partitions I can only see the sdb2 and sdc2 to the other 2 parts (sdd2 and sde2) I can't do anything as example:

    ~# mdadm -E /dev/sdb2
    /dev/sdb2:
    Magic : a92b4efc
    Version : 00.90.00
    UUID : 87d7046f:df6d1477:72ffd84f:4551f136
    Creation Time : Mon Jul 9 17:48:52 2007
    Raid Level : raid5
    Used Dev Size : 244091392 (232.78 GiB 249.95 GB)
    Array Size : 732274176 (698.35 GiB 749.85 GB)
    Raid Devices : 4
    Total Devices : 4
    Preferred Minor : 2

    Update Time : Tue Mar 16 15:33:41 2010
    State : clean
    Active Devices : 4
    Working Devices : 4
    Failed Devices : 0
    Spare Devices : 0
    Checksum : 69df4f7f - correct
    Events : 2999182

    Layout : left-symmetric
    Chunk Size : 256K

    Number Major Minor RaidDevice State
    this 0 8 2 0 active sync

    0 0 8 2 0 active sync
    1 1 8 18 1 active sync /dev/sdb2
    2 2 8 34 2 active sync /dev/sdc2
    3 3 8 50 3 active sync


    sdc2 is the same... but:

    ~# mdadm -E /dev/sdd2
    mdadm: cannot open /dev/sdd2: No such file or directory


    It seem slike there are 2 disks out of the raid...
    CAN ANYONE GIVE ME A HAND?
    Many thanks in advance.

  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,533
    Perhaps someone lurking on the forums can help you recover your data. It's a day late, so to speak, but to run a system with RAID and no UPS with automatic shutdown software is just asking for total disaster. With normal discs, a power failure usually will leave you with the ability to run fsck on your file system(s) and recover most of your data, or all of it with a journaling file system such as ext3, jfs, etc. With a RAID, a power failure is likely to scramble the discs enough to be completely unrecoverable.
    Sometimes, real fast is almost as good as real time.
    Just remember, Semper Gumbi - always be flexible!

  3. #3
    Just Joined!
    Join Date
    Mar 2010
    Location
    Portugal
    Posts
    2
    Thanks for your post. Although it isn't a tip to recover my data is always nice to have some concerned replys. My hope in this raid is 1 in a scale of 0-10 but I'm not givving up for the moment. I'm not a linux expert but maybe there is someone out there that just have the genius tip for me to do the right thing and then the miracle happens...

Posting Permissions

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