headers
Martin Diaz, Luis | 1 Dec 2010 11:02
Favicon

RE: replace one disk in isw RAID1 array

Dear Hanson

I could see your problem is generated by a exchange of disk. When you install the new disk and the raid-card
make the raid, it generate a new number of fake raid, completely different to the ancient number. 

I have had that problem and I solved it bootloading the server with a "tools distribution-disk" like the
fantastic (at last for me) systemrescuecd with the option "dodmraid" at prompt boot. When the
distribuition has loaded the server, already I could type all the differents orders of dmraid system like
"dmraid -s". So I could see the new number of fakeraid. This number is too important to write it because you
have to decompress the initrd of your server, looking for the old fake-raid number and exchange it.

As you can see, the problem you have, was caused by the initrd since it was wrote inside the number of the
fakeraid. This number is written when you install the server.

I have a script to resolve this problem in the IBM Xservers 205. I send you a copy to help you about this
question. This scripts has to run  on the systemrescuecd (of another system-tools distribution).

You may need to change the file /etc /fstab, but I'm not sure. In my case if I change it because I also use
logical volumes.

I hope I have helped in solving the problem and excuse for my bad english.

################################################################################
#                                                                              #
# Script que genera un nuevo initrd para los servidores IBM xSeries 205        #
# necesario cada vez que se regenera el RAID asi como en el proceso de         #
# instalacion                                                                  #
#                                                                              #
# Madrid 13 de Marzo de 2009                                                   #
# Luis Martin Diaz                                                             #
(Continue reading)

Permalink | Reply | 2 comments |
headers
Ian Stakenvicius, Aerobiology Research | 1 Dec 2010 15:32
Picon
Favicon

Re: replace one disk in isw RAID1 array

How did you add the new blank disk to the array?  ie, did you use the
Raid Setup in the BIOS to mark the disk as part of the array?  Or just
use dmraid commands?  I only have a little bit of experience with this,
but I believe the issue may have to do with the raid metadata on the new
disk being missing??

On 30/11/10 06:54 PM, Aaron Hanson wrote:
> Oops; forgot the most important command, where I try to initiate a rebuild with the new disk:
>
> bash (try 'info') lib > dmraid -dR isw_bdidaifdia_Raid1 /dev/sdb
> DEBUG: _find_set: searching isw_bdidaifdia
> DEBUG: _find_set: not found isw_bdidaifdia
> DEBUG: _find_set: searching isw_bdidaifdia_Raid1
> DEBUG: _find_set: searching isw_bdidaifdia_Raid1
> DEBUG: _find_set: not found isw_bdidaifdia_Raid1
> DEBUG: _find_set: not found isw_bdidaifdia_Raid1
> ERROR: isw: wrong number of devices in RAID set "isw_bdidaifdia_Raid1" [1/2] on /dev/sda
> DEBUG: set status of set "isw_bdidaifdia_Raid1" to 4
> DEBUG: _find_set: searching isw_bdidaifdia_Raid1
> DEBUG: _find_set: searching isw_bdidaifdia_Raid1
> DEBUG: _find_set: found isw_bdidaifdia_Raid1
> DEBUG: _find_set: found isw_bdidaifdia_Raid1
> DEBUG: _find_set: searching isw_bdidaifdia_Raid1
> DEBUG: _find_set: searching isw_bdidaifdia_Raid1
> DEBUG: _find_set: found isw_bdidaifdia_Raid1
> DEBUG: _find_set: found isw_bdidaifdia_Raid1
> DEBUG: _find_set: searching isw_bdidaifdia_Raid1
> DEBUG: _find_set: searching isw_bdidaifdia_Raid1
> DEBUG: _find_set: found isw_bdidaifdia_Raid1
> DEBUG: _find_set: found isw_bdidaifdia_Raid1
(Continue reading)

Permalink | Reply | 2 comments |
headers
Aaron Hanson | 1 Dec 2010 18:03
Favicon

RE: replace one disk in isw RAID1 array


> -----Original Message-----
> From: ataraid-list-bounces <at> redhat.com [mailto:ataraid-list-
> bounces <at> redhat.com] On Behalf Of Ian Stakenvicius, Aerobiology Research
> Sent: Wednesday, December 01, 2010 6:33 AM
> To: ATARAID (eg, Promise Fasttrak, Highpoint 370) related discussions
> Subject: Re: replace one disk in isw RAID1 array
> 
> How did you add the new blank disk to the array?  ie, did you use the Raid
> Setup in the BIOS to mark the disk as part of the array?  Or just use dmraid
> commands? 
[Aaron Hanson] 
I think I covered that. I simply did a physical disk replacement with power off.  After powering the system
back on, I tried to use 'dmraid -R <new device>' as an attempt to add the new device to the array.

But I'm new to ataraid; I don't really know that I'm using the correct procedure.  I'm looking for someone on
this list actually knows the typical and correct way to replace a disk in an ataraid array.  I presume there
is the simple step of physically replacing the bad disk with a good one, then some 'dmraid' commands. But 
can't seem to find the right 'dmraid' command(s).

Thanks for your response.

-Aaron
Permalink | Reply | 1 comment |
headers
Ian Stakenvicius, Aerobiology Research | 1 Dec 2010 18:16
Picon
Favicon

Re: replace one disk in isw RAID1 array

OK.  That, as far as I know, is not sufficient.  DMRAID allows the
kernel to set up raid devices based on the metadata that is on the
drives, but that metadata will not exist on the new drive, you have to
add it first (in the BIOS, most likely).  I would recommend rebooting
and entering the BIOS's raid management tool, and adding the new drive
to the array there.  It might let you do it without rebuilding the
array, but it might not.

I'm pretty sure that "dmraid -R" just triggers a rebuild procedure -- in
your case (ie with RAID1), it re-synchronizes the two drives.  But AFAIK
it won't set up a blank drive, ie, it won't create the proper metadata
on an uninitialized drive.

On 01/12/10 12:03 PM, Aaron Hanson wrote:
>
>> -----Original Message-----
>> From: ataraid-list-bounces <at> redhat.com [mailto:ataraid-list-
>> bounces <at> redhat.com] On Behalf Of Ian Stakenvicius, Aerobiology Research
>> Sent: Wednesday, December 01, 2010 6:33 AM
>> To: ATARAID (eg, Promise Fasttrak, Highpoint 370) related discussions
>> Subject: Re: replace one disk in isw RAID1 array
>>
>> How did you add the new blank disk to the array?  ie, did you use the Raid
>> Setup in the BIOS to mark the disk as part of the array?  Or just use dmraid
>> commands? 
> [Aaron Hanson] 
> I think I covered that. I simply did a physical disk replacement with power off.  After powering the system
back on, I tried to use 'dmraid -R <new device>' as an attempt to add the new device to the array.
>
> But I'm new to ataraid; I don't really know that I'm using the correct procedure.  I'm looking for someone on
(Continue reading)

Permalink | Reply | 0 comments |
headers
Aaron Hanson | 1 Dec 2010 18:20
Favicon

RE: replace one disk in isw RAID1 array

Hello Martin -
Comments in-line;

> -----Original Message-----
> From: ataraid-list-bounces <at> redhat.com [mailto:ataraid-list-
> bounces <at> redhat.com] On Behalf Of Martin Diaz, Luis
> Sent: Wednesday, December 01, 2010 2:02 AM
> To: ATARAID (eg, Promise Fasttrak, Highpoint 370) related discussions
> Subject: RE: replace one disk in isw RAID1 array
> 
> Dear Hanson
> 
> I could see your problem is generated by a exchange of disk. When you
> install the new disk and the raid-card make the raid, it generate a new
> number of fake raid, completely different to the ancient number.
> 
> I have had that problem and I solved it bootloading the server with a "tools
> distribution-disk" like the fantastic (at last for me) systemrescuecd with the
> option "dodmraid" at prompt boot. When the distribuition has loaded the
> server, already I could type all the differents orders of dmraid system like
> "dmraid -s". So I could see the new number of fakeraid. This number is too
> important to write it because you have to decompress the initrd of your
> server, looking for the old fake-raid number and exchange it.
> 
[Aaron Hanson] 
I think I understand the situation you are describing; the root device cannot be found by the kernel during
boot because it includes the name of the RAID, which has changed.  That is not the case for me. As you can see in
my earlier note, the name of the RAID set for me is ' isw_bdidaifdia_Raid1'; it is missing one member, but
the name has not changed.  It is true that the system is unable to boot after one member has been removed (this
is worrisome too). But I'm already doing as you suggested; I'm net-booting to a rescue linux system to
(Continue reading)

Permalink | Reply | 1 comment |
headers
Ian Stakenvicius, Aerobiology Research | 1 Dec 2010 18:34
Picon
Favicon

Re: replace one disk in isw RAID1 array

On 01/12/10 12:20 PM, Aaron Hanson wrote:
>
> It is true that the system is unable to boot after one member has been removed (this is worrisome too). 
This might have to do with the MBR's not being copied or installed on
both drives (or if you're using grub as your boot loader, it's
installation is still looking for the stage1.5 and stage2 files on the
first drive).  If this is the case, there are ways to get around it
(after your raid1 is back up and running, of course) by installing grub
manually on both disks.
Permalink | Reply | 0 comments |
headers
Luca Berra | 2 Dec 2010 08:44
Picon

Re: replace one disk in isw RAID1 array

On Tue, Nov 30, 2010 at 11:48:37PM +0000, Aaron Hanson wrote:
>Hi All -
>
>This seems like it should be a very common procedure.  I've researched this a lot before bothering this
list, I hope someone can comment. In short:
I have replaced dmraid with mdadm 3.1.x for handling intel matrix raid
and i find the interface much more understandable and better working.

L.

--

-- 
Luca Berra -- bluca <at> comedia.it
Permalink | Reply | 1 comment |
headers
Aaron Hanson | 2 Dec 2010 17:15
Favicon

RE: replace one disk in isw RAID1 array

> I have replaced dmraid with mdadm 3.1.x for handling intel matrix raid and i
> find the interface much more understandable and better working.
> 
> L.
> 
> --
> Luca Berra -- bluca <at> comedia.it
[Aaron Hanson] 
Thanks for the tip.  I am using an older version of mdadm but I will upgrade and give it a try.
-Aaron
Permalink | Reply | 0 comments |
headers
Ian Stakenvicius, Aerobiology Research | 13 Dec 2010 20:10
Picon
Favicon

build issues in dmraid-1.0.0.rc16-3

Hi -- while packaging this release for Gentoo, I ran into a few issues with the build system:

1.  --enable-shared_lib does nothing

2. the static lib always installs

3. when using --enable-static_lib and a recent device-mapper (from the lvm2 package), compilation fails due to the fact that it will not link against udev

I have patched my copy to deal with 2 and 3, and can provide these patches if desired.  I got around #3 using pkg-config checks.

Regards,
Ian

_______________________________________________
Ataraid-list mailing list
Ataraid-list <at> redhat.com
https://www.redhat.com/mailman/listinfo/ataraid-list
Permalink | Reply | 1 comment |
headers
Heinz Mauelshagen | 14 Dec 2010 10:48
Picon
Favicon

Re: build issues in dmraid-1.0.0.rc16-3

On Mon, 2010-12-13 at 14:10 -0500, Ian Stakenvicius, Aerobiology
Research wrote:
> Hi -- while packaging this release for Gentoo, I ran into a few issues
> with the build system:
> 
> 1.  --enable-shared_lib does nothing
> 
> 2. the static lib always installs
> 
> 3. when using --enable-static_lib and a recent device-mapper (from the
> lvm2 package), compilation fails due to the fact that it will not link
> against udev
> 
> I have patched my copy to deal with 2 and 3, and can provide these
> patches if desired.  I got around #3 using pkg-config checks.

Ian,

thanks for reporting these issues.
Please provide your patches.

Regards,
Heinz
> 
> Regards,
> Ian
> 
> _______________________________________________
> Ataraid-list mailing list
> Ataraid-list <at> redhat.com
> https://www.redhat.com/mailman/listinfo/ataraid-list
Permalink | Reply | 0 comments |

Gmane