0

I have an issue with a new mdadm raid.

When i try to:

root@dys:~# mdadm --add --verbose /dev/md0 /dev/sdb1
mdadm: Cannot open /dev/sdb1: Device or resource busy

dmraid i pointed as the usual problem but it's not even installed.

Also tried to check it with lsof and no result.

Im just out of ideeas

the output of /proc/mdstat if of any help:

root@dys:~# cat /proc/mdstat
Personalities : [raid1]
md1 : active (auto-read-only) raid1 sdb2[2] sda2[1]
      7858164 blocks super 1.2 [2/2] [UU]

md0 : active (auto-read-only) raid1 sda1[1]
      968900472 blocks super 1.2 [2/1] [_U]

unused devices: <none>
Debrian
  • 154
  • 2
  • 12

1 Answers1

1

What about this way: mdadm /dev/md0 -a /dev/sdb1 ?

What is the output of lsblk /dev/sdb1?

poige
  • 9,448
  • 2
  • 25
  • 52
  • Same result: mdadm /dev/md0 -a /dev/sdb1 mdadm: Cannot open /dev/sdb1: Device or resource busy – Debrian Apr 06 '13 at 18:05
  • @Adrian, ok, let's go further — see update – poige Apr 07 '13 at 02:27
  • 1
    Ok that helped a lot. First of all lsblk is not present in debian stable, so i had to get it from testing and discovered that /dev/sdb1 was mounted on /, although mount and umount where saying it's not. I redo the grub configuration (the first time i miss-copied a uuid it seems) and now everything works according to plan. Lesson learned lsblk is a nice tool. – Debrian Apr 07 '13 at 08:45