Results 1 to 9 of 9

Thread: Missing hal.dll, but UBUNTU is what won't boot...

  1. #1
    Join Date
    May 2009
    Beans
    5

    Missing hal.dll, but UBUNTU is what won't boot...

    Hey, so I had installed ubuntu yesterday using wubi, and everything went fine, I was using it, and then came to find that it had only made a like 8gb install on the 150 partition. So I uninstalled that and used the cd to install and it seemed to go perfectly (this is something that hadn't been working for me earlier (which is why i used wubi) b/c of the "out of range" error). But when I try to boot into ubuntu at the boot menu it gives me the oh so common "missing/corrupted hal.dll" error. the odd thing is windows boots just fine! it's when i boot ubuntu that i get the windows is missing...error! i tried replacing the hal.dll file in the c:\windows\system32 folder, but still the same error. I have 2 drives, 1 is 150gb's and just 1 partition for windows. the other is 500gb's total and split into 2 partitions, 1 150gb for ubuntu, and 1 350gb for storage for both os's.

    my boot file looks like this:
    Code:
    [boot loader]
    timeout=30
    default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
    [operating systems]
    multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home Edition" /noexecute=optin /fastdetect
    C:\wubildr.mbr="Ubuntu"
    now the thing is there is no "wubildr.mbr" file visible in the c:\ drive.

    soooo....what can/should i do? i'd really like to use ubuntu and don't want to have to try out other distro's.

  2. #2
    Join Date
    May 2009
    Beans
    5

    Re: Missing hal.dll, but UBUNTU is what won't boot...

    Anyone??

  3. #3
    Join Date
    Apr 2008
    Beans
    3,317
    Distro
    Kubuntu 9.10 Karmic Koala

    Re: Missing hal.dll, but UBUNTU is what won't boot...

    Please wait for 24 hours before bumping your thread.

    In order to get a clearer picture of your setup, I suggest to boot from the Ubuntu LiveCD and download the Boot Info Script to your desktop:

    https://sourceforge.net/projects/bootinfoscript/

    Then open a terminal (Applications > Accessories > Terminal) and type:

    Code:
    sudo bash ~/Desktop/boot_info_script*.sh
    That will create a "RESULTS.txt" file in the same directory from where the script is run, namely your desktop; please copy/paste the contents of the RESULTS.txt file to your next post (use the code tags).

  4. #4
    Join Date
    May 2009
    Beans
    5

    Re: Missing hal.dll, but UBUNTU is what won't boot...

    Code:
    ============================= Boot Info Summary: ==============================
    
     => Grub0.97 is installed in the MBR of /dev/sda and looks on the same drive 
        in partition #1 for /boot/grub/stage2 and /boot/grub/menu.lst.
     => Windows is installed in the MBR of /dev/sdb
    
    sda1: _________________________________________________________________________
    
        File system:       ext3
        Boot sector type:  -
        Boot sector info:  
        Operating System:  Ubuntu 9.04
        Boot files/dirs:   /boot/grub/menu.lst /etc/fstab
    
    sda2: _________________________________________________________________________
    
        File system:       Extended Partition
        Boot sector type:  -
        Boot sector info:  
    
    sda5: _________________________________________________________________________
    
        File system:       swap
        Boot sector type:  -
        Boot sector info:  
    
    sdb1: _________________________________________________________________________
    
        File system:       ntfs
        Boot sector type:  Windows XP
        Boot sector info:  No errors found in the Boot Parameter Block.
        Operating System:  Windows XP
        Boot files/dirs:   /boot.ini /ntldr /NTDETECT.COM
    
    =========================== Drive/Partition Info: =============================
    
    Drive: sda ___________________ _____________________________________________________
    
    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: 0xd03ac7f5
    
    Partition  Boot         Start           End          Size  Id System
    
    /dev/sda1    *             63   953,779,049   953,778,987  83 Linux
    /dev/sda2         953,779,050   976,768,064    22,989,015   5 Extended
    /dev/sda5         953,779,113   976,768,064    22,988,952  82 Linux swap / Solaris
    
    
    Drive: sdb ___________________ _____________________________________________________
    
    Disk /dev/sdb: 160.0 GB, 160041885696 bytes
    255 heads, 63 sectors/track, 19457 cylinders, total 312581808 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Disk identifier: 0x10a110a1
    
    Partition  Boot         Start           End          Size  Id System
    
    /dev/sdb1    *             63   312,560,639   312,560,577   7 HPFS/NTFS
    
    
    blkid -c /dev/null: ____________________________________________________________
    
    /dev/loop0: TYPE="squashfs" 
    /dev/sda1: UUID="dc902571-46d0-4d28-96e4-ff6d0a8616c1" SEC_TYPE="ext2" TYPE="ext3" 
    /dev/sda5: TYPE="swap" 
    /dev/sdb1: UUID="8EFC4D04FC4CE7D3" TYPE="ntfs" 
    
    =============================== "mount" output: ===============================
    
    proc on /proc type proc (rw)
    sysfs on /sys type sysfs (rw)
    tmpfs on /lib/modules/2.6.28-11-generic/volatile type tmpfs (rw,mode=0755)
    tmpfs on /lib/modules/2.6.28-11-generic/volatile type tmpfs (rw,mode=0755)
    tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
    varrun on /var/run type tmpfs (rw,nosuid,mode=0755)
    varlock on /var/lock type tmpfs (rw,noexec,nosuid,nodev,mode=1777)
    udev on /dev type tmpfs (rw,mode=0755)
    tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
    devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
    rootfs on / type rootfs (rw)
    /dev/sr0 on /cdrom type iso9660 (ro,noatime)
    /dev/loop0 on /rofs type squashfs (ro,noatime)
    fusectl on /sys/fs/fuse/connections type fusectl (rw)
    tmpfs on /tmp type tmpfs (rw,nosuid,nodev)
    binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
    gvfs-fuse-daemon on /home/ubuntu/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=ubuntu)
    
    
    =========================== sda1/boot/grub/menu.lst: ===========================
    
    # 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        10
    
    ## 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=dc902571-46d0-4d28-96e4-ff6d0a8616c1 ro xforcevesa
    
    ## default grub root device
    ## e.g. groot=(hd0,0)
    # groot=dc902571-46d0-4d28-96e4-ff6d0a8616c1
    
    ## 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
    
    ## specify if running in Xen domU or have grub detect automatically
    ## update-grub will ignore non-xen kernels when running in domU and vice versa
    ## e.g. indomU=detect
    ##      indomU=true
    ##      indomU=false
    # indomU=detect
    
    ## 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 9.04, kernel 2.6.28-11-generic
    uuid        dc902571-46d0-4d28-96e4-ff6d0a8616c1
    kernel        /boot/vmlinuz-2.6.28-11-generic root=UUID=dc902571-46d0-4d28-96e4-ff6d0a8616c1 ro xforcevesa quiet splash 
    initrd        /boot/initrd.img-2.6.28-11-generic
    quiet
    
    title        Ubuntu 9.04, kernel 2.6.28-11-generic (recovery mode)
    uuid        dc902571-46d0-4d28-96e4-ff6d0a8616c1
    kernel        /boot/vmlinuz-2.6.28-11-generic root=UUID=dc902571-46d0-4d28-96e4-ff6d0a8616c1 ro xforcevesa  single
    initrd        /boot/initrd.img-2.6.28-11-generic
    
    title        Ubuntu 9.04, memtest86+
    uuid        dc902571-46d0-4d28-96e4-ff6d0a8616c1
    kernel        /boot/memtest86+.bin
    quiet
    
    ### END DEBIAN AUTOMAGIC KERNELS LIST
    
    # This is a divider, added to separate the menu items below from the Debian
    # ones.
    title        Other operating systems:
    root
    
    
    # This entry automatically added by the Debian installer for a non-linux OS
    # on /dev/sdb1
    title        Microsoft Windows XP Home Edition
    rootnoverify    (hd1,0)
    savedefault
    makeactive
    map        (hd0) (hd1)
    map        (hd1) (hd0)
    chainloader    +1
    
    
    =============================== sda1/etc/fstab: ===============================
    
    # /etc/fstab: static file system information.
    #
    # Use 'vol_id --uuid' to print the universally unique identifier for a
    # device; this may be used with UUID= as a more robust way to name devices
    # that works even if disks are added and removed. See fstab(5).
    #
    # <file system> <mount point>   <type>  <options>       <dump>  <pass>
    proc            /proc           proc    defaults        0       0
    # / was on /dev/sda1 during installation
    UUID=dc902571-46d0-4d28-96e4-ff6d0a8616c1 /               ext3    relatime,errors=remount-ro 0       1
    # swap was on /dev/sda5 during installation
    UUID=00fd72a7-f79e-48a7-af16-d389e5b14c53 none            swap    sw              0       0
    /dev/scd0       /media/cdrom0   udf,iso9660 user,noauto,exec,utf8 0       0
    
    =================== sda1: Location of files loaded by Grub: ===================
    
    
      83.0GB: boot/grub/menu.lst
      83.0GB: boot/grub/stage2
      83.0GB: boot/initrd.img-2.6.28-11-generic
      83.0GB: boot/vmlinuz-2.6.28-11-generic
      83.0GB: initrd.img
      83.0GB: vmlinuz
    
    ================================ sdb1/boot.ini: ================================
    
    [boot loader] 
    timeout=30 
    default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS 
    [operating systems] 
    multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home Edition" /noexecute=optin /fastdetect 
    C:\wubildr.mbr="Ubuntu"
    This is really annoying. Does the fact that that file it points to from my original boot.ini doesn't exist? Can I use a different bootloader to try and boot? Would my MBR be messed up and need to be fixed? I just don't understand how this is happening and what to do.

    This is what my menu.lst file says in the grub folder on my ubuntu install (i can see it by booting into the live cd and exploring the drive):
    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        10
    
    ## 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=dc902571-46d0-4d28-96e4-ff6d0a8616c1 ro xforcevesa
    
    ## default grub root device
    ## e.g. groot=(hd0,0)
    # groot=dc902571-46d0-4d28-96e4-ff6d0a8616c1
    
    ## 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
    
    ## specify if running in Xen domU or have grub detect automatically
    ## update-grub will ignore non-xen kernels when running in domU and vice versa
    ## e.g. indomU=detect
    ##      indomU=true
    ##      indomU=false
    # indomU=detect
    
    ## 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 9.04, kernel 2.6.28-11-generic
    uuid        dc902571-46d0-4d28-96e4-ff6d0a8616c1
    kernel        /boot/vmlinuz-2.6.28-11-generic root=UUID=dc902571-46d0-4d28-96e4-ff6d0a8616c1 ro xforcevesa quiet splash 
    initrd        /boot/initrd.img-2.6.28-11-generic
    quiet
    
    title        Ubuntu 9.04, kernel 2.6.28-11-generic (recovery mode)
    uuid        dc902571-46d0-4d28-96e4-ff6d0a8616c1
    kernel        /boot/vmlinuz-2.6.28-11-generic root=UUID=dc902571-46d0-4d28-96e4-ff6d0a8616c1 ro xforcevesa  single
    initrd        /boot/initrd.img-2.6.28-11-generic
    
    title        Ubuntu 9.04, memtest86+
    uuid        dc902571-46d0-4d28-96e4-ff6d0a8616c1
    kernel        /boot/memtest86+.bin
    quiet
    
    ### END DEBIAN AUTOMAGIC KERNELS LIST
    
    # This is a divider, added to separate the menu items below from the Debian
    # ones.
    title        Other operating systems:
    root
    
    
    # This entry automatically added by the Debian installer for a non-linux OS
    # on /dev/sdb1
    title        Microsoft Windows XP Home Edition
    rootnoverify    (hd1,0)
    savedefault
    makeactive
    map        (hd0) (hd1)
    map        (hd1) (hd0)
    chainloader    +1
    Last edited by captj; May 2nd, 2009 at 02:22 AM.

  5. #5
    Join Date
    Apr 2008
    Beans
    3,317
    Distro
    Kubuntu 9.10 Karmic Koala

    Re: Missing hal.dll, but UBUNTU is what won't boot...

    Are you sure that you did a Wubi install and not a regular install?
    The script did not detect any traces of Wubi (other than the entry in boot.ini)
    But you do seem to have a regular Ubuntu install on your 500GB drive.

    What happens when set your bios to boot from 500GB drive? You should get the Grub menu, which allows you do boot into Ubuntu and XP.

  6. #6
    Join Date
    May 2009
    Beans
    5

    Re: Missing hal.dll, but UBUNTU is what won't boot...

    Quote Originally Posted by meierfra. View Post
    Are you sure that you did a Wubi install and not a regular install?
    The script did not detect any traces of Wubi (other than the entry in boot.ini)
    But you do seem to have a regular Ubuntu install on your 500GB drive.

    What happens when set your bios to boot from 500GB drive? You should get the Grub menu, which allows you do boot into Ubuntu and XP.
    i had said for this install i had NOT used wubi, just installed normally from the cd. the one that had been working in the very beginning was the one that worked and THAT one was installed using wubi.

  7. #7
    Join Date
    Apr 2008
    Beans
    3,317
    Distro
    Kubuntu 9.10 Karmic Koala

    Re: Missing hal.dll, but UBUNTU is what won't boot...

    Sorry, I got confused, since you were still trying to boot into Ubuntu via the entry in the XP boot menu. That entry is left over from your old Wubi install.


    Anyway, see what happens if you set your bios to boot from the 500GB drive.

  8. #8
    Join Date
    May 2009
    Beans
    5

    Re: Missing hal.dll, but UBUNTU is what won't boot...

    FIXED FIXED FIXED!!!!!!!!
    thank you so much!!!!!
    i changed the boot order in my bios so that the ubuntu drive was first so that it used the grub bootloader instead of the windows one! YAY!!!! Now to make it all awesome again! haha. well, really, first i have to shrink the partition from the whole drive, down to like 150gb's and format the rest to ntfs for shared storage between the two os's! YAYY!
    thank you again!

  9. #9
    Join Date
    Apr 2008
    Beans
    3,317
    Distro
    Kubuntu 9.10 Karmic Koala

    Re: Missing hal.dll, but UBUNTU is what won't boot...

    FIXED FIXED FIXED!!!!!!!!
    Great.

    I have to shrink the partition from the whole drive, down to like 150gb's and format the rest to ntfs for shared storage between the two os'
    Just be aware that shrinking a 488 GB partition down to 150 GB might take a while.

Tags for this Thread

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
  •