I am not sure what bd_claim is, but it is somewhat like open(). My guess is your disk is in use, maybe nounted. Run this command and send the output. df Guy > -----Original Message----- > From: linux-raid-owner@xxxxxxxxxxxxxxx [mailto:linux-raid- > owner@xxxxxxxxxxxxxxx] On Behalf Of rrk > Sent: Sunday, March 27, 2005 1:38 PM > To: linux-raid@xxxxxxxxxxxxxxx > Subject: Raid1 problem can't add remove or mark faulty -- it did work > > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > mdstat after reboot > > root@crm_svr:~# cat /proc/mdstat > Personalities : [linear] [raid0] [raid1] [raid5] [multipath] [raid6] > [raid10] > md0 : active raid1 hdc1[1] > 155268096 blocks [2/1] [_U] > > unused devices: <none> > > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > the below error shows after a boot when excuted in kde konsole > > root@crm_svr:/home/rob# mdadm /dev/md0 -a /dev/hda1 > mdadm: hot add failed for /dev/hda1: Invalid argument > > but this error is shown from a tty console > > md: could not bd_claim hda1 > md: error, md_import_device() returned -16 > mdadm: hot add failed for /dev/hda1 : invalid argument > > @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ > this is what shows in dmesg > > md: could not bd_claim hda1. > md: error, md_import_device() returned -16 > md: could not bd_claim hda1. > md: error, md_import_device() returned -16 > md: could not bd_claim hda1. > md: error, md_import_device() returned -16 > > i had this bd_claim error when i first tried to build the array > but it went away when i wiped every thing and started over > this box is the only time i have seen this error and i > tried using different drives -- but of the same type -- when > the problem showed up on the initial build > > > > > - > To unsubscribe from this list: send the line "unsubscribe linux-raid" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
