[SOLVED] can't boot from ssd after "reset" from recovery usb flash drive

I have a Twist s230u with the original Hitachi 500GB hdd, running Windows 8.1.  I want to replace the Hitachi 500GB hdd in my Twist s230u with a PNY 240GB SSD that i've purchased.
While running Windows from the Hitachi HDD drive I followed the "create a recovery drive" procedure to create a recovery usb.  Then I removed the Hitachi HDD from the s230u and installed the PNY 240 SSD in its place.  I booted the s230u from the recovery flash drive that I made.  I selected the "Reset Your PC" option and then the option to wipe all partition/files.  After the Reset completes, I try booting from the SSD but am unable to do so.  I just go back to the F12 boot menu.
I put the SSD in a drive dock attached to another computer.  Disk Management shows the partitions as follows - 
I've looked at the partitions on the SSD after the Reset - Disk Management console shows a 1000 MB Recovery partition, a 260MB EFI System partition, and a 221GB primary partition with volume label Windows8_OS.  It is not marked as Boot, Page File, or Crash Dump.
Diskpart shows an an additional 128MB Reserved partition between the EFI partition and the primary partition.
I do notice that the 10.6 Lenovo Recovery partition is not present - but I did make sure that I included that partition on the recovery key - though the files on the recovery key only use 8.03 GB for some reason.  Made the key on two different flash media.
Diskpart also shows the following for the SSD:
DISKPART> attributes disk
Current Read-only State : No
Read-only : No
Boot Disk : No
Pagefile Disk : No
Hibernation File Disk : No
Crashdump Disk : No
Clustered Disk : No
(It also looks like this when I run DISKPART from the recovery media with the SSD inside the internal drive bay of the s230u.)
When I did the Reset on the SSD in the s230u, and when I tried to boot from it - I had the Secure Boot disabled, the "Legacy Boot first" option set, etc.  
Can anyone point me in the right direction to be able to boot Windows 8.1 from this SSD in the s230u?  I've been working on this for a couple of days.
(I also tried cloning the HDD to the SDD using Minitool Partition Wizard, Macrium Reflect, Clonezilla, Acronis, etc - the SSD wouldn't boot after those clone operations either, and I thought maybe I'd have better luck with a reinstall from the USB recovery media.
(I also tried installing from a Windows 8 iso I burned to a DVD.  I got a product id mismatch message when I tried to install from that, and I was not allowed to proceed.)

well, I seem to have solved my own problem.  Maybe someone will learn from my mistakes.
I went into System Setup, went to the Startup tab, and changed the boot setting from "Both" to "UEFI Only".  After doing this I booted from my USB recovery drive, and Reset the PC.  After the Reset, I booted the s230u from the ssd, and I booted into a fresh Windows 8 installation.  
It seems that the Reset operation could not work properly while the boot setting was "Both" (UEFI and Legacy) and "Legacy First."
I got a clue when I looked at the contents of the EFI System Partition and there was nothing there except a Temp folder. The EFI System Partition had not been properly written by the Reset operation.  I got some helpful hints on how to see the contents of the EFI System Partition here - http://www.fixedbyvonnie.com/2013/12/how-to-repair-the-efi-bootloader-in-windows-8/#.U-Qz2_ldW7q
I've also buggered up my original HDD now, so that it won't boot to Windows now.  Now to fix that!  

Similar Messages

  • I tried to export photos from iMac to iPad using a USB flash drive.  The photos are on the drive but when I plug it into the iPad, the iPad says the device requires too much power.  Any ideas of what type of USB flash drive I should use?

    I tried to export photos from iMac to iPad using a USB flash drive.  The photos are on the drive but when I plug it into the iPad, the iPad says the device requires too much power.  Any ideas of what type of USB flash drive I should use?

    You can transfer photos outside of iTunes. I do it all the time. THat said, i have a 50/50 success rate with them. I'd avoid sandisk and kingston, their bundled software triggers the 'too much power' warning.
    I've had mixed luck with lexar, some work, some don't.
    I did have good luck with an older 4 gig geek squad one.
    Look for drives without software on them, without bright LED lights and I haven't gotten any larger than 4 gig to work, but that may just be me.
    For a less troublesome way? h onestly, I use a SD card that I've formatted with the DCIM folder. I've never had one of them trigger the 'too much power' warning. Just make sure they're not SDXC. those don't work.

  • I recently purchased my first Mac Book Pro and I copied all my Word documents from my old PC to a usb flash drive. How do I copy them to my new mac?

    I recently purchase my first Mac Book Pro. I copied all my Word documents from my old PC to a USB flash drive with the intention of downloading the content into my new computer. I installed Word for Mac previously. I can not figure out how to download the content of the flash drive into the Mac. Probably very simple but obviously I am a new user. Any suggestions?

    Drag them from the drive to the Documents item in the Finder's sidebar.
    (60701)

  • How do i install and boot mac os 10.4 on a usb flash drive?

    i want to make a bootable flash drive for my powerbook g4 and i have a mac os 10.4 on a install disk.. i want to be able to boot from the flash drive.

    At some point in the past, when the hardware was more recent, some said they
    were able to make it work. To boot a PowerPC G4 iBook (USB2.0 ports) from a
    USB flash drive memory device. The read/write speed of the USB flash had to
    be optimal and the capacity large enough to accommodate the booting and also
    the necessity for Virtual Memory to run on the USB flash drive, as with a HDD.
    Some suggested they made a clone of a working system, boot from USB flash.
    https://www.google.com/?gws_rd=ssl#q=ibook+g4+boot+from+usb
    There still are some bits and pieces of information pointing to discussions or
    other topics of similar concept; some of the older sites aren't online any more
    where claims and 'proof' were given that this worked out OK. Figuring the older
    Apple portables were adapted to use CF or other camera memory cards, for use
    in systems prior to OS X...
    Sounds like a fun diversion, to take ones mind off weather, and other incidentals.

  • How Can I Back Up My iTunes Library To A USB Flash Drive?

    I have around 5GB of files in my iTunes Library and I don't want to have to use multiple blank cds (dvds) to get my files onto my new iMac. On top of that I can't my cd-writer doesn't work. So I bought an 8GB USB Flash Drive and I just want to know how I can get my iTunes Library to back up to my USB Flash Drive.

    Is all your music, as well as your iTunes folder, in My Music? If so, copy your My Music folder to the drive. That will back up all the songs, and the iTunes library files, which happen to be located in iTunes/iTunesMusic.
    In case you are asking how to copy: Close iTunes. Insert the USB drive into the machine and open it like a folder. Then you can use drag and drop to put stuff in it.

  • [Solved] Can't boot into Arch after deleting some partitons

    About 6 months ago I installed Arch on a machine that used to run Ubuntu. Had some trouble at the time getting to boot into Arch but somehow managed. Now eventually decided to delete the old Ubuntu partitons to free up some space using gparted. Arch partition number changed from sda12 to sda6.
    On rebooting after deleting ubuntu partitions with gparted, I got an ubuntu splash screen and a whole lot of ubuntu boot options. Somehow these were all contained in my Arch's /boot/grub/menu.lst. Arch is all on one partition and no separate boot partition (which I had with Ubuntu - maybe I haven't deleted that and this is the problem?). Will need to check that out.
    I can chroot into Arch and did the following -
    grub> find /boot/grub/stage1
    (hd0,5)
    grub> root (hd0,5)
    Filesystem type is ext2fs, partition type 0x83
    grub> setup (hd0)
    Checking if "/boot/grub/stage1" exists... yes
    Checking if "/boot/grub/stage2" exists... yes
    Checking if "/boot/grub/e2fs_stage1_5" exists... yes
    Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 16 sectors are embedded.
    succeeded
    Running "install /boot/grub/stage1 (hd0) (hd0)1+16 p (hd0,5)/boot/grub/stage2 /boot/grub/menu.lst"... succeed
    ed
    Done.
    grub>
    The Arch /boot/grub/menu.lst had a whole lot of ubuntu stuff in it but I edited to the following -
    # 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 3
    ## 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
    ## default grub root device
    ## e.g. groot=(hd0,0)
    # groot=(hd0,3)
    title Arch uuid
    #root (hd0,5)
    uuid d15cf4f9-18ca-4ec5-95bc-db0f6f264736
    kernel /boot/vmlinuz26 root=/dev/sda6 ro vga=775
    intrd /boot/kernel26.img
    title Arch hd
    root (hd0,5)
    kernel /boot/vmlinuz26 root=/dev/sda6
    intrd /boot/kernel26.img
    I have a bootinfo script which gives the following (from the chroot environment) -
    Boot Info Script 0.55 dated February 15th, 2010
    ============================= Boot Info Summary: ==============================
    => Grub 0.97 is installed in the MBR of /dev/sda and looks on the same drive
    in partition #6 for /boot/grub/stage2 and /boot/grub/menu.lst.
    => No boot loader is installed in the MBR of /dev/sdb
    sda1: _________________________________________________________________________
    File system: swap
    Boot sector type: -
    Boot sector info:
    sda2: _________________________________________________________________________
    File system: Extended Partition
    Boot sector type: -
    Boot sector info:
    sda5: _________________________________________________________________________
    File system: ext3
    Boot sector type: -
    Boot sector info:
    Mounting failed:
    mount: /dev/sda5 already mounted or sda5 busy
    sda6: _________________________________________________________________________
    File system: ext3
    Boot sector type: -
    Boot sector info:
    Mounting failed:
    mount: /dev/sda5 already mounted or sda5 busy
    mount: /dev/sda6 already mounted or sda6 busy
    sda7: _________________________________________________________________________
    File system: ext3
    Boot sector type: -
    Boot sector info:
    Operating System:
    Boot files/dirs:
    sda3: _________________________________________________________________________
    File system: ext3
    Boot sector type: -
    Boot sector info:
    Operating System: Ubuntu 10.04.1 LTS
    Boot files/dirs: /etc/fstab
    sda4: _________________________________________________________________________
    File system: ext3
    Boot sector type: -
    Boot sector info:
    Operating System:
    Boot files/dirs: /grub/menu.lst /grub/grub.cfg /grub/core.img
    sdb1: _________________________________________________________________________
    File system: xfs
    Boot sector type: -
    Boot sector info:
    Operating System:
    Boot files/dirs:
    =========================== Drive/Partition Info: =============================
    Drive: sda ___________________ _____________________________________________________
    Disk /dev/sda: 750.2 GB, 750155292160 bytes
    255 heads, 63 sectors/track, 91201 cylinders, total 1465147055 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    Partition Boot Start End Size Id System
    /dev/sda1 417,690 6,554,519 6,136,830 82 Linux swap / Solaris
    /dev/sda2 25,414,954 1,465,144,064 1,439,729,111 5 Extended
    /dev/sda5 25,414,956 1,360,287,809 1,334,872,854 83 Linux
    /dev/sda6 1,360,287,873 1,423,198,349 62,910,477 83 Linux
    /dev/sda7 1,423,198,413 1,465,144,064 41,945,652 83 Linux
    /dev/sda3 6,554,520 25,414,829 18,860,310 83 Linux
    /dev/sda4 * 63 417,689 417,627 83 Linux
    Drive: sdb ___________________ _____________________________________________________
    Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
    255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    Partition Boot Start End Size Id System
    /dev/sdb1 2,048 1,953,523,711 1,953,521,664 83 Linux
    blkid -c /dev/null: ____________________________________________________________
    Device UUID TYPE LABEL
    /dev/loop0 squashfs
    /dev/sda1 2a95d85a-45fe-4584-88dd-0ee20e651ec5 swap
    /dev/sda2: PTTYPE="dos" PART_ENTRY_SCHEME="dos" PART_ENTRY_TYPE="0x5" PART_ENTRY_NUMBER="2"
    /dev/sda3 32495e1a-227c-4d23-9f63-b1319def0dd9 ext3
    /dev/sda4 d6dc69b0-967d-4886-b62d-8c0d6be06b41 ext3
    /dev/sda5 37971286-b8d3-4a1b-9f94-4008288fed6d ext3 data
    /dev/sda6 d15cf4f9-18ca-4ec5-95bc-db0f6f264736 ext3 30GB-02
    /dev/sda7 eb736131-b558-4404-9b83-7f1e6d9e76ae ext3 var
    /dev/sda: PTTYPE="dos"
    /dev/sdb1 0e83045d-a0bd-4d36-b61d-bdb905130dc2 xfs 1TB-04
    /dev/sdb: PTTYPE="dos"
    ============================ "mount | grep ^/dev output: ===========================
    Device Mount_Point Type Options
    /dev/sda12 / ext3 (rw,commit=0)
    =============================== sda3/etc/fstab: ===============================
    # /etc/fstab: static file system information.
    # <file system> <mount point> <type> <options> <dump> <pass>
    proc /proc proc defaults 0 0
    # /dev/sda1 = swap
    /dev/sda1 none swap sw 0 0
    # /dev/sda3 = root
    #UUID=32495e1a-227c-4d23-9f63-b1319def0dd9
    /dev/sda3 / ext3 relatime,errors=remount-ro 0 1
    # /dev/sda4 = boot
    # UUID=d6dc69b0-967d-4886-b62d-8c0d6be06b41
    /dev/sda4 /boot ext3 relatime 0 2
    # /dev/sda5 = home
    # UUID=670eee83-0a3e-429c-863f-b9ecced9f97e
    /dev/sda5 /home ext3 relatime 0 2
    #/dev/sda6
    #UUID=37971286-b8d3-4a1b-9f94-4008288fed6d
    /dev/sda6 /home/ben/Data ext3 defaults,relatime 0 0
    # /dev/sda7
    # UUID=fdb14ca4-d71d-489f-a00e-6e608770674c
    /dev/sda7 /var ext3 relatime 0 2
    # /dev/sda8
    /dev/sda8 /opt ext3 relatime 0 2
    # /dev/sda10 - Arch
    /dev/sda10 /mnt/arch ext3 relatime 0 2
    # Not sure what this is doing here
    # Have commented it out - May be the reason why xbmc and mythtv were crashing on dvd insert and play
    # /dev/hda /media/cdrom0 udf,iso9660 user,noauto,exec,utf8 0 0
    # /dev/sde1
    # uuid appears to be 644406B3570C1846 -> ../../sde1
    #/dev/sde1 /home/ben/Data/TVRecordings-1TB01 xfs defaults,relatime 0 0
    #1TB-01
    UUID=76f3823a-81dc-45c9-a0b7-2bc6c3beb2f8 /media/1TB-01 xfs noatime,nodiratime,allocsize=512m 0 0 #remove
    d defaults, relatime
    # 1TB-02
    UUID=59cbf7a1-7008-40d0-96ed-c6f231823d4f /media/1TB-02 xfs noatime,nodiratime,allocsize=512m 0 0 #remove
    d defaults, relatime
    # 1TB-03
    UUID=0e936800-3c53-4b87-abc8-19be0ffca7f9 /media/1TB-03 xfs noatime,nodiratime,allocsize=512m 0 0 #remove
    d defaults, relatime
    # 750GB-02 ext3 Partition
    # UUID giving problems, trying with dev
    # UUID=c23b9c9a-66fc-4256-9211-73156c1ac64a /media/750GB-02_ext3 ext3 defaults,relatime 0 0
    /dev/sde2 /media/750GB-02_ext3 ext3 defaults,relatime 0 0
    ============================= sda4/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 3
    ## 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=32495e1a-227c-4d23-9f63-b1319def0dd9 ro
    ## default grub root device
    ## e.g. groot=(hd0,0)
    # groot=(hd0,3)
    ## 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 10.04.1 LTS, kernel 2.6.32-26-generic
    root (hd0,3)
    kernel /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-26-generic
    quiet
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-26-generic (recovery mode)
    root (hd0,3)
    kernel /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    initrd /initrd.img-2.6.32-26-generic
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-24-generic
    root (hd0,3)
    kernel /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-24-generic
    quiet
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-24-generic (recovery mode)
    root (hd0,3)
    kernel /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    initrd /initrd.img-2.6.32-24-generic
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-23-generic
    root (hd0,3)
    kernel /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-23-generic
    quiet
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-23-generic (recovery mode)
    root (hd0,3)
    kernel /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    initrd /initrd.img-2.6.32-23-generic
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-22-generic
    root (hd0,3)
    kernel /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-22-generic
    quiet
    title Ubuntu 10.04.1 LTS, kernel 2.6.32-22-generic (recovery mode)
    root (hd0,3)
    kernel /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    initrd /initrd.img-2.6.32-22-generic
    title Ubuntu 10.04.1 LTS, memtest86+
    root (hd0,3)
    kernel /memtest86+.bin
    quiet
    ### END DEBIAN AUTOMAGIC KERNELS LIST
    ============================= sda4/grub/grub.cfg: =============================
    # DO NOT EDIT THIS FILE
    # It is automatically generated by /usr/sbin/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
    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
    insmod ext2
    set root='(hd0,3)'
    search --no-floppy --fs-uuid --set 32495e1a-227c-4d23-9f63-b1319def0dd9
    if loadfont /usr/share/grub/unicode.pf2 ; then
    set gfxmode=640x480
    insmod gfxterm
    insmod vbe
    if terminal_output gfxterm ; then true ; else
    # For backward compatibility with versions of terminal.mod that don't
    # understand terminal_output
    terminal gfxterm
    fi
    fi
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    set locale_dir=($root)/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 ###
    menuentry 'Ubuntu, with Linux 2.6.32-26-generic' --class ubuntu --class gnu-linux --class gnu --class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-26-generic
    menuentry 'Ubuntu, with Linux 2.6.32-26-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
    -class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    echo 'Loading Linux 2.6.32-26-generic ...'
    linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    echo 'Loading initial ramdisk ...'
    initrd /initrd.img-2.6.32-26-generic
    menuentry 'Ubuntu, with Linux 2.6.32-24-generic' --class ubuntu --class gnu-linux --class gnu --class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    linux /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-24-generic
    menuentry 'Ubuntu, with Linux 2.6.32-24-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
    -class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    echo 'Loading Linux 2.6.32-24-generic ...'
    linux /vmlinuz-2.6.32-24-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    echo 'Loading initial ramdisk ...'
    initrd /initrd.img-2.6.32-24-generic
    menuentry 'Ubuntu, with Linux 2.6.32-23-generic' --class ubuntu --class gnu-linux --class gnu --class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    linux /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-23-generic
    menuentry 'Ubuntu, with Linux 2.6.32-23-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
    -class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    echo 'Loading Linux 2.6.32-23-generic ...'
    linux /vmlinuz-2.6.32-23-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    echo 'Loading initial ramdisk ...'
    initrd /initrd.img-2.6.32-23-generic
    menuentry 'Ubuntu, with Linux 2.6.32-22-generic' --class ubuntu --class gnu-linux --class gnu --class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    linux /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash
    initrd /initrd.img-2.6.32-22-generic
    menuentry 'Ubuntu, with Linux 2.6.32-22-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu -
    -class os {
    recordfail
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    echo 'Loading Linux 2.6.32-22-generic ...'
    linux /vmlinuz-2.6.32-22-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro single
    echo 'Loading initial ramdisk ...'
    initrd /initrd.img-2.6.32-22-generic
    ### END /etc/grub.d/10_linux ###
    ### BEGIN /etc/grub.d/20_memtest86+ ###
    menuentry "Memory test (memtest86+)" {
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    linux16 /memtest86+.bin
    menuentry "Memory test (memtest86+, serial console 115200)" {
    insmod ext2
    set root='(hd0,4)'
    search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41
    linux16 /memtest86+.bin console=ttyS0,115200n8
    ### END /etc/grub.d/20_memtest86+ ###
    ### BEGIN /etc/grub.d/30_os-prober ###
    menuentry "Arch Linux (on /dev/sda10)" {
    insmod ext2
    set root='(hd0,10)'
    search --no-floppy --fs-uuid --set 26851879-58d1-4d65-90b4-e0845fe1176c
    linux /boot/vmlinuz26 root=/dev/sda10 ro
    initrd /boot/kernel26.img
    menuentry "Arch Linux Fallback (on /dev/sda10)" {
    insmod ext2
    set root='(hd0,10)'
    search --no-floppy --fs-uuid --set 26851879-58d1-4d65-90b4-e0845fe1176c
    linux /boot/vmlinuz26 root=/dev/sda10 ro
    initrd /boot/kernel26-fallback.img
    #### 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.
    # From Arch grub menu.lst
    # (0) Arch Linux
    #title Arch Linux [/boot/vmlinuz26]
    #root (hd0,0)
    #kernel /vmlinuz26 root=/dev/sda3 ro
    #initrd /kernel26.img
    #Note: With a separate boot partition, omit /boot from the path, (i.e. type set prefix=(hdX,Y)/grub and insmod
    (hdX,Y)/grub/linux.mod).
    #This introduces the "linux" and "initrd" commands, which should be familiar (see #Configuration).
    #An example, booting Arch Linux:
    #set root=(hd0,5)
    #linux /boot/vmlinuz26 root=/dev/sda5
    #initrd /boot/kernel26.img
    #boot
    ###menuentry "Arch1" {
    ###insmod ext2
    ###set root='(hd0,10)'
    #search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 = FOR UBUNTU THIS IS THE BOOT
    PARTITION
    #linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash = FOR
    UBUNTU THIS IS THE ROOT PARTITION
    #initrd /initrd.img-2.6.32-26-generic
    ###search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 # UBUNTU'S BOOT PARTITION UU
    ID
    ###linux /boot/vmlinuz-26 root=635d7d02-3f5b-4af6-9c74-16b2af8cc7fd ro quiet splash # ARCH'S ROOT UUID
    ###initrd /boot/kernel26.img
    # /dev/sda10 uuid = 635d7d02-3f5b-4af6-9c74-16b2af8cc7fd - obtain using ls -l /dev/disk/by-uuid/
    ###menuentry "Arch2" {
    ###insmod ext2
    ###set root='(hd0,4)' #= TRYING UBUNTU'S BOOT
    #search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 = FOR UBUNTU THIS IS THE BOOT
    PARTITION
    #linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash = FOR
    UBUNTU THIS IS THE ROOT PARTITION
    #initrd /initrd.img-2.6.32-26-generic
    #search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 # UBUNTU'S BOOT PARTITION UUID
    ###linux /boot/vmlinuz-26 root=/dev/sda10 ro quiet splash # TRYING ARCH'S ROOT DEVICE FORMAT
    ###initrd /boot/kernel26.img
    # /dev/sda10 uuid = 635d7d02-3f5b-4af6-9c74-16b2af8cc7fd - obtain using ls -l /dev/disk/by-uuid/
    ###menuentry "Arch3" {
    ###insmod ext2
    ###set root='(hd0,10)' #= TRYING UBUNTU'S BOOT IN HD FORMAT
    #search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 = FOR UBUNTU THIS IS THE BOOT
    PARTITION
    #linux /vmlinuz-2.6.32-26-generic root=UUID=32495e1a-227c-4d23-9f63-b1319def0dd9 ro quiet splash = FOR
    UBUNTU THIS IS THE ROOT PARTITION
    #initrd /initrd.img-2.6.32-26-generic
    #search --no-floppy --fs-uuid --set d6dc69b0-967d-4886-b62d-8c0d6be06b41 # UBUNTU'S BOOT PARTITION UUID
    ###linux /boot/vmlinuz-26 root=/dev/sda10 ro quiet splash # TRYING ARCH'S ROOT DEVICE FORMAT
    ###initrd /boot/kernel26.img
    # /dev/sda10 uuid = 635d7d02-3f5b-4af6-9c74-16b2af8cc7fd - obtain using ls -l /dev/disk/by-uuid/
    ### END /etc/grub.d/40_custom ###
    =================== sda4: Location of files loaded by Grub: ===================
    .0GB: grub/core.img
    .0GB: grub/grub.cfg
    .0GB: grub/menu.lst
    .0GB: grub/stage2
    .0GB: initrd.img-2.6.32-22-generic
    .0GB: initrd.img-2.6.32-23-generic
    .1GB: initrd.img-2.6.32-24-generic
    .1GB: initrd.img-2.6.32-26-generic
    .0GB: vmlinuz26
    .0GB: vmlinuz-2.6.32-22-generic
    .0GB: vmlinuz-2.6.32-23-generic
    .1GB: vmlinuz-2.6.32-24-generic
    .0GB: vmlinuz-2.6.32-26-generic
    =============================== StdErr Messages: ===============================
    No volume groups found
    mdadm: No arrays found in config file or automatically
    [/quote]
    Output of fdisk -l from chroot is -
    [quote]Disk /dev/sda: 750.2 GB, 750155292160 bytes
    255 heads, 63 sectors/track, 91201 cylinders, total 1465147055 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0x0000b084
    Device Boot Start End Blocks Id System
    /dev/sda1 417690 6554519 3068415 82 Linux swap / Solaris
    /dev/sda2 25414954 1465144064 719864555+ 5 Extended
    /dev/sda3 6554520 25414829 9430155 83 Linux
    /dev/sda4 * 63 417689 208813+ 83 Linux
    /dev/sda5 25414956 1360287809 667436427 83 Linux
    /dev/sda6 1360287873 1423198349 31455238+ 83 Linux
    /dev/sda7 1423198413 1465144064 20972826 83 Linux
    Partition table entries are not in disk order
    Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
    255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 4096 bytes
    I/O size (minimum/optimal): 4096 bytes / 4096 bytes
    Disk identifier: 0x00025bd3
    Device Boot Start End Blocks Id System
    /dev/sdb1 2048 1953523711 976760832 83 Linux
    I need to post this now and come back from a different machine to note the error messages I am now getting on boot. ...
    Note that when I boot and press esc to get the menu I get the menu.lst I created (in the second quote) above in /dev/sda6, ie the one with the Arch hd and uuid entries - so grub is looking there and finding that menu.lst, but something goes wrong after that.
    OK. Have now booted the machine and after pressing esc and selecting the uuid entry (the same thing happens with the hd entry) I get a whole lot of stuff, but what seems relevant is (typing it out) -
    List of all partitions:
    No filesystem could mount root, tried:
    Kernel panic - not syncing: VS: Unable to mount root fs on unknown-block(0,0)
    Pid: 1, comm: swapper Not tainted 2.6.39-Arch #1
    If anyone can help I'd really appreciate it. This is my MythTV machine so the WAF is about to take a big dive!
    If I could just install grub to the MBR as if this was a new installation of Arch that would be great.
    I am really lost as to what is going on, which I'm sure is evident.
    Thanks a lot
    belbo
    Last edited by belbo (2011-08-12 13:31:23)

    Hi. Unfortunately that didn't help.
    So next, based on this post https://wiki.archlinux.org/index.php/Ke … el_version I chrooted into Arch and (a) rolled back and (b) reinstalled my kernel but that didn't help either. I suspected it wouldn't because the kernel was working fine before I deleted the partitions in question.
    [2011-08-08 23:32] ==> Image generation successful
    [2011-08-08 23:32] upgraded kernel26 (2.6.39.3-1 -> 2.6.39.3-1)
    I then did a pacman -Suy and the linux package has now replaced kernel26. ( See this wiki entry http://www.archlinux.org/news/changes-t … filenames/). I didn't change anything in menu.lst owing to this and it seems there is no need to. Unfortunately this hasn't helped either - still getting the kernel panic. 
    Pacman.log relating to the new kernel package below -
    [2011-08-09 00:22] Running 'pacman -Suy'
    [2011-08-09 00:22] synchronizing package lists
    [2011-08-09 00:23] starting full system upgrade
    [2011-08-09 00:23] Running 'pacman -Suy'
    [2011-08-09 00:23] synchronizing package lists
    [2011-08-09 00:23] starting full system upgrade
    [2011-08-09 00:26] removed python-mygpoclient (1.5-1)
    [2011-08-09 00:26] removed kernel26 (2.6.39.3-1)
    [2011-08-09 00:26] warning: /boot/grub/menu.lst installed as /boot/grub/menu.lst.pacnew
    [2011-08-09 00:26] upgraded grub (0.97-17 -> 0.97-19)
    [2011-08-09 00:26] upgraded icu (4.8-1 -> 4.8.1-1)
    [2011-08-09 00:26] upgraded linux-firmware (20110512-2 -> 20110727-1)
    [2011-08-09 00:26] >>> Updating module dependencies. Please wait ...
    [2011-08-09 00:26] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
    [2011-08-09 00:26] ==> Building image from preset: 'default'
    [2011-08-09 00:26] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
    [2011-08-09 00:26] ==> Starting build: 3.0-ARCH
    [2011-08-09 00:26] -> Parsing hook: [base]
    [2011-08-09 00:26] -> Parsing hook: [udev]
    [2011-08-09 00:26] -> Parsing hook: [autodetect]
    [2011-08-09 00:26] -> Parsing hook: [pata]
    [2011-08-09 00:26] -> Parsing hook: [scsi]
    [2011-08-09 00:26] -> Parsing hook: [sata]
    [2011-08-09 00:26] -> Parsing hook: [filesystems]
    [2011-08-09 00:26] -> Parsing hook: [usbinput]
    [2011-08-09 00:26] ==> Generating module dependencies
    [2011-08-09 00:26] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
    [2011-08-09 00:26] 7079 blocks
    [2011-08-09 00:26] ==> Image generation successful
    [2011-08-09 00:26] ==> Building image from preset: 'fallback'
    [2011-08-09 00:26] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
    [2011-08-09 00:26] ==> Starting build: 3.0-ARCH
    [2011-08-09 00:26] -> Parsing hook: [base]
    [2011-08-09 00:26] -> Parsing hook: [udev]
    [2011-08-09 00:26] -> Parsing hook: [pata]
    [2011-08-09 00:26] -> Parsing hook: [scsi]
    [2011-08-09 00:26] -> Parsing hook: [sata]
    [2011-08-09 00:26] -> Parsing hook: [filesystems]
    [2011-08-09 00:26] -> Parsing hook: [usbinput]
    [2011-08-09 00:26] ==> Generating module dependencies
    [2011-08-09 00:26] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
    [2011-08-09 00:26] 23360 blocks
    [2011-08-09 00:26] ==> Image generation successful
    [2011-08-09 00:26] installed linux (3.0.1-1)
    I don't think I've mentioned that my old menu.lst seems to have disappeared and so must have been on one of the partitions that were deleted. I did have 2 Arch installations when I was setting things up months ago and that menu.lst may have been on the other partition but pointing to this partiton's kernel for booting. Presumably that's possible since this partiton is definitely the one I have been using for the last several months (confirmed by log and other files updated in the last few days etc). Even so, I suppose that probably wouldn't be relevant to this issue, since grub is finding the menu.lst on this partition when it boots so it is looking in the intended place now.
    It seems I'm at a bit of a dead end. It seems these kernel panics are usually because there is something wrong with the kernel - which there wasn't with mine (and presumably the kernel in the new linux package is fine) or there is a typo in menu.lst (I can't see one and nobody has pointed one out yet) or menu.lst is pointing to the wrong partition (mine is pointing to the same partition and /boot directory that is found by grub - which is where my boot image is located - so it seems to be correct). I have nevertheless tried editing the menu.lst entry when booting to boot from different partitions but so far that hasn't worked either.
    If anybody has other ideas I'd really appreciate it.
    If not, some suggestions on re-installing would also be appreciated. I have a recent tar archive of the partition, but presumably reinstalling that wouldn't be of much use since it would just put back what is currently there. I guess that I need to format the partition, create a separate boot partition, do a fresh install of Arch into the formatted partition (and with boot in the new boot partition). And then restore my tar backup (excluding the boot directory) into the formatted partition?
    Any assistance greatly appreciated.
    Thanks
    belbo
    Last edited by belbo (2011-08-08 23:17:49)

  • [SOLVED]Can't boot into OS after installation

    Hello all,
    I've ran into a few problems already all of which I could solve with somme googling etc.
    Until now the installation of arch Linux went pretty smoothly until I rebooted to get into the OS via grub (version 2), once I select Arch Linux in the menu the os starts booting but it stops at this: "a start job is running for dhcpcd on enp7s0 (x s/1m31s)" this always fails. After that 3 extra lines appear starting with a green OK all saying reached target ..........
    This is where no more progress is made, the only keys that generate a response are Ctrl+alt+Del then the system reboots.
    Here is a clear image of the status of the machine
    https://i.imgur.com/queQkEOh.jpg
    EDIT: If you guys need any extra information please ask, but I can't access the systems config files or anything due to this problem so suggestions on how to pull that data are welcome
    -- mod edit: converted img tags to url - Trilby --
    Last edited by Covati (2014-10-06 13:04:05)

    Trilby wrote:
    Welcome to the forums - please see the forum guidelines on how to post including image size restrictions.
    As for the issue - can you Alt-F2 or Alt-F3 to get to another tty?
    It worked, wow I feel dumb now.
    Anyways thank you for helping me out, I will look into the guidelines.
    Can mark this thread as solved!

  • How can I get my Windows computer to recognize my USB flash drive?

    I have a jump drive, & every time I plug it in, the computer won't  read it. I've tried different USB ports, & even another computer. It  just won't show up, help please! Any advice would be greatly  appreciated.

    Suggest you post your question on a Windows forum, as it reallly has nothing to do with anything Apple related.
    http://forums.windowsforum.org/

  • HP Mini 110-3520ca constantly restarts when trying to restore from usb flash drive

    Hi,
    I have a HP Mini 110-3520ca that I upgraded to Windows 8, but was having issues with freeze ups and shut downs so I decided to go back to Windows 7 Starter.    When I tried to restore to factory default the files were corrupted and I couldn't restore from the recovery hard drive or my external back up files.  I ordered the recovery  USB flash drive from HP and tried to restore from it.  It completes the Recovery Preparation and the Software Installation finishes, Windows starts to load, but Ithen it goes back to welcome to Recovery Manager.  When I try to start Windows without the flash drive I get an error log that is below.  Can someone tell me how to fix this or what needs to be done to get my Windows working again, any help would be greatly appreciated.
    Carol.
    Error Log: 
    Component: TDC Preinstall Diagnostic Tools for Windows 7 - TDC
    Timing: Factory Update
    This is not a Regional SKU
    This is not an RCTO P2PP SKU
    Error: Different LOC# detected:
    Error: SKU number LOC# = 00
    Error: REGSKU/OptionDashCode.ini value for ABC = 12
    Error: SKU number incorrect for this LOC#=ABC.
    Next Step: Please dash sku number with xxxxxx-12x
    Next Step: Or use EEPROM and change LOC# in either SKU Number or CTO Localization Code
    [17:16:38.37] ------------------------------------------------------------------------------------------
    ***CTO Error condition has been dtected in [Factory Update] phase !! ***
    [17:16:38.38] Suggest to create PIN-log and send to TWN PDC NB-PreinPM for further analysis ...
    [17:16:38.38] ------------------------------------------------------------------------------------------
    [17:13:54.75] Start BBOffline.cmd...
    UPDrv=[C:]
    [17:13:54.77] Set UIA Error Code to 951
    [17:13:55.39] WinPE is 32bit.
    [17:13:55.39] Starts [FixUps].
    [17:13:55.41] ---------------------------------------------------------------------
    [17:13:55.41] FixUps.cmd...
    [17:13:55.41] create overall progress info...
    [17:14:15.89] FixUps.cmd completed...
    [17:14:15.89] ---------------------------------------------------------------------
    [17:14:15.91] Starts [Tweaks for SSRD].
    [17:14:15.92] ---------------------------------------------------------------------
    [17:14:15.92] SSRD Tweaks to change user default locale...
    [17:14:15.92] Copy C:\System.sav\Util\TDC\MCPP\FBIRES\FBIUSRES.DLL.
    [17:14:16.09] Run "Dism.exe /image:C:\ /Set-SKUIntlDefaults:en-US -image:C:".
    [17:14:23.50] ---------------------------------------------------------------------
    [17:14:23.50] Launch PININST.exe for Offline ...
    [17:14:33.78] Starts [Sleep 10 sec].
    [17:14:43.86] Starts [Create RStoneFUpdate.INI].
    [17:15:20.91] Starts [create 1GB Pagefile for offline].
    Volume in drive C has no label.
    Volume Serial Number is 868D-C760
    Directory of C:\system.sav\bbv
    10/27/2014 05:15 PM 1,073,741,824 pagefile.sys
    1 File(s) 1,073,741,824 bytes
    0 Dir(s) 38,502,694,912 bytes free
    [17:15:21.04] move boot.wim from FactoryUpdate to 2ndCap.
    [17:15:21.10] Brand detection.
    [17:15:21.80] ---------------------------------------------------------------------
    [17:16:10.26] Start SysID Check...
    [17:16:13.30] Start Option Code Checks...
    SKU_DEF_COUNTRY=[39]
    SKU_DEF_SYS_LOC=[fr-CA]
    Reset country in administrator...
    Reset country in Default user...
    Reset System localed
    Deployment Image Servicing and Management tool
    Version: 6.1.7600.16385
    Image Version: 6.1.7600.16385
    Reporting offline international settings.
    Default system UI language : en-US
    System locale : fr-CA
    Default time zone : Pacific Standard Time
    User locale for default user : en-US
    Location : Canada (GEOID = 39)
    Active keyboard(s) : 0409:00000409
    Keyboard layered driver : PC/AT Enhanced Keyboard (101/102-Key)
    Installed language(s): en-US
    Type : Fully localized language.
    The operation completed successfully.
    Updated System Locale info..
    [17:16:27.37] Start PIN Tweaks...
    [17:16:28.38] ---------------------------------------------------------------------
    [17:16:28.40] PIN Tweaks to hide All for BurnBoot BBV and BBV2 on restored image...
    [17:16:28.40] ----------------------------------------
    [17:16:28.40] Tweaks for OOBE's Unattend.xml
    [17:16:28.40] to pick up the proper file...
    [17:16:28.41] ----------------------------------------
    [17:16:28.41] rename unattend.org to unattend.or_
    [17:16:28.44] ----------------------------------------
    [17:16:28.44] without Light Sensor..
    [17:16:28.48] ----------------------------------------
    [17:16:28.49] This is Restored image by SSRD [SSRD.flg]...
    [17:16:28.51] ---------------------------------------------------------------------
    [17:16:29.40] Start MIR Tweaks...
    [17:16:30.43] ---------------------------------------------------------------------
    [17:16:30.43] [MIR Tweaks] ...
    [17:16:30.43] ---------------------------------------------------------------------
    [17:16:31.44] Start Factory Update(s)...
    [17:16:33.45] Start QFE Offline installation...
    [17:16:38.13] PININST_OFF: PASSED...
    [17:16:38.21] Type C:\System.sav\Logs\BBFindEr.log...
    [17:16:38.23] Type C:\System.sav\Logs\BBFindE0.log...
    ---------- C:\SYSTEM.SAV\LOGS\PININST_OFF.LOG
    Result=PASSED
    [17:16:38.24] There was no QFE installation...
    [17:16:38.24] Check FUList.log if there is duplicate Desc...
    Couldn't access C:\System.sav\logs\FUList.log...
    [17:16:38.35] No Duplicated Desc is found... PASSED.
    [17:16:38.37] There was no Factory Update...

    Hi @Savvy58
    I did some further looking into that Error Log you posted. Basically, it means that is looking for a certain location that doesn't seem to be there. This could be a problem with the USB Recovery drive that you have. I would recommend that you contact HP. You can reach HP Total Care at 1-800-474-6836 in North America or start here if you live outside of North America.
    Please click “Accept as Solution ” if you feel my post solved your issue.
    Click the “Kudos Thumbs Up" on the right to say “Thanks” for helping!
    Thank you,
    BHK6
    I work on behalf of HP

  • [Solved] Can't boot arch after merge linux partition

    Before this i have issue with my partition table, but i can fix it with testdisk.
    After that, i merge all my linux partition into one. I mean like this
    Before i merge my linux partition:
    / >> /dev/sda3
    /var >> /dev/sda4
    swapfile >> /dev/sda6
    /home >> /dev/sda7
    My new partition
    / >> /dev/sda3
    swapfile >> /dev/sda6
    i can't boot my arch after i backup and moved my home and var directory to /dev/sda3 with livecd.
    How to fix this issue?
    Last edited by nizar (2009-03-28 04:18:29)

    Solved by myself! LOL
    I edit and remove /dev/sda4 and /dev/sda7 in my /etc/fstab file with livecd.
    Now, arch boot without /dev/sda4 and /dev/sda7

  • Can't boot os x after bootcamp

    Hello.
    The problem:
    Yesterday I installed windows 7 on my early 2009 (mavericks) mac pro via boot camp.
    I have three HD in my mac. One for os x, one for documents, and one for the windows. Before I start bootcamp I formatted my HD into NTFS for Win.
    I run the bootcamp and everything went well, until the standard windows partition screen show up. I select the "bootcamp" HD, but i only can continue the installing if I format the hard drive.
    The Win7 run well, but now I can't boot into os x.
    When I hold down "options", only the windows appear as a selectable option.
    I installed bootcamp on windows manually (4.0.4033 according to Boot Camp: System requirements for Microsoft Windows operating systems)
    when I try to restart to osx the bootcamp say "there is no bootable volume".
    i only see the "bootcamp" HD, and I can't treat the other two.
    What I tried
    Resetting NVRAM and PRAM
    Holding down various key combinations (Options, Command + R, Options + R)
    When I take out the "Machintos hd" a flashing folder pic appears.
    I don't have the installation disk for os x, and I don't want to uninstall the os x..
    There is any solution for my problem?

    1. How many physical drives do you have in the MacPro?
    2. Was Windows and OS X installed on the same physical drive?
    3. In the case of the Tower MacPro with more than one drive, all drives that are not intended for Windows use must be physically removed from drive bays, before Windows is installed.
    4. If you cannot see OS X, use an external disk (Firewire or USB with 16GB or more) and install a fresh copy of OS X and both you MacPro and the the disk with Windows can be corrected, if possible.
    5. OSX re-installation leaves you files intact, unless you tell the OS X Installer to erase the designated drive.
    6. Step 4 can also uses a USB flash drive, if necessary.
    The error message is because a drive which was present when Windows was installed (it is stored in the BCD for W7/W8 or boot manager/loader)is no longer available. It is complaining about it.
    If you put this drive back, can you boot into Windows successfully? If yes, can you post a screen shot of Control Panel -> System -> Administrative Tools -> Computer Management -> Disk Management.

  • Can't boot from a USB flash drive

    I believe this ability was lost after updating to BIOS 80.52 following HP's "strong recommendation".No warning was given that this update would remove this ability and see that "Due to security changes, after this BIOS update is installed, previous versions cannot be reinstalled."
    I have tried disabling Secure Boot and enabling Legacy Boot, and tried re-applying BIOS defaults.
    Is there a particular combination of BIOS settings that I haven't been able to find?As the warranty on my computer expired in July 2014, the HP Customer Support Contact page won't even accept my request for assistance - despite the "strongly recommended" BIOS update being made available *after* this date. I require the ability to boot from USB flash drives ... how can this now be achieved?
    Is there an HP BIOS for a more recent HP product with the JasmineR motherboard (or an AMI or other BIOS) available and how could I install it?
    Boot a BIOS flashing program from CD or DVD and somehow bypass the HP BIOS's block on updates? Thanks in advance for any advice

    Hi, thanks for the quick reply. I don't have another PC handy but will try to find one. The USB flash drive definitely does NOT appear in the boot menu - even as an HDD or CD/DVD as I have seen mentioned elsewhere as a possibility - and all USB devices are enabled in the BIOS settings and USB HDD and USB Floppy/CD are above rEFInd and all other entries in the boot order. I should also have mentioned that I've tried a (Lexar) USB flash drive prepared approximately a year ago with GParted Live which *has* previously booted the machine, and also different models of flash drives (Toshiba, Transcend) and different methods of preparing them such as burning bootable ISO images with Win32DiskImager, Universal USB Installer and Rufus, and manually creating and formatting a bootable FAT32 partition with diskpart (as per https://technet.microsoft.com/en-us/library/jj200124.aspx) and copying in System Rescue CD/GParted/Clonezilla files, ensuring there is an /EFI/BOOT/BOOTX64.efi file. In diskpart, the "attributes disk" command shows that the USB drives are not marked as bootable and "help attributes disk" says READONLY is currently the only disk flag that may be changed. (Don't know if this means anything as the GParted disk isn't "bootable" but did boot) Did the BIOS update disable enumerating USB devices until later in the Windows 8.1 boot process? 

  • Can I boot the 380e bios ugrade from the cd drive rather than the floppy disk?

    Can I boot the 380e bios upgrade from the cd drive rather than the floppy disk? I don't have any floppies around and I don't want to order them online just for this one task. The bios disk images are here. http://support.lenovo.com/en_US/detail.page?LegacyDocID=DSHY-46AKPY

    I'm sorry that I can't answer your CD vs diskette question, but you mention updating your 380E BIOS and the link you've included is for the 390E.
    Here's the 380E BIOS link: http://support.lenovo.com/en_US/downloads/detail.page?DocID=DS001672
    What version are you currently at?
    Regards.
    English Community   Deutsche Community   Comunidad en Español   Русскоязычное Сообщество
    Community Resources: Participation Rules • Images in posts • Search (Advanced) • Private Messaging
    PM requests for individual support are not answered. If a post solves your issue, please mark it so.
    X1C3 Helix X220 X301 X200T T61p T60p Y3P • T520 T420 T510 T400 R400 T61 Y2P Y13
    I am not a Lenovo employee.

  • MSI P965 Neo-F (MS-7235) problem booting from USB flash drive

    Hi, all!
    I was wondering if someone can help me. I am trying to install Windows 7 x64 on my 320GB HDD that is connected to my MSI P965 Neo-F (MS-7235) mobo (The CPU is a Core2Duo 6600 with 6GB of RAM). I created a bootable USB 8GB flash drive using Microsoft's "Windows 7 DVD USB Download Tool" and bootsect.exe (Needed to create a boot sector on the USB drive) from the MS store. I successfully tested the resulting bootable USB drive using freeware MobaLiveCD (Sorry, you'll have to Google "mobalivecd" since this forum doesn't seem to allow external links) running under Windows XP SP3 x86 (32bit). Under MobaLive's QEMU, Windows 7 setup loaded its files and produced an error message basically saying that it could not install Windows 7 x64 under an x86 OS (No surprise there since QEMU is emulating a 32bit processor - The point is that the bootable USB drive I created works).
    I then went into my mobo's CMOS and under Advanced BIOS Features -> Boot Sequence -> 1st Boot Device, set the value to "USB-HDD" and rebooted my machine. The USB drive probably was not detected by the mobo under that setting because it proceeded to boot from my HDD which is the 2nd Boot Device. I repeated the same process using each one of the  four USB ports in the rear of the mobo (I don't have the optional USB panel that the MSI users manual mentions) to no avail. I also tried setting the 1st Boot Device to "USB-FDD" and repeated the process for each USB port but the mobo still will not boot from the USB drive (It does not recognize it). When I set the 1st Boot Device to "USB-ZIP" and rebooted, the mobo hangs after "Verifying DMI Pool Data ..." which is no surprise since I am not using a USB ZIP drive but a USB flash drive. It appears that under that setting, it recognizes that there is a USB device attached but it is expecting a response (From a USB ZIP drive). I had no idea it would be this frustrating to boot from a USB flash drive! If anyone knows how to make this mobo boot from a USB flash drive, please let me know. Any assistance would be greatly appreciated. Thanks!
       

    Quote from: RemusM on 12-June-14, 17:51:30
    The P965 Neo motherboard is 8 years old, so don't expect miracles. .... You need to format the USB stick in the proper way. You may use this utility to do it: hxxp://www.prime-expert.com/flashboot/ Also, it's a good idea to use the first (USB0) connector (controlled by Intel ICH8) for the USB flash drive. Good luck.
    Thank You for your fast response, RemusM!
    I'm not looking for a miracle. I'm just looking for a mobo that does what it is supposed to do: Allow me to boot from a USB flash drive (I don't think that is too much to ask for even from a board that was made in 2006)!
    Thanks for recommending FlashBoot. I see under their "Why FlashBoot" section that it "... does not shift to user the burden of choice between "USB-ZIP" and "USB-HDD" at format time and proper BIOS setup at boot time. ... and every USB disk is formatted in such way that it will work in every environment properly, regardless of current BIOS setting.", so I will give it a try and let you know about the results afterwards.

  • I recently received a mac book air 11 inch for christmas ... i beliehve it was bought in the states from my father i was unaware of the specs until i opened and read it... and i was wondering if i can still do the upgrade to 8gb ram and bigger flash drive

    i recently received a mac book air 11 inch for christmas ... i beliehve it was bought in the states from my father i was unaware of the specs until i opened and read it... and i was wondering if i can still do the upgrade to 8gb ram and bigger flash drive.. is this possible and for how much? its only a week old.

    Your 14 days are up, however you could take your case to Apple Inc. regarding same,
    however those are the stipulations.
    RAM cannot be upgraded however, period, its permanent on the logic board after mfg.
    As for the SSD (solid state drive), upgrading same is a bad premise 9 times out of 10.
    No notebooks is a mass storage device, and you need an external HD for data redundancy and backups regardless.
    data that is static on your SSD and not used very often has no logical reason to be ON the notebooks, and best saved on a superslim external HD ($60)
    SSD are very expensive, even a small one,  HD are cheap as dirt and users are recommended to have one regardless for many good reasons.

Maybe you are looking for