My best guess is that they switched from using privileged containers to unprivileged containers. Make sure to collect and provide all necessary information Read more It doesn’t do anything other than ensure that the partitions can be mounted, and this is where it’s failing. Sign up for a new account in our community. Changed in linux Ubuntu: This bug is missing log files that will aid in diagnosing the problem.
|Date Added:||19 March 2014|
|File Size:||58.17 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Package: libdevmapper-dev (2:1.02.77-6ubuntu2)
Joseph Salisbury jsalisbury on You need to log in to change this bug’s status. To post a comment you must log in.
You are not directly subscribed to this bug’s notifications. Other bug subscribers Subscribe someone else. Found this older bug: Sign in Already have an account? No such device Failure to communicate with kernel device-mapper driver.
I think we know almost the entire story now. Already have an account?
Ubuntu – Details of package libdevmapper-dev in trusty
What do you think about it Igor? If you have an armhf device with an up-to-date Zesty, can you please check? Linux Kernel Device Mapper userspace library Homepage: Can you switch to newer kernel via armbian-config.
It’s never passed on sx so that’s not a regression.
lvcreate doesn’t work – solved – Common issues – Armbian forum
Required device-mapper target s not detected in your kernel. This bug is missing log files that will aid in diagnosing the problem.
You need to be a member in order to leave a comment. Make sure to collect and provide all necessary information Ahd more Command failed where as the failure in the log file says: This is probably a regression only on armhf, so the logs generated on amd64 won’t be helpful.
Go To Topic Listing Common issues. Maybe a new missing dependency? Email me about changes to this bug report. Very clearly the armhf container tests passed for several months, and then stopped working.
It doesn’t do anything other than ensure that the partitions can be mounted, and this is where it’s failing. This bug affects znd people.
Changed in lvm2 Ubuntu: Check that device-mapper is available in the kernel. No upgrade log present probably fresh install dmi. Active threads Mark site read. See the above referenced bug for further discussion. Check that device-mapper is available in the kernel.
Here’s a log of a recent run:. In any event, I’m going to close this bug.