![](https://seccdn.libravatar.org/avatar/cabdbf4d350ab6a15265803acab1634d.jpg?s=120&d=mm&r=g)
On 2018-10-06 8:15 a.m., Dave Howorth wrote:
Yeah, I was hoping somebody here might know. One other piece of information that might or might not be relevant. There's a line in the journal that says:
Oct 06 09:45:44 acer-suse dracut-initqueue[309]: inactive '/dev/mint_vg/live-tv_lv' [100.00 GiB] inherit
There seems to be an old bug that couldn't to be reproduced: https://bugzilla.opensuse.org/show_bug.cgi?id=946176
I have no idea whether it's relevant or how to test. I don't understand the bug report.
If you have other file system on LVM that mount OK then this is not the problem. The bug related to startup and initialization of the WHOLE LVM subsystem. Check you have lvmetad running. And more: # find /tmp /run /etc/systemd/ /usr/lib/systemd -name '*lvm*' which gives you a bit of information overload, eh? if you look at VGCHANGE(8) you will see there is the --activate Somewhere you system @systemd level should be doing that. But once again, if you have any other file systems mounted on LVM in that volume group, this is not the problem. This is easy enough to check. In the limiting case try creating a new LV in that VG and put some other FS, ext4 perhaps, on it and see if that can be mounted somewhere. If it can, if you have other mounted FS in that VG that work, then the problem is not with LVM. I you have other mounter XFS volumes, then it is not the intrinsic XFS code that is the problem. if not, then you can check this by creating a new LV in that VG and put an XFS on it and try mounting that. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org