I've now got SUSE 10.2 set up with RAID and LVM on my server. However,
I don't seem to be able to re-add a "failed" drive, without rebooting.
The drives are hot-swapable. When I use the command mdadm /dev/md0/
-add /dev/sdxx I get a "device busy" error message. Even removing the
drive with the
James Knott wrote:
> I've now got SUSE 10.2 set up with RAID and LVM on my server. However,
> I don't seem to be able to re-add a "failed" drive, without rebooting.
> The drives are hot-swapable. When I use the command mdadm /dev/md0/
> -add /dev/sdxx I get a "device busy" error message. Even
Rui Santos wrote:
> James Knott wrote:
>> I've now got SUSE 10.2 set up with RAID and LVM on my server. However,
>> I don't seem to be able to re-add a "failed" drive, without rebooting.
>> The drives are hot-swapable. When I use the command mdadm /dev/md0/
>> -add /dev/sdxx I get a "device b
Rui Santos wrote:
> Rui Santos wrote:
>
>> James Knott wrote:
>>
>>> I've now got SUSE 10.2 set up with RAID and LVM on my server. However,
>>> I don't seem to be able to re-add a "failed" drive, without rebooting.
>>> The drives are hot-swapable. When I use the command mdadm /dev/md0/
James Knott wrote:
> Rui Santos wrote:
>> Rui Santos wrote:
>>
>>> James Knott wrote:
>>>
I've now got SUSE 10.2 set up with RAID and LVM on my server. However,
I don't seem to be able to re-add a "failed" drive, without rebooting.
The drives are hot-swapable. When I use
Rui Santos wrote:
> James Knott wrote:
>
>> Rui Santos wrote:
>>
>>> Rui Santos wrote:
>>>
>>>
James Knott wrote:
> I've now got SUSE 10.2 set up with RAID and LVM on my server. However,
> I don't seem to be able to re-add a "failed" drive, wi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The Sunday 2007-06-24 at 23:06 -0400, James Knott wrote:
> netfinity:~ # mdadm --add /dev/md0 /dev/sdd2
> mdadm: add new device failed for /dev/sdd2 as 4: Invalid argument
>
> If I now reboot, I'll be able to add the drive, using the same command,
On Mon, 2007-06-25 at 11:49 +0200, Carlos E. R. wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> The Sunday 2007-06-24 at 23:06 -0400, James Knott wrote:
>
>
> > netfinity:~ # mdadm --add /dev/md0 /dev/sdd2
> > mdadm: add new device failed for /dev/sdd2 as 4: Invalid argument
> >
Roger Oberholtzer wrote:
> On Mon, 2007-06-25 at 11:49 +0200, Carlos E. R. wrote:
>
> The Sunday 2007-06-24 at 23:06 -0400, James Knott wrote:
>
>
> >>> netfinity:~ # mdadm --add /dev/md0 /dev/sdd2
> >>> mdadm: add new device failed for /dev/sdd2 as 4: Invalid argument
> >>>
> >>> If I now reboot,
Carlos E. R. wrote:
>
> The Sunday 2007-06-24 at 23:06 -0400, James Knott wrote:
>
>
> > netfinity:~ # mdadm --add /dev/md0 /dev/sdd2
> > mdadm: add new device failed for /dev/sdd2 as 4: Invalid argument
>
> > If I now reboot, I'll be able to add the drive, using the same command,
> > like so.
>
>
On 6/25/07, Roger Oberholtzer <[EMAIL PROTECTED]> wrote:
4. insert the new disks.
One more thing: I have a udev rule so my SATA disks have the same kernel
name when they are put in the same physical slot (I have 4 removable
SATS disks bays). If you do not have this, sdd can become sde (and s
On Mon, 2007-06-25 at 16:26 -0400, Greg Freemyer wrote:
> On 6/25/07, Roger Oberholtzer <[EMAIL PROTECTED]> wrote:
> > 4. insert the new disks.
> >
>
> >
> > One more thing: I have a udev rule so my SATA disks have the same kernel
> > name when they are put in the same physical slot (I have 4 remo
12 matches
Mail list logo
