Page 3 of 4 FirstFirst 1234 LastLast
Results 21 to 30 of 31

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

  1. #21
    Join Date
    Nov 2009
    Location
    North Vancouver
    Beans
    Hidden!
    Distro
    Edubuntu 12.04 Precise Pangolin

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

    Why don't you post the results of the bootinfoscript. This will give some more info on your partitions and maybe show what bootloader you have (it will most likely be unknown if it's the custom Asus one).

    I wouldn't give up just yet. If you can still boot Windows, is there an Asus program that will allow you to kick of the recovery from within Windows and then reboot to complete?

  2. #22
    Join Date
    Jan 2012
    Beans
    32

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

    Hi bcbc thanks,

    There are no asus tools for restoring other than perhaps using something like AI recovery and making a whole bunch of DVDs. I was hoping to get around that as I don't have a DVD drive in my UL20a 12 inch notebook


    Here are the results of the bootinfoscript:


    Boot Info Script 0.60 from 17 May 2011


    ============================= Boot Info Summary: ===============================

    => Windows is installed in the MBR of /dev/sda.

    sda1: __________________________________________________ ________________________

    File system: ntfs
    Boot sector type: Windows Vista/7
    Boot sector info: No errors found in the Boot Parameter Block.
    Operating System:
    Boot files: /bootmgr /boot/BCD

    sda2: __________________________________________________ ________________________

    File system: ntfs
    Boot sector type: Windows Vista/7
    Boot sector info: No errors found in the Boot Parameter Block.
    Operating System: Windows 7
    Boot files: /bootmgr /Boot/BCD /Windows/System32/winload.exe
    /wubildr /wubildr.mbr

    sda3: __________________________________________________ ________________________

    File system: Extended Partition
    Boot sector type: Unknown
    Boot sector info:

    sda5: __________________________________________________ ________________________

    File system: ntfs
    Boot sector type: -
    Boot sector info: No errors found in the Boot Parameter Block.
    Operating System:
    Boot files: /ubuntu/winboot/wubildr /ubuntu/winboot/wubildr.mbr
    /ubuntu/disks/root.disk /ubuntu/disks/swap.disk

    sda5/Wubi: __________________________________________________ ___________________

    File system: ext4
    Boot sector type: -
    Boot sector info:
    Operating System: Ubuntu 10.10
    Boot files: /boot/grub/grub.cfg /etc/fstab

    ============================ Drive/Partition Info: =============================

    Drive: sda __________________________________________________ ___________________

    Disk /dev/sda: 250.1 GB, 250059350016 bytes
    255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes

    Partition Boot Start Sector End Sector # of Sectors Id System

    /dev/sda1 * 2,048 30,716,279 30,714,232 7 NTFS / exFAT / HPFS
    /dev/sda2 30,716,280 152,810,279 122,094,000 7 NTFS / exFAT / HPFS
    /dev/sda3 152,810,280 488,392,064 335,581,785 f W95 Extended (LBA)
    /dev/sda5 152,810,343 488,392,064 335,581,722 7 NTFS / exFAT / HPFS


    "blkid" output: __________________________________________________ ______________

    Device UUID TYPE LABEL

    /dev/loop0 c4e73368-ce25-498f-9887-aa63ea4b8dc6 ext4
    /dev/sda1 EC60A75C60A72BF0 ntfs RECOVERY
    /dev/sda2 3C76B1C676B18166 ntfs OS
    /dev/sda5 27C001CAA8B90A8D ntfs DATA

    ================================ Mount points: =================================

    Device Mount_Point Type Options

    /dev/loop0 / ext4 (rw,errors=remount-ro,commit=0)
    /dev/sda2 /media/OS fuseblk (rw,nosuid,nodev,allow_other,blksize=4096,default_ permissions)
    /dev/sda5 /host fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,def ault_permissions,allow_other,blksize=4096)


    ======================== sda5/Wubi/boot/grub/grub.cfg: =========================

    --------------------------------------------------------------------------------
    #
    # 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 ###
    --------------------------------------------------------------------------------

    ============================= sda5/Wubi/etc/fstab: =============================

    --------------------------------------------------------------------------------
    # /etc/fstab: static file system information.
    #
    # Use 'blkid -o value -s 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 nodev,noexec,nosuid 0 0
    /host/ubuntu/disks/root.disk / ext4 loop,errors=remount-ro 0 1
    /host/ubuntu/disks/swap.disk none swap loop,sw 0 0
    --------------------------------------------------------------------------------

    ================= sda5/Wubi: Location of files loaded by Grub: =================

    GiB - GB File Fragment(s)

    3.226070404 = 3.463966720 boot/grub/grub.cfg 1
    2.101917267 = 2.256916480 boot/initrd.img-2.6.32-26-generic 2
    3.945312500 = 4.236247040 boot/initrd.img-2.6.35-27-generic 2
    5.203125000 = 5.586812928 boot/initrd.img-2.6.35-28-generic 2
    3.909111023 = 4.197376000 boot/initrd.img-2.6.35-31-generic 2
    5.264095306 = 5.652279296 boot/initrd.img-2.6.35-32-generic 2
    3.038982391 = 3.263082496 boot/vmlinuz-2.6.32-26-generic 1
    3.585330963 = 3.849719808 boot/vmlinuz-2.6.35-27-generic 1
    3.897972107 = 4.185415680 boot/vmlinuz-2.6.35-28-generic 1
    4.937358856 = 5.301448704 boot/vmlinuz-2.6.35-31-generic 1
    4.080932617 = 4.381868032 boot/vmlinuz-2.6.35-32-generic 1
    5.264095306 = 5.652279296 initrd.img 2
    3.909111023 = 4.197376000 initrd.img.old 2
    4.080932617 = 4.381868032 vmlinuz 1
    4.937358856 = 5.301448704 vmlinuz.old 1

    ======================== Unknown MBRs/Boot Sectors/etc: ========================

    Unknown BootLoader on sda3

    00000000 eb 58 90 46 52 44 4f 53 34 2e 31 00 02 10 20 00 |.X.FRDOS4.1... .|
    00000010 02 00 00 00 00 f8 00 00 3f 00 ff 00 28 b3 1b 09 |........?...(...|
    00000020 3b 8b 38 01 08 27 00 00 00 00 00 00 12 05 00 00 |;.8..'..........|
    00000030 01 00 06 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
    00000040 80 00 29 f2 2c 9e 58 4e 4f 20 4e 41 4d 45 20 20 |..).,.XNO NAME |
    00000050 20 20 46 41 54 33 32 20 20 20 fc fa 29 c0 8e d8 | FAT32 ..)...|
    00000060 bd 00 7c b8 e0 1f 8e c0 89 ee 89 ef b9 00 01 f3 |..|.............|
    00000070 a5 ea 7a 7c e0 1f 00 00 60 00 8e d8 8e d0 8d 66 |..z|....`......f|
    00000080 e0 fb 88 56 40 be c1 7d e8 f4 00 66 31 c0 66 89 |...V@..}...f1.f.|
    00000090 46 44 8b 46 0e 66 03 46 1c 66 89 46 48 66 89 46 |FD.F.f.F.f.FHf.F|
    000000a0 4c 66 8b 46 10 66 f7 6e 24 66 01 46 4c b8 00 02 |Lf.F.f.n$f.FL...|
    000000b0 3b 46 0b 74 08 01 c0 ff 06 34 7d eb f3 66 8b 46 |;F.t.....4}..f.F|
    000000c0 2c 66 50 e8 94 00 72 4d c4 5e 76 e8 b7 00 31 ff |,fP...rM.^v...1.|
    000000d0 b9 0b 00 be f1 7d f3 a6 74 15 83 c7 20 83 e7 e0 |.....}..t... ...|
    000000e0 3b 7e 0b 75 eb 4a 75 e0 66 58 e8 34 00 eb d2 26 |;~.u.Ju.fX.4...&|
    000000f0 ff 75 09 26 ff 75 0f 66 58 29 db 66 50 e8 5a 00 |.u.&.u.fX).fP.Z.|
    00000100 72 0d e8 80 00 4a 75 fa 66 58 e8 14 00 eb ec 8a |r....Ju.fX......|
    00000110 5e 40 ff 6e 76 be ee 7d e8 64 00 30 e4 cd 16 cd |^@.nv..}.d.0....|
    00000120 19 06 57 53 89 c7 c1 e7 02 50 8b 46 0b 48 21 c7 |..WS.....P.F.H!.|
    00000130 58 66 c1 e8 07 66 03 46 48 bb 00 20 8e c3 29 db |Xf...f.FH.. ..).|
    00000140 66 3b 46 44 74 07 66 89 46 44 e8 38 00 26 80 65 |f;FDt.f.FD.8.&.e|
    00000150 03 0f 26 66 8b 05 5b 5f 07 c3 66 3d f8 ff ff 0f |..&f..[_..f=....|
    00000160 73 15 66 48 66 48 66 0f b6 56 0d 66 52 66 f7 e2 |s.fHfHf..V.fRf..|
    00000170 66 5a 66 03 46 4c c3 f9 c3 31 db b4 0e cd 10 ac |fZf.FL...1......|
    00000180 3c 00 75 f5 c3 52 56 57 66 50 89 e7 6a 00 6a 00 |<.u..RVWfP..j.j.|
    00000190 66 50 06 53 6a 01 6a 10 89 e6 8a 56 40 b4 42 cd |fP.Sj.j....V@.B.|
    000001a0 13 89 fc 66 58 73 08 50 30 e4 cd 13 58 eb d9 66 |...fXs.P0...X..f|
    000001b0 40 03 5e 0b 73 07 8c c2 80 c6 10 8e c2 5f 00 fe |@.^.s........_..|
    000001c0 ff ff 07 fe ff ff 3f 00 00 00 1a 92 00 14 00 00 |......?.........|
    000001d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
    *
    000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.|
    00000200

  3. #23
    Join Date
    Nov 2009
    Location
    North Vancouver
    Beans
    Hidden!
    Distro
    Edubuntu 12.04 Precise Pangolin

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

    So you have a normal Windows bootloader. So it doesn't look like it's a custom bootloader issue (since you don't recall replacing it).

    And the boot flag is on the recovery partition (/dev/sda1) so booting it from Ubuntu makes no difference.

    But you did mention that you can boot Windows, and there is an option to burn recovery DVD's from within Windows. Have you tried this option?
    Creating the Recovery DVD:
    1. Double-click the AI Recovery Burner icon on the Window desktop.

  4. #24
    Join Date
    Jan 2012
    Beans
    32

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

    Hi bcbc thanks,

    It seems like that is the last resort option using the AI recovery,

    I would need to get a DVD drive and DVDs so I have not tried this yet. I do have AI recovery though.
    Given what showed up on the bootinfoscript, you think this is probably the last option I have?

    If there was some way to restore the OEM bootloader, I could see a solution but that doesn't seem at all possible without using AI recovery and making the DVDs.

  5. #25
    Join Date
    Nov 2009
    Location
    North Vancouver
    Beans
    Hidden!
    Distro
    Edubuntu 12.04 Precise Pangolin

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

    Quote Originally Posted by dsurfer21 View Post
    Hi bcbc thanks,

    It seems like that is the last resort option using the AI recovery,

    I would need to get a DVD drive and DVDs so I have not tried this yet. I do have AI recovery though.
    Given what showed up on the bootinfoscript, you think this is probably the last option I have?

    If there was some way to restore the OEM bootloader, I could see a solution but that doesn't seem at all possible without using AI recovery and making the DVDs.
    Well the problem is that it's not clear whether there is in fact an OEM bootloader - you stated that you hadn't replaced the bootloader and since this cannot happen by installing Wubi or running bcdedit (or by accident) etc. I would have to assume that there is no OEM bootloader.
    In order to install a Window bootloader you need to actually boot a windows repair CD (or copy from a backed up Windows bootloader). Neither of which you could forget.

    So I would say this is more likely some deficiency in the Asus factory restore procedure - but where I cannot say. Perhaps it's the interruption of the windows boot manager... this is all speculation because unless Asus publishes the mechanism it is using all we can do is guess.

    If you want to experiment you could go to "Startup & Recovery" settings, change the 'time to display operating systems' to zero. (Double check to make sure that Windows is set as the default OS to boot in this case, or you won't boot Windows again without a repair CD).
    Also make sure the 'time to display recovery options when needed' is checked
    Then retry the whole F9 thing.

    If that doesn't work, then yes the AI recovery tool seems the most convenient. But the F9 recovery is obviously better than having to pay for an external DVD drive.

    The other thing you could do is phone Asus and see if they have some tips. The recovery partition is there, it's just a question of how to get it to run.

  6. #26
    Join Date
    Jan 2012
    Beans
    32

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

    Hi bcbc thanks!
    I tried your startup and recovery suggestions and f9 and did not get to any factory restore menu.

    I had sent Asus an email and never heard back. I doubt I will get any support since my machine is a year and a 3/4 old.

    Any last suggestions? A while ago I had created a system image onto an external flash drive and also a system restore CD. I'm not sure if that is enough to format a hard drive and reinstall everything without the F9 option or buying a DVD drive.

    I'm wondering if I should just format the recovery partition and use the space for something else given the backup I made? Any advice?

  7. #27
    Join Date
    Nov 2009
    Location
    North Vancouver
    Beans
    Hidden!
    Distro
    Edubuntu 12.04 Precise Pangolin

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

    Quote Originally Posted by dsurfer21 View Post
    Hi bcbc thanks!
    I tried your startup and recovery suggestions and f9 and did not get to any factory restore menu.

    I had sent Asus an email and never heard back. I doubt I will get any support since my machine is a year and a 3/4 old.

    Any last suggestions? A while ago I had created a system image onto an external flash drive and also a system restore CD. I'm not sure if that is enough to format a hard drive and reinstall everything without the F9 option or buying a DVD drive.

    I'm wondering if I should just format the recovery partition and use the space for something else given the backup I made? Any advice?
    My advice is to leave it. You had a problem with Windows so you wanted to restore. Removing the partition isn't going to help that, plus it's your active boot partition - so odds are it will break your boot (which while probably fixable isn't so easy without a suitable rescue disk).

    Also, you can still create the restore DVD's which likely require that partition (just a guess, but I'd say they transfer the boot partition contents to 3 DVDs and add the code to boot from it and restore.

    So, my advice is definitely - don't mess with the recovery partition. Create the recover DVDs when you get the chance, and also create a bootable USB that contains the Windows 7 repair CD.

  8. #28
    Join Date
    May 2009
    Location
    Illinois (United States)
    Beans
    440
    Distro
    Ubuntu 12.10 Quantal Quetzal

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

    This is a strange situation, because I too have an Asus.

    And somehow, the F9 to restore option is still listed when by BIOS posts.

    Except not only do I not have the recovery partition, but I don't even have the original hard drive.

    I assume pressing F9 to recover on my system will undoubtedly fail if I were to try it.

    But its strange that I still have the option, when I don't even have the original hard drive, and you still have the partition intact, but your missing the F9 option.

  9. #29
    Join Date
    Jun 2011
    Beans
    2

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

    I have the same problem with Asus Eeepc 1005HA.

    After a few trial and error to make the Recovery partition work (as before), I realized that pressing F9 key makes the Recovery partition Active, to boot from that partition.

    If boot sector of that partition is changed somehow, it makes the Windows partition active again and boots from there, so it seems that nothing has happened. The same happens when recovery process from partition is intact and you exit the process normally.

    When you format that Windows partition, pressing F9 makes the Recovery patition Active and does not return back if it can not boot from Recovery partition.

    This was my experience!

  10. #30
    Join Date
    Jun 2011
    Beans
    2

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

    ... So far I did a manual recovery using the the recovery image of the OS that is contained as a Norton Ghost file on the Recovery partition.

    I am working to find out how I can revive the recovery process by F9 key.

Page 3 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
  •