Hi, I'm sorry, but there is just not enough information to make any sort of diagnosis on what caused the issue. The 'grub-probe' error messages in the upgrade can be ignored. They're there only because grub-pc package is installed, but it is not being used. The pv-grub aki from amazon is loading the image.
Can you please collect a get-console-output of a failed instance? Alternatively, you are welcome to give me access to the ami that you upgraded and failed, and I can try to look. Without one of those bits of information, we really can't make any progress on this bug. As Ben noted, the issue does not occur on current AMIs. Without being able to reproduce or see information on a failed state, we simply cannot help. I've tried to reproduce by launching a t1.micro instance of 'ami-311f2b45' (eu-west-1 ebs/ubuntu-lucid-10.04-i386-server-20110201.1). That is the oldest ami available that uses the pv-grub kernel you reported this issue on (aki-4deec439). I then ran 'sudo apt-get update && sudo apt-get dist-upgrade'. After that was successfull, I rebooted. The system came up fine into the kernel 'vmlinuz-2.6.32-342-ec2' (which is shown in your output). ** Attachment added: "console output showing boot into 2.6.32-312 and reboot into 2.6.32-342" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/927805/+attachment/2795080/+files/console-output.txt ** Changed in: cloud-init (Ubuntu) Importance: High => Medium ** Changed in: cloud-init (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/927805 Title: t1.micro instance defect after dist-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/927805/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
