[Bug 54002] Re: LVM/MD root filesystem not found by uuid
Latest 2.6.17-8 kernel converted my lvm back to uuid, don't know why. -- 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: [Bug 54002] Re: LVM/MD root filesystem not found by uuid
Am Thursday 14 September 2006 16:26 schrieb Scott James Remnant: > Fabio should be uploading a fixed mdrun initramfs script after Knot 3 > freeze that at least works around the problem > > ** Changed in: udev (Ubuntu) > Sourcepackagename: udev => mdadm > Assignee: Scott James Remnant => Fabio Massimo Di Nitto After todays update booting by UUID works for straight MD RAID1. Good work! Dominik -- Be at war with your vices, at peace with your neighbours, and let every new year find you a better man. (Benjamin Franklin, 1706-1790) -- 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: LVM/MD root filesystem not found by uuid
The new mdadm has been uploaded but it will be approved only after knot-3 cd is out. It's a matter of a few hours and it is also a duplicate of 57607. ** Changed in: mdadm (Ubuntu) Status: Confirmed => Fix Released -- 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: [Bug 54002] Re: LVM/MD root filesystem not found by uuid
Am Thursday 14 September 2006 16:26 schrieb Scott James Remnant: > Fabio should be uploading a fixed mdrun initramfs script after Knot 3 > freeze that at least works around the problem > > ** Changed in: udev (Ubuntu) > Sourcepackagename: udev => mdadm > Assignee: Scott James Remnant => Fabio Massimo Di Nitto Ok. I'll check it then and let you know. Regards, Dominik -- Be at war with your vices, at peace with your neighbours, and let every new year find you a better man. (Benjamin Franklin, 1706-1790) -- 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: LVM/MD root filesystem not found by uuid
Fabio should be uploading a fixed mdrun initramfs script after Knot 3 freeze that at least works around the problem ** Changed in: udev (Ubuntu) Sourcepackagename: udev => mdadm Assignee: Scott James Remnant => Fabio Massimo Di Nitto -- 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: LVM/MD root filesystem not found by uuid
Matt, it's true that Linux did and does a lot of things traditional Unices didn't and don't do. But that is neither here nor there and I shouldn't have mentioned this in the first place. I raised my objections regarding mount by UUID and it's up to you guys to check their validity regarding Ubuntu's goals. As for the problem at hand: I am willing to aid in resolving this issue, so if you want me to test something, let me know about it. Regards, Dominik -- 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: [Bug 54002] Re: LVM/MD root filesystem not found by uuid
On Tue, Sep 12, 2006 at 07:09:39AM -, Dominik Kubla wrote: > Scott, > > nobody does mount by UUID. Neither *BSD, Solaris, AIX, HP-UX, Tru64 does > it. These Unix derivatives have pretty smart engineering teams around. > That should tell you something... Modern Linux is doing quite a lot of things that those systems have never done. This isn't about following their lead. :-) -- - mdz -- 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: LVM/MD root filesystem not found by uuid
Scott, nobody does mount by UUID. Neither *BSD, Solaris, AIX, HP-UX, Tru64 does it. These Unix derivatives have pretty smart engineering teams around. That should tell you something... As for the valid configurations: Category A (Will probably never work): 1. loopback mounts (eg. crypto root) -> kills secure mobile devices 2. network mounts (eg. nfs root or raid with nbd) -> kills one half of thin client setups 3. layered mounts (eg. unionfs) -> kills the other half of thin client setups and one half of embedded devices 4. tmpfs root -> kills the other half of embedded devices Category B (Probably resolveable but changes expected behaviour) 5. disaster recovery with replicated root file systems (eg. rsync): there the UUIDs of both filesystem have to be different, otherwise they wouldn't be unique -> kills quite common DR strategy and effectively kills the use in corporate server environments 6. bare metal recovery: restore tape backup to newly installed system will result in a unbootable setup because UUID no longer matches... -> a support nightmare, effectively kills the use in corporate desktop environments Category C (Has severe side-effects) 7. systems with SAN/iSCSI storage: udev will scan all devices it sees to determine the UUID. this is likely to take a long time ((I know of hosts with several hundred SAN storage volumes assigned to them) and prone to disrupting the operation of other hosts (since Linux does not honor SCSI reservation)-> this kills the enterprise server setups. -- 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: [Bug 54002] Re: [Bug 54002] Re: LVM/MD root filesystem not found by uuid
On Mon, 2006-09-11 at 18:58 +, Dominik Kubla wrote: > Am Monday 11 September 2006 00:24 schrieb Matt Zimmerman: > > Reopening udev task, as md detection doesn't seem to be sorted yet. > > > > MD folks, please provide details. > > > > ** Changed in: udev (Ubuntu) > >Status: Fix Released => Confirmed > > We have two issues at hand: > > 1. Mounting by UUID does not work for MD in initramfs. I am trying to track > this one down (but I think this is a waste of time because there will always > be rather common scenarios where mounting by UUID will never work. But this > should be discussed elsewhere). I'll have to rig a serial terminal to capture > the console output and create a custom initramfs which will drop to a shell > right before it attempts to mount the root device so that I can do some > debugging. > break=mount on the kernel command-line. > 2. update-grub changes MD to mount by UUID even so it does not work at the > moment. This one is rather easy to fix: > I'd rather fix #1. and make mount-by-UUID work. Scott -- Scott James Remnant [EMAIL PROTECTED] -- 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: [Bug 54002] Re: LVM/MD root filesystem not found by uuid
Am Monday 11 September 2006 00:24 schrieb Matt Zimmerman: > Reopening udev task, as md detection doesn't seem to be sorted yet. > > MD folks, please provide details. > > ** Changed in: udev (Ubuntu) >Status: Fix Released => Confirmed We have two issues at hand: 1. Mounting by UUID does not work for MD in initramfs. I am trying to track this one down (but I think this is a waste of time because there will always be rather common scenarios where mounting by UUID will never work. But this should be discussed elsewhere). I'll have to rig a serial terminal to capture the console output and create a custom initramfs which will drop to a shell right before it attempts to mount the root device so that I can do some debugging. 2. update-grub changes MD to mount by UUID even so it does not work at the moment. This one is rather easy to fix: --- update-grub.orig2006-09-11 20:49:34.0 +0200 +++ update-grub 2006-09-11 20:51:48.0 +0200 @@ -692,6 +692,9 @@ ;; /dev/evms/*) ;; + /dev/md*) # Don't convert MD for now since there is an + # unresolved bug preventing it from working. + ;; /dev/*) if [ -L "$DEV" ] && readlink | grep -q "^/dev/mapper/" then This can be backed-out when mounting by UUID for MD works. Regards, Dominik -- Be at war with your vices, at peace with your neighbours, and let every new year find you a better man. (Benjamin Franklin, 1706-1790) -- 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: LVM/MD root filesystem not found by uuid
Reopening udev task, as md detection doesn't seem to be sorted yet. MD folks, please provide details. ** Changed in: udev (Ubuntu) Status: Fix Released => Confirmed -- 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: LVM/MD root filesystem not found by uuid
Just believe it. UUID for MD devices broke my edgy root=/dev/md0 test box *again* this weekend. If I've set root=/dev/md0 in menu.lst, please, trust me and don't break my box again. If I can further help debug this, please tell me how. -jonathan -- 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: [Bug 54002] Re: [Bug 54002] Re: [Bug 54002] Re: LVM/MD root filesystem not found by uuid
On Sun, Sep 10, 2006 at 08:37:14PM -, Dominik Kubla wrote: > Am Sunday 10 September 2006 21:02 schrieb Matt Zimmerman: > > You're making assumptions about the behaviour of a 1000+-line program by > > reading one comment. > > No, I am not making assumptions. You stated that grub-update will not convert > LVM/devmapper entries anymore to avoid corruption of the system boot process. > I demonstrated that the system boot process is still corrupted for the rather > simple case of root disks being mirrored with MD. No, you didn't. You grepped for a string in the update-grub script and claimed that this was evidence that it "corrupted" the system. I can't agree there. This conversion is a necessary step in order to support future changes in the kernel which will change the naming and order in which storage devices are detected. This is not necessary for LVM or EVMS volumes. However, as far as I am aware, md devices are assigned in sequential order based on a device scan, which means that they are susceptible to breakage due to these ordering changes, and should be mounted by uuid rather than by explicit device path. If that isn't working correctly for you, then please help us to debug the problem. > > If you read the convert_kopt_to_uuid function referenced above, you'll see > > that it includes conditional code intended to exclude device-mapper (LVM) > > and EVMS devices from the conversion. > > I went through this file line by line and I can say I have a rather good > understanding what it attempts to do and what it does. > > You are the one making assumptions here: about how a system is configured. > That is something you can not know reliably. So following the principle of > least impact you should not change anything without explicit consent by the > system administrator requesting the task. In general, I would agree, but in this case, the conversion is necessary in order to avoid breakage in the future. You can read the background for this decision in https://launchpad.net/distros/ubuntu/+spec/probe-for-root-filesystem and https://launchpad.net/distros/ubuntu/+spec/libata-for-all-ata-disks If you have specific criticism of the decision, then please address it to the development mailing list at [EMAIL PROTECTED], and limit discussion in this bug report to the matter at hand. > > If you have problems with the conversion, a constructive bug report with > > details of your configuration would be appreciated. > > My problem is that you convert the file at all. I do not want this setting to > be converted, even if mounting by UUID would be working. I'm afraid this is unavoidable, as I've tried to explain above. > But as I understand now, the problem is not a technical one, so i will > simply dpkg-divert /sbin/update-grub and disable the conversion stuff in > my local copy and be done with it. This will not further the process of fixing the problem. I know of no reason why UUID mounting of md devices should not work, so your assistance in debugging the problem would be appreciated. -- - mdz -- 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: [Bug 54002] Re: [Bug 54002] Re: LVM/MD root filesystem not found by uuid
Am Sunday 10 September 2006 21:02 schrieb Matt Zimmerman: > On Sun, Sep 10, 2006 at 06:26:50PM -, Dominik Kubla wrote: > > # egrep -nC1 "Update.*root device.*UUID" /sbin/update-grub > > 751- > > 752:# Update the root device to mount-by-UUID > > 753-kopt=$(convert_kopt_to_uuid "$kopt") > > You're making assumptions about the behaviour of a 1000+-line program by > reading one comment. No, I am not making assumptions. You stated that grub-update will not convert LVM/devmapper entries anymore to avoid corruption of the system boot process. I demonstrated that the system boot process is still corrupted for the rather simple case of root disks being mirrored with MD. > If you read the convert_kopt_to_uuid function referenced above, you'll see > that it includes conditional code intended to exclude device-mapper (LVM) > and EVMS devices from the conversion. I went through this file line by line and I can say I have a rather good understanding what it attempts to do and what it does. You are the one making assumptions here: about how a system is configured. That is something you can not know reliably. So following the principle of least impact you should not change anything without explicit consent by the system administrator requesting the task. > If you have problems with the conversion, a constructive bug report with > details of your configuration would be appreciated. My problem is that you convert the file at all. I do not want this setting to be converted, even if mounting by UUID would be working. But as I understand now, the problem is not a technical one, so i will simply dpkg-divert /sbin/update-grub and disable the conversion stuff in my local copy and be done with it. Regards, Dominik -- Be at war with your vices, at peace with your neighbours, and let every new year find you a better man. (Benjamin Franklin, 1706-1790) -- 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: [Bug 54002] Re: LVM/MD root filesystem not found by uuid
On Sun, Sep 10, 2006 at 06:26:50PM -, Dominik Kubla wrote: > # egrep -nC1 "Update.*root device.*UUID" /sbin/update-grub > 751- > 752:# Update the root device to mount-by-UUID > 753-kopt=$(convert_kopt_to_uuid "$kopt") You're making assumptions about the behaviour of a 1000+-line program by reading one comment. If you read the convert_kopt_to_uuid function referenced above, you'll see that it includes conditional code intended to exclude device-mapper (LVM) and EVMS devices from the conversion. If you have problems with the conversion, a constructive bug report with details of your configuration would be appreciated. Thanks, -- - mdz -- 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: LVM/MD root filesystem not found by uuid
Matt, I am not trying to be dense or malevolent. I am well aware that Edgy is a development release, etc. But I am also a computer professional who has to deal with incident reports on a daily basis, so I have a quite good understanging of the issues involved. In my opinion the handling of this bug report has not been adequate. Just to demonstrate the facts: # env COLUMNS=120 dpkg -l grub [...] ii grub 0.97-11ubuntu10 GRand Unified Bootloader # egrep -nC1 "Update.*root device.*UUID" /sbin/update-grub 751- 752:# Update the root device to mount-by-UUID 753-kopt=$(convert_kopt_to_uuid "$kopt") # grep -c UUID /boot/grub/menu.lst 0 # /sbin/update-grub Searching for GRUB installation directory ... found: /boot/grub Testing for an existing GRUB menu.list file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... Found kernel: /boot/vmlinuz-2.6.17-7-generic Found kernel: /boot/memtest86+.bin Updating /boot/grub/menu.lst ... done # grep -c UUID /boot/grub/menu.lst 3 So as you can see, even your "fixed" version silently corrupts the system. Against the expressed intention of the system owner/administrator who changed the relevant configuration file. Sorry, but this is simply not acceptable. Especially since upstream Debian can detect manual changes of a config file and will not change it. -- 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: [Bug 54002] Re: LVM/MD root filesystem not found by uuid
On Sun, Sep 10, 2006 at 05:51:06PM -, Benjamin_L wrote: > Then there seems to be a problem with the fix as 2.6.17-7 reverted my > lvm back to uuid. The kernel doesn't change your fstab or grub configuration. The former is done by udev, the latter by grub itself. Most likely your system was converted by older versions of these packages. The current versions no longer perform this conversion, and I doubt they attempt to undo a previous conversion. -- - mdz -- 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: LVM/MD root filesystem not found by uuid
Then there seems to be a problem with the fix as 2.6.17-7 reverted my lvm back to uuid. -- 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: LVM/MD root filesystem not found by uuid
grub (0.97-11ubuntu10) edgy; urgency=low * Don't transition LVM, evms and dev-mapper devices. (Ubuntu #54002) -- Scott James Remnant <[EMAIL PROTECTED]> Mon, 21 Aug 2006 09:48:55 +0200 ** Changed in: grub (Ubuntu) Importance: Untriaged => High Assignee: (unassigned) => Scott James Remnant Status: Rejected => Fix Released -- 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: LVM/MD root filesystem not found by uuid
I think either usplash or newer kernels still convert lvm to uuid. -- 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: LVM/MD root filesystem not found by uuid
Same problem here. root on LVM, boot hangs on "waiting for root filesystem". Also, my home is on LVM, which doesn't get mounted because the fstab was converted to UUIDs, and for my LVM Volumes, no entries in /dev/disk/by-uuid/ get created. ** Bug 54189 has been marked a duplicate of this bug -- 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: LVM/MD root filesystem not found by uuid
** Changed in: udev (Ubuntu) Status: Unconfirmed => Fix Released -- 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: LVM/MD root filesystem not found by uuid
I'm using lvm, otherwise I wouldn't have commented. -- 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: [Bug 54002] Re: LVM/MD root filesystem not found by uuid
On Fri, Aug 18, 2006 at 06:21:25AM -, Benjamin_L wrote: > I got the same problem here using two SATA disks without any RAID > configuration. Had to revert the entries using the live cd all times the > updater reverts to uuids. If you are not using LVM or RAID, then you likely have a different bug. Please file it separately with complete details. -- - mdz -- 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: LVM/MD root filesystem not found by uuid
I got the same problem here using two SATA disks without any RAID configuration. Had to revert the entries using the live cd all times the updater reverts to uuids. -- 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: LVM/MD root filesystem not found by uuid
This could also be considered a problem with the initramfs, and not with
udev.
The problem is actually with the /init file in the initramfs, it
converts a UUID=* entry into a ROOT entry of "/dev/disk/by-
uuid/${ROOT#UUID=}". This is needed, since the mount command included in
the initramfs does not understand the -U (mount by UUID) option. This,
combined with the fact that udev does not create /dev/disk/by-uuid/
entries for LVM partitions means that booting with an LVM root is not
possible without modifying the grub boot entry.
This also explains why mount with the UID specified in the fstab works,
as this uses the more advanced non-initramfs mount that does know how to
deal with UUID=* entries.
Hope this helps towards a solution, since this is a really disastrous
bug, that prevents LVM root systems from booting. Even worse, because of
the new tendency to fix initrd images when initramfs-tools are
"improved" it can even break a running system and make what used to work
stop working.
--
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: LVM/MD root filesystem not found by uuid
Scott, have you looked into this further? If this indeed fails for all LVM and/or MD devices, it would be serious indeed ** Changed in: udev (Ubuntu) Importance: Untriaged => High Assignee: (unassigned) => Scott James Remnant -- 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
