Login or Register to Ask a Question and Join Our Community


SuSE

Raid5

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems Linux SuSE Raid5
# 1  
Old 03-21-2012
Raid5
Hi all,

I am currently using opensuse 12.1,
We have Raid 5 array of 8 disks. A friend of mine accidently removed a drive & place it back and also added a new disk to it(making it 9 disks). now the output of mdadm --detail is as shown below

Code:
si64:/dev # mdadm --detail /dev/md3
/dev/md3:
        Version : 01.00.03
  Creation Time : Sun Oct 23 16:04:53 2011
     Raid Level : raid5
     Array Size : 6837318656 (6520.58 GiB 7001.41 GB)
  Used Dev Size : 1953519616 (1863.02 GiB 2000.40 GB)
   Raid Devices : 8
  Total Devices : 7
Preferred Minor : 3
    Persistence : Superblock is persistent

  Intent Bitmap : Internal

    Update Time : Wed Mar 21 13:11:11 2012
          State : active, degraded
 Active Devices : 6
Working Devices : 6
 Failed Devices : 1
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 128K

           Name : 3
           UUID : ff736409:5b1a6101:0f1f75c0:529a4f95
         Events : 71108

    Number   Major   Minor   RaidDevice State
       0       8       33        0      active sync   /dev/sdc1
       1       8       49        1      active sync   /dev/sdd1
       2       8       65        2      active sync   /dev/sde1
       3       0        0        3      removed
       4       8       97        4      active sync   /dev/sdg1
       5       8      113        5      active sync   /dev/sdh1
       6       8      129        6      active sync   /dev/sdi1
       7       0        0        7      removed

       3       8       81        -      faulty spare
si64:/dev #

the output of fdisk -l
Code:
si64:/dev # fdisk -l

Disk /dev/sda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0009d7e4

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1        3134    25173823+  fd  Linux raid autodetect
/dev/sda2   *        3135       14593    92044417+  fd  Linux raid autodetect

Disk /dev/sdb: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000b4651

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1        3134    25173823+  fd  Linux raid autodetect
/dev/sdb2            3135       14593    92044417+  fd  Linux raid autodetect

Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0003805f

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1               1      121601   976760001   fd  Linux raid autodetect

Disk /dev/sdd: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000e6da1

   Device Boot      Start         End      Blocks   Id  System
/dev/sdd1               1      121601   976760001   fd  Linux raid autodetect

Disk /dev/sde: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x5c2facf2

   Device Boot      Start         End      Blocks   Id  System
/dev/sde1               1      121601   976760001   fd  Linux raid autodetect

Disk /dev/sdg: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000d3e99

   Device Boot      Start         End      Blocks   Id  System
/dev/sdg1               1      121601   976760001   fd  Linux raid autodetect

Disk /dev/sdh: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x5c2face6

   Device Boot      Start         End      Blocks   Id  System
/dev/sdh1               1      121601   976760001   fd  Linux raid autodetect

Disk /dev/sdi: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000001

   Device Boot      Start         End      Blocks   Id  System
/dev/sdi1               1      121601   976760001   fd  Linux raid autodetect

Disk /dev/sdj: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000d272b

   Device Boot      Start         End      Blocks   Id  System
/dev/sdj1               1      121601   976760001   fd  Linux raid autodetect

Disk /dev/md1: 94.2 GB, 94253408256 bytes
2 heads, 4 sectors/track, 23011086 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x00000000

Disk /dev/md1 doesn't contain a valid partition table

Disk /dev/md0: 25.7 GB, 25777917952 bytes
2 heads, 4 sectors/track, 6293437 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x00000000

Disk /dev/md0 doesn't contain a valid partition table

Disk /dev/md3: 7001.4 GB, 7001414303744 bytes
2 heads, 4 sectors/track, 1709329664 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x00000000

Disk /dev/md3 doesn't contain a valid partition table

Disk /dev/sdk: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0003ac92

   Device Boot      Start         End      Blocks   Id  System
/dev/sdk1               1      267350  2147483647+  83  Linux
/dev/sdk4               1           1           0+  ee  EFI GPT

Partition table entries are not in disk order

Disk /dev/sdl: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000b6b5b

   Device Boot      Start         End      Blocks   Id  System
/dev/sdl1               1      121601   976760001   fd  Linux raid autodetect
si64:/dev #

prior to this we dint have any disks with 'removed' status.
How do I fix this?

Please let me know if you need more info

Thank you,
Raj
# 2  
Old 03-22-2012
This is not SUSE specific. Read this, it will give you what you need:


The Software-RAID HOWTO
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Red Hat

Install RHEL6 on x3650M4 with RAID5

Hi All, I have a new x3650 M4 server with hardware RAID 5 configured 4 x 300 GB (HDD). The Raid controller is ServeRAID M5110e. Im getting "device not found" error during hardisk detection of RHEL6 install using DVD. Some pages over the net pointed to using ServerGuide media for... (1 Reply)
Discussion started by: Solaris_Begin
1 Replies

2. Hardware

RAID5 + STRIPED LUNs

Hello Experts, I have few doubts on RAID 5 with LUNs carved as STRIPE and CONCAT RAID 5 = STRIPE + Parity mirroring I would like to know if the LUNs carved are CONCATE from RAID 5 disk array. Are the I/Os are spread accross the disks within the RAID 5 Array? And if I do carve STRIPED... (1 Reply)
Discussion started by: sybadm
1 Replies

3. UNIX for Advanced & Expert Users

RAID5 multi disk failure

Hi there, Don't know if my title is relevant but I'm dealing with dangerous materials that I don't really know and I'm very afraid to mess anything up. I have a Debian 5.0.4 server with 4 x 1TB hard drives. I have the following mdstat Personalities : md1 : active raid1 sda1 sdd1... (3 Replies)
Discussion started by: chebarbudo
3 Replies

4. Filesystems, Disks and Memory

Problem booting a linux (RAID5)

Hello, we have a problem with our system, a machine with a RAID5: - We can boot the system from CD only, if we try to boot from hard-disk the GRUB seems to be "freezed". What is the difference, why we can boot from CD if something is wrong? - Allways we retreive an error like: "raid array is... (6 Replies)
Discussion started by: aristegui
6 Replies

5. AIX

how to mirror raid5

Hi, I have an ssa filesystem to move to san. We don't want any downtime. I heard that you can do a mirroring of existing file system on the san. The file system is a type of either raid 0, raid 1, or raid 5. Anyone know how to do this? Thanks in advance, itik (4 Replies)
Discussion started by: itik
4 Replies

6. AIX

Software-based RAID5 on Aix

Hello All. Is it possible? (5 Replies)
Discussion started by: sapbcer
5 Replies

7. Solaris

RAID5 problems on solaris

I have one volume raid5 with 3 slice one of them is maintenance state. I replace this slice and resync the volume. when I try to mount the file system another slice goes to last erred. Again resync and the state goes to OK but the slice in mantenance persist. I try to enabled this but persist in... (2 Replies)
Discussion started by: usdsia
2 Replies

8. AIX

Can not increase capacity of the vg using raid5 with ssa disks

hi all, i have an p620 server. it has 2 scsi 18gb disks for aix4.3 OS and 3 ssa disks for database and an serialRAID adapter. 3 ssa disks configured raid level 5. to increase capacity of the datavg, i buy 2 ssa 18gb disks. but i can not add them to the existing datavg. i did the following... (1 Reply)
Discussion started by: tinhlx
1 Replies

9. SCO

Raid5 Failure

Forgive me, I do not know much about RAID so I'm going to be as detailed as possible. This morning, our server's alarm was going. I found that one of our drives have failed. (we have 3) It is an Adaptec ATA RAID 2400A controller I'm purchasing a new SCSI drive today. My questions: ... (2 Replies)
Discussion started by: gseyforth
2 Replies

10. SCO

image src to raid5 sco open server

Hi all! I am in need of some advice. I have a sco open server with NO redundancy. I am exploring different ways of trying to backup everything. Either to an image (ghost) or tape. Only problem is I dont know how. Using ghost in windows is pretty straight forward, but not know much about unix I... (1 Reply)
Discussion started by: dlucas313
1 Replies
Login or Register to Ask a Question