It probably was a one time thing - recent updates didn't break so I
don't mind closing this one.
** Changed in: devmapper (Ubuntu)
Status: Incomplete => Invalid
--
After today's update to devmapper, system does not boot successfully
https://bugs.launchpad.net/bugs/144735
You received this
** Changed in: devmapper (Ubuntu)
Importance: Undecided => High
Status: New => Incomplete
--
After today's update to devmapper, system does not boot successfully
https://bugs.launchpad.net/bugs/144735
You received this bug notification because you are a member of Ubuntu
Bugs, which is t
** Changed in: devmapper (Ubuntu)
Status: Invalid => New
--
After today's update to devmapper, system does not boot successfully
https://bugs.launchpad.net/bugs/144735
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubun
I wasn't using a self compiled kernel, but Ubuntu's generic kernel.
I want to try the latest updates, but as the computer doesn't boot I
have no way to get it to fetch updates.
--
After today's update to devmapper, system does not boot successfully
https://bugs.launchpad.net/bugs/144735
You rece
Problem caused by self-compiled kernel, almost certainly a missing
option (check our config) or wrong initramfs
** Changed in: devmapper (Ubuntu)
Status: Confirmed => Invalid
--
After today's update to devmapper, system does not boot successfully
https://bugs.launchpad.net/bugs/144735
You
I had the same problem today with dmraid devices. Removing the invalid
symlinks under /dev/mapper/ and running dmsetup mknodes recreated them
fine. After that I ran update-initramfs for the custom kernel and now
everything works fine also after boot. Probably just updating initramfs
will be enough
And running the Ubuntu supplied 2.6.22-12-generic, the problem doesn't
occur.
--
After today's update to devmapper, system does not boot successfully
https://bugs.launchpad.net/bugs/144735
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubu
I can confirm this: For me, the boot doesn't fail because I don't have
any lvm-ed partition automounted (other than root), but manually
mounting partitions fails ("too many levels of symbolic links"), and
/dev/mapper is full of symlinks like above.
I should note that I'm running a custom self-comp
