I have an md entry referring to a badly removed RAID1 device (by me) after
the associated device crashed (can't afford a replacement drive at this
time).
Despite attempts to remove the reference, after a reboot I see:
================================
$ cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4]
[raid10]
md2 : inactive sdc[1](S)
488385560 blocks super 1.2
unused devices: <none>
================================
I am trying to repurpose the good drive as a not-RAID device. I have done
sudo mdadm --zero-superblock /dev/sdc
and
sudo mdadm --zero-superblock --force /dev/sdc
and even low level formatted /dev/sdc
But the info in /proc/mdstat and
================================
$ sudo ls -l /dev/md*
brw-rw---- 1 root disk 9, 2 Jul 30 19:34 /dev/md2
/dev/md:
total 0
lrwxrwxrwx 1 root root 8 Jul 30 19:34 2 -> /dev/md2
================================
prevents the new ext3 partition /dev/sdc1 from
being mounted ("mount point is busy"). After executing
================================
$ sudo mdadm --manage --stop /dev/md2
mdadm: stopped /dev/md2
$ cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4]
[raid10]
unused devices: <none>
================================
and /dev/sdc1 can be mounted by device name or UUID.
Note - I have hidden mdadm.conf
================================
$ ls /etc/mdadm/mdadm.conf
ls: cannot access /etc/mdadm/mdadm.conf: No such file or directory
================================
At this point I am willing to uninstall, reinstall, or deactivate
(how?) md but I would rather do it right.
Any suggestions will be appreciated.
Please respond directly: skipcoombe@xxxxxxxxx
Thank you,
Skip
--
Skip Coombe
skip.coombe@xxxxxxxxx
--
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
