[Bug 54002] Re: No need to convert LVM volumes to UUIDs
** Changed in: grub (Ubuntu) Status: Unconfirmed = Confirmed -- No need to convert LVM volumes to UUIDs https://launchpad.net/bugs/54002 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54002] Re: No need to convert LVM volumes to UUIDs
** Bug 56155 has been marked a duplicate of this bug -- No need to convert LVM volumes to UUIDs https://launchpad.net/bugs/54002 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54002] Re: No need to convert LVM volumes to UUIDs
Looking at the logic in the actual 'init' script in:
/usr/share/initramfs-tools/
I see a case for a root specifying a UUID
UUID=*)
ROOT=/dev/disk/by-uuid/${ROOT#UUID=}
;;
This logic also caused my upgrade from Dapper to Edgy to fail because of my
root on LVM. I had to change these back to /dev/mapper* addresses to achieve a
boot. My LVM's also don't show up in /dev/disk/by-uuid
-David
--
No need to convert LVM volumes to UUIDs
https://launchpad.net/bugs/54002
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54002] Re: No need to convert LVM volumes to UUIDs
Not a grub bug, leaving open against udev for now ** Changed in: grub (Ubuntu) Status: Confirmed = Rejected ** Summary changed: - No need to convert LVM volumes to UUIDs + LVM/MD root filesystem not found by uuid ** Description changed: Hi there! There is no need to convert LVM volumes to UUIDs: LVM finds its physical volumes on all disks and maps the logical volumes stored on them to well defined names. This is pretty similar to what libvolumeid does... but since LVM's logical volumes are named by the user it tends to have better names then those numbers used as UUIDs. + Note: the original reporter indicated the bug was in package 'libvolumeid0'; however, that package was not published in Baltix. -- LVM/MD root filesystem not found by uuid https://launchpad.net/bugs/54002 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54002] Re: No need to convert LVM volumes to UUIDs
For what it is worth: LVM volumes are never listed with their UUID under /dev/disk/by-id/, not even on a ubuntu system that is fully up and running! So it is simply impossible to address a LVM volume in ubuntu by its UUID! Maybe it would be a good idea to verify that the UUID of a volume is actually found under /dev/disk/by-id before updating grub? This would stop the grub-updater-script from doing something incredibly stupid:-) -- No need to convert LVM volumes to UUIDs https://launchpad.net/bugs/54002 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54002] Re: No need to convert LVM volumes to UUIDs
Oh, aurelian suggests that UUIDs are not required to be listed in /dev/disk/by-id/ to work... if that really is the case, then my last comment is obsolete:-) If the UUID system is not based on the entries in /dev/disk/by-id/ then it would be terribly nice if somebody could take the time and explain how this magic is worked. -- No need to convert LVM volumes to UUIDs https://launchpad.net/bugs/54002 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54002] Re: No need to convert LVM volumes to UUIDs
** Bug 56177 has been marked a duplicate of this bug -- No need to convert LVM volumes to UUIDs https://launchpad.net/bugs/54002 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54002] Re: No need to convert LVM volumes to UUIDs
Initramfs scripts cannot mount my root on lvm volume since conversion to UUID. I think that the /usr/share/initramfs-tools/scripts/local-top/lvm script which is supposed to activate the root on lvm volume is unable to work with a root partition specified as an UUID: it try to parse the root partition variable using a '/dev/mapper/something' pattern. I also think that it cannot be made to work as the vgchange tool need a volume group name which I don't see how it can be guessed from just the UUID of a not-yet activated logical volume belonging to this volume group. It can be workarounded by modifying back /boot/grub/menu.lst but you also have to manually tweak the update-grub script as it blindly want to convert it back to an UUID on each invocation. -- No need to convert LVM volumes to UUIDs https://launchpad.net/bugs/54002 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54002] Re: No need to convert LVM volumes to UUIDs
Debian also had this problem and resolved it by not converting /dev/mapper: http://packages.debian.org/changelogs/pool/main/g/grub/grub_0.97-13/changelog.html#versionversion0.97-4 -- No need to convert LVM volumes to UUIDs https://launchpad.net/bugs/54002 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54002] Re: No need to convert LVM volumes to UUIDs
$ ls -l /dev/mapper ls: /dev/mapper: No such file or directory Your making assumptions again... As I said in the earlier message: You simply can't know how a system looks like. So you'd better not change settings that might break it without the expressed consent of the system administrator. Regards, Dominik -- No need to convert LVM volumes to UUIDs https://launchpad.net/bugs/54002 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54002] Re: No need to convert LVM volumes to UUIDs
I somewhat agree with your point... BUT ubuntu is a defined base. It has its device mapper stuff in /dev/mapper (which does not exist if you do not use it!). So for a ubuntu install script it is safe to assume that partitions that start with /dev/mapper are device mapper based and not to be touched. Of course you can map /dev/mapper to something different as system administrator, but then you are on your own and can not expect ubuntu to do a sensible thing. I do think that changing something fundamental as /etc/fstab needs to give some warning to the system administrator... and indeed that was given (or I would not had the opportunity to fix this issue before rebooting;-). -- No need to convert LVM volumes to UUIDs https://launchpad.net/bugs/54002 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54002] Re: No need to convert LVM volumes to UUIDs
Damn... this bug was supposed to go to ubuntu edgy. How do I change that? ** Also affects: udev (Ubuntu) Importance: Untriaged Status: Unconfirmed -- No need to convert LVM volumes to UUIDs https://launchpad.net/bugs/54002 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54002] Re: No need to convert LVM volumes to UUIDs
Not in baltix. ** Changed in: Baltix Status: Unconfirmed = Rejected -- No need to convert LVM volumes to UUIDs https://launchpad.net/bugs/54002 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54002] Re: No need to convert LVM volumes to UUIDs
I was not sure whether this broke boot-up or not since I converted grub and fstab back before rebooting:-) I am pretty sure now that it does break boot up since the LVM driver do not get an entry in /dev/disks/by-id/ ... -- No need to convert LVM volumes to UUIDs https://launchpad.net/bugs/54002 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54002] Re: No need to convert LVM volumes to UUIDs
I have mixed feelings about this. I was about to report a similar bug for grub as the move to UUID everywhere currently prevents my edgy system from booting (I can boot if I put back the old root=/dev/mapper/ argument in grub). I am marking this as also affecting grub, for the record. On the other hand, I find UUID better than labels or lvm volume names as they are more likely to be uniq. A while ago I put a friend's hard drive in my computer to get its data back, we where both using LVM with identical volume names, which was a bit problematic (I don't remember the details though). UUIDS might help in this area, but pushing the user to choose non-clashing LVM names might be enough. ** Also affects: grub (Ubuntu) Importance: Untriaged Status: Unconfirmed -- No need to convert LVM volumes to UUIDs https://launchpad.net/bugs/54002 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54002] Re: No need to convert LVM volumes to UUIDs
By no need, do you just mean that you feel it's not useful to do it -- or is there some bug caused by doing so? What does an LVM volume device name look like? -- No need to convert LVM volumes to UUIDs https://launchpad.net/bugs/54002 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 54002] Re: No need to convert LVM volumes to UUIDs
I guess that the original reporter really did mean not needed, but it my case, it causes a bug :) I have just checked, it is still present after recreating my initramfs. The problem is that it can not find my LVM volume by UUID. The strange thing is that /etc/fstab has also been modified to use UUID (making it much less nice to edit manually) and it did not cause any problem, though my /home partition is also a LVM one and it does _NOT_ appear in /dev/disk/by-uuid/ !! My exact setup is LVM on software RAID 5. I am not very fluent with the initramfs process so I can not tell in which state it is when it drops me the busybox shell, but I could give you output of commands run from it if needed. LVM partitions are under /dev/mapper/ and the user can choose their name. Mine are called: vg_$VG-lv_$HOST$PART where $VG designs the volume group to which it belongs, $HOST is my hostname (to avoid clashes when adding disks from a similar installation from another host) and $PART is the role of this volume (home, root32 and root64 in my case). -- No need to convert LVM volumes to UUIDs https://launchpad.net/bugs/54002 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
