Can't Boot after latest Feisty Upgrade
John Graddy
jwgraddy at valornet.com
Sun Apr 8 22:33:55 UTC 2007
Thanks to Peter and NoOp for their responses to my message. I haven't
tried your suggestions yet because I found out that I had given
incorrect information. My system indeed does boot after the update,
However, there is a delay of over two minutes in the boot process. If I
wait long enough, the boot is successful.
In trying to find out what was happening, I did the following.
Synchronized my watch with my computer clock.
Powered up and entered the Grub menu. I began the boot process at
16:46:58. After the boot completed, I logged in and checked the boot
messages in /var/log/messages.
The first two messages in /var/log/messages were
"Apr 8 16:49:20 john syslogd 1.4.1#20ubuntu4: restart.
Apr 8 16:49:20 john
kernel:Inspecting /boot/System.map-2.6.20-14-generic
Note that the time on the "restart" message is 2:22 after Grub initiated
the boot.
How can I find out what the delay is?
Thanks,
John
On Sat, 2007-04-07 at 13:07 +1000, Peter Garrett wrote:
> On Fri, 06 Apr 2007 09:36:51 -0500
> John Graddy <jwgraddy at valornet.com> wrote:
>
> > I have installed all updates since Herd 2 was made available. The
> > update today (6 April) built a new Kernel (2.6.20-14). After updating,
> > I can't boot. I can drop back to 2.6.20-13 and boot successfully. I
> > fully expected to get a notification that updates were available, but I
> > don't get such a notification.
>
> For troubleshooting purposes, I would try booting the new kernel in
> "rescue" mode - you can choose this from the grub menu on boot ( hit <esc>
> to get a menu if you don't get one by default)
>
> See if the new kernel boots to s root prompt ( # prompt) . If it does, you
> can run something like " dmesg >> /home/yourusername/dmesg.dump " This
> should give you a file in your home directory with a record of what
> happened during boot, which might give you some clues what went wrong. You
> might want to submit a bug report against linux-source-2.6.20 on launchpad
> and attach that file, and the output of lspci -vvn
> ( same method; lspci -vvn >> lspci.dump )
>
> This is assuming a fix is not in the works, and there are no other bugs
> that look similar, of course...
>
> Try a search at
> https://launchpad.net/ubuntu/+bugs
>
> For instance,
>
> https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/103773
> https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/103696
>
> Peter
>
More information about the ubuntu-users
mailing list