Here I thought I was getting an actual answer ;-).
This sending people from the cabin to the wall doesn't really help. My
question was a user support question, not a developer question. There are
rarely any questions like this on the dev list, there are rarely any
emails at all anyway, except for very technical or development-central
themes.
Such as review requests and all, and messages about integration work.
You can also see that you did forward it but no one responded.
You might imagine a developer saying "This is not really a developer
question, perhaps you should send it to the user support list." And so we
go....
This separation of users and developers is not really helpful particularly
as many of the "15.10 releases" are very public and apparently offered in
such a way as to raise interest in using and downloading them, and rightly
so perhaps. On .. Well. If you create alpha and beta releases you should
expect downloads and feedback. If you then do not provide any channel for
communication about it, from the perspective of someone who is actually
trying it....
And most very likely the exact same thing that I wrote about would be true
for 14.10 and 15.04. Would that be any different?. Except that on 15.10,
it might be easier to fix and it has more of a forward notion that there
might be an interest in including it once a solution has been seen. But to
a dev list I can only say
Would there be an interest in including this support?.
On Fri, 28 Aug 2015, Myriam Schweingruber wrote:
I am pretty sure that these questions are better addressed to the
kubuntu-devel list, as you are using an unreleased version and I doubt
this should go to the user support list.
Regards, Myriam
---------- Forwarded message ----------
From: Xen <[email protected]>
Date: Fri, Aug 28, 2015 at 9:38 PM
Subject: 15.10 fails to boot thin-LVM
To: [email protected]
I have a 15.10 install that I copied onto a thinly provisioned LVM.
After this change, the system wouldn't boot anymore. I'm not sure
about the exact error messages at this point, but suffice to say for
now that there were errors about the thin-volumes not being able to be
loaded. This may actually have to do with the package
thin-provisioning-tools not being installed by default, or not being
included in the initrd.
I can't regen my initrd at this point due to the other problem of not
being able to chroot into my install. I will have to boot it from a
regular partition, try to regen the initrd (how can I do that if it
won't know I'll need it?) and then boot from there when the thing is
copied back onto the thin.
It is because activating a thin-volume will try to use thin_check and
if it's not there, it will fail :(. A pretty bad dependency, I must
say.
But it's the same as cryptsetup... I think it really needs thin_check
in the initrd to even begin loading the volumes.
Does anyone have a recipe for getting this working?
I can
- boot the system from a regular partition
- install the package from there
-
- regenerate the initrd and install it
What is the third step? Will it work automatically? Do I need to
provide a hook for initramfs-tools or something?.
Regards, Bart
ps. I would also suggest to add thin-provisioning-tools to the base
image of Kubuntu.
https://github.com/igorpecovnik/lib/issues/50
--
kubuntu-users mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/kubuntu-users
--
Protect your freedom and join the Fellowship of FSFE:
http://www.fsfe.org
Please don't send me proprietary file formats,
use ISO standard ODF instead (ISO/IEC 26300)
--
kubuntu-devel mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
--
kubuntu-devel mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
