/srv/irclogs.ubuntu.com/2006/10/28/#ubuntu-boot.txt

=== 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
penguin42hmm pretty empty09:22
penguin42I'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
penguin42(Yes minute!)09:23
makxremove quiet from grub boot args09:24
makxalso splash09:24
penguin42already 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 reader09:25
penguin42I've got a sysrq-t in the bug report I filed: https://launchpad.net/distros/ubuntu/+bug/6888809:26
makxhmm seems more like an mdadm bug than a kernel one09:27
makxbut you might want to ask on a week day on #ubuntu-kernel09:27
makxalso you could add a set -x to the mdadm boot script and see what's taking so much time09:28
penguin42makx: I'm confused how far the boot has got at that point - am I out of initrd at that point?09:29
makxcan't tell from your snipps09:29
makxif you see a call to init before the pause yes09:30
makxRunning /scripts/init-bottom is the last message from initramfs09:31
penguin42I'm not sure I do - but let me see what I've got in the logs09:34
penguin42makx: 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 initrd09:38
makxthe messages from the initramfs don't land in /var/log/messages09:44
makxwhat i told you can see it on boot :)09:44
penguin42yeh but only if I'm quick and watch very carefully!09:44
penguin42but what about the fact that busybox is still running - that surely sounds like it is the initrd?09:45
makxbusybox is not running it's not a damon, what do you mean?09:48
makxs/damon/daemon/09:48
penguin42makx: Look at my sysrq-t trace - it shows some busybox processes running09:49
penguin42I assume that busybox is used by the initrd but nothing else?09:49
makxyes it's inside09:49
penguin42ok, are there any good ways of debugging a bad initrd or is it just a case of scattering echo's around the scripts?09:50
makxyou should have an mdadm script in /usr/share/initramfs-tools/scripts/local-top/ just add an set -x and see what is the troubeling cmd09:51
makxthen the next time you can boot with break=top and try to issue the same to double check..09:52
makxah when you change that mdadm script don't forget to rebuild initramfs with update-initramfs -u09:53
penguin42ok, 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 do09:53
penguin42makx: Can you see that script - can you see htf it isn't supposed to wait for a few minutes?09:55
makxthe slumber is waiting for your devices to appear afais09:56
penguin42ok - but how does it get out of that loop when it does? I can't see anything that breaks out of the while09:56
makxare you booting with lilo?09:56
penguin42no09:56
makxok09:56
=== penguin42 can't see how that script is supposed to work quickly
makx+while [ "$configureduuids" ] 09:58
makxthis seems the wrong way09:58
penguin42yeh there is something then which removes the uuid's if it found it09:59
penguin42and that script provides *no* feedback for something that could wait for 10 minutes10:00
makxi need sleep, pls add feedback to bug report :)10:01
makxonly a guest here..10:01
penguin42hey thanks :-)10:01
penguin42hmm I think I know why this happens - that script assumes the UUID= is the last thing on the line in the mdadm.conf10:02
=== penguin42 sets the package as mdadm and suggests a fix
=== penguin42 goes
=== penguin42 [n=dg@tu006.demon.co.uk] has left #ubuntu-boot ["Leaving"]

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!