Page 2 of 4 FirstFirst 1234 LastLast
Results 11 to 20 of 31

Thread: Asus UL20A problem with F9 Factory Restore after Ubuntu installation

  1. #11
    Join Date
    Jan 2012
    Beans
    32

    Re: Asus UL20A problem with F9 Factory Restore after Ubuntu installation

    Hi bcbc,
    Thanks!

    When I start up I see the windows boot manager menu and it shows Windows Home Premium or Ubuntu. If I select Ubuntu, it shows two versions of Linux, then recovery mode for linux, then another two versions of Linux, and then recovery mode for linux.

    I had tried each option and none of them start the factory restore option. I am not sure how to boot the recovery partition.

  2. #12
    Join Date
    Nov 2009
    Location
    North Vancouver
    Beans
    Hidden!
    Distro
    Edubuntu 14.04 Trusty Tahr

    Re: Asus UL20A problem with F9 Factory Restore after Ubuntu installation

    Can you post your grub.cfg please? Also your /etc/default/grub file. Thanks

  3. #13
    Join Date
    Jan 2012
    Beans
    32

    Re: Asus UL20A problem with F9 Factory Restore after Ubuntu installation

    Hi bcbc,

    here is the /etc/default/grub file:

    # If you change this file, run 'update-grub' afterwards to update
    # /boot/grub/grub.cfg.

    GRUB_DEFAULT=0
    GRUB_HIDDEN_TIMEOUT=0
    GRUB_HIDDEN_TIMEOUT_QUIET=true
    GRUB_TIMEOUT=10
    GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
    GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
    GRUB_CMDLINE_LINUX="acpi_backlight=vendor"

    GRUB_CMDLINE_LINUX_DEFAULT="rootflags=umask=002,ui d=1000,gid=1000 quiet splash"


    # Uncomment to enable BadRAM filtering, modify to suit your needs
    # This works with Linux (no patch required) and with any kernel that obtains
    # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
    #GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xe fefefef"

    # Uncomment to disable graphical terminal (grub-pc only)
    #GRUB_TERMINAL=console

    # The resolution used on graphical terminal
    # note that you can use only modes which your graphic card supports via VBE
    # you can see them in real GRUB with the command `vbeinfo'
    #GRUB_GFXMODE=640x480

    # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
    #GRUB_DISABLE_LINUX_UUID=true

    # Uncomment to disable generation of recovery mode menu entries
    #GRUB_DISABLE_LINUX_RECOVERY="true"

    # Uncomment to get a beep at grub start
    #GRUB_INIT_TUNE="480 440 1"



    Here is the /boot/grub/grub.cfg file:






    #
    # DO NOT EDIT THIS FILE
    #
    # It is automatically generated by grub-mkconfig using templates
    # from /etc/grub.d and settings from /etc/default/grub
    #

    ### BEGIN /etc/grub.d/00_header ###
    if [ -s $prefix/grubenv ]; then
    set have_grubenv=true
    load_env
    fi
    set default="0"
    if [ "${prev_saved_entry}" ]; then
    set saved_entry="${prev_saved_entry}"
    save_env saved_entry
    set prev_saved_entry=
    save_env prev_saved_entry
    set boot_once=true
    fi

    function savedefault {
    if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
    fi
    }

    function recordfail {
    set recordfail=1
    if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; fi
    }

    function load_video {
    insmod vbe
    insmod vga
    }

    insmod part_msdos
    insmod ntfs
    set root='(hd0,msdos5)'
    search --no-floppy --fs-uuid --set 27C001CAA8B90A8D
    loopback loop0 /ubuntu/disks/root.disk
    set root=(loop0)
    if loadfont /usr/share/grub/unicode.pf2 ; then
    set gfxmode=640x480
    load_video
    insmod gfxterm
    fi
    terminal_output gfxterm
    insmod part_msdos
    insmod ntfs
    set root='(hd0,msdos5)'
    search --no-floppy --fs-uuid --set 27C001CAA8B90A8D
    loopback loop0 /ubuntu/disks/root.disk
    set root=(loop0)
    set locale_dir=($root)/boot/grub/locale
    set lang=en
    insmod gettext
    if [ "${recordfail}" = 1 ]; then
    set timeout=-1
    else
    set timeout=10
    fi
    ### END /etc/grub.d/00_header ###

    ### BEGIN /etc/grub.d/05_debian_theme ###
    set menu_color_normal=white/black
    set menu_color_highlight=black/light-gray
    ### END /etc/grub.d/05_debian_theme ###

    ### BEGIN /etc/grub.d/10_linux ###
    ### END /etc/grub.d/10_linux ###

    ### BEGIN /etc/grub.d/10_lupin ###
    menuentry "Ubuntu, Linux 2.6.35-32-generic" {
    insmod part_msdos
    insmod ntfs
    set root='(hd0,msdos5)'
    search --no-floppy --fs-uuid --set 27C001CAA8B90A8D
    loopback loop0 /ubuntu/disks/root.disk
    set root=(loop0)
    linux /boot/vmlinuz-2.6.35-32-generic root=UUID=27C001CAA8B90A8D loop=/ubuntu/disks/root.disk ro acpi_backlight=vendor rootflags=umask=002,uid=1000,gid=1000 quiet splash
    initrd /boot/initrd.img-2.6.35-32-generic
    }
    menuentry "Ubuntu, Linux 2.6.35-32-generic (recovery mode)" {
    insmod part_msdos
    insmod ntfs
    set root='(hd0,msdos5)'
    search --no-floppy --fs-uuid --set 27C001CAA8B90A8D
    loopback loop0 /ubuntu/disks/root.disk
    set root=(loop0)
    linux /boot/vmlinuz-2.6.35-32-generic root=UUID=27C001CAA8B90A8D loop=/ubuntu/disks/root.disk ro single acpi_backlight=vendor
    initrd /boot/initrd.img-2.6.35-32-generic
    }
    menuentry "Ubuntu, Linux 2.6.35-31-generic" {
    insmod part_msdos
    insmod ntfs
    set root='(hd0,msdos5)'
    search --no-floppy --fs-uuid --set 27C001CAA8B90A8D
    loopback loop0 /ubuntu/disks/root.disk
    set root=(loop0)
    linux /boot/vmlinuz-2.6.35-31-generic root=UUID=27C001CAA8B90A8D loop=/ubuntu/disks/root.disk ro acpi_backlight=vendor rootflags=umask=002,uid=1000,gid=1000 quiet splash
    initrd /boot/initrd.img-2.6.35-31-generic
    }
    menuentry "Ubuntu, Linux 2.6.35-31-generic (recovery mode)" {
    insmod part_msdos
    insmod ntfs
    set root='(hd0,msdos5)'
    search --no-floppy --fs-uuid --set 27C001CAA8B90A8D
    loopback loop0 /ubuntu/disks/root.disk
    set root=(loop0)
    linux /boot/vmlinuz-2.6.35-31-generic root=UUID=27C001CAA8B90A8D loop=/ubuntu/disks/root.disk ro single acpi_backlight=vendor
    initrd /boot/initrd.img-2.6.35-31-generic
    }
    menuentry "Ubuntu, Linux 2.6.35-28-generic" {
    insmod part_msdos
    insmod ntfs
    set root='(hd0,msdos5)'
    search --no-floppy --fs-uuid --set 27C001CAA8B90A8D
    loopback loop0 /ubuntu/disks/root.disk
    set root=(loop0)
    linux /boot/vmlinuz-2.6.35-28-generic root=UUID=27C001CAA8B90A8D loop=/ubuntu/disks/root.disk ro acpi_backlight=vendor rootflags=umask=002,uid=1000,gid=1000 quiet splash
    initrd /boot/initrd.img-2.6.35-28-generic
    }
    menuentry "Ubuntu, Linux 2.6.35-28-generic (recovery mode)" {
    insmod part_msdos
    insmod ntfs
    set root='(hd0,msdos5)'
    search --no-floppy --fs-uuid --set 27C001CAA8B90A8D
    loopback loop0 /ubuntu/disks/root.disk
    set root=(loop0)
    linux /boot/vmlinuz-2.6.35-28-generic root=UUID=27C001CAA8B90A8D loop=/ubuntu/disks/root.disk ro single acpi_backlight=vendor
    initrd /boot/initrd.img-2.6.35-28-generic
    }
    menuentry "Ubuntu, Linux 2.6.35-27-generic" {
    insmod part_msdos
    insmod ntfs
    set root='(hd0,msdos5)'
    search --no-floppy --fs-uuid --set 27C001CAA8B90A8D
    loopback loop0 /ubuntu/disks/root.disk
    set root=(loop0)
    linux /boot/vmlinuz-2.6.35-27-generic root=UUID=27C001CAA8B90A8D loop=/ubuntu/disks/root.disk ro acpi_backlight=vendor rootflags=umask=002,uid=1000,gid=1000 quiet splash
    initrd /boot/initrd.img-2.6.35-27-generic
    }
    menuentry "Ubuntu, Linux 2.6.35-27-generic (recovery mode)" {
    insmod part_msdos
    insmod ntfs
    set root='(hd0,msdos5)'
    search --no-floppy --fs-uuid --set 27C001CAA8B90A8D
    loopback loop0 /ubuntu/disks/root.disk
    set root=(loop0)
    linux /boot/vmlinuz-2.6.35-27-generic root=UUID=27C001CAA8B90A8D loop=/ubuntu/disks/root.disk ro single acpi_backlight=vendor
    initrd /boot/initrd.img-2.6.35-27-generic
    }
    menuentry "Ubuntu, Linux 2.6.32-26-generic" {
    insmod part_msdos
    insmod ntfs
    set root='(hd0,msdos5)'
    search --no-floppy --fs-uuid --set 27C001CAA8B90A8D
    loopback loop0 /ubuntu/disks/root.disk
    set root=(loop0)
    linux /boot/vmlinuz-2.6.32-26-generic root=UUID=27C001CAA8B90A8D loop=/ubuntu/disks/root.disk ro acpi_backlight=vendor rootflags=umask=002,uid=1000,gid=1000 quiet splash
    initrd /boot/initrd.img-2.6.32-26-generic
    }
    menuentry "Ubuntu, Linux 2.6.32-26-generic (recovery mode)" {
    insmod part_msdos
    insmod ntfs
    set root='(hd0,msdos5)'
    search --no-floppy --fs-uuid --set 27C001CAA8B90A8D
    loopback loop0 /ubuntu/disks/root.disk
    set root=(loop0)
    linux /boot/vmlinuz-2.6.32-26-generic root=UUID=27C001CAA8B90A8D loop=/ubuntu/disks/root.disk ro single acpi_backlight=vendor
    initrd /boot/initrd.img-2.6.32-26-generic
    }
    ### END /etc/grub.d/10_lupin ###

    ### BEGIN /etc/grub.d/20_linux_xen ###
    ### END /etc/grub.d/20_linux_xen ###

    ### BEGIN /etc/grub.d/20_memtest86+ ###
    ### END /etc/grub.d/20_memtest86+ ###

    ### BEGIN /etc/grub.d/30_os-prober ###
    menuentry "Windows 7 (loader) (on /dev/sda1)" {
    insmod part_msdos
    insmod ntfs
    set root='(hd0,msdos1)'
    search --no-floppy --fs-uuid --set EC60A75C60A72BF0
    chainloader +1
    }
    menuentry "Windows 7 (loader) (on /dev/sda2)" {
    insmod part_msdos
    insmod ntfs
    set root='(hd0,msdos2)'
    search --no-floppy --fs-uuid --set 3C76B1C676B18166
    chainloader +1
    }
    ### END /etc/grub.d/30_os-prober ###

    ### BEGIN /etc/grub.d/40_custom ###
    # This file provides an easy way to add custom menu entries. Simply type the
    # menu entries you want to add after this comment. Be careful not to change
    # the 'exec tail' line above.
    ### END /etc/grub.d/40_custom ###

    ### BEGIN /etc/grub.d/41_custom ###
    if [ -f $prefix/custom.cfg ]; then
    source $prefix/custom.cfg;
    fi
    ### END /etc/grub.d/41_custom ###

  4. #14
    Join Date
    Nov 2009
    Location
    North Vancouver
    Beans
    Hidden!
    Distro
    Edubuntu 14.04 Trusty Tahr

    Re: Asus UL20A problem with F9 Factory Restore after Ubuntu installation

    So you should see an entry for "Windows 7 (loader) (on /dev/sda1)" in your grub menu. It's there and it's pointing at your recovery partition. If you're not seeing it... maybe something is corrupted. But it should be at the bottom of the grub menu.

    You could try to boot it manually if you can't see it:
    1. Boot
    2. Select Ubuntu
    3. Hit 'C' when you see the grub menu.
    4. Enter the following at the command prompt:
    Code:
    insmod part_msdos
    insmod ntfs
    set root='(hd0,msdos1)'
    chainloader +1
    boot
    That should boot your recovery partition. What happens after that? If your recovery is successful you won't have Wubi anymore. So backup the contents of /host/ubuntu/disks (i.e. root.disk and other virtual disks if you have any).

    Good luck.

  5. #15
    Join Date
    Jan 2012
    Beans
    32

    Re: Asus UL20A problem with F9 Factory Restore after Ubuntu installation

    Hi bcbc,

    When I follow your instructions and get to the command line and run the following:

    insmod part_msdos
    insmod ntfs
    set root='(hd0,msdos1)'

    and then try chainloader +1 it says no such partition.


    if I try this:

    insmod part_msdos
    insmod ntfs
    set root=`(hd0,msdos1)'
    chainloader +1

    I get a > and blinking cursor (before the chainloader +1 command the I would see grub> and a blinking cursor).

    Then when I type boot and hit enter, I just get another > and blinking cursor and nothing happens.

    The difference between the first and second try is that I used ` and ' before/after the (hd0,msdos1) in my second try. I'm not sure which is the right way.

    Thanks!!

  6. #16
    Join Date
    Nov 2009
    Location
    North Vancouver
    Beans
    Hidden!
    Distro
    Edubuntu 14.04 Trusty Tahr

    Re: Asus UL20A problem with F9 Factory Restore after Ubuntu installation

    Try:
    set root=(hd0,1)

    No quotes and that's a zero and a one

  7. #17
    Join Date
    Jan 2012
    Beans
    32

    Re: Asus UL20A problem with F9 Factory Restore after Ubuntu installation

    hi bcbc thanks!

    I tried that and it takes me back to the Windows Boot Menu where I can select Windows 7 Home Premium or Ubuntu. There is no option for factory recovery.

    I logged back in to the grub command prompt and did ls and saw the following:

    loop(0) (hd0) (hd0,2) (hd0,5) (hd0,1)

    not sure if they were in that exact order.

    I tried the commands you suggested and tried each of those except for loop(0). The hd0,5 does nothing and the rest take me back to the Windows Boot Menu.

    Do you think there is any issue with the configuration of my disks? These are the settings in Windows 7 when I run disk management.




    RECOVERY
    14.65 GB NTFS
    Healthy (System, Active, Primary Partition)

    OS (C: )
    58.22 GB NTFS
    Healthy (Boot, Page File, Crash Dump, Pimary Partition)

    DATA (D: )
    160.02 GB NTFS
    Healthy (Logical Drive)

  8. #18
    Join Date
    Nov 2009
    Location
    North Vancouver
    Beans
    Hidden!
    Distro
    Edubuntu 14.04 Trusty Tahr

    Re: Asus UL20A problem with F9 Factory Restore after Ubuntu installation

    I suppose you've true hitting the F8 key as windows boots to get the extended boot menu?

    I'm running out of ideas.

  9. #19
    Join Date
    Jan 2012
    Beans
    32

    Re: Asus UL20A problem with F9 Factory Restore after Ubuntu installation

    hi bcbc thanks,

    Yes I have hit F8 to get the extended windows boot menu to see all the different options (like Safe Mode... etc) but no where in there does it show factory restore.

    I don't have any other ideas other than to just format that recovery partition and add 15GB more to my C: so I have more space on it.
    Last edited by dsurfer21; January 30th, 2012 at 05:41 AM.

  10. #20
    Join Date
    Jan 2012
    Beans
    32

    Re: Asus UL20A problem with F9 Factory Restore after Ubuntu installation

    Hi bcbc,

    any other hints or things i should try before I give up?

    thanks..

Page 2 of 4 FirstFirst 1234 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
  •