linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* addingdrive to raid 1
@ 2007-03-25  6:44 Robert Stanford
  2007-03-26 11:17 ` Neil Brown
  0 siblings, 1 reply; 2+ messages in thread
From: Robert Stanford @ 2007-03-25  6:44 UTC (permalink / raw)
  To: linux-raid

Hi All, Long time Linux software raid user, first real problem.

I built md2 with 1 missing drive and am now trying to add a drive (hda4)

The partition that is hda4 was previously part of another  raid array 
md1 that no longer exists.

I have zeroed the superblock in hda4, however when I try to add it it 
sync's instantly, no rebuild.

The original raid array md1 is several years old and was built with the 
old raidtools package.

I even ran
dd if=/dev/zero of=/dev/hda4
just to be sure that nothing was left on the partition from the previous 
raid setup and still no joy.

Any help would be appreciated

Kind Regards
Robert Stanford

---------------------------------------------------------
/proc/mdstat
Personalities : [raid1]
md2 : active raid1 hdc4[0]
      72894848 blocks [2/1] [U_]



mdadm --examine /dev/hdc4
/dev/hdc4:
          Magic : a92b4efc
        Version : 00.90.03
           UUID : 90844a43:c57dd8a1:5a5eed64:48faee6c
  Creation Time : Sat Mar 24 06:33:03 2007
     Raid Level : raid1
   Raid Devices : 2
  Total Devices : 1
Preferred Minor : 2

    Update Time : Sun Mar 25 16:30:59 2007
          State : clean
 Active Devices : 1
Working Devices : 1
 Failed Devices : 1
  Spare Devices : 0
       Checksum : 32ea145b - correct
         Events : 0.5610


      Number   Major   Minor   RaidDevice State
this     0      22        4        0      active sync   /dev/hdc4

   0     0      22        4        0      active sync   /dev/hdc4
   1     1       0        0        1      faulty removed



mdadm --examine /dev/hda4
mdadm: No super block found on /dev/hda4 (Expected magic a92b4efc, got 
00000000)



mdadm --add /dev/md2 /dev/hda4
mdadm: hot added /dev/hda4



Personalities : [raid1]
md2 : active raid1 hda4[1] hdc4[0]
      72894848 blocks [2/2] [UU]



 /var/log/kern.log
Mar 25 16:33:11 server kernel: md: bind<hda4>
Mar 25 16:33:11 server kernel: RAID1 conf printout:
Mar 25 16:33:11 server kernel:  --- wd:1 rd:2
Mar 25 16:33:11 server kernel:  disk 0, wo:0, o:1, dev:hdc4
Mar 25 16:33:11 server kernel:  disk 1, wo:1, o:1, dev:hda4
Mar 25 16:33:11 server kernel: md: syncing RAID array md2
Mar 25 16:33:11 server kernel: md: minimum _guaranteed_ reconstruction 
speed: 1000 KB/sec/disc.
Mar 25 16:33:11 server kernel: md: using maximum available idle IO 
bandwidth (but not more than 200000 KB/sec) for reconstruction.
Mar 25 16:33:11 server kernel: md: using 128k window, over a total of 
72894848 blocks.
Mar 25 16:33:11 server kernel: md: md2: sync done.
Mar 25 16:33:11 server kernel: RAID1 conf printout:
Mar 25 16:33:11 server kernel:  --- wd:2 rd:2
Mar 25 16:33:11 server kernel:  disk 0, wo:0, o:1, dev:hdc4
Mar 25 16:33:11 server kernel:  disk 1, wo:0, o:1, dev:hda4



mdadm --set-faulty  /dev/md2 /dev/hda4
mdadm: set /dev/hda4 faulty in /dev/md2
mdadm -r  /dev/md2 /dev/hda4
mdadm: hot removed /dev/hda4
mdadm --zero-superblock /dev/hda4



/var/log/kern.log
Mar 25 16:34:09 server kernel: raid1: Disk failure on hda4, disabling 
device.
Mar 25 16:34:09 server kernel: ^IOperation continuing on 1 devices
Mar 25 16:34:09 server kernel: RAID1 conf printout:
Mar 25 16:34:09 server kernel:  --- wd:1 rd:2
Mar 25 16:34:09 server kernel:  disk 0, wo:0, o:1, dev:hdc4
Mar 25 16:34:09 server kernel:  disk 1, wo:1, o:0, dev:hda4
Mar 25 16:34:09 server kernel: RAID1 conf printout:
Mar 25 16:34:09 server kernel:  --- wd:1 rd:2
Mar 25 16:34:09 server kernel:  disk 0, wo:0, o:1, dev:hdc4
Mar 25 16:34:13 server kernel: md: unbind<hda4>
Mar 25 16:34:13 server kernel: md: export_rdev(hda4)



mdadm --examine /dev/hda4
/dev/hda4:
          Magic : a92b4efc
        Version : 00.90.03
           UUID : 90844a43:c57dd8a1:5a5eed64:48faee6c
  Creation Time : Sat Mar 24 06:33:03 2007
     Raid Level : raid1
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 2

    Update Time : Sun Mar 25 16:33:11 2007
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0
       Checksum : 32ea14e0 - correct
         Events : 0.5616


      Number   Major   Minor   RaidDevice State
this     1       3        4        1      active sync   /dev/hda4

   0     0      22        4        0      active sync   /dev/hdc4
   1     1       3        4        1      active sync   /dev/hda4



^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: addingdrive to raid 1
  2007-03-25  6:44 addingdrive to raid 1 Robert Stanford
@ 2007-03-26 11:17 ` Neil Brown
  0 siblings, 0 replies; 2+ messages in thread
From: Neil Brown @ 2007-03-26 11:17 UTC (permalink / raw)
  To: Robert Stanford; +Cc: linux-raid

On Sunday March 25, rob@stanford.com.au wrote:
> Hi All, Long time Linux software raid user, first real problem.
> 
> I built md2 with 1 missing drive and am now trying to add a drive (hda4)
> 
> The partition that is hda4 was previously part of another  raid array 
> md1 that no longer exists.
> 
> I have zeroed the superblock in hda4, however when I try to add it it 
> sync's instantly, no rebuild.
> 
> The original raid array md1 is several years old and was built with the 
> old raidtools package.
> 
> I even ran
> dd if=/dev/zero of=/dev/hda4
> just to be sure that nothing was left on the partition from the previous 
> raid setup and still no joy.
> 
> Any help would be appreciated

You didn't say what kernel version.
I'd guess 2.6.18.  You want 2.6.18.2 or later to fix this problem.

NeilBrown

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2007-03-26 11:17 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-03-25  6:44 addingdrive to raid 1 Robert Stanford
2007-03-26 11:17 ` Neil Brown

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).