Topic: SME Raid 5 Problem

[BoZz]

Hello all,

I just build a SME box to replace my old one with 4 harddrives. Install went well including software raid. So I removed one drive to test raid and box started without problem. Replaced drive and all ok except the array has not picked the drive backup? I have read some posts but still unsure how I rebuild the raid on drive 4 ? Any feedback would be very helpful. raid info below:

Personalities : [raid1] [raid5]
md2 : active raid5 sdc2[2] sdb2[1] sda2[0]
      585761280 blocks level 5, 256k chunk, algorithm 2 [4/3] [UUU_]
     
md1 : active raid1 sdc1[2] sdb1[1] sda1[0]
      104320 blocks [4/3] [UUU_]


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

Disk /dev/sda: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          13      104391   fd  Linux raid autodetect
/dev/sda2              14       24321   195254010   fd  Linux raid autodetect

Disk /dev/sdb: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

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

Disk /dev/sdc: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

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

Disk /dev/sdd: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdd1   *           1          13      104391   fd  Linux raid autodetect
/dev/sdd2              14       24321   195254010   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 /dev/md2: 599.8 GB, 599819550720 bytes
2 heads, 4 sectors/track, 146440320 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

[chaloner]

Usually the hardware would take care of it...

What controller do you have? Have you tired shutdown and go into the controller bios and look at any options for drive replacement and rebuild?

Chaloner Hale

[BoZz]

I'm running software raid.

[mike_mattos]

I ran into problems with 2 SATA drives, finally erased the second drive, reinstalled it and the RAID system saw the new drive, prompted me to add it and did a full repair.

But as long as I used a drive with apartitions, the raid system would not do a repair.

[BoZz]

have removed to partitions but have not been prompted to do a raid repair?

[BoZz]

Thanks for the tip, one little command ( mdadm -a /dev/md1 /dev/sdd ) and all is good, it's now rebuilding.


thanks

brett

www.wxdata.com.au

[BoZz]

The raid has failed to build, any ideas
Disk /dev/sdd doesn't contain a valid partition table
Disk /dev/md1 doesn't contain a valid partition table
Disk /dev/md2 doesn't contain a valid partition table

Disk /dev/sda: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1          13      104391   fd  Linux raid autodetect
/dev/sda2              14       24321   195254010   fd  Linux raid autodetect

Disk /dev/sdb: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

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

Disk /dev/sdc: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

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

Disk /dev/sdd: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes


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


Disk /dev/md2: 599.8 GB, 599819550720 bytes
2 heads, 4 sectors/track, 146440320 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

[kruhm]

Software raids are partition based, not disk based. Your new disk doesn't have any partitions. You need to:
-partition it then.
-add the partitions back into the raid.

[Snoopyski]

Hello,

I got the same problem with a RAID 1 !!!

TO fix it YOU have 2 choice !!!

Put a brand new hard drive with same spec...

Or do a "Quick Erase" Low Level Format/Zero Format with the same drive you pull off...

Please let me know,

Snoopyski