Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: Cold start requires restart

  1. #1
    Join Date
    Jun 2008
    Beans
    3

    Cold start requires restart

    Greetings from a Ubuntu (and Linux) newbie. I've successfully downloaded and installed 8.04 LTS on a machine devoted entirely to Ubuntu. After installing off the cd, I reset my BIOS to boot off the hard drive. I typically shutdown the machine and turn off its power after I'm through for the day. When I cold start the machine the next day, I see a brief message about GRUB, then I get the Ubuntu logo splash screen with the horizontally oscillating gauge--but that's it: it just sits there like that. After waiting 15 minutes I hit the reset switch. That worked: in short order it went through GRUB, then the splash screen, then presented the login screen. I logged in any everything was fine, as far as I can tell. This happens every time I shutdown. Is this the design behaviour, or do I need to change something?

  2. #2
    Join Date
    Feb 2007
    Location
    U.S.A.
    Beans
    1,835
    Distro
    Ubuntu 8.04 Hardy Heron

    Re: Cold start requires restart

    That is not normal behavior no.

    With the little information given I'm going out on a limb and guessing:

    fsck is running and taking its sweet time

    or the box is trying to connect to the network and hanging, then on second boot since its established an address it just jumps right in.

    My best 2 guesses

  3. #3
    Join Date
    Jan 2007
    Location
    United States, VA
    Beans
    856
    Distro
    Ubuntu 8.04 Hardy Heron

    Re: Cold start requires restart

    Could you hit Ctrl-Alt-F1 while it is booting and post back here with what it is saying? Just write it down, you have about fifteen minutes .

  4. #4
    Join Date
    Jan 2007
    Location
    United States, VA
    Beans
    856
    Distro
    Ubuntu 8.04 Hardy Heron

    Re: Cold start requires restart

    Ok, yeah, that could be fsck checking your disk. It checks every thirty boots, so, this is after thirty days, I am assuming. It checks the disk so there is no unseen errors and such.

    However, it is faster than defraging the disk .

  5. #5
    Join Date
    Oct 2007
    Location
    United Kingdom
    Beans
    762
    Distro
    Ubuntu 9.10 Karmic Koala

    Re: Cold start requires restart

    Quote Originally Posted by st33med View Post
    Ok, yeah, that could be fsck checking your disk. It checks every thirty boots, so, this is after thirty days, I am assuming. It checks the disk so there is no unseen errors and such.

    However, it is faster than defraging the disk .
    It also typically doesn't take 15mins...
    "Python, the language that wraps itself around a problem to squeeze out a solution, swallowing it whole."
    Linux user number #14284
    "A journey of a thousand miles begins with a single step." - Confucius.

  6. #6
    Join Date
    Jan 2007
    Location
    United States, VA
    Beans
    856
    Distro
    Ubuntu 8.04 Hardy Heron

    Re: Cold start requires restart

    Quote Originally Posted by ByteJuggler View Post
    It also typically doesn't take 15mins...
    On an old or slow machine, it could. I had Gutsy Gibbon previously take ten minutes to check.

  7. #7
    Join Date
    Jun 2008
    Beans
    3

    Re: Cold start requires restart

    Thank you all very much for your suggestions. I am not at the machine now (it's @ home, I'm @ work). I will analyze the situation tonight, as suggested. I'll start by letting it run longer before I try a reset. I'll post back later. Thanks again.

  8. #8
    Join Date
    Oct 2007
    Beans
    441

    Re: Cold start requires restart

    Hmm, fsck should say its running the test on the screen, it wont do it in the background. Also the pattern of the problem doesn't make sense for that - why would it try every other go.

    I'd have a peak through your system logs in System, admin, system logs to see if anything is obviously amiss and post it here. Not really sure under which section you're most likely to find something useful I'm afraid, so there's a lot to wade through. Hopefully someone can point you more in the right direction, although you can use the time stamps to help if you know when it crashed.

  9. #9
    Join Date
    Mar 2006
    Location
    Williams Lake
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: Cold start requires restart

    Sounds like a hardware problem. Pull the side off your computer and check all your connections, make sure all your peripherals are plugged in securely.

    Jim

  10. #10
    Join Date
    Jun 2008
    Beans
    3

    Re: Cold start requires restart

    After getting home I switched the machine on and waited. Same behaviour as per my original post, except that it eventually switched from the splash screen to a bare terminal screen running "BusyBox". I let that run for 2.5 hours before I gave up & hit the restart switch (which brought up the Ubuntu login screen reasonably quickly). While running, BusyBox spewed forth many screens full of what I take to be error messages, mostly "exception Emask" and "Buffer I/O error" messages. Many of the messages appear to relate to logical partition sda8.

    I shutdown then rebooted & hit Ctrl-Alt-F1 as suggested by st33med. That produced many messages having the same format as the BusyBox messages, one example being:

    [ 46.382033] ata1.00: exception Emask 0x0 Sact 0x0 Serr 0x0 action 0x2 frozen

    FWIW, the machine is an old P4 with 1GB RAM (newly installed), one 40GB & one 4GB drive. I initially installed Ubuntu using what appeared to be the easiest option offered by the cd: 'let Ubuntu have the entire disk'. Subsequent reading made me think I'd be better off partitioning my drives, so I reinstalled Ubuntu and while doing so I used the partitioning feature to yield this:

    Disk /dev/sda: 40.0 GB, 40027029504 bytes
    255 heads, 63 sectors/track, 4866 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x8e014932

    Device Boot Start End Blocks Id System
    /dev/sda1 * 1 12 96358+ 83 Linux <-- /boot
    /dev/sda2 13 741 5855692+ 83 Linux <-- /
    /dev/sda3 742 4267 28322595 5 Extended
    /dev/sda5 742 1470 5855661 83 Linux <-- /usr
    /dev/sda6 1471 1713 1951866 83 Linux <-- /var
    /dev/sda7 1714 1835 979933+ 83 Linux <-- /tmp
    /dev/sda8 1836 4267 19535008+ 83 Linux <-- /home

    Disk /dev/sdb: 4325 MB, 4325529600 bytes
    255 heads, 63 sectors/track, 525 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0x107a1079

    Device Boot Start End Blocks Id System
    /dev/sdb1 1 243 1951866 82 Linux swap / Solaris

    I'm inclined to think that I have hardware problems as some of you have suggested, but I'm mystified because once I login the machine seems fine. I do not yet have any plans for the machine except using it to learn about Ubuntu, linux, etc. I thought that a mothballed machine would be ideal but it may be that the machine is defective in some manner. Should I run System/Administration/Hardware Testing?

Page 1 of 2 12 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •