Disk2vhd efi vhdx vm fails to boot (solved)

Edit:  I was able to work around this.  From what I've read, a bare metal restore from a physical to virtual machine is not supported, but that's what I tried and it worked beautifully.  The only thing that went right today.
So, disk2vhd isn't needed (and as we've seen, didn't work).  Instead I took these steps:
1. Control Panel -> File History.  After it finishes searching for drives, at the bottom left of the page is a link to System Image Backup.  Run it, and select a target drive for the backup.  I used a 64Gb key drive.  Next, it will
show you the volumes that will be backed up.  It automatically selects (and you cannot deselect) the volumes required for a bare metal restore.  Any additional volumes are optional.  You'll probably want to deselect the target drive for the
backup.
2. After the backup is complete, either move the drive over to the Hyper-V host or access it over the network.
3. In Hyper-V Manager, create a VHDX virtual disk from the backup drive.  Then create a blank VHDX that is at least the size of the original machine's system disk (which may have multiple volumes).  In my case, this was a 2Tb disk, to which I added
an extra 128Gb just to be sure.  This isn't the size of the image backup, it's the size of the disk from which the image backup was taken.  I made my disks fixed size.  I don't know if it would work otherwise.
4. Create a Gen 2 virtual machine (this was necessary for me since my original machine used EFI boot).  On the SCSI host adapter, attach the blank disk that will take the image restore, and attach a second disk containing the image backup (this can
be deleted later). 
5. Create a second SCSI host adapter and attach a DVD drive to it (also may be deleted later).  Not sure if you really need the second adapter but I was just being cautious.  Assign the ISO image for your original machine's install disc (Windows
8.1 Pro Update 1, in my case) to the DVD.  Set the DVD to boot.
6. Run the VM and press a key when prompted to run from the DVD.  Select the Repair option, and drill down until you get to a page with the option for a System Image Restore.  Click on that and then select the drive containing your backup when
prompted.  It will inform you that drive C: (your blank drive) will be wiped out and resized to match the original system drive that was backed up.  Then let it run.  In my case it took maybe three or four minutes, but it was a very sparsely
populated 2Tb drive.
7. After the restore completes, you should be good to go.  After testing the new VM, I deleted the second SCSI disk with the backup image, as well as the DVD and its host adapter.
=================================================
I ran disk2vhd on a recently built Windows 8.1 x64 machine.  The conversion completed successfully, but I'm having no luck finding the right recipe to booting it in Hyper-V on a Server 2012 R2 machine.  I've tried both Gen 1 and Gen 2 (with and
without Secure Boot enabled).  In both cases it apparently fails to find a boot loader.  The virtual disk is VHDX.
I ran disk2vhd twice.  Once including the additional volumes Windows creates for EFI, and once without.  The result is the same either way.
Any help much appreciated.

Hi Michael,
Thanks for your sharing .
I am afraid the physical host is using UEFI .(I test disk2vhd on MBR partition ,it works )
EDIT:
Here is another similar thread :
http://social.technet.microsoft.com/Forums/windowsserver/en-US/9a668872-0f58-4da3-a407-2f2018d42b50/windows-server-2012-r2-datacenter-how-to-create-hyperv-which-will-be-the-replica-of-host-os?forum=winserverhyperv
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

  • Systemd.timesyncd fails on boot [Solved]

    Upgraded systemd to 217-1 and now each boot sees timesyncd fail:
    ● systemd-timesyncd.service - Network Time Synchronization
    Loaded: loaded (/usr/lib/systemd/system/systemd-timesyncd.service; enabled)
    Active: failed (Result: start-limit) since Fri 2014-10-31 10:25:59 NZDT; 5min ago
    Docs: man:systemd-timesyncd.service(8)
    Process: 303 ExecStart=/usr/lib/systemd/systemd-timesyncd (code=exited, status=1/FAILURE)
    Main PID: 303 (code=exited, status=1/FAILURE)
    Status: "Shutting down..."
    Oct 31 10:25:59 Shiv systemd[1]: Failed to start Network Time Synchronization.
    Oct 31 10:25:59 Shiv systemd[1]: Unit systemd-timesyncd.service entered failed state.
    Oct 31 10:25:59 Shiv systemd[1]: systemd-timesyncd.service failed.
    Oct 31 10:25:59 Shiv systemd[1]: start request repeated too quickly for systemd-timesyncd.service
    Oct 31 10:25:59 Shiv systemd[1]: Failed to start Network Time Synchronization.
    Oct 31 10:25:59 Shiv systemd[1]: Unit systemd-timesyncd.service entered failed state.
    Oct 31 10:25:59 Shiv systemd[1]: systemd-timesyncd.service failed.
    Once I log in, I am able to restart the service without any complaint.
    Anyone else seeing this?
    # edit: perhaps related to this fixed(?) bug: http://lists.freedesktop.org/archives/s … 03199.html

    tl;dr answer:
    # sed -i 's/ remote-fs.target$//' /usr/lib/systemd/system/systemd-journal-flush.service
    Long answer:
    In systemd 217 a few changes were made with regard to ordering of early boot units, resulting in certain setups which used to work with systemd 216 to make problems with systemd 217. The fix above was also applied in systemd upstream by this commit:
    commit 919699ec301ea507edce4a619141ed22e789ac0d
    Author: Lennart Poettering <[email protected]>
    Date: Fri Oct 31 16:22:36 2014 +0100
    units: don't order journal flushing afte remote-fs.target
    Instead, only depend on the actual file systems we need.
    This should solve dep loops on setups where remote-fs.target is moved
    into late boot.
    For example, in my case, connman.service explicitly requests to be ordered before remote-fs.target, leading to all kinds of fun:
    systemd[1]: Found ordering cycle on basic.target/start
    systemd[1]: Found dependency on sysinit.target/start
    systemd[1]: Found dependency on systemd-tmpfiles-setup.service/start
    systemd[1]: Found dependency on systemd-journal-flush.service/start
    systemd[1]: Found dependency on remote-fs.target/start
    systemd[1]: Found dependency on connman.service/start
    systemd[1]: Found dependency on basic.target/start
    systemd[1]: Breaking ordering cycle by deleting job systemd-tmpfiles-setup.service/start
    systemd-timesyncd[201]: Failed to allocate manager: No such file or directory
    systemd[1]: systemd-timesyncd.service: main process exited, code=exited, status=1/FAILURE
    systemd[1]: Failed to start Network Time Synchronization.
    systemd[1]: Unit systemd-timesyncd.service entered failed state.
    systemd[1]: systemd-timesyncd.service failed.
    Explanation:
    systemd-journal-flush.service wants to be ordered after remote-fs.target whereas connman.service wants to be ordered before remote-fs.target. Additionally, connman.service requires basic.target. (This is implicit behavior for units which don't declare "DefaultDependencies=no".) This is why basic.target ends up getting pulled in so early in the first place.
    Furthermore, systemd-timesyncd.service relies on properly initialized runtime directories in order to work, so it wants to be ordered after systemd-tmpfiles-setup.service.
    In order to be able to start basic.target, systemd breaks the ordering cycle by taking systemd-tmpfiles-setup.service out of the transaction, thereby preventing systemd-timesyncd.service from starting up correctly.
    Last edited by csn (2014-11-01 22:18:37)

  • Dhcpcd fails at boot (SOLVED)

    Hi peoples.....
    this is a very common problem in arch so i've seen, but i followed many instructions and looked at the wiki,
    and so far i can't fix it....
    when i boot into arch... when it gets to "network" it says busy... and ends up failing... dhcp fails.........
    to get internet working, i have to open a konsole, log in as root, and enter "dhcpcd" then my internet works....
    i've tried quite a few suggestions... such as adding to my /etc/rc.local file... which is this:
    #!/bin/bash
    # /etc/rc.local: Local multi-user startup script.
    dhcpcd -k eth0 dhcpcd -nd eth0
    here is my rc.conf file which to me, looks right
    # /etc/rc.conf - Main Configuration for Arch Linux
    # LOCALIZATION
    # LOCALE: available languages can be listed with the 'locale -a' command
    # HARDWARECLOCK: set to "UTC" or "localtime"
    # USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
    # TIMEZONE: timezones are found in /usr/share/zoneinfo
    # KEYMAP: keymaps are found in /usr/share/kbd/keymaps
    # CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
    # CONSOLEMAP: found in /usr/share/kbd/consoletrans
    # USECOLOR: use ANSI color sequences in startup messages
    LOCALE="en_US.utf8"
    HARDWARECLOCK=""
    USEDIRECTISA="no"
    TIMEZONE="Australia/Perth"
    KEYMAP="us"
    CONSOLEFONT=
    CONSOLEMAP=
    USECOLOR="yes"
    # HARDWARE
    # MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
    # MOD_BLACKLIST: Prevent udev from loading these modules
    # MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
    # NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
    MOD_AUTOLOAD="yes"
    #MOD_BLACKLIST=() #deprecated
    MODULES=()
    # Scan for LVM volume groups at startup, required if you use LVM
    USELVM="no"
    # NETWORKING
    # HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
    HOSTNAME="archbox"
    # Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
    # Interfaces to start at boot-up (in this order)
    # Declare each interface then list in INTERFACES
    #   - prefix an entry in INTERFACES with a ! to disable it
    #   - no hyphens in your interface names - Bash doesn't like it
    # DHCP:     Set your interface to "dhcp" (eth0="dhcp")
    # Wireless: See network profiles below
    #Static IP example
    #eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
    eth0="dhcp"
    INTERFACES=(eth0)
    ROUTES=(!gateway)
    # Routes to start at boot-up (in this order)
    # Declare each route then list in ROUTES
    #   - prefix an entry in ROUTES with a ! to disable it
    gateway="default gw 192.168.0.1"
    ROUTES=(!gateway)
    # Enable these network profiles at boot-up.  These are only useful
    # if you happen to need multiple network configurations (ie, laptop users)
    #   - set to 'menu' to present a menu during boot-up (dialog package required)
    #   - prefix an entry with a ! to disable it
    # Network profiles are found in /etc/network.d
    # This now requires the netcfg package
    #NETWORKS=(main)
    # DAEMONS
    # Daemons to start at boot-up (in this order)
    #   - prefix a daemon with a ! to disable it
    #   - prefix a daemon with a @ to start it up in the background
    DAEMONS=(syslog-ng network xorg hal kdm netfs crond)
    I even tried making a profile copied from examples..... which for me... was wired ethernet-dhcp, since im using a wired connection with dhcp...... and trying to connect to it using netcfg then profile name..... here is my profile input
    CONNECTION="ethernet-iproute"
    DESCRIPTION="A basic dhcp ethernet connection using iproute"
    INTERFACE="eth0"
    IP="dhcp"
    and theres also 1 other suggestion that i tried... which was adding "dhcp eth0" to my /etc/rc.d/network but dhcpcd still fails on reboot and i have to keep manually enabling it.....
    any suggestions???
    thanx in advance
    kaddy
    Last edited by kaddy (2009-09-28 15:53:04)

    lol. anybody?????
    I've tried everything in the wiki under networking, i've tried several other suggestions that helped others, but it seems i can only get my internet to work by manually runniny "dhcpcd"
    but it is annoying to do that everytime i boot.....(i wonder if i can make it start during boot...? but how? its not a daemon.....?"
    anyways.....
    more than happy to try any suggestions..... theres bound to be something wrong here... unless dhcpcd is buggy!
    I even tried wicd and couldn't get it to work properly.... but thats another story.....
    I've tried removing ! from gateway in rc.conf...... i've tried moving the hal daemon last, as i found out it can effect other daemons if run before network........
    funny thing is, about 1 out of 10 times, everything starts up ok, with no fails... but after another reboot, back to the norm.
    im out of ideas........
    im almost gonna give up on this issue........ i don't know what else i can try
    Last edited by kaddy (2009-09-27 16:29:00)

  • Filesystem check failed while booting [SOLVED]

    I tried to get some help from my previous post but got no answers, so I'll summarize in hope of getting an answer:
    I've installed linux before windows because I had this operating system before. But, when I've partitioned I've made a NTFS type 83 for windows, cause I know I'd install it later on.
    Now, I've restored my bootloader (grub) but when I try to boot my arch linux copy, a message tells me that my partition sda2 which is my Windows one, isn't clean or corrupt.
    all my linux partition are clean, but my NTFS windows partition make me unable to boot on my linux OS with this error msg:
    fsck.ext4: Bad magic number in super-block while trying to open /dev/sda2
    /dev/sda2:
    The superblock could not be read or does not describe a correct ext filesystem. If the devine is valid and it really contains an ext2 filesystem (and not swao or ufs or simething else), then the superblock is corrupt, and you might try running e2fsck with an alternate superbloc:
    e2fsck -b 8193 <device>
    Next I can do is entering the root psw and use the command line, I really need help to restore my linux partition without formating anything, please.
    My guess is that linux doesn't reorganize the partition as it is NTFS and doesn't boot for this reason, but didn't find how to fix it over internet yet, some help would be really appreciated.
    Last edited by Mazh (2011-06-10 20:30:39)

    My partition layout is:
    fdisk -l output:
    /dev/sda1 ID (5) extended (don't know what's that didn't think I've made that myself, maybe coming from windows when I installed the NTFS partition)
    /dev/sda2 * HPFS/NTFS/exFAT ID (7) (strange cause I had set 87 but well, windows is working correctly it seems)
    /dev/sda3 ID (83) linux
    /dev/sda5 ID (83) linux
    /dev/sda6 ID (83) linux
    /dev/sda7 ID (83) linux
    /dev/sda8 * ID (83) linux
    yep, it's actually strange that my fsck.ext4 check my sda2 partition NTFS...
    cat /etc/fstab:
    /dev/sda2 /home ext4 defaults 0 1
    /dev/sda5 swap defaults 0 0
    /dev/sda6 /var ext4 defaults 0 1
    /dev/sda7 /usr ext4 defaults 0 1
    /dev/sda8 / ext4 defaults 0 1
    menu.lst
    linux grub
    /dev/sd0 (fd0)
    /dev/sda (hd0)
    /dev/sdb2 (hd1,1)
    /dev/sda3 (hd0,2)
    title arch linux
    root (hd0,7)
    kernel /bootvmlinuz26 root=/dev/sda8 ro
    initrd /boot/kernel26.img
    the arch fallback (same)
    title Windows xp lite sp3
    rootnoverify (hd0,1)
    makeactive
    chainloader +1
    I really have to write by hands, so if you wants more info tell me and I'll write more.
    it's strange, could you explain me what does mean hd1 or hd0? isn't the 1st and second hard drive? and the second array the partition? cause if so, i've only 1 drive. But I'm probably not correct. Hope you get enough info to get me out of this problem!
    And no, I'm not using UUIDs, thx for your suggestion!

  • "Filesystem check failed" on boot [Solved]

    It seems to not like /home or /. Tried reinstalling Arch using ext3 instead of ext4 but I still get the same error. I tried searching for a fix on the forums already but couldn't find one that worked for me.
    Misc Info:
    - Using VirtualBox 3.1.2
    - Using 2009.08 netinstall iso
    Last edited by NightKev (2010-02-17 05:15:11)

    I don't know how you would do so in VB, but on my desktop I used an Arch LiveCD to reinstall GRUB in order to get /root and the kernel image working from the /boot directory. I entered the command "grub" as root in a terminal to open the grub prompt "grub>" then I entered "find /boot/grub/stage1" and received back" (hd1,1)" which is where my root partition was located. I then entered "root (hd1,1)" and then "setup (hd0)" and then "quit". It installed GRUB to the MBR. I don't know if that's helpful in your case though, but if GRUB is installed it could be.

  • [SOLVED] Arch Linux Duke (2007) Fails to Boot

    Folks, I have a unique and challenging problem that has exhausted my Arch Linux skills, and so I am now turning to you.
    I have a vintage Pentium Pro 200 system (that’s 200 MHz folks! – 200 MHz 686 architecture – the original 686!), two CPUs, running a dual boot between Windows NT 4.0 and Arch Linux Duke (2007). It has 512 MB of RAM and a 120 GB hard drive, partitioned up between Windows NT and Linux. I built this system new in 2007, hence the dated version of Arch.  It has run like a charm all these years, granted not getting that much use. After about a year of no use at all, I fired the system up last week to help with a little research for a blog post I was writing on networking Windows NT 4.0 and Mac OS 8.6. Windows NT 4.0 fired right up with no issue, and after I was done testing what needed to be tested I tried to boot over to Arch.
    After a year of disuse, Arch unexpectedly and stubbornly refused to boot. The boot process started up just fine, but towards the end, it declared that it could not mount the root file system on the root device and took a kernel panic and stopped. My Arch skills have gotten a bit rusty in the last few years, but I dusted them off and went to work. My guess was a file system or superblock error. Arch wouldn’t boot, but I dragged out my trusty RIPLinux 2.9 Rescue Live CD and fired it up. It came right up and ran, and I was able to mount the Arch partition and view all the files… everything seemed to be there; it just wouldn’t boot. Windows NT 4.0 AND RIPLinux both boot and run on the machine, so the hardware is fine as well.
    A little information on the disk layout. Windows NT 4.0 is in the first partition on the hard drive. The extended partition has a second Windows NT 4.0 partition (sort of a /home partition for Windows NT 4.0), followed by the main Arch partition (the one I am trying to boot), followed by a swap partition and then the largest partition, which I use to share data between Arch and Windows NT 4.0 (I have loaded an ext2/3 driver into Windows NT 4.0 and it happily accesses the Linux partitions on the box).
    RIPLinux’s e2fsck did find some issues with the Arch partition and I had it repair them all. I checked again afterwards that all the files were still there, and they were. With the partition now known to be clean, and the superblock repaired from one of the backups, all should have been well. However, Arch still wouldn’t (and still won’t) boot.
    RIPLinux has a kind of a chain loader function, so I had it attempt to start up Arch for me. However, this was flummoxed by the fact that Arch addresses all my hard drive partitions as /dev/sdax and RIPLinux addresses them as /dev/hdax. Hence, without a common language, it was hard to get the one to start the other. Still, using this function, I have been able to get a crippled version of Arch running on the machine again. No modules had been loaded, and so it couldn’t do almost anything, but there it was (and is), Arch Linux Duke, at the CLI level. From there, I can see all the files, I can move freely in and out of my user account and the root account, but I can’t make the thing actually boot properly.
    If you have read this far, you are a trooper.  Summarizing what I know, the hardware is good, the file system is clean, the superblock is good, I can mount it cleanly from a live CD and I can chain load a crippled version of Arch. Here is the boot process blow-by-blow. When I try to do a normal boot, the Windows NT 4.0 loader passes control to the Lilo boot sector I have placed on hda1 (sda1 in Duke’s parlance). Lilo takes over, present a menu and when I select Duke, takes off. Arch Linux Duke starts to boot. It gets a good long way along, all the way along to:
    :: Loading udev events                [Pass]
    :: Mount root Read-only
    :: Checking file systems
    This is where it stops.
    The next thing I see is:
    /dev/sda6
    The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else) then the superblock is corrupt and you might try running e2fsck with an alternate superblock:
        E2fsck –b 8193 <device>
    I then get a sort of character based splash screen that says
    **********FILE SYSTEM CHECK FAILED ****************************
    *   Please repair manually and reboot. Note that the root file system
    *   is currently mounted read-only. To remount it read-write, type:
    *   mount –n –o remount,rw /.  When you exit the maintenance
    *   shell, the system will reboot automatically
    Give root password for maintenance
    At this point, I give the root password and enter the maintenance shell as root. I typed in “mount” and the first entry I got back is
    /dev/sda6 on / type ext3 (rw)
    This is exactly the root partition that the start up complains about. It is clearly there.  I can see it, I can walk around it… it is clearly there. Why won’t it boot? Despite the message, the superblock is fine – it passes every test e2fsck can throw at it.
    At this point, I did a “e2fsck /dev/hda6 (which is how RIPLinux would have passed it into Arch” and it says it is “clean”. I suspect that the Superblock message is because Arch sees root as sda6, while RIP passed it in as hda6...
    Deciding to see what Arch would be seeing as it tried to set things up in the boot sequence, I tried the following next:
    # mknod “/dev/root2” b 3 6   
    (“3” because RIPLinux refers to my hard drive as IDE, while Arch refers to it by major number “8”, which is SCSI. By the way, it IS an IDE drive – not sure why Arch insists on using the sdx nomenclature instead of hdx)
    Then I entered “mount /dev/root2 /mnt/hda6” and “ls /mnt/hda6”
    All was well. I can make the node, I can mount it, and I can see the contents. All is clearly well, but something is clearly wrong enough that Arch can’t boot.
    I am totally out of ideas. I have tried every trick I know and am out of tricks. I would welcome any insights as to what I could try to get this venerable Arch installation back on its legs.
    By the way, the key section of the /etc/lilo.conf file (lest anyone want to know) is:
    image = /boot/vmlinuz26
       root = /dev/sda6
       label = ArchLinux-Duke
       initrd = /boot/kernel26.img
       read-only
    I am stumped. Thanks in advance for any and all pointers you may be able to offer.
    Last edited by mac57 (2014-06-02 17:42:21)

    Folks, thanks for all your helpful comments, and I wanted to report back to you that I finally overcame the issue, and ArchLinux-Duke (2007) is once again executing flawlessly on my old Pentium Pro 200 system. I won't bother reporting here all the blind allies I went down as I tried to figure out what was wrong, but in the end, literally moments before I was about to give up and overwrite my Arch installation with a new Linux variant (antiX seemed well suited for such old and low power hardware), my attention was drawn to a note I had made in my files back in 2007 about a problem with similar symptoms. In that case, I had just deleted ZenWalk Linux from the hard drive (both Arch and Zen had been on the drive), and merged several partitions to make use of the newly free space. This had changed Arch's view of the drive lettering, and what had been its /dev/sddx root device was now /dev/sdcx. Arch failed to boot, throwing off the same errors I was seeing now. I wish I had recalled that note a month or so ago! It would have saved me a lot of work and a lot of frustration.
    At any rate, as a last step, and testing the idea that maybe the drive lettering had changed for some reason, I repeatedly manually booted Arch, specifying root=/dev/sda6, then /dev/sdb6, then /dev/sdd6, and finally, /dev/sdc6. Eureka! Arch now considered itself to be on /dev/sdc6 whereas previously it had been on /dev/sda6. This got me part way there, but the boot failed at the filesystem check stage and threw me into root. I disabled the file system check in /etc/rc.sysinit and got farther. Then I cleaned up /etc/fstab to agree with the new sdc naming, and I was back on the air fully.
    So, what had happened was that Arch had changed its view of the drive it was on from sda6 to sdc6. While I could not understand why this "sudden" change had occurred, at least I had a solution, and had Arch back up and running.
    Trolling through the rest of my notes, I found the answer. In 2012, the Tekram SCSI card in the machine failed, and I ultimately replaced it with an Adaptec card. The Tekram card did not have a BIOS segment on it. The Adaptec card did. My guess is that this caused the two internal SCSI devices I have built into the system (Iomega ZIP and Jaz respectively) to be enumerated first, claiming the "sda" and "sdb". device names. That left "sdc" for the root device, and that is where Arch went next.  This is my guess anyway.
    I should have caught this issue back in 2012, at the time, but from my notes, I can see that I tested the new card thoroughly using the  Windows NT 4.0 side of the machine, but never thought to bring up Arch as well. Hence, this problem lay dormant for two years, before I attempted to fire up Arch last month and blundered right into it.
    It has not all been bad. I have learned more about the ext2 and ext3 file systems and superblocks in the intervening time than I will ever need to use. I have learned how to manually boot Linux on a machine whose BIOS is so old that it cannot address the disk cylinder that the kernel is on and I have completely refreshed the many general Linux skills that used to just flow from my finger tips. It has been a frustrating experience, but ultimately a successful and useful one.
    Just wanted to let everyone know that this is now [SOLVED]. I would mark the post as such, but I don't see any obvious way to do that. Thanks again everyone.

  • Kernels 3.10.6 and 3.10.7 fail to boot with EFI stub

    Been using rEFInd for some time now. Current installed version is 0.7.1. Kernels 3.10.5 and earlier would boot without incident. Yesterday I upgraded to 3.10.6 and boot failed. As a workaround, I copied the Liquorix kernel and initramfs from my Kubuntu partition; to my mild surprise, this worked. My next test was to install the 3.10.7 Zen kernel from heftig's repository. This kernel boots fine (I added a version number string to the name of the kernel image and the initramfs so that rEFInd would automatically match them). After that, I enabled Arch testing and updated the Arch kernel to 3.10.7; this also fails to boot just like the 3.10.6 kernel did.
    I'm a fan of boot text, so I've configured rEFInd in text mode only. Here's my refind.conf, with almost no changes from defaults:
    timeout 20
    textonly 1
    use_graphics_for
    scan_all_linux_kernels
    And my /boot/refind_linux.conf:
    "Boot to X" "ro root=/dev/sda3 nox2apic nmi_watchdog=0 elevator=noop acpi_osi=Linux pcie_aspm=force raid=noautodetect systemd.unit=graphical.target"
    "Boot to single user" "ro root=/dev/sda3 nox2apic nmi_watchdog=0 elevator=noop acpi_osi=Linux pcie_aspm=force raid=noautodetect systemd.unit=multi-user.target"
    # "Boot to recovery" "ro root=/dev/sda3 nox2apic nomodeset systemd.unit=rescue.target"
    Finally, details abot my laptop -- a ThinkPad T520:
    steve@t520 ~ $ inxi -xxSMCGDp
    System: Host: t520 Kernel: 3.10.7-1-zen x86_64 (64 bit, gcc: 4.8.1)
    Desktop: KDE 4.11.00 (Qt 4.8.5) dm: kdm Distro: Arch Linux
    Machine: System: LENOVO product: 423926U version: ThinkPad T520 Chassis: type: 10
    Mobo: LENOVO model: 423926U Bios: LENOVO version: 8AET63WW (1.43 ) date: 05/08/2013
    CPU: Dual core Intel Core i7-2620M CPU (-HT-MCP-) cache: 4096 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 10769.3
    Clock Speeds: 1: 1188.00 MHz 2: 1809.00 MHz 3: 1809.00 MHz 4: 1080.00 MHz
    Graphics: Card: NVIDIA GF119M [Quadro NVS 4200M] bus-ID: 01:00.0 chip-ID: 10de:1057
    X.Org: 1.14.2 driver: nvidia Resolution: [email protected]
    GLX Renderer: NVS 4200M/PCIe/SSE2 GLX Version: 4.3.0 NVIDIA 325.15 Direct Rendering: Yes
    Drives: HDD Total Size: 1256.3GB (8.2% used)
    1: id: /dev/sda model: M4 size: 256.1GB serial: 000000001140031E608A temp: 0C
    2: id: /dev/sdb model: HGST_HTS721010A9 size: 1000.2GB serial: JG40006PG61HKC temp: 43C
    Partition: ID: / size: 108G used: 37G (37%) fs: ext4
    ID: /boot/efi size: 511M used: 3.1M (1%) fs: vfat
    ID: /mnt/kubuntu size: 118G used: 59G (53%) fs: ext4
    ID: swap-1 size: 9.64GB used: 0.00GB (0%) fs: swap
    Last edited by steveriley (2013-08-19 05:27:15)

    Steve, your picture is far too large for these forums.  You are going to want to put it in some kind of a picture sharing/hosting site and link back to it.  Otherwise it will end up disappeared (likely via black magic) from your post.  I don't think that it provides any useful information anyway.  If you want to post your kernel command line that is great.  But posting a picture of a frozen screen with no output... doesn't really do much good.
    Efistub has been a bit shaky since 3.6 actually.  There is a monster thread about this already, the title of which references 3.6, but the content continues on through several kernel releases.  Still people continually report this as being an issue.  What I do is I keep a normal efi bootloader (one that doesn't rely on efistub) at the ready all the time.  My choice was elilo, but since [testing] started including syslinux-efi in the syslinxu package, I have started using that... though I still have elilo set up.
    Can you boot with efistub from the UEFI Shell or gummiboot?  I prefer gummiboot, but I have had this problem in the past, and when I did, I was able to boot with rEFInd... which was strange.  Some people even report that simply having a direct efibootmgr entry in their firmware causes it to magically work.  Though there should be to reasonable explanation for this, it was confirmed by several people in the mentioned thread.

  • [SOLVED] "Filesystem check failed" during boot process

    I was using XFCE on my netbook recently and clicked "shutdown".  It logged out to the command prompt and nothing happened.  Assuming that I'd clicked "logout" by mistake, I typed "pacman -Syu" to run an update...  And moments later it suddenly started the shutdown process.
    Now, whenever I boot up, I see the message below.  I tried booting from a GParted CD to check the filesystems for errors, but none were detected.
    Can anyone suggest what I might need to do to fix the problem?
    rootfs: clean, 11026/246512 files, 477083/984576 blocks
    home: clean, 4386/527280 files, 237183/2105344 blocks
    /dev/sdb2 is mounted. e2fsck: Cannot continue, aborting.
    ************* FILESYSTEM CHECK FAILED ************
    * Please repair manually and reboot. Note that the root
    * file system is currently mounted read-only. To remount
    * it read-write type: mount -n -o remount,rw /
    * when you exit the maintenance shell the system will
    * reboot automatically.
    Give root password for maintenance
    (or type Control-D to continue):
    Last edited by esuhl (2012-03-27 01:20:07)

    Thank you all for your replies :-)
    hadrons123 wrote:What happens when you do try the suggestion given by it?
    I don't exactly know how I should "repair manually"...  I thought a filesystem check in GParted would have been enough...
    lijpbasin wrote:You can boot the system using a archlinux live cd, and run fsck manually on every linux partition in the old system with options.
    DON'T mount any of the filesystems before running fsck, or your data will probably be lost. If you want to check the partition information first, run fdisk -l with root privileges.
    Thanks.  I tried booting from an ArchBang live CD last night and ran "e2fsck -pcv" on each partition.  The check completed, but the problem persists...  I just tried again using "fsck" as you suggested and got the following output (but the machine still fails to boot with the same error as before):
    fsck from util-linux 2.20.1
    e2fsck 1.41.14 (22-Dec-2010)
    usr was not cleanly unmounted, check forced.
    Pass 1: Checking inodes, blocks, and sizes
    Pass 2: Checking directory structure
    Pass 3: Checking directory connectivity
    Pass 4: Checking reference counts
    Pass 5: Checking group summary information
    usr: 115811/458752 files (1.7% non-contiguous), 783161/1834496 blocks
    Gcool wrote:
    /dev/sdb2 is mounted. e2fsck: Cannot continue, aborting.
    As mentioned already, the reason it's failing is because the /dev/sdb2 partition is mounted before it can be fsck'd. What is this partition exactly (which filesystem, what's on it, mountpoint,...)?
    I'm not overly familiar with the Linux boot process, but why would it suddenly be mounting this partition before fsck-ing it?  Even if it was mounted when the netbook shutdown, surely the boot process starts with all partitions unmounted...?  Anyway, the partition details from /etc/fstab are below.
    <file system> <dir> <type> <options> <dump> <pass>
    tmpfs /tmp tmpfs nodev,nosuid 0 0
    /dev/sda1 / ext2 defaults,noatime 0 1
    /dev/sdb1 /home ext2 defaults,noatime,user_xattr 0 1
    /dev/sdb2 /usr ext2 defaults,noatime 0 1
    I'm (now) aware that mounting /usr as a separate partition is a bad idea and (having read the "Error when booting with the new initscripts" thread), I have told pacman to ignore updates to the initscripts package (until I figure out how best to work round or fix that issue).
    Shark wrote:Write umount /dev/sdb2 in konsole or unmount partition in gparted by right click on problematic partition and click unmount. Than proced.
    If I type "umount /dev/sdb2" at the prompt, I get the following error:
    umount: /usr: device is busy.
    (In some cases useful info about processes that use
    the device is found by lsof(8) or fuser(1))
    I tried "umount -l /dev/sdb2" to unmount when the device becomes free... but it never does.
    I also booted into GParted, but there is no option to "unmount" /dev/sdb2.  There is a "mount" option in the menu, but it is greyed out.  If I open a terminal window from the GParted Live environment and type "sudo umount /dev/sdb2" I get the following message:
    umount: /dev/sdb2: not mounted
    DSpider wrote:Are you mounting the root drive with "ro" (read only) in fstab?
    No (as shown above).  I don't *think* I've messed anything up with fstab or any other config files -- everything was working perfectly till the netbook shutdown whilst pacman was running.

  • [SOLVED] Luks with /arch/setup installation , fails at boot

    Hi all,
    So I tried to install arch on virtualbox with encrypted partitions (root /, /home/ and swap), but it fails at boot.
    /dev/sda1 is /boot
    /dev/sda2 is swap
    /dev/sda3 is /
    /dev/sda4 is /home
    The root partition seems to be loading fine because it asks for my password, then the boot sequence goes on, until the /home/ (apparently) :
    :: Bringing up loopback interface
    :: Unlocking encrypted volumes: chome..Usage: cryptsetup [-?vyrq] (...all the options...can't copy paste with virtualbox)
    /sbin/cryptsetup: Unknown action
    failed [FAIL]
    /dev/mapper/croot: clean, 27576/457856 files, 166316/1830898 blocks
    fsck.ext4: No such file or directory while trying to open /dev/mapper/chome
    Possibly non-existent device?
    /dev/sda1: clean,29/24096 files, 20790/96356 blocks
    [FAIL]
    It seems that it tries to open /dev/mapper/chome but it's not mounted yet
    In my /etc/crypttab, I added the lines :
    chome /dev/sda4 none luks
    cswap /dev/sda2 none luks
    /etc/fstab (I didn't change anything, /arch/setup configured it that way) :
    /dev/mapper/chome /home ext4 defaults 0 1
    /dev/mapper/croot / ext4 defaults 0 1
    /dev/mapper/cswap swap swap defaults 0 0
    /dev/sda1 /boot ext2 defaults 0 1
    And grub :
    title Arch Linux
    root (hd0,0)
    kernel /vmlinuz-linux root=/dev/mapper/croot cryptdevice=/dev/sda3:croot ro
    initrd /initramfs-linux.img
    What I wanted to do was to have swap,root and home encrypted partitions mounted at boot, but maybe it is not possible?
    I tried a lot of configurations for /etc/fstab and /etc/crypttab according to what I could find on the net but nothing worked. I read the whole tutorial https://wiki.archlinux.org/index.php/Sy … _with_LUKS but there is no config for fstab or crypttab or grub when installing with /arch/setup
    Thanks for any help !
    Last edited by John0000 (2012-04-12 12:50:18)

    Indeed you have a point, putting password in plaintext isn't very safe.
    There is a good alternative though: https://wiki.archlinux.org/index.php/Sy … _a_Keyfile
    the reason why you don't have a passphrase for root in a file somewhere is that you provide this passphrase during boot-time.
    Somewhere during boot you get the option to unlock you root device by typing in a passphrase... right?
    ro means that the volume is mounted read only http://linux.die.net/man/8/mount

  • [SOLVED] QEMU-KVM fails to boot if passed q35 machine type

    As I understand it, qemu still uses the PII3X as the default machine type.  I had been using -machine type=q35,accel=kvm for a few weeks to learn more about qemu and KVM.  With this code I could boot a win7 VM and I confirmed the ICH9 chipset appeared in the device manager.
    After a system update I am no longer able to pass that command.  I am using the linux-0.2 image located here.
    If I enter this code, the system boots normally:
    qemu-system-x86_64 -enable-kvm -boot order=c linux-0.2.img
    This however does not work and the bios complains that there is no bootable media found (after waiting for pxe):
    qemu-system-x86_64 -enable-kvm -boot order=c -M q35 linux-0.2.img
    qemu is 1.7.0-2 (built 02/19/14 but this is the only package in pacman's cache)
    seabios is 1.7.3.1-2 (built 09/21/13)
    I actually tried this on two different machines with the same result.  What can I do next to troubleshoot?  Thanks.
    Last edited by gizzard (2014-04-13 15:55:25)

    R00KIE wrote:
    The iso should boot, yes. I did try using -M q35 with a WinXP image I have here and it started to boot (I get blue screens and automatic reboots since lots of things change with -M q35).
    One different thing I have however is the specification of the interface type for disks. Try using "-drive file=/path/to/image,if=scsi" or "-drive file=/path/to/image,if=virtio", that seems to make it work for me, it still might make Win7 complain though.
    I think I'm getting closer thanks to your help.  Adding the if variable allows the debian image to boot using the q35 machine type.  Here are results of some trials (command and result):
    1. qemu-system-x86_64 -enable-kvm -cpu host -m 1024 debian-live-7.4-amd64-standard.iso
    - boots fine
    user@debian:~$ lspci | grep ACPI
    00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
    2. qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -machine type=q35,accel=kvm debian-live-7.4-amd64-standard.iso
    - fails to boot
    3. qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -machine type=q35,accel=kvm -drive file=debian-live-7.4-amd64-standard.iso,if=ide
    - fails to boot
    4. qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -machine type=q35,accel=kvm -drive file=debian-live-7.4-amd64-standard.iso,if=scsi
    - boots fine
    user@debian:~$ lspci | grep AHCI
    00:1f.2 SATA controller: Intel Corporation 82901IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] (rev 02)
    user@debian:~$ lspci | grep SCSI
    00:03.0 SCSI storage controller: LSI Logic / Symbios Logic 53c895a
    4. qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -machine type=q35,accel=kvm -drive file=debian-live-7.4-amd64-standard.iso,if=virtio
    - boots fine
    user@debian:~$ lspci | grep AHCI
    00:1f.2 SATA controller: Intel Corporation 82901IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] (rev 02)
    user@debian:~$ lspci | grep SCSI
    00:03.0 SCSI storage controller: Red Hat, Inc Virtio block device
    I will try these options with the win7 VM and report back.  I may need to recreate it from scratch, so it might take a little while.

  • IBook G4 fails to boot with internal HD installed, works when removed

    The short version: My iBook started failing to boot via any method (gray screen) and the boot menu (Option during startup) would freeze. Replaced HD, things were better. Six months into new HD, nearly the same symptoms appear again. Removed HD, now running off different HD via FireWire.
    The long version–
    Back in late 2008-12, my iBook started failing to boot up. Usually it would refuse to boot from any source. Booting the internal disk (10.4.11) would get to a gray screen without any logo and stay there. Holding down Option, the boot menu would come up, but it would usually freeze before it displayed any volumes. Booting from CD (AHT, or OS install disc) would fail in nearly the same way as booting from the internal drive. Target Disk Mode would start, but once the other machine tried to access the drive, the FireWire logo would stop moving and the drive would never show up on the other computer. Very rarely, the machine would get a bit further through one of the boot mechanisms, but it usually froze while booting or just after login.
    This machine has gone through three logic boards in the past, so I suspected that was the problem again. I took it to a local Genius Bar and the Genius explained that it was probably the hard drive. He said that sometimes, depending on the way the drive fails, it can "take out" other parts of the system due to drawing too much current, etc.
    I was a bit skeptical, but it was going to be much cheaper to replace the HD myself than it would be to send it in for a MLB replacement. So I ordered a new HD (80G) and a USB-to-ATA/SATA adapter. I hoped that I would be able to use the adapter to savlage a bit more data off the drive (it originally failed right before a backup!).
    After extracting the HD (40G), I connected it to the USB adapter and was able to access the drive just fine. I used another machine to run another backup from the recently removed HD (40G) to one of my FireWire backup drives and proceeded to put the iBook back together with the new HD (80G).
    Once it was all back together, the new HD worked fine. I was able to restore the recent backup from my FireWire drive to the internal, and it worked fine. The only oddity I noticed was that the new drive was apparently trying to sleep several times a minute. I used smartctl (installed via MacPorts) to adjust the power management setting on the drive, and that seemed to help. I also started running smartd (also via MacPorts) to better monitor the new drive.
    Recently, a bit more than six months after the new HD was installed, the new HD started showing errors in the system.log. I never found any errors in the logs after the previous HD failed (even though I could look through the logs just fine with the drive attached through the ATA-USB adapter).
    Jul 2 18:04:40 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 2 18:33:43 Blinky smartd\[217]: Device: disk0, ATA error count increased from 0 to 30\n
    Jul 3 02:03:42 Blinky smartd\[217]: Device: disk0, ATA error count increased from 30 to 31\n
    Jul 3 03:03:42 Blinky smartd\[217]: Device: disk0, ATA error count increased from 31 to 32\n
    Jul 6 23:33:42 Blinky smartd\[217]: Device: disk0, ATA error count increased from 32 to 33\n
    Jul 7 00:33:42 Blinky smartd\[217]: Device: disk0, ATA error count increased from 33 to 34\n
    Jul 7 12:42:24 Blinky smartd\[217]: Device: disk0, ATA error count increased from 34 to 36\n
    Jul 7 13:17:59 Blinky kernel\[0]: disk0s3: I/O error.
    +same error message a bit faster than one every 3 seconds+
    Jul 7 13:23:00 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 13:33:44 Blinky smartd\[217]: Device: disk0, ATA error count increased from 36 to 615\n
    Jul 7 21:17:05 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 21:17:12 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 21:17:12 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 21:17:12 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 21:17:15 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 21:17:18 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 21:17:21 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 21:17:23 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 21:17:29 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 21:18:17 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 21:19:21 Blinky kernel\[0]: disk0s3: I/O error.
    Jul 7 21:19:23 Blinky kernel\[0]: disk0s3: I/O error.
    I did not notice the errors until the afternoon of the 7th when the problem became evident. The events around 13:00 happened when I was trying to run a backup. The first backup failed in an odd way (when I came back to check on it later that evening, SuperDuper! seemed to have quit running). So I restarted the backup and started looking around in the logs. That is when I noticed the kernel I/O error messages. When I asked smartctl to query the drive, it showed that many errors had been occurring and it displayed the drive's log of the last five or so errors (alas, I did not save this output). Meanwhile the re-run of SuperDuper! was having problems again. It seemed to have hung (no SDAgent or SDCopy processes were running, but the main UI was still there). Since the backup was not getting anywhere, I decided to shutdown for a while and try again later.
    When I did try again later, I was back in the situation of six months ago. It would not boot at all (no internal, no FireWire, no CD/DVD, boot menu hangs, Target Disk Mode hangs). So, I opened up the system, removed the HD and put it back together without an internal HD. The machine is now able to boot and run from FireWire. Again, the (6 month old, 80G) HD "works fine" via the USB adapter. If SMART were available through the USB adapter, I could check to see if the drive is continuing to have problems. I used SuperDuper! to copy the HD to a volume on my FireWire drive which is how I an now running the system.
    Has anyone had any similar problems? Any idea why my iBook seems to be killing/rejecting hard drives? (I say killing because, while the drive is connected internally, it certainly seems to be dying. I say rejecting because once the drive is out of the system, both the drive and the system seem to "recover".) I have read messages there where others report success having their iBook MLB resoldered ("reball"). Has anyone experienced substantially similar issues that were solved with a resolder repair?
    Thanks!

    I was able to test my “failing” ATA drives in a G4 Mac mini (I had to take the mini apart because its drive had finally failed). I was able to successfully boot the Mac mini with either of my iBook drives installed. Once booted, +Disk Utility+ said that each one's SMART Status was Verified. I used smartctl to pull the full SMART info while I had them installed in the Mac mini.
    Since the drives were still “good”, I think this emphasizes that the problem is with the ATA interface on my iBook's logic board. Maybe it is broken, or maybe it just needs to be resoldered. For now I am happy just booting off an external Firewire drive.
    BTW, I ended up installing the 6 month old 80G drive in the mini. It has been working OK for 10 days now. As long as it continues to operate normally in the mini, it will serve as evidence that my iBook's HD ATA controller is borked. I just hope the ATA controller is more capable of accepting its fallibility than was HAL.
    There is a minor problem with the 80G in the mini in that I am unable to use hdapm to change the aggressive head unloading that the drive suffers. I was able to adjust it with hdapm while it was in my iBook. I am able to adjust it with hdparm under Linux on the mini. Luckily the change I made while booted in Linux "sticks" after rebooting back into Mac OS X (I hear it will be lost if the drive is completely powered off though).

  • New Windows server 2003 Hyper-V guest fails to boot

    Hello,
    I'm currently doing some virtualization experiments on my new server hardware. The host hardware is:
    IBM x3650 M4
    x2 Xeon E5-2609
    32GB RAM
    x2 480 GB SSDs
    Server OS: Windows server 2012
    I'd like to test some legacy app virtualization. I've configured a VM and have installed Windows server 2003. The install is done via DVD. The issue at hand is that after the initial installation, the server fails to boot. The VM goes into a reboot loop
    and so far the only error logging I'm able to find is in the hosts event log. 
    Log Name: Microsoft-Windows-Hyper-V-Worker-Admin
    Source: Microsoft-Windows-Hyper-V-Worker
    Date: 7/8/2014 2:14:48 PM
    Event ID: 18560
    Task Category: None
    Level: Critical
    Keywords:
    User: NT VIRTUAL MACHINE\A0D20FA4-B27B-4B58-85C1-87D74B0ADD2D
    Computer: CCSTS1.cnet2k.cornerstonecredit.net
    Description:
    'LegacyTS' was reset because an unrecoverable error occurred on a virtual processor that caused a triple fault. If the problem persists, contact Product Support. (Virtual machine ID A0D20FA4-B27B-4B58-85C1-87D74B0ADD2D)
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="Microsoft-Windows-Hyper-V-Worker" Guid="{51DDFA29-D5C8-4803-BE4B-2ECB715570FE}" />
    <EventID>18560</EventID>
    <Version>0</Version>
    <Level>1</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2014-07-08T21:14:48.544007000Z" />
    <EventRecordID>159</EventRecordID>
    <Correlation />
    <Execution ProcessID="1512" ThreadID="3536" />
    <Channel>Microsoft-Windows-Hyper-V-Worker-Admin</Channel>
    <Computer>CCSTS1.cnet2k.cornerstonecredit.net</Computer>
    <Security UserID="S-1-5-83-1-2698121124-1264104059-3615998341-769460811" />
    </System>
    <UserData>
    <VmlEventLog xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
    <VmName>LegacyTS</VmName>
    <VmId>A0D20FA4-B27B-4B58-85C1-87D74B0ADD2D</VmId>
    <Rax>0x0</Rax>
    <Rbx>0x0</Rbx>
    <Rcx>0x0</Rcx>
    <Rdx>0x0</Rdx>
    <Rsp>0x804de00c</Rsp>
    <Rbp>0x0</Rbp>
    <Rsi>0x0</Rsi>
    <Rdi>0x0</Rdi>
    <R8>0x0</R8>
    <R9>0x0</R9>
    <R10>0x0</R10>
    <R11>0x0</R11>
    <R12>0x0</R12>
    <R13>0x0</R13>
    <R14>0x0</R14>
    <R15>0x0</R15>
    <Rip>0x80547c7c</Rip>
    <Rflags>0x10046</Rflags>
    <FpControlStatus>7F030000000000000000000000000000</FpControlStatus>
    <XmmControlStatus>0000000000000000801F0000FFFF0000</XmmControlStatus>
    <Cr0>0x8001003d</Cr0>
    <Cr2>0x804ddffc</Cr2>
    <Cr3>0xa02000</Cr3>
    <Cr4>0x20</Cr4>
    <Cr8>0xf</Cr8>
    <Xfem>0x1</Xfem>
    <Dr0>0x0</Dr0>
    <Dr1>0x0</Dr1>
    <Dr2>0x0</Dr2>
    <Dr3>0x0</Dr3>
    <Dr6>0xffff0ff0</Dr6>
    <Dr7>0x400</Dr7>
    <Es>0000000000000000FFFFFFFF2300F3C0</Es>
    <Cs>0000000000000000FFFFFFFF08009BC0</Cs>
    <Ss>0000000000000000FFFFFFFF100093C0</Ss>
    <Ds>0000000000000000FFFFFFFF2300F3C0</Ds>
    <Fs>00F0DFFF00000000FF1F0000300093C0</Fs>
    <Gs>0000000000000000FFFFFFFF00000000</Gs>
    <Ldtr>00000000000000000000000000000000</Ldtr>
    <Tr>90685580000000006800000050008B00</Tr>
    <Idtr>000000000000FF0700F4038000000000</Idtr>
    <Gdtr>000000000000FF0300F0038000000000</Gdtr>
    <Tsc>0x148e4294</Tsc>
    <ApicBase>0xfee00900</ApicBase>
    <SysenterCs>0x0</SysenterCs>
    <SysenterEip>0x0</SysenterEip>
    <SysenterEsp>0x0</SysenterEsp>
    </VmlEventLog>
    </UserData>
    </Event>
    My VM config
    <?xml version="1.0" encoding="UTF-16" standalone="yes"?>
    <configuration>
    <_24984ed0-bdad-4b90-82b2-5d59f874e91e_>
    <ChannelInstanceGuid type="string">{E4E9CD0E-4BBF-4C1B-B655-715781690655}</ChannelInstanceGuid>
    </_24984ed0-bdad-4b90-82b2-5d59f874e91e_>
    <_7d80d3db-61ee-4879-8879-5609f1100ad0_>
    <address type="string">5353,00000000,00</address>
    <version type="integer">1</version>
    </_7d80d3db-61ee-4879-8879-5609f1100ad0_>
    <_83f8638b-8dca-4152-9eda-2ca8b33039b4_>
    <controller0>
    <drive0>
    <pathname type="string">E:\Hyper-V\VHD\LegacyTS.vhdx</pathname>
    <pool_id type="string"></pool_id>
    <type type="string">VHD</type>
    </drive0>
    <drive1>
    <pathname type="string"></pathname>
    <type type="string">NONE</type>
    </drive1>
    </controller0>
    <controller1>
    <drive0>
    <pathname type="string">SCSI\CDROM&amp;VEN_IBM_SATA&amp;PROD_DEVICE_81Y3681\4&amp;1864BF9E&amp;0&amp;010000</pathname>
    <pool_id type="string"></pool_id>
    <type type="string">ISO</type>
    </drive0>
    <drive1>
    <pathname type="string"></pathname>
    <type type="string">NONE</type>
    </drive1>
    </controller1>
    <version type="integer">5</version>
    </_83f8638b-8dca-4152-9eda-2ca8b33039b4_>
    <_8e3a359f-559a-4b6a-98a9-1690a6100ed7_>
    <port0>
    <connection type="string"></connection>
    </port0>
    <port1>
    <connection type="string"></connection>
    </port1>
    <version type="integer">2</version>
    </_8e3a359f-559a-4b6a-98a9-1690a6100ed7_>
    <_8f0d2762-0b00-4e04-af4f-19010527cb93_>
    <controller0>
    <drive0>
    <pathname type="string"></pathname>
    <type type="string">VFD</type>
    </drive0>
    </controller0>
    <version type="integer">1</version>
    </_8f0d2762-0b00-4e04-af4f-19010527cb93_>
    <_a80e9c62-750a-4a6b-9548-d46677e806be_>
    <ChannelInstanceGuid type="string">{23c9c636-93de-4aec-9bef-220766177a24}</ChannelInstanceGuid>
    <Connection>
    <AltPortName type="string">Dynamic Ethernet Switch Port</AltPortName>
    <AltSwitchName type="string">Intel(R) I350 Gigabit Network Connection - Virtual Switch</AltSwitchName>
    <AuthorizationScope type="string"></AuthorizationScope>
    <ChimneyOffloadWeight type="integer">0</ChimneyOffloadWeight>
    <Feature_C885BFD1-ABB7-418F-8163-9F379C9F7166>
    <DisplayName type="string"></DisplayName>
    <Flags type="integer">0</Flags>
    <Setting_97274751-A1EC-4DC2-941D-B7F9A1AED814>
    <Data type="bytes">AAIAAGQAAAAAAAAAAQAAAAAAAAA=
    </Data>
    <Version type="integer">256</Version>
    </Setting_97274751-A1EC-4DC2-941D-B7F9A1AED814>
    <Settings>
    <Id type="string">97274751-A1EC-4DC2-941D-B7F9A1AED814</Id>
    </Settings>
    </Feature_C885BFD1-ABB7-418F-8163-9F379C9F7166>
    <Features>
    <Id type="string">C885BFD1-ABB7-418F-8163-9F379C9F7166</Id>
    </Features>
    <HostResources>
    <HostResource type="string">8758EB1A-9687-41FC-9319-AE867D46BA5C</HostResource>
    </HostResources>
    <PoolId type="string"></PoolId>
    <PreventIPSpoofing type="bool">False</PreventIPSpoofing>
    <TestReplicaPoolId type="string"></TestReplicaPoolId>
    <TestReplicaSwitchName type="string"></TestReplicaSwitchName>
    </Connection>
    <FriendlyName type="string">Network Adapter</FriendlyName>
    <IsConnected type="bool">True</IsConnected>
    <MacAddress type="string">00-15-5D-01-18-02</MacAddress>
    <MacAddressIsStatic type="bool">False</MacAddressIsStatic>
    <PortName type="string">E7F02418-A1EB-4FF9-84F8-BF461B2D00C6</PortName>
    <SwitchName type="string">8758EB1A-9687-41FC-9319-AE867D46BA5C</SwitchName>
    <VpciInstanceGuid type="string">{E9444985-111B-404A-82FE-48608A397676}</VpciInstanceGuid>
    </_a80e9c62-750a-4a6b-9548-d46677e806be_>
    <_ac6b8dc1-3257-4a70-b1b2-a9c9215659ad_>
    <base_board>
    <serial_number type="string">9595-3600-2199-6834-7686-3927-30</serial_number>
    </base_board>
    <bios_guid type="string">{B54BE7B5-05A4-4C4A-A2BD-D63272C7CCCD}</bios_guid>
    <bios_serial_number type="string">9595-3600-2199-6834-7686-3927-30</bios_serial_number>
    <boot>
    <device0 type="string">Optical</device0>
    <device1 type="string">HardDrive</device1>
    <device2 type="string">Network</device2>
    <device3 type="string">Floppy</device3>
    </boot>
    <chassis>
    <asset_tag type="string">8437-8592-0329-9603-9215-1886-12</asset_tag>
    <serial_number type="string">9595-3600-2199-6834-7686-3927-30</serial_number>
    </chassis>
    <num_lock type="bool">False</num_lock>
    <version type="integer">2</version>
    </_ac6b8dc1-3257-4a70-b1b2-a9c9215659ad_>
    <_db8b9818-b4bb-4725-b99d-b4612716b6b4_>
    <version type="integer">0</version>
    </_db8b9818-b4bb-4725-b99d-b4612716b6b4_>
    <global_settings>
    <devices>
    <allow_reduced_fc_redundancy type="bool">False</allow_reduced_fc_redundancy>
    <generation_id type="string">883d11122d9b7b2c521be0c045ef3760</generation_id>
    <storage_allow_full_scsi_command_set type="bool">False</storage_allow_full_scsi_command_set>
    </devices>
    <disk_merge_pending type="bool">False</disk_merge_pending>
    <metrics>
    <devicetype>
    <deviceinstance>
    <guid type="string">B637F346-6A0E-4DEC-AF52-BD70CB80A21D</guid>
    <metric>
    <enabled type="bool">False</enabled>
    <lastcomputedtime type="integer">0</lastcomputedtime>
    <peaktime type="integer">0</peaktime>
    <poolid type="string"></poolid>
    <resourcetypeid type="string">B637F347-6A0E-4DEC-AF52-BD70CB80A21D</resourcetypeid>
    <starttime type="integer">0</starttime>
    <typecode type="string">3F6F1051-C8FC-47EF-9821-C07240848748;0</typecode>
    <value type="integer">0</value>
    </metric>
    </deviceinstance>
    <guid type="string">B637F346-6A0E-4DEC-AF52-BD70CB80A21D</guid>
    </devicetype>
    <devicetype>
    <deviceinstance>
    <guid type="string">4764334D-E001-4176-82EE-5594EC9B530E</guid>
    <metric>
    <enabled type="bool">False</enabled>
    <lastcomputedtime type="integer">0</lastcomputedtime>
    <peaktime type="integer">0</peaktime>
    <poolid type="string"></poolid>
    <resourcetypeid type="string">4764334E-E001-4176-82EE-5594EC9B530E</resourcetypeid>
    <starttime type="integer">0</starttime>
    <typecode type="string">394DCE66-458F-4895-AE56-41D7C9602A49</typecode>
    <value type="integer">0</value>
    </metric>
    <metric>
    <enabled type="bool">False</enabled>
    <lastcomputedtime type="integer">0</lastcomputedtime>
    <peaktime type="integer">0</peaktime>
    <poolid type="string"></poolid>
    <resourcetypeid type="string">4764334E-E001-4176-82EE-5594EC9B530E</resourcetypeid>
    <starttime type="integer">0</starttime>
    <typecode type="string">FF85EA46-9933-4436-BE5D-C96827399966</typecode>
    <value type="integer">0</value>
    </metric>
    <metric>
    <enabled type="bool">False</enabled>
    <lastcomputedtime type="integer">0</lastcomputedtime>
    <peaktime type="integer">0</peaktime>
    <poolid type="string"></poolid>
    <resourcetypeid type="string">4764334E-E001-4176-82EE-5594EC9B530E</resourcetypeid>
    <starttime type="integer">0</starttime>
    <typecode type="string">04BDF59E-580D-4441-8828-FFFE44472D2D</typecode>
    <value type="integer">0</value>
    </metric>
    </deviceinstance>
    <guid type="string">4764334D-E001-4176-82EE-5594EC9B530E</guid>
    </devicetype>
    <devicetype>
    <deviceinstance>
    <guid type="string">83F8638B-8DCA-4152-9EDA-2CA8B33039B4</guid>
    <metric>
    <enabled type="bool">False</enabled>
    <lastcomputedtime type="integer">0</lastcomputedtime>
    <peaktime type="integer">0</peaktime>
    <poolid type="string"></poolid>
    <resourcetypeid type="string">70BB60D2-A9D3-46AA-B654-3DE53004B4F8</resourcetypeid>
    <starttime type="integer">0</starttime>
    <typecode type="string">AD29978B-AAB6-44AE-81CD-0609BF929F18;0\0\L</typecode>
    <value type="integer">0</value>
    </metric>
    </deviceinstance>
    <guid type="string">83F8638B-8DCA-4152-9EDA-2CA8B33039B4</guid>
    </devicetype>
    </metrics>
    <owner>
    <sid type="string">S-1-5-21-1940488291-1951097212-1584025624-1392</sid>
    </owner>
    <power>
    <host_shutdown>
    <action type="integer">1</action>
    </host_shutdown>
    <host_startup>
    <action type="integer">1</action>
    </host_startup>
    </power>
    <snapshots>
    <list>
    <size type="integer">0</size>
    </list>
    </snapshots>
    <unexpected_termination>
    <action type="integer">1</action>
    </unexpected_termination>
    <vhd_path_acled type="bool">True</vhd_path_acled>
    </global_settings>
    <manifest>
    <size type="integer">11</size>
    <vdev001>
    <device type="string">58f75a6d-d949-4320-99e1-a2a2576d581c</device>
    <flags type="integer">1</flags>
    <instance type="string">58F75A6D-D949-4320-99E1-A2A2576D581C</instance>
    <name type="string">Microsoft Synthetic Mouse</name>
    </vdev001>
    <vdev002>
    <device type="string">197f74e3-b84b-46de-8ae6-82f1cd181cdc</device>
    <flags type="integer">1</flags>
    <instance type="string">197F74E3-B84B-46DE-8AE6-82F1CD181CDC</instance>
    <name type="string">Microsoft Synthetic Keyboard</name>
    </vdev002>
    <vdev003>
    <device type="string">f3cf6965-e8d3-44a9-9b7d-a04245ea7525</device>
    <flags type="integer">1</flags>
    <instance type="string">F3CF6965-E8D3-44A9-9B7D-A04245EA7525</instance>
    <name type="string">Microsoft Synthetic Video</name>
    </vdev003>
    <vdev004>
    <device type="string">84eaae65-2f2e-45f5-9bb5-0e857dc8eb47</device>
    <flags type="integer">1</flags>
    <instance type="string">84EAAE65-2F2E-45F5-9BB5-0E857DC8EB47</instance>
    <name type="string">Microsoft Heartbeat Component</name>
    </vdev004>
    <vdev005>
    <device type="string">2a34b1c2-fd73-4043-8a5b-dd2159bc743f</device>
    <flags type="integer">1</flags>
    <instance type="string">2A34B1C2-FD73-4043-8A5B-DD2159BC743F</instance>
    <name type="string">Microsoft Key-Value Pair Exchange Component</name>
    </vdev005>
    <vdev006>
    <device type="string">9f8233ac-be49-4c79-8ee3-e7e1985b2077</device>
    <flags type="integer">1</flags>
    <instance type="string">9F8233AC-BE49-4C79-8EE3-E7E1985B2077</instance>
    <name type="string">Microsoft Shutdown Component</name>
    </vdev006>
    <vdev007>
    <device type="string">2497f4de-e9fa-4204-80e4-4b75c46419c0</device>
    <flags type="integer">1</flags>
    <instance type="string">2497F4DE-E9FA-4204-80E4-4B75C46419C0</instance>
    <name type="string">Microsoft Time Synchronization Component</name>
    </vdev007>
    <vdev008>
    <device type="string">5ced1297-4598-4915-a5fc-ad21bb4d02a4</device>
    <flags type="integer">1</flags>
    <instance type="string">5CED1297-4598-4915-A5FC-AD21BB4D02A4</instance>
    <name type="string">Microsoft VSS Component</name>
    </vdev008>
    <vdev009>
    <device type="string">6c5addb9-a11a-4e8e-84cb-e6208201db63</device>
    <flags type="integer">1</flags>
    <instance type="string">6C5ADDB9-A11A-4E8E-84CB-E6208201DB63</instance>
    <name type="string">Microsoft RDV Component</name>
    </vdev009>
    <vdev010>
    <device type="string">2fc216b0-d2e2-4967-9b6d-b8a5c9ca2778</device>
    <flags type="integer">1</flags>
    <instance type="string">A80E9C62-750A-4A6B-9548-D46677E806BE</instance>
    <name type="string">Synthetic Ethernet Port</name>
    </vdev010>
    <vdev011>
    <device type="string">d422512d-2bf2-4752-809d-7b82b5fcb1b4</device>
    <flags type="integer">1</flags>
    <instance type="string">24984ED0-BDAD-4B90-82B2-5D59F874E91E</instance>
    <name type="string">Synthetic SCSI Controller</name>
    </vdev011>
    <version type="integer">260</version>
    </manifest>
    <properties>
    <global_id type="string">B37E54CD-FFBB-44DA-8B7C-322B922EAD72</global_id>
    <highly_available type="bool">False</highly_available>
    <last_powered_off_time type="integer">130493284127496105</last_powered_off_time>
    <last_powered_on_time type="integer">130493284065876653</last_powered_on_time>
    <last_state_change_time type="integer">130493284127496105</last_state_change_time>
    <name type="string">LegacyTS</name>
    <notes type="string"></notes>
    <type_id type="string">Virtual Machines</type_id>
    <version type="integer">1024</version>
    </properties>
    <settings>
    <global>
    <logical_id type="string">B37E54CD-FFBB-44DA-8B7C-322B922EAD72</logical_id>
    </global>
    <memory>
    <bank>
    <dynamic_memory_enabled type="bool">True</dynamic_memory_enabled>
    <limit type="integer">1048576</limit>
    <priority type="integer">5000</priority>
    <reservation type="integer">512</reservation>
    <size type="integer">4096</size>
    <target_memory_buffer type="integer">20</target_memory_buffer>
    </bank>
    <vnuma>
    <max_size_per_node type="integer">14770</max_size_per_node>
    </vnuma>
    </memory>
    <processors>
    <count type="integer">1</count>
    <features>
    <limit type="bool">False</limit>
    </features>
    <limit type="integer">100000</limit>
    <limit_cpuid type="bool">False</limit_cpuid>
    <reservation type="integer">0</reservation>
    <vnuma>
    <count_per_node>
    <max type="integer">4</max>
    </count_per_node>
    <node_per_socket>
    <max type="integer">1</max>
    </node_per_socket>
    </vnuma>
    <weight type="integer">100</weight>
    </processors>
    <stopped_at_host_shutdown type="bool">False</stopped_at_host_shutdown>
    <vnuma>
    <enabled type="bool">False</enabled>
    </vnuma>
    </settings>
    </configuration>
    If its relevant, the host is not yet activated license wise. I downloaded the demo version so I could test my idea before making a purchase to go ahead with full implementation. 
    As it stands right now I'm not sure how to troubleshoot this. Many searches on google have not turned up any helpful info. Does anyone have any ideas?
    Thanks,
    D

    Hi ,
    First , please refer to the supported guest OS of windows 2012 hyper-v :
    http://technet.microsoft.com/library/hh831531.aspx
    2003/R2 should be with sp2 and max 2 virtual processors .
    "'LegacyTS' was reset because an unrecoverable error occurred on a virtual processor that caused a triple fault."
    If the issue is not due to the above items , you can try to check the "CPU compatibility " in that VM settings for troubleshooting:
     Hope it helps
    Best Regards
    Elton Ji
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Compaq Notebook CQ-45 137TX fails to boot

    Hello,
    I own a Compaq CQ-45 137TX (Intel Core 2 Duo P7350, 3 GB RAM, 320GB HDD, nVidia GeForce 9200M GS, Windows 7(upgraded from Vista)) with a broken LCD Screen. Since repairing the screen made no sense for such an old laptop, I started using it as a desktop by attaching an external monitor and input devices. The computer worked fine for the past few months.
    Upon restarting the computer after a hiatus of a week or so, the computer failed to boot and display anything on the external monitor. I think it is failing POST.
    The laptop gives out multiple beeps continually (not continuous, multiple beeps that don't end).
    I thought that the RAM is faulty and tried to reboot the machine by trying one RAM stick at a time (since the laptop has two). It didn't work for either of the two sticks tried in both slots individually.
    I think both the RAM sticks may be faulty, however, I am unable to borrow a RAM stick to test on it.
    Before buying a new one, I would like someone to clarify or point out other hardware that may faulty in this laptop. I have had people tell me that my Graphic Card may have given up.
    Thank you for your assistance.

    Hello @root123 ,
    Welcome to the HP Forums!
    I understand you're unable to boot up your CQ-45 notebook.
    It's unlikely to be RAM if neither card worked in either of the two DIMM slots. It is possible that both cards or slots have failed, but highly unlikely.
    The beeping should tell you exactly what the error is. Try looking through this document which should help you identify the error: Computer Does Not Start and the LEDs Blink or the Computer Beeps.
    You may also want to try this document as well: Troubleshooting Black Screen Displays with No Error Messages During Startup or Boot.
    Let me know if you're able to identify the failure with the beep code and we'll go from there.
    Please click the "Kudos, Thumbs Up" at the bottom of this post if you want to say "Thanks" for helping!
    Please click "Accept as Solution" if you feel my post solved your issue, it will help others find the solution.
    The Great Deku Tree
    I work on behalf of HP.

  • Arch fails to boot after installation (BIOS mode)

    I finished my Arch installation, following the Beginner's Guide, and once I unmounted the partitions and rebooted, GRUB failed to boot into Arch. I'm not exactly sure what the problem is though. Basically what happens is I power on the machine, the Dell splash screen comes up, GRUB loads, I choose
    Arch Linux, with Linux core repo kernel
    the kernel and ramdisk attempt to load, then some message about "recovering journal" appears, and then I return back to the Dell splash screen. The same thing happens even if I choose the second option
    Arch Linux, with Linux core repo kernel (Fallback initramfs)
    However, when I choose to boot Win XP everything boots just fine. My apologies for the quality of the videos and pictures.
    Here's a video of what happens:
    http://youtu.be/uC96kX6iTjI
    I suspect this has to do with this error I got when I generated the "grub.cfg". Although I'm not entirely sure because my understanding is that this error would affect booting Win XP which in fact boots perfectly fine. 
    Error (and no I'm not using any lvm volumes)
    http://imgur.com/qqxpoGG
    I believe these are the portions of the "grub.cfg" that load Arch and Win XP. I got these by pressing "e" while on their menu entry in the GRUB bootloader.
    Arch (I had to scroll down to see the rest, hence two pictures)
    http://imgur.com/79dBw2C
    http://imgur.com/qusEfL0
    Win XP
    http://imgur.com/oLnLlT0
    Any idea how I can fix this? Any help is greatly appreciated and please be patient, I know, I'm a noob.
    * I'm not sure if this is of any significance but I had a problem very similar to this when trying to get the Arch install to boot via usb (this computer doesn't have CD/DVD drive). I solved it by following this excerpt from the Beginner's Guide.
    Troubleshooting boot problems
    If you are using an Intel video chipset and the screen goes blank during the boot process, the problem is likely an issue with Kernel Mode Setting. A possible workaround may be achieved by rebooting and pressing
    e
    over the entry that you are trying to boot (i686 or x86_64). At the end of the string type
    nomodeset
    and press
    Enter
    Here's a video of what it looked like:
    http://youtu.be/vXRcbU0zdto
    The computer specs:
    OS: Windows XP Professional 32 bit Version 2002 Service Pack 3
    CPU: Intel Pentium 4 @ 3.00 GHz
    RAM: 2 GB DDR2
    HDD: 80 GB

    Hi,
    why did you not try adding nomodeset with the regular boot? During the net-install no video drivers will be installed;
    you have to install them after reboot after installing xorg. The (video)problem you had with booting from usb is still
    present.

  • Both my backup drives show up, but fail to boot, staying in grey screen with spin wheel.

    I did some maintenance, copying lots of files, running Cocktail for the first time (failing to note exactly what I did) and after running Disk Warrior on both my bootable external drives (one OWC, one LaCie) they both hang in grey Apple screen with spinny wheel and never boot up, though both did earlier in the day, and have never failed to boot in years of service. Both appear on the desktop, show vertified in Disk Utility and booted up fine one day before all the maintenance. I don't know what Cocktail may have done, but it may have created a (now solved) problem for Photoshop 7, which crashed thereafter while loading, something that's only ever happened twice in six years. I managed to track down a TWAIN plug-in that had always been in Photoshop, something to do with scanning, but was now causing the crash. Anyhow, Photoshop is now working again, (after just removing that plug-in) but neither backup will boot up. Please don't suggest a system archive and install. I'm hoping for some miracle little file that once removed will restore the booting of the two externals. Your help is greatly appreciated. Please assume I am brain damaged and spell things out for the simple-minded. Thanks in advance.
    I hope BDAqua sees this.
    I only have one iBook, and it's less than half full; couldn't figure how to edit below that I'm now on 10.4.11. See what I mean?

    Since you are using your two external drives for booting, do you have clones on them?
    If so, why not simply update the clones? I'll bet they'd boot for you if you do that.
    I'll put out a call for BDAqua.

Maybe you are looking for

  • 7.0.2 monitor agent, linux, email

    How does the Linux monitor agent perform email notification? Have a complaint that not all events are being emailed, consistently.

  • InDesign CS6 & CC - form field PDF output very erratic, unusable, disappointing ...failure.

    Hi Until very recently, my workflow has been to add the form fields in Acrobat. However due to problems getting form fields to tag properly in this workflow the client has requested that the form fields be added in InDesign which on one page or very

  • Help understanding patch set 10.1.2.3.0

    Server: windows server 2003 OAS: 10.1.2.0.2 Installation Type Forms and Reports Services (only) Developer Suite: Forms [32 Bit] Version 10.1.2.0.2 (Production) My problem is I need to install this 10.1.2.3.0 patch to fix the "sticky cursor" issue. It

  • Cannot determine Internet graphics server on portal

    Hi Experts, We have installed BI server and EP (NW2004s). BI Java is installed on Portal. While running the BI query from WAD, with a template, only the tabular data is displayed and we are unable to display the graphs. There is an error message in p

  • JFileChooser "Cancel" option

    Hi, i would be happy if nebody could show me thru this problem.. actually,i'm making a dialog,which has a "finish" button..as soon as the user clicks on it,a file save dialog pops up ..the problem is if the user clicks on "Cancel",exceptions are gene