On 28.04.2015 16:53, Stefan G. Weichinger wrote: > > I now booted from a recent sysresccd ... and it didn't assemble/detect > the LVM-PV ... *sigh* > > So I couldn't even mount the LV to chroot in there. > > The mdadm-RAID-devices were there and active. > > I didn't want to screw around with the LVM too much as there is data on > there (yes, there are backups, but ...). > > pvscan always told me something like: > > No device found for PV hMMm0m-w4Ds-SU77-ATjF-iF1A-0qfq-V2IcXb > > ....
ok, one step further: (no exact cut and paste because of java-based KVM access) pvscan --cache tells me: Found duplicate PV hMMm0m-w4Ds-SU77-ATjF-iF1A-0qfq-V2IcXb: using /dev/sdj1 not /dev/md3 -- md3 is the correct array to form the PV ... /dev/sdj1 is actually a partition that is an active *member* of the array /dev/md3 I tried to filter this partition by editing lvm.conf without success. Under suse I don't see /dev/sdj1 as pv: # pvdisplay /dev/sdj1 Failed to read physical volume "/dev/sdj1" - Should I * "pvremove /dev/sdj1" from sysresccd * in suse: remove sdj1 from array md3 ... overwrite header and re-add ? Oh my. !! BUT -> I now found another nice fact: /dev/md2 (NO LVM) is unused since the initial installation. I even *documented* that in the project wiki years ago. 40 GB of unused space on a RAID1 of SAS hdds. Nice! Sounds like my new rootfs ;-) dracut plus these md-lines should work then. Stefan
