On Mon, 2006-09-11 at 20:10 +0000, Dominik Kubla wrote: > I doubt that this is possible for all valid configurations. I could name at > least six valid configurations/situations where it will not work out of the > box, will not work ever or will have side-effects so severe that it will lead > to an immediate ban of all Ubuntu installations by the authorities. > What are these valid configurations?
It would help somewhat if you would actually explain them, instead of just asserting that there's a problem. > But for the problem at hand I think I may have found it. It looks like you > have a circular dependency in /scripts/local-top: > > I did a boot with break=mount, then sourced scripts/functions and executed > run_scripts scripts/local-top. Then I checked /dev/disk. There were only > directories by-id and by-path, no by-uuid. > Ok, so this implies that none of the block devices that existed at that point had UUIDs. > md depends on udev. So udev will be called first. But it will not create > by-UUID entries for RAID components. mdrun has not been executed at this time > so it will also not create by-uuid entries for the MD devices. > This makes sense. > Then md starts the RAID devices but udev already ran so the device links will > never be created and the "mount root" step will wait forever for the device > files to appear. > udev is RUNNING, not has already ran. This implies that md is somehow not causing the kernel to issue uevents for the block devices it's creating? That should be relatively simple to fix, I would guess. Another option would be to integrate the various md components in such a way that they're triggered by the kernel uevents for the underlying block devices, thus the md portions are in place and the UUID symlinks created. Either or both of these things would be good things. > So I think you will have top put /dev/md* on the exclusion list as well. And > that pretty much limits your new booting scheme to desktop systems without > fault-tolerance or recovery features. Given the fact that Ubuntu now also > targets the Enterprise desktop and server markets I'd have to say: Forget > mount by-uuid. > Which means that next release, no system with md/raid/etc. will boot or be able to locate its root filesystem. I win on the doomsday war ;) We're not switching to mount-by-UUID for no good reason, you know. 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
