[Expired for initramfs-tools (Ubuntu) because there has been no activity
for 60 days.]
** Changed in: initramfs-tools (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
Is this still happening for anyone?
** Changed in: initramfs-tools (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/29858
Title:
root on lvm
Djamu and Vince (tucsonclimber): I think you're experiencing a bug
that's different than this one (bug #360237). I don't have the bug
described here, but I was bitten by #360237.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
Milko - you are correct - bug #360237 exactly describes my problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/29858
Title:
root on lvm fails to boot.
To manage notifications about this
I was affected by this bug on a lucid (10.04) two step upgrade from 9.04
(Jaunty) (Jaunty to Karmic to Lucid) with an active root snapshot. I
found that the 2.6.31.-22 kernel worked consistently and all later
kernels attempted (2.6.32-22 and 2.6.32-25) failed in one of two ways:
The most common
I marked bug 255477 as a duplicate of this. I anyone disagrees, please
change it back.
This bug has been hanging around for a long time and for those who get
bitten by it it means server down time at console level (which is always
a pain) and the need to repair the system with an alternate boot
Rats, cannot do that. ;)
--
root on lvm fails to boot.
https://bugs.launchpad.net/bugs/29858
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
On lucid server x86-64 after aptitude upgrade system was left
unbootable. mount in initramfs said device not found for /dev/mapper
/ubuntu-root. I fixed it after adding rootfstype=ext4 in
/boot/grub/grub.cfg.
--
root on lvm fails to boot.
https://bugs.launchpad.net/bugs/29858
You received this
This bug affects me with 2.6.32.21.22 on lucid.
With kernel 2.6.32.19 it does work for me, plymouth asks for the pass phrase
and I can successfully login.
--
root on lvm fails to boot.
https://bugs.launchpad.net/bugs/29858
You received this bug notification because you are a member of Ubuntu
This bug affects me with 2.6.32-19.28 kernel on lucid. Kernel 2.6.31-17
works though...
--
root on lvm fails to boot.
https://bugs.launchpad.net/bugs/29858
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
Is there a resolution available for this ?
I upgraded server from 8.04.1 8.10 and am using a LVM root with snapshots.
unfortunately the new 2.6.27-7-server kernel fails to mount the LVM root (
halts after initramfs )
older kernel ( 2.6.24-21-server ) does work
--
root on lvm fails to
I filed a similar bug here
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/255477 for hardy.
Might be a dupe? The problem is still present though.
--
root on lvm fails to boot.
https://bugs.launchpad.net/bugs/29858
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: initramfs-tools (Ubuntu)
Assignee: Adam Conrad (adconrad) = (unassigned)
--
root on lvm fails to boot.
https://bugs.launchpad.net/bugs/29858
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
Still there on Feisty.
I just had this problem (Stans, except I only have a boot partition and a
ubuntu partition, no Fedora) when upgrading to feisty using apt-get
dist-upgrade. After rebooting, feisty doesn't see my VolumeGroup
/dev/mapper/vg1, stalling around the the line lookdevice-mapper:
This could be a problem with your initrd. Are you seeing /dev/mapper
devices within your initramfs? Maybe initramfs-tools just forgot to
include lvm support in your initrd?
--
root on lvm fails to boot.
https://launchpad.net/bugs/29858
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I have also experienced this problem (as Stan has described) but with a
fresh install of Dapper alt install. Everything works according to plan
(and according to the wiki entry) but then I fall into the same pit: It
kept telling me the filesystem didn't exist until I tried mount -t ext3
I'm trying to boot Ubuntu from the boot partition set up by my primary
Fedora Core 5 installation, where Ubuntu is installed (via the alternate
install iso) on an LVM partition as a secondary Linux distro.
I had tried multiple things to get Ubuntu to boot on my system and
finally arrived at
17 matches
Mail list logo
