Announcement

Collapse
No announcement yet.

Gutsy won't boot - FIXED

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Gutsy won't boot - FIXED

    Hi,

    Suddenly today Gutsy won't startup from the hard drive. It will start with the Live CD and I can mount the partitions.

    When I start the PC I see a black screen with a flashing _ at the top left, after about 5 seconds the flashing _ moves down one line. That's it.

    What can I do to start Gutsy?

    menu.lst looks like
    Code:
     
    # menu.lst - See: grub(8), info grub, update-grub(8)
    #      grub-install(8), grub-floppy(8),
    #      grub-md5-crypt, /usr/share/doc/grub
    #      and /usr/share/doc/grub-doc/.
    
    ## default num
    # Set the default entry to the entry number NUM. Numbering starts from 0, and
    # the entry number 0 is the default if the command is not used.
    #
    # You can specify 'saved' instead of a number. In this case, the default entry
    # is the entry saved with the command 'savedefault'.
    # WARNING: If you are using dmraid do not use 'savedefault' or your
    # array will desync and will not let you boot your system.
    default		0
    
    ## timeout sec
    # Set a timeout, in SEC seconds, before automatically booting the default entry
    # (normally the first entry defined).
    timeout		30
    
    ## hiddenmenu
    # Hides the menu by default (press ESC to see the menu)
    # hiddenmenu
    
    # Pretty colours
    #color cyan/blue white/blue
    
    ## password ['--md5'] passwd
    # If used in the first section of a menu file, disable all interactive editing
    # control (menu entry editor and command-line) and entries protected by the
    # command 'lock'
    # e.g. password topsecret
    #   password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
    # password topsecret
    
    #
    # examples
    #
    # title		Windows 95/98/NT/2000
    # root		(hd0,0)
    # makeactive
    # chainloader	+1
    #
    # title		Linux
    # root		(hd0,1)
    # kernel	/vmlinuz root=/dev/hda2 ro
    #
    
    #
    # Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST
    
    ### BEGIN AUTOMAGIC KERNELS LIST
    ## lines between the AUTOMAGIC KERNELS LIST markers will be modified
    ## by the debian update-grub script except for the default options below
    
    ## DO NOT UNCOMMENT THEM, Just edit them to your needs
    
    ## ## Start Default Options ##
    ## default kernel options
    ## default kernel options for automagic boot options
    ## If you want special options for specific kernels use kopt_x_y_z
    ## where x.y.z is kernel version. Minor versions can be omitted.
    ## e.g. kopt=root=/dev/hda1 ro
    ##   kopt_2_6_8=root=/dev/hdc1 ro
    ##   kopt_2_6_8_2_686=root=/dev/hdc2 ro
    # kopt=root=UUID=d6f4e5cf-61e5-47b6-a433-7c3d29bedd69 ro
    
    ## Setup crashdump menu entries
    ## e.g. crashdump=1
    # crashdump=0
    
    ## default grub root device
    ## e.g. groot=(hd0,0)
    # groot=(hd0,1)
    
    ## should update-grub create alternative automagic boot options
    ## e.g. alternative=true
    ##   alternative=false
    # alternative=true
    
    ## should update-grub lock alternative automagic boot options
    ## e.g. lockalternative=true
    ##   lockalternative=false
    # lockalternative=false
    
    ## additional options to use with the default boot option, but not with the
    ## alternatives
    ## e.g. defoptions=vga=791 resume=/dev/hda5
    # defoptions=quiet splash
    
    ## should update-grub lock old automagic boot options
    ## e.g. lockold=false
    ##   lockold=true
    # lockold=false
    
    ## Xen hypervisor options to use with the default Xen boot option
    # xenhopt=
    
    ## Xen Linux kernel options to use with the default Xen boot option
    # xenkopt=console=tty0
    
    ## altoption boot targets option
    ## multiple altoptions lines are allowed
    ## e.g. altoptions=(extra menu suffix) extra boot options
    ##   altoptions=(recovery) single
    # altoptions=(recovery mode) single
    
    ## controls how many kernels should be put into the menu.lst
    ## only counts the first occurence of a kernel, not the
    ## alternative kernel options
    ## e.g. howmany=all
    ##   howmany=7
    # howmany=all
    
    ## should update-grub create memtest86 boot option
    ## e.g. memtest86=true
    ##   memtest86=false
    # memtest86=true
    
    ## should update-grub adjust the value of the default booted system
    ## can be true or false
    # updatedefaultentry=false
    
    ## should update-grub add savedefault to the default options
    ## can be true or false
    # savedefault=false
    
    ## ## End Default Options ##
    
    title		Ubuntu 7.10, kernel 2.6.22-14-generic
    root		(hd0,1)
    kernel		/boot/vmlinuz-2.6.22-14-generic root=UUID=d6f4e5cf-61e5-47b6-a433-7c3d29bedd69 ro quiet splash
    initrd		/boot/initrd.img-2.6.22-14-generic
    quiet
    
    title		Ubuntu 7.10, kernel 2.6.22-14-generic (recovery mode)
    root		(hd0,1)
    kernel		/boot/vmlinuz-2.6.22-14-generic root=UUID=d6f4e5cf-61e5-47b6-a433-7c3d29bedd69 ro single
    initrd		/boot/initrd.img-2.6.22-14-generic
    
    title		Ubuntu 7.10, memtest86+
    root		(hd0,1)
    kernel		/boot/memtest86+.bin
    quiet
    
    ### END DEBIAN AUTOMAGIC KERNELS LIST
    fdisk looks like
    Code:
    ubuntu@ubuntu:~$ sudo fdisk -lu
    
    Disk /dev/hda: 80.0 GB, 80026361856 bytes
    255 heads, 63 sectors/track, 9729 cylinders, total 156301488 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Disk identifier: 0x0005aacc
    
     Device Boot   Start    End   Blocks Id System
    /dev/hda1    39054015 156296384  58621185  5 Extended
    /dev/hda2 *     63  39054014  19526976 83 Linux
    /dev/hda5   136777410 156296384  9759487+ 82 Linux swap / Solaris
    /dev/hda6    39054141 136761344  48853602 83 Linux
    
    Partition table entries are not in disk order
    
    Disk /dev/sda: 500.1 GB, 500107862016 bytes
    255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Disk identifier: 0x000cda0d
    
     Device Boot   Start    End   Blocks Id System
    /dev/sda1       63 976768064 488384001 83 Linux
    
    Disk /dev/sdb: 519 MB, 519569408 bytes
    255 heads, 63 sectors/track, 63 cylinders, total 1014784 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Disk identifier: 0x46703228
    
     Device Boot   Start    End   Blocks Id System
    /dev/sdb1       63  1014740   507339  b W95 FAT32
    Partition 1 has different physical/logical endings:
      phys=(1023, 254, 63) logical=(63, 41, 63)
    ubuntu@ubuntu:~$

    #2
    Re: Gutsy won't boot

    When the flashing "_" is sitting there (after it moves down one line), you probably can do Alt-F1 and get a command line. Log in there, then enter
    Code:
    startx
    and you should get your desktop.

    You'll probably want to refer to this to fix it:

    http://kubuntuforums.net/forums/inde...opic=3085112.0

    Comment


      #3
      Re: Gutsy won't boot

      Sorry, I didn't say that the flashing _ appears immediately after the BIOS has finished doing its thing.

      Usually the BIOS takes about 60 seconds and then beeps, a message from GRUB appears 'Stage 1.5.' and then Kubuntu starts up.

      Now I hear the beep and then the flashing _ appears, I've tried several combinations of keys. The only keys that work are Caps/Num Lock and ctr/alt/delete.

      Comment


        #4
        Re: Gutsy won't boot

        Eeeeeeeeewwwwwwwww.

        So, you're not even getting to the boot menu, eh?

        Did you change anything in BIOS? Or leave a non-bootable CD in the drive? Or change the boot sequence for some reason? It sounds like it's not even looking at your hard drive to boot. :P

        Comment


          #5
          Re: Gutsy won't boot

          I did change a BIOS seeting earlier today. I enabled the parallel port with intention of using an old Agfa scanner, but I've restarted since.

          I've just disabled the parallel port and checked the boot sequence. The boot order appears to be the same. HDA, SDA then CD-Rom.

          If the BIOS can't find an OS won't it tell me - Invalid boot disk or similar useful message.

          I don't know what I have done but it has started up again.

          I've just re-enabled the parallel port in the BIOS and it has restarted again. This is very odd.

          Thanks for your help and ideas.

          Comment


            #6
            Re: Gutsy won't boot

            Maybe the bootloader (or Master Boot Record) got corrupted somehow? Hard to tell. The blinking cursor could mean anything. You can re-install the bootloader GRUB and see if that helps (it won't hurt anything, and it will rule out that part of the boot process).

            From your Live Kubuntu CD, open K > System > Konsole and type
            sudo grub
            to get a grub> prompt; then
            grub> root (hd0,1)
            grub> setup (hd0)
            grub> quit
            $ exit

            exit out of the Live CD session and re-boot to test it (first removing the Live CD when so prompted, of course).

            (there's a space after root and a space after setup)
            An intellectual says a simple thing in a hard way. An artist says a hard thing in a simple way. Charles Bukowski

            Comment


              #7
              Re: Gutsy won't boot

              OK -- I see your post now! Good you got it

              (keep my post above handy though ...
              An intellectual says a simple thing in a hard way. An artist says a hard thing in a simple way. Charles Bukowski

              Comment


                #8
                Re: Gutsy won't boot

                glad you got it working again - could you now edit the subject line and add something like SOLVED please - cheers!
                Once your problem is solved please mark the topic of the first post as SOLVED so others know and can benefit from your experience! / FAQ

                Comment

                Working...
                X