search for: md_import_device

...pes to 'fd' but when I try and rebuild the array I get: mdadm /dev/md0 -a /dev/hdg1 mdadm: hot add failed for /dev/hdg1: Invalid argument If I look at /var/log/messages, I have: Oct 5 16:04:39 petdoctors kernel: md: could not bd_claim hdg1. Oct 5 16:04:39 petdoctors kernel: md: error, md_import_device() returned -16 >From other postings, this seems to imply the hdg1 partition is mounted but I can find no evidence of this (df or cat /proc/mounts or lsof). I have done sone googling and found others having fun with this but no specific solution. Anyone? Thanks Nigel Kendrick

...k and the new one is set up with two disks in a softraid. I managed to solve the problem and thought I'd present it here to benefit others. attempting to add sda3 to md2 says: mdadm: hot add failed for /dev/sda3: Invalid argument dmesg says: md: could not bd_claim sda3. md: error, md_import_device() returned -16 Drive is not mounted or in use by the OS. SMART error logs do not indicate any disk failures. I can boot up to a rescue CD and the array assembles just fine. Go figure the old install used partition labels to determine the boot device. So GRUB grabbed the first disk /dev/sda, on w...

..., bootserver=1.2.3.4, rootserver=1.2.3.4, rootpath= md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. md: Loading md0: /dev/sda2 end_request: I/O error, dev sda2, sector 20971392 md: disabled device sda2, could not read superblock. md: sda2 has invalid sb, not importing! md: md_import_device returned -22 end_request: I/O error, dev sdb2, sector 20971392 md: disabled device sdb2, could not read superblock. md: sdb2 has invalid sb, not importing! md: md_import_device returned -22 md: starting md0 failed md: Loading md1: /dev/sda1 end_request: I/O error, dev sda1, sector 524160 md: disabl...