=== JanC [n=janc@lugwv/member/JanC] has joined #ubuntu-boot === archis [n=archis@unaffiliated/archis] has joined #ubuntu-boot === archis [n=archis@unaffiliated/archis] has left #ubuntu-boot ["Ex-Chat"] === penguin42 [n=dg@tu006.demon.co.uk] has joined #ubuntu-boot [09:22] hmm pretty empty [09:23] I've got a 6 minute hang during edgy boot - is there anything I can do to get the boot process to spit out any diags? [09:23] (Yes minute!) [09:24] remove quiet from grub boot args [09:24] also splash [09:25] already done that ; it shows nothing during the pause that happens just after detecting a usb flash card reader and between starting RAID - and it still happens if I remove the flash card reader [09:26] I've got a sysrq-t in the bug report I filed: https://launchpad.net/distros/ubuntu/+bug/68888 [09:27] hmm seems more like an mdadm bug than a kernel one [09:27] but you might want to ask on a week day on #ubuntu-kernel [09:28] also you could add a set -x to the mdadm boot script and see what's taking so much time [09:29] makx: I'm confused how far the boot has got at that point - am I out of initrd at that point? [09:29] can't tell from your snipps [09:30] if you see a call to init before the pause yes [09:31] Running /scripts/init-bottom is the last message from initramfs [09:34] I'm not sure I do - but let me see what I've got in the logs [09:38] makx: I don't see anything like that in the /var/log/messages - and that trace still shows a lot of busybox calls which make me wonder if its still in the initrd [09:44] the messages from the initramfs don't land in /var/log/messages [09:44] what i told you can see it on boot :) [09:44] yeh but only if I'm quick and watch very carefully! [09:45] but what about the fact that busybox is still running - that surely sounds like it is the initrd? [09:48] busybox is not running it's not a damon, what do you mean? [09:48] s/damon/daemon/ [09:49] makx: Look at my sysrq-t trace - it shows some busybox processes running [09:49] I assume that busybox is used by the initrd but nothing else? [09:49] yes it's inside [09:50] ok, are there any good ways of debugging a bad initrd or is it just a case of scattering echo's around the scripts? [09:51] you should have an mdadm script in /usr/share/initramfs-tools/scripts/local-top/ just add an set -x and see what is the troubeling cmd [09:52] then the next time you can boot with break=top and try to issue the same to double check.. [09:53] ah when you change that mdadm script don't forget to rebuild initramfs with update-initramfs -u [09:53] ok, I think I can see it possibly - there is a thing called 'slumber' in local-top/md and its something to do with sleeping but I can't quit esee what its trying to do [09:55] makx: Can you see that script - can you see htf it isn't supposed to wait for a few minutes? [09:56] the slumber is waiting for your devices to appear afais [09:56] ok - but how does it get out of that loop when it does? I can't see anything that breaks out of the while [09:56] are you booting with lilo? [09:56] no [09:56] ok === penguin42 can't see how that script is supposed to work quickly [09:58] +while [ "$configureduuids" ] [09:58] this seems the wrong way [09:59] yeh there is something then which removes the uuid's if it found it [10:00] and that script provides *no* feedback for something that could wait for 10 minutes [10:01] i need sleep, pls add feedback to bug report :) [10:01] only a guest here.. [10:01] hey thanks :-) [10:02] hmm I think I know why this happens - that script assumes the UUID= is the last thing on the line in the mdadm.conf === penguin42 sets the package as mdadm and suggests a fix === penguin42 goes === penguin42 [n=dg@tu006.demon.co.uk] has left #ubuntu-boot ["Leaving"]