Topic: RAID complicated problem

[ocavid]

I have very uncomfortable problem.

This about my RAID (mirror)

with the command cat /proc/mdstat

Personalities : [raid1]
md2 : active raid1 sdb2[1]
      312464128 blocks [2/1] [_U]

md1 : active raid1 sdb1[1]
      101312 blocks [2/1] [_U]

unused devices: <none>

on the server console manage/manage disk redundancy this what i got.

Current Disk Status

Installed Dsiks: sda sdb
Used disks: sdb
Free disks: sda

There is an unused disk drive inyour system.  Do you want to add it the existing RAID array(s)?

WARNING: ALL DATA ON THE NEW DISK WILL BE DESTROYED!

<Yes> <No>

============================

with the command mdadm --detail /dev/md1 /dev/md2
/dev/md1:
        Version : 00.90.01
  Creation Time : Fri Jun 29 13:06:12 2007
     Raid Level : raid1
     Array Size : 101312 (98.95 MiB 103.74 MB)
    Device Size : 101312 (98.95 MiB 103.74 MB)
   Raid Devices : 2
  Total Devices : 1
Preferred Minor : 1
    Persistence : Superblock is persistent

    Update Time : Wed Feb 27 17:32:53 2008
          State : clean, degraded
 Active Devices : 1
Working Devices : 1
 Failed Devices : 0
  Spare Devices : 0

           UUID : a060ae7d:fba25698:a8495f9c:a3d4723e
         Events : 0.5432

    Number   Major   Minor   RaidDevice State
       0       0        0        -      removed
       1       8       17        1      active sync   /dev/sdb1
/dev/md2:
        Version : 00.90.01
  Creation Time : Fri Jun 29 13:06:13 2007
     Raid Level : raid1
     Array Size : 312464128 (297.99 GiB 319.96 GB)
    Device Size : 312464128 (297.99 GiB 319.96 GB)
   Raid Devices : 2
  Total Devices : 1
Preferred Minor : 2
    Persistence : Superblock is persistent

    Update Time : Wed Feb 27 17:46:45 2008
          State : clean, degraded
 Active Devices : 1
Working Devices : 1
 Failed Devices : 0
  Spare Devices : 0

           UUID : 31ef8d14:26795c09:48d8328e:c53afdee
         Events : 0.8876642

    Number   Major   Minor   RaidDevice State
       0       0        0        -      removed
       1       8       18        1      active sync   /dev/sdb2

Any guide to manually repair this problem?

thank you,
OcaVid

Additional info...

fdisk -l

Disk /dev/sda: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          13      101376+  fd  Linux raid autodetect
Partition 1 does not end on cylinder boundary.
/dev/sda2              13       38913   312467295   fd  Linux raid autodetect

Disk /dev/sdb: 320.0 GB, 320072933376 bytes
102 heads, 51 sectors/track, 120173 cylinders
Units = cylinders of 5202 * 512 = 2663424 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1          39      101413+  fd  Linux raid autodetect
/dev/sdb2              40      120173   312468534   fd  Linux raid autodetect

Disk /dev/md1: 103 MB, 103743488 bytes
2 heads, 4 sectors/track, 25328 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

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

Disk /dev/md2: 319.9 GB, 319963267072 bytes
2 heads, 4 sectors/track, 78116032 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

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

Disk /dev/dm-0: 317.7 GB, 317760471040 bytes
2 heads, 4 sectors/track, 77578240 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/dm-0 doesn't contain a valid partition table

Disk /dev/dm-1: 2080 MB, 2080374784 bytes
2 heads, 4 sectors/track, 507904 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/dm-1 doesn't contain a valid partition table

Disk /dev/dm-2: 320.0 GB, 320072932352 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

     Device Boot      Start         End      Blocks   Id  System
/dev/dm-2p1   *           1          13      101376+  fd  Linux raid autodetect
Partition 1 does not end on cylinder boundary.
/dev/dm-2p2              13       38913   312467295   fd  Linux raid autodetect

Disk /dev/dm-3: 103 MB, 103809536 bytes
255 heads, 63 sectors/track, 12 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-3 doesn't contain a valid partition table

Disk /dev/dm-4: 319.9 GB, 319966510080 bytes
255 heads, 63 sectors/track, 38900 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/dm-4 doesn't contain a valid partition table

[thomasch]

Looks like a normal pre-managed RAID1 to me..
just add sda to raid array from server console::5.manage disk redundancy

[Reinhold]

Seems there is more history to this than you have told us so far

Both disks are sized 320GB,
but geometries/partitions are significantly different  (not done by SME)
both are marked/partitioned as Raid ... (not by SME incl. 'problem')

Disk /dev/sda: 320.0 GB, 320072933376 bytes
Disk /dev/sdb: 320.0 GB, 320072933376 bytes

<sda>
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
<sdb>
102 heads, 51 sectors/track, 120173 cylinders
Units = cylinders of 5202 * 512 = 2663424 bytes

Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          13      101376+  fd  Linux raid autodetect
Partition 1 does not end on cylinder boundary.
/dev/sda2              13       38913   312467295   fd  Linux raid autodetect
   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1          39      101413+  fd  Linux raid autodetect
/dev/sdb2              40      120173   312468534   fd  Linux raid autodetect

You do have a working SME (obviously)

Assuming:
The disks ARE SAME MAKE AND MODEL  (does not seem to be true)
...some of the above is generated by a previous usage of sda
...and you have no data on sda that you might want to rescue
you might just try and follow thomasch's advice - go let SME do it's 'manage' thing 

IF SME FAILS ... than most likely you really have quite different disks
(look at heads  & sectors/track) ... which a stock SME cannot use
You may want to read:
http://wiki.contribs.org/Raid

Regards
Reinhold

P.S.: You might also want to clear the MBR on sda first
(DANGEROUS - know what you do !)
#dd if=/dev/zero of=/dev/sda bs=512 count=1

P.P.S.: If there is a need to continue pls post results of:
hdparm -I /dev/sda
hdparm -I /dev/sdb