md_import_device returned -16 raid1

md_import_device returned -16 raid1

[Jim Radford]

Greetings all:

Having a bit of difficulty with raid1, I built the array lastnight with 
two new drives, and it built fine but when I rebooted I get the following 
error when trying to start the array:

I'm running Mandrake 10.1 kernel 2.6.8.1-12mdk

[root@localhost jradford]# mdadm --version
mdadm - v1.7.0 - 11 August 2004

[root@bengali jradford]# mdadm -A -s
mdadm: failed to add /dev/hdc to /dev/md0: Device or resource busy
mdadm: /dev/md0 has been started with 1 drive (out of 2).

The following error message shows up in dmesg:

[root@bengali jradford]# dmesg | grep md:
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.
md: md0 stopped.
md: could not lock unknown-block(22,0).
md: md_import_device returned -16
md: bind<hdb>

my /proc/mdstat:

[root@bengali jradford]# cat /proc/mdstat
Personalities : [raid1]
md0 : active raid1 hdb[0]
       195360896 blocks [2/1] [U_]

unused devices: <none>

Some drive specific information

[root@bengali jradford]# mdadm -E /dev/hdb
/dev/hdb:
           Magic : a92b4efc
         Version : 00.90.00
            UUID : 9d09bd52:e44dc514:4e6b732f:5263e2f8
   Creation Time : Fri Jul 15 21:16:18 2005
      Raid Level : raid1
     Device Size : 195360896 (186.31 GiB 200.05 GB)
    Raid Devices : 2
   Total Devices : 2
Preferred Minor : 0

     Update Time : Sat Jul 16 07:33:32 2005
           State : clean
  Active Devices : 2
Working Devices : 2
  Failed Devices : 0
   Spare Devices : 0
        Checksum : 5ca8741a - correct
          Events : 0.326


       Number   Major   Minor   RaidDevice State
this     0       3       64        0      active sync   /dev/hdb

    0     0       3       64        0      active sync   /dev/hdb
    1     1      22        0        1      active sync   /dev/hdc

[root@localhost jradford]# mdadm -E /dev/hdc
/dev/hdc:
           Magic : a92b4efc
         Version : 00.90.00
            UUID : 9d09bd52:e44dc514:4e6b732f:5263e2f8
   Creation Time : Fri Jul 15 21:16:18 2005
      Raid Level : raid1
     Device Size : 195360896 (186.31 GiB 200.05 GB)
    Raid Devices : 2
   Total Devices : 2
Preferred Minor : 0

     Update Time : Sat Jul 16 07:33:32 2005
           State : clean
  Active Devices : 2
Working Devices : 2
  Failed Devices : 0
   Spare Devices : 0
        Checksum : 5ca873ef - correct
          Events : 0.326


       Number   Major   Minor   RaidDevice State
this     1      22        0        1      active sync   /dev/hdc

    0     0       3       64        0      active sync   /dev/hdb
    1     1      22        0        1      active sync   /dev/hdc

And for the md status:

[root@bengali mdadm-2.0-devel-2]# mdadm -D /dev/md0
/dev/md0:
         Version : 00.90.01
   Creation Time : Fri Jul 15 21:16:18 2005
      Raid Level : raid1
      Array Size : 195360896 (186.31 GiB 200.05 GB)
     Device Size : 195360896 (186.31 GiB 200.05 GB)
    Raid Devices : 2
   Total Devices : 1
Preferred Minor : 0
     Persistence : Superblock is persistent

     Update Time : Sat Jul 16 07:33:32 2005
           State : clean, degraded
  Active Devices : 1
Working Devices : 1
  Failed Devices : 0
   Spare Devices : 0

            UUID : 9d09bd52:e44dc514:4e6b732f:5263e2f8
          Events : 0.326

     Number   Major   Minor   RaidDevice State
        0       3       64        0      active sync   /dev/hdb
        1       0        0        -      removed



If I try and add hdc to the array With version 1.9.0 I get
mdadm: hot add failed for /dev/hdc: Invalid argument
but the same message in dmesg as above.

with 2.0devel2 I get:
mdadm: Cannot open /dev/hdc: Device or resource busy
But also the same message in dmesg as above

Any advice would be greatly appreciated.

Regards,
Jim

-- 
==========================================================================
Jim Radford <jradford@npl.com>
http://www.jimradford.com/
==========================================================================

Re: md_import_device returned -16 raid1

[Tyler]

Unless the mandrake kernel has backported patches in its kernel sources, 
I would suggest trying a newer kernel... current is 2.6.12.2, and just 
about 2.6.13.

Tyler.

Jim Radford wrote:

> Greetings all:
>
> Having a bit of difficulty with raid1, I built the array lastnight 
> with two new drives, and it built fine but when I rebooted I get the 
> following error when trying to start the array:
>
> I'm running Mandrake 10.1 kernel 2.6.8.1-12mdk
>
> [root@localhost jradford]# mdadm --version
> mdadm - v1.7.0 - 11 August 2004
>
> [root@bengali jradford]# mdadm -A -s
> mdadm: failed to add /dev/hdc to /dev/md0: Device or resource busy
> mdadm: /dev/md0 has been started with 1 drive (out of 2).
>
> The following error message shows up in dmesg:
>
> [root@bengali jradford]# dmesg | grep md:
> md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
> md: Autodetecting RAID arrays.
> md: autorun ...
> md: ... autorun DONE.
> md: md0 stopped.
> md: could not lock unknown-block(22,0).
> md: md_import_device returned -16
> md: bind<hdb>
>
> my /proc/mdstat:
>
> [root@bengali jradford]# cat /proc/mdstat
> Personalities : [raid1]
> md0 : active raid1 hdb[0]
>       195360896 blocks [2/1] [U_]
>
> unused devices: <none>
>
> Some drive specific information
>
> [root@bengali jradford]# mdadm -E /dev/hdb
> /dev/hdb:
>           Magic : a92b4efc
>         Version : 00.90.00
>            UUID : 9d09bd52:e44dc514:4e6b732f:5263e2f8
>   Creation Time : Fri Jul 15 21:16:18 2005
>      Raid Level : raid1
>     Device Size : 195360896 (186.31 GiB 200.05 GB)
>    Raid Devices : 2
>   Total Devices : 2
> Preferred Minor : 0
>
>     Update Time : Sat Jul 16 07:33:32 2005
>           State : clean
>  Active Devices : 2
> Working Devices : 2
>  Failed Devices : 0
>   Spare Devices : 0
>        Checksum : 5ca8741a - correct
>          Events : 0.326
>
>
>       Number   Major   Minor   RaidDevice State
> this     0       3       64        0      active sync   /dev/hdb
>
>    0     0       3       64        0      active sync   /dev/hdb
>    1     1      22        0        1      active sync   /dev/hdc
>
> [root@localhost jradford]# mdadm -E /dev/hdc
> /dev/hdc:
>           Magic : a92b4efc
>         Version : 00.90.00
>            UUID : 9d09bd52:e44dc514:4e6b732f:5263e2f8
>   Creation Time : Fri Jul 15 21:16:18 2005
>      Raid Level : raid1
>     Device Size : 195360896 (186.31 GiB 200.05 GB)
>    Raid Devices : 2
>   Total Devices : 2
> Preferred Minor : 0
>
>     Update Time : Sat Jul 16 07:33:32 2005
>           State : clean
>  Active Devices : 2
> Working Devices : 2
>  Failed Devices : 0
>   Spare Devices : 0
>        Checksum : 5ca873ef - correct
>          Events : 0.326
>
>
>       Number   Major   Minor   RaidDevice State
> this     1      22        0        1      active sync   /dev/hdc
>
>    0     0       3       64        0      active sync   /dev/hdb
>    1     1      22        0        1      active sync   /dev/hdc
>
> And for the md status:
>
> [root@bengali mdadm-2.0-devel-2]# mdadm -D /dev/md0
> /dev/md0:
>         Version : 00.90.01
>   Creation Time : Fri Jul 15 21:16:18 2005
>      Raid Level : raid1
>      Array Size : 195360896 (186.31 GiB 200.05 GB)
>     Device Size : 195360896 (186.31 GiB 200.05 GB)
>    Raid Devices : 2
>   Total Devices : 1
> Preferred Minor : 0
>     Persistence : Superblock is persistent
>
>     Update Time : Sat Jul 16 07:33:32 2005
>           State : clean, degraded
>  Active Devices : 1
> Working Devices : 1
>  Failed Devices : 0
>   Spare Devices : 0
>
>            UUID : 9d09bd52:e44dc514:4e6b732f:5263e2f8
>          Events : 0.326
>
>     Number   Major   Minor   RaidDevice State
>        0       3       64        0      active sync   /dev/hdb
>        1       0        0        -      removed
>
>
>
> If I try and add hdc to the array With version 1.9.0 I get
> mdadm: hot add failed for /dev/hdc: Invalid argument
> but the same message in dmesg as above.
>
> with 2.0devel2 I get:
> mdadm: Cannot open /dev/hdc: Device or resource busy
> But also the same message in dmesg as above
>
> Any advice would be greatly appreciated.
>
> Regards,
> Jim
>

Re: md_import_device returned -16 raid1

[Jim Radford]

I've got a 2.6.11 kernel which has 0.90.1 instead of 0.90.0 md driver in it, 
and the same errors occur. What version of the md driver is in 2.6.12/3?

Thanks
Jim

md: md driver 0.90.1 MAX_MD_DEVS=256, MD_SB_DISKS=27

On Sat, 16 Jul 2005, Tyler wrote:
> Unless the mandrake kernel has backported patches in its kernel sources, I 
> would suggest trying a newer kernel... current is 2.6.12.2, and just about 
> 2.6.13.
> 
> Tyler.
> 
> Jim Radford wrote:
> 
>> Greetings all:
>> 
>> Having a bit of difficulty with raid1, I built the array lastnight with 
>> two new drives, and it built fine but when I rebooted I get the following 
>> error when trying to start the array:
>> 
>> I'm running Mandrake 10.1 kernel 2.6.8.1-12mdk
>> 
>> [root@localhost jradford]# mdadm --version
>> mdadm - v1.7.0 - 11 August 2004
>> 
>> [root@bengali jradford]# mdadm -A -s
>>> failed to add /dev/hdc to /dev/md0: Device or resource busy
>>> /dev/md0 has been started with 1 drive (out of 2).
>> 
>> The following error message shows up in dmesg:
>> 
>> [root@bengali jradford]# dmesg | grep md:
>>> md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
>>> Autodetecting RAID arrays.
>>> autorun ...
>>> ... autorun DONE.
>>> md0 stopped.
>>> could not lock unknown-block(22,0).
>>> md_import_device returned -16
>>> bind<hdb>
>> 
>> my /proc/mdstat:
>> 
>> [root@bengali jradford]# cat /proc/mdstat
>> Personalities : [raid1]
>> md0 : active raid1 hdb[0]
>> 195360896 blocks [2/1] [U_]
>> 
>> unused devices: <none>
>> 
>> Some drive specific information
>> 
>> [root@bengali jradford]# mdadm -E /dev/hdb
>> /dev/hdb:
>> Magic : a92b4efc
>> Version : 00.90.00
>>        UUID : 9d09bd52:e44dc514:4e6b732f:5263e2f8
>> Creation Time : Fri Jul 15 21:16:18 2005
>> Raid Level : raid1
>> Device Size : 195360896 (186.31 GiB 200.05 GB)
>> Raid Devices : 2
>> Total Devices : 2
>> Preferred Minor : 0
>> 
>> Update Time : Sat Jul 16 07:33:32 2005
>>        State : clean
>> Active Devices : 2
>> Working Devices : 2
>> Failed Devices : 0
>> Spare Devices : 0
>> Checksum : 5ca8741a - correct
>> Events : 0.326
>> 
>> 
>>     Number   Major   Minor   RaidDevice State
>> this     0       3       64        0      active sync   /dev/hdb
>> 
>> 0     0       3       64        0      active sync   /dev/hdb
>> 1     1      22        0        1      active sync   /dev/hdc
>> 
>> [root@localhost jradford]# mdadm -E /dev/hdc
>> /dev/hdc:
>> Magic : a92b4efc
>> Version : 00.90.00
>>        UUID : 9d09bd52:e44dc514:4e6b732f:5263e2f8
>> Creation Time : Fri Jul 15 21:16:18 2005
>> Raid Level : raid1
>> Device Size : 195360896 (186.31 GiB 200.05 GB)
>> Raid Devices : 2
>> Total Devices : 2
>> Preferred Minor : 0
>> 
>> Update Time : Sat Jul 16 07:33:32 2005
>>        State : clean
>> Active Devices : 2
>> Working Devices : 2
>> Failed Devices : 0
>> Spare Devices : 0
>> Checksum : 5ca873ef - correct
>> Events : 0.326
>> 
>> 
>>     Number   Major   Minor   RaidDevice State
>> this     1      22        0        1      active sync   /dev/hdc
>> 
>> 0     0       3       64        0      active sync   /dev/hdb
>> 1     1      22        0        1      active sync   /dev/hdc
>> 
>> And for the md status:
>> 
>> [root@bengali mdadm-2.0-devel-2]# mdadm -D /dev/md0
>> /dev/md0:
>>     Version : 00.90.01
>> Creation Time : Fri Jul 15 21:16:18 2005
>> Raid Level : raid1
>> Array Size : 195360896 (186.31 GiB 200.05 GB)
>> Device Size : 195360896 (186.31 GiB 200.05 GB)
>> Raid Devices : 2
>> Total Devices : 1
>> Preferred Minor : 0
>> Persistence : Superblock is persistent
>> 
>> Update Time : Sat Jul 16 07:33:32 2005
>>        State : clean, degraded
>> Active Devices : 1
>> Working Devices : 1
>> Failed Devices : 0
>> Spare Devices : 0
>> 
>> UUID : 9d09bd52:e44dc514:4e6b732f:5263e2f8
>> Events : 0.326
>> 
>> Number   Major   Minor   RaidDevice State
>> 0       3       64        0      active sync   /dev/hdb
>> 1       0        0        -      removed
>> 
>> 
>> 
>> If I try and add hdc to the array With version 1.9.0 I get
>> mdadm: hot add failed for /dev/hdc: Invalid argument
>> but the same message in dmesg as above.
>> 
>> with 2.0devel2 I get:
>> mdadm: Cannot open /dev/hdc: Device or resource busy
>> But also the same message in dmesg as above
>> 
>> Any advice would be greatly appreciated.
>> 
>> Regards,
>> Jim
> 
>

-- 
==========================================================================
Jim Radford <jradford@npl.com>
http://www.jimradford.com/
==========================================================================

Re: md_import_device returned -16 raid1

[Neil Brown]

On Saturday July 16, jradford@npl.com wrote:
> Greetings all:
> 
> Having a bit of difficulty with raid1, I built the array lastnight with 
> two new drives, and it built fine but when I rebooted I get the following 
> error when trying to start the array:
> 
> I'm running Mandrake 10.1 kernel 2.6.8.1-12mdk
> 
> [root@localhost jradford]# mdadm --version
> mdadm - v1.7.0 - 11 August 2004
> 
> [root@bengali jradford]# mdadm -A -s
> mdadm: failed to add /dev/hdc to /dev/md0: Device or resource busy

This is telling you that /dev/hdc is 'busy'.
Maybe a filesystem is mounted of it, or of a partition of it?

Could it already be in use?

NeilBrown

Re: md_import_device returned -16 raid1

[Jim Radford]

I'm not exactly sure what could be making it busy, I don't have it 
mounted, and I can't seem to find anything in /proc that shows it is in 
use in another way. I can't think of a way to check what might be 
causing it to think it is in use. Even during boot before userspace it is 
giving the same error.

Thanks for your assistance.

[...]
Bridge firewalling registered
md: Autodetecting RAID arrays.
md: autorun ...
md: ... autorun DONE.

[...]

md: md0 stopped.
md: could not bd_claim hdc.
md: md_import_device returned -16
md: bind<hdb>
md: raid1 personality registered as nr 3
raid1: raid set md0 active with 1 out of 2 mirrors
kjournald starting.  Commit interval 5 seconds

[...]


/dev/hda1 on / type ext3 (rw)
none on /proc type proc (rw)
none on /sys type sysfs (rw)
/dev/hda6 on /home type ext3 (rw)

On Sun, 17 Jul 2005, Neil Brown wrote:

> On Saturday July 16, jradford@npl.com wrote:
>> Greetings all:
>>
>> Having a bit of difficulty with raid1, I built the array lastnight with
>> two new drives, and it built fine but when I rebooted I get the following
>> error when trying to start the array:
>>
>> I'm running Mandrake 10.1 kernel 2.6.8.1-12mdk
>>
>> [root@localhost jradford]# mdadm --version
>> mdadm - v1.7.0 - 11 August 2004
>>
>> [root@bengali jradford]# mdadm -A -s
>> mdadm: failed to add /dev/hdc to /dev/md0: Device or resource busy
>
> This is telling you that /dev/hdc is 'busy'.
> Maybe a filesystem is mounted of it, or of a partition of it?
>
> Could it already be in use?
>
> NeilBrown
>

-- 
==========================================================================
Jim Radford <jradford@npl.com>
http://www.jimradford.com/
==========================================================================

Re: md_import_device returned -16 raid1

[Jim Radford]

lvm2 seems to be the cause, I removed all lv/vg/pv's and it started fine. 
My guess is I need to change something in the mandrake initscripts (order 
wise) to make sure lvm doesn't kick into gear until the raid has started.

Thanks for your thoughts!

Jim

On Sat, 16 Jul 2005, Jim Radford wrote:

> I'm not exactly sure what could be making it busy, I don't have it mounted, 
> and I can't seem to find anything in /proc that shows it is in use in another 
> way. I can't think of a way to check what might be causing it to think it is 
> in use. Even during boot before userspace it is giving the same error.
>
> Thanks for your assistance.
>
> [...]
> Bridge firewalling registered
>> Autodetecting RAID arrays.
>> autorun ...
>> ... autorun DONE.
>
> [...]
>
>> md0 stopped.
>> could not bd_claim hdc.
>> md_import_device returned -16
>> bind<hdb>
>> raid1 personality registered as nr 3
> raid1: raid set md0 active with 1 out of 2 mirrors
> kjournald starting.  Commit interval 5 seconds
>
> [...]
>
>
> /dev/hda1 on / type ext3 (rw)
> none on /proc type proc (rw)
> none on /sys type sysfs (rw)
> /dev/hda6 on /home type ext3 (rw)
>
> On Sun, 17 Jul 2005, Neil Brown wrote:
>
>> On Saturday July 16, jradford@npl.com wrote:
>>> Greetings all:
>>> 
>>> Having a bit of difficulty with raid1, I built the array lastnight with
>>> two new drives, and it built fine but when I rebooted I get the 
>>> following
>>> error when trying to start the array:
>>> 
>>> I'm running Mandrake 10.1 kernel 2.6.8.1-12mdk
>>> 
>>> [root@localhost jradford]# mdadm --version
>>> mdadm - v1.7.0 - 11 August 2004
>>> 
>>> [root@bengali jradford]# mdadm -A -s
>>> mdadm: failed to add /dev/hdc to /dev/md0: Device or resource busy
>> 
>> This is telling you that /dev/hdc is 'busy'.
>> Maybe a filesystem is mounted of it, or of a partition of it?
>> 
>> Could it already be in use?
>> 
>> NeilBrown
>> 
>
>

-- 
==========================================================================
Jim Radford <jradford@npl.com>
http://www.jimradford.com/
==========================================================================

Re: md_import_device returned -16 raid1

[Luca Berra]

On Sat, Jul 16, 2005 at 04:32:05PM -0700, Jim Radford wrote:
>lvm2 seems to be the cause, I removed all lv/vg/pv's and it started fine. 
>My guess is I need to change something in the mandrake initscripts (order 
>wise) to make sure lvm doesn't kick into gear until the raid has started.
>
check you have 
    md_component_detection = 1

in /etc/lvm/lvm.conf, it should be the default.

Regards,
L.

-- 
Luca Berra -- bluca@comedia.it
        Communication Media & Services S.r.l.
 /"\
 \ /     ASCII RIBBON CAMPAIGN
  X        AGAINST HTML MAIL
 / \

Re: md_import_device returned -16 raid1

[Jim Radford]

On Mon, 18 Jul 2005, Luca Berra wrote:

> On Sat, Jul 16, 2005 at 04:32:05PM -0700, Jim Radford wrote:
>> lvm2 seems to be the cause, I removed all lv/vg/pv's and it started fine. 
>> My guess is I need to change something in the mandrake initscripts (order 
>> wise) to make sure lvm doesn't kick into gear until the raid has started.
>> 
> check you have 
> md_component_detection = 1
>
> in /etc/lvm/lvm.conf, it should be the default.

That is the default, however the way Mandrake does their initscript I had 
to move the LVM stuff until after the raid is started to make it work 
right. It is working great now.

Jim

-- 
==========================================================================
Jim Radford <jradford@npl.com>
http://www.jimradford.com/
==========================================================================

Re: md_import_device returned -16 raid1

[Luca Berra]

On Mon, Jul 18, 2005 at 03:12:07PM -0700, Jim Radford wrote:
>On Mon, 18 Jul 2005, Luca Berra wrote:
>
>>On Sat, Jul 16, 2005 at 04:32:05PM -0700, Jim Radford wrote:
>>>lvm2 seems to be the cause, I removed all lv/vg/pv's and it started fine. 
>>>My guess is I need to change something in the mandrake initscripts (order 
>>>wise) to make sure lvm doesn't kick into gear until the raid has started.
>>>
>>check you have 
>>md_component_detection = 1
>>
>>in /etc/lvm/lvm.conf, it should be the default.
>
>That is the default, however the way Mandrake does their initscript I had 
>to move the LVM stuff until after the raid is started to make it work 
>right. It is working great now.

it should not be needed at all. lvms that are part of raids should be
ignored by the first lvm run due to md_component_detection = 1, if this
does not apply to you would you care open a bug at qa.mandriva.com
against LVM, i'll look into it..

L.

-- 
Luca Berra -- bluca@comedia.it
        Communication Media & Services S.r.l.
 /"\
 \ /     ASCII RIBBON CAMPAIGN
  X        AGAINST HTML MAIL
 / \