Device or resource busy
Hi,
I have an existing RAID1 consisting of the 2 disks /dev/sdc and /dev/sdd. However after upgrading to Karmic, one of them fails to be added to the array:
# mdadm --assemble /dev/md0 /dev/sdc /dev/sdd
mdadm: cannot open device /dev/sdc: Device or resource busy
mdadm: /dev/sdc has no superblock - assembly aborted
At boot time, mdadm detects /dev/mapper/
# mdadm --assemble /dev/md0 /dev/mapper/
mdadm: cannot open device /dev/mapper/
mdadm: /dev/mapper/
I'm not sure about the differences between /dev/sdX and /dev/mapper/sil_* though, but it seems only the devices in /dev/mapper are recognized by mdadm:
# mdadm -v --misc --examine /dev/sdc
mdadm: No md superblock detected on /dev/sdc.
# mdadm -v --misc --examine /dev/sdd
mdadm: No md superblock detected on /dev/sdd.
# mdadm -v --misc --examine /dev/mapper/
mdadm: No md superblock detected on /dev/mapper/
# mdadm -v --misc --examine /dev/mapper/
/dev/mapper/
Magic : a92b4efc
Version : 00.90.00
UUID : b661b5fd:
Creation Time : Thu Jul 8 23:17:29 2004
Raid Level : raid1
Used Dev Size : 195358336 (186.31 GiB 200.05 GB)
Array Size : 195358336 (186.31 GiB 200.05 GB)
Raid Devices : 2
Total Devices : 1
Preferred Minor : 0
Update Time : Tue Feb 2 15:47:35 2010
State : clean
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0
Checksum : de9fb1fd - correct
Events : 16940626
Number Major Minor RaidDevice State
this 1 252 1 1 active sync /dev/block/252:1
0 0 0 0 0 removed
1 1 252 1 1 active sync /dev/block/252:1
The devices are also listed differntly by blkid:
/dev/sdc: TYPE="silicon_
/dev/sdd: TYPE="silicon_
/dev/mapper/
Can anyone enlighten me as to why /dev/mapper/
Furthermore, why is the sdc device busy? It's certainly not mounted already. Might it be a drive error?
Some system info:
Ubuntu Karmic 64-bit
Linux 2.6.31-19-generic
Thanks,
- Johannes
Question information
- Language:
- English Edit question
- Status:
- Solved
- For:
- Ubuntu mdadm Edit question
- Assignee:
- No assignee Edit question
- Solved by:
- Johannes H. Jensen
- Solved:
- Last query:
- Last reply: