I found the problem, here is what happened:
When first creating the raid partition for the lvm, I saved the config
to /etc/mdadm.conf
Everything worked fine, because somehow it still got detected and was
assembled as md127. I didnt notice and went on.
It seems that after an update (not shure which) it does not do the
automated search and assembling of the unconfigured raid partitions
anymore. I put the missing configuration in /etc/mdadm/mdadm.conf and
everything is fine again.
thanks, Sebastian
Am 10.03.2016 um 14:43 schrieb Dan Ritter:
On Thu, Mar 10, 2016 at 01:37:06PM +0100, Sebastian Weckend wrote:
In the backup of the LVM configuration I found
physical_volumes {
pv0 {
id = "zKO1Xq-VGmI-nX8P-Rwh3-wiFn-GuD4-26dAoZ"
device = "/dev/md127" # Hint only
status = ["ALLOCATABLE"]
flags = []
dev_size = 5798400896 # 2.70009 Terabytes
pe_start = 2048
pe_count = 707812 # 2.70009 Terabytes
}
}
but there is no /dev/md127. So it seems it is a software-raid problem.
Did I configure the software-raid wrong? And why did it disappear
just now? Any idea how I get the partition back?
Does it appear in /proc/mdstat in any form? I suspect that the
device got renamed.
Any mentions of mdadm in dmesg output?
You can examine specific partitions with mdadm -Q /dev/sdXX
-dsr-
