BOOTMGR image is corrupt, system cannot boot
Hey there! My english is not the best, but i'll try:
Maybe anyone can help me?
my laptop (HP 620) fell down. Nothing works anymore!
Failured ID: OLKWLM-00070E-XD6U3A-60R603
Produkt ID: WT 092EA#ABD
Hard disc drive capacity : 320 GB
Hard disc 1
Is there anything i can do by myself??
Thanks for your help!!
Hi Julo1907
This failure ID is a HDD error.
Error code: 303
More detailed: Hard Disk 1 Quick Test Failure
If you computer is under warranty I will recommend you to take contact to HP(I don't know if this work for a commercial computer)
Check you warranty here
A HDD error 303 can be 2 thing.
1. It can be a HDD error where the HDD is dead.
2. It can be a HDD controller on the moderboard there is broken or dead.
If it's out of warranty I will recommend you to replace your harddrive, since 9/10 times is it the HDD there are dead.
There is not much you can do about this error. Only get it repaired or replace the HDD by yourself.
Hope it answered your question
Best regards
Zincas
I work on behalf of HP
Similar Messages
-
DVD - bootmgr corrupt system cannot boot
Good afternnon,
the DVD cannot be used to run te set up - Vista Home Premium 64bit.
Once lunched a black screen shows only "bootmgr corrupt system cannot boot"
What I have to do? Is it possible to receive a new copy?
Thx
FD'Hi,
Can you test in another computer?
It seems this is related to your installation media. If so, it is recommended to try a good copy.
Alex Zhao
TechNet Community Support -
After updating kernel and ZFS modules, system cannot boot
Starting Import ZFS pools by cache file...
[ 4.966034] VERIFY3(0 == zap_lookup(ddt->ddt_os, ddt->ddt_spa->spa_ddt_stat_object, name, sizeof (uint64_t), sizeof (ddt_histogram_t) / sizeof (uint64_t), &hht->ddt_histogram[type][class])) failed (0 == 6)
[ 4.966100] PANIC at ddt.c:124:ddt_object_load()
[*** ] A start job is running for Import ZFS pools by cache (Xmin Ys / no limit)
And then occasionally I see
[ 240.576219] Tainted: P O 3.19.2-1-ARCH #1
Anyone else experiencing the same?Thanks!
I did the same and it worked... kind of. The first three reboots it failed (but did not stop the system from booting) producing:
zpool[426]: cannot import 'data': one or more devices is currently unavailable
systemd[1]: zfs-import-cache.service: main process exited, code=exited, status=1/FAILURE
The second boot also resulted in a kernel panic, but as far as I can tell unrelated to zfs.
After reboot one and three imported the pool manually.
From the fourth reboot on loading from cache file always succeeded. However, I it takes faily long (~8 seconds) and even shows
[*** ] A start job is running for Import ZFS pools by cache (Xmin Ys / no limit)
briefly. Altough I might only notice that because the recent updates sped up oder parts of the boot process. Did you observe a slowdown during boot time, too, kinghajj?
Last edited by robm (2015-03-22 01:21:05) -
System cannot boot after last update
I think that problem in display detection.
X server log file:
[ 26.434]
X.Org X Server 1.16.1
Release Date: 2014-09-21
[ 26.434] X Protocol Version 11, Revision 0
[ 26.434] Build Operating System: Linux 3.16.1-1-ARCH x86_64
[ 26.434] Current Operating System: Linux black 3.16.4-1-ARCH #1 SMP PREEMPT Mon Oct 6 08:22:27 CEST 2014 x86_64
[ 26.434] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=5db39538-f615-41e7-a67f-49b03b6a24be rw quiet
[ 26.434] Build Date: 21 September 2014 10:53:13AM
[ 26.435] (II) Module ABI versions:
[ 26.435] X.Org ANSI C Emulation: 0.4
[ 26.435] X.Org Video Driver: 18.0
[ 26.435] X.Org XInput driver : 21.0
[ 26.435] X.Org Server Extension : 8.0
[ 26.436] (EE) systemd-logind: failed to get session: PID 531 does not belong to any known session
[ 26.436] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 26.438] (--) PCI: (0:0:2:0) 8086:0122:1043:844d rev 9, Mem @ 0xfb400000/4194304, 0xb0000000/268435456, I/O @ 0x0000f000/64
[ 26.438] (--) PCI:*(0:1:0:0) 10de:0600:1043:8268 rev 162, Mem @ 0xfa000000/16777216, 0xc0000000/268435456, 0xf8000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/131072
[ 26.438] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 26.438] (II) LoadModule: "glx"
[ 26.438] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 26.447] (II) Module glx: vendor="NVIDIA Corporation"
[ 26.447] compiled for 4.0.2, module version = 1.0.0
[ 26.447] Module class: X.Org Server Extension
[ 26.447] (II) NVIDIA GLX Module 343.22 Thu Sep 11 15:55:13 PDT 2014
Is problem in xorg server or nvidia driver? I don't know what to do.Trilby wrote:
The system certainly boots - you just cant start X it would seem.
What was updated? How do you start X? Is that the full log, it looks like it has been cut off?
Yes, system starts but I can only work through ssh. Here is the last full log:
[ 26.918]
X.Org X Server 1.16.1
Release Date: 2014-09-21
[ 26.918] X Protocol Version 11, Revision 0
[ 26.918] Build Operating System: Linux 3.16.1-1-ARCH x86_64
[ 26.918] Current Operating System: Linux black 3.16.4-1-ARCH #1 SMP PREEMPT Mon Oct 6 08:22:27 CEST 2014 x86_64
[ 26.918] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=5db39538-f615-41e7-a67f-49b03b6a24be rw quiet
[ 26.918] Build Date: 21 September 2014 10:53:13AM
[ 26.918]
[ 26.919] Current version of pixman: 0.32.6
[ 26.919] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 26.919] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 26.919] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Oct 14 21:33:08 2014
[ 26.919] (==) Using config file: "/etc/X11/xorg.conf"
[ 26.919] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 26.919] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 26.919] (==) ServerLayout "Layout0"
[ 26.919] (**) |-->Screen "Screen0" (0)
[ 26.919] (**) | |-->Monitor "Monitor0"
[ 26.919] (**) | |-->Device "Device0"
[ 26.919] (**) |-->Input Device "Keyboard0"
[ 26.919] (**) |-->Input Device "Mouse0"
[ 26.919] (==) Automatically adding devices
[ 26.919] (==) Automatically enabling devices
[ 26.919] (==) Automatically adding GPU devices
[ 26.919] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 26.919] Entry deleted from font path.
[ 26.919] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/,
/usr/share/fonts/100dpi/,
/usr/share/fonts/75dpi/
[ 26.919] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 26.919] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 26.919] (WW) Disabling Keyboard0
[ 26.919] (WW) Disabling Mouse0
[ 26.919] (II) Loader magic: 0x818d80
[ 26.919] (II) Module ABI versions:
[ 26.919] X.Org ANSI C Emulation: 0.4
[ 26.919] X.Org Video Driver: 18.0
[ 26.919] X.Org XInput driver : 21.0
[ 26.919] X.Org Server Extension : 8.0
[ 26.920] (EE) systemd-logind: failed to get session: PID 543 does not belong to any known session
[ 26.920] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 26.921] (--) PCI: (0:0:2:0) 8086:0122:1043:844d rev 9, Mem @ 0xfb400000/4194304, 0xb0000000/268435456, I/O @ 0x0000f000/64
[ 26.921] (--) PCI:*(0:1:0:0) 10de:0600:1043:8268 rev 162, Mem @ 0xfa000000/16777216, 0xc0000000/268435456, 0xf8000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/131072
[ 26.921] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 26.921] (II) LoadModule: "glx"
[ 26.922] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 26.928] (II) Module glx: vendor="NVIDIA Corporation"
[ 26.928] compiled for 4.0.2, module version = 1.0.0
[ 26.928] Module class: X.Org Server Extension
[ 26.928] (II) NVIDIA GLX Module 343.22 Thu Sep 11 15:55:13 PDT 2014
[ 26.928] (II) LoadModule: "nvidia"
[ 26.928] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 26.928] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 26.928] compiled for 4.0.2, module version = 1.0.0
[ 26.928] Module class: X.Org Video Driver
[ 26.928] (II) NVIDIA dlloader X Driver 343.22 Thu Sep 11 15:34:47 PDT 2014
[ 26.928] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 26.928] (++) using VT number 7
[ 26.940] (II) Loading sub module "fb"
[ 26.940] (II) LoadModule: "fb"
[ 26.940] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 26.940] (II) Module fb: vendor="X.Org Foundation"
[ 26.940] compiled for 1.16.1, module version = 1.0.0
[ 26.940] ABI class: X.Org ANSI C Emulation, version 0.4
[ 26.940] (II) Loading sub module "wfb"
[ 26.940] (II) LoadModule: "wfb"
[ 26.940] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 26.941] (II) Module wfb: vendor="X.Org Foundation"
[ 26.941] compiled for 1.16.1, module version = 1.0.0
[ 26.941] ABI class: X.Org ANSI C Emulation, version 0.4
[ 26.941] (II) Loading sub module "ramdac"
[ 26.941] (II) LoadModule: "ramdac"
[ 26.941] (II) Module "ramdac" already built-in
[ 26.941] (WW) NVIDIA(0): The NVIDIA GeForce 8800 GTS 512 GPU installed in this system
[ 26.941] (WW) NVIDIA(0): is supported through the NVIDIA 340.xx Legacy drivers.
[ 26.941] (WW) NVIDIA(0): Please visit http://www.nvidia.com/object/unix.html for
[ 26.941] (WW) NVIDIA(0): more information. The 343.22 NVIDIA driver will ignore
[ 26.941] (WW) NVIDIA(0): this GPU. Continuing probe...
[ 26.941] (EE) No devices detected.
[ 26.941] (EE)
Fatal server error:
[ 26.941] (EE) no screens found(EE)
[ 26.941] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 26.941] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 26.941] (EE)
Thank you for your answer! -
Bootmngr mgr image is corrupt , the system cannot boot
the lap top had windows xp Media Center Edition
Model - hp pavilion dv 5040 us
This question was solved.
View Solution.Hey Charlie,
There is a few reason for this error message. It is possible that the hard drive has failed. I would first start with running the built in self test on the hard drive. Since this is a drive error it would be the best place to start. Follow the steps here on how to Perform a Hard drive self test
Let me know what this returns.
Thanks,
Sean
-------------How do I give Kudos? | How do I mark a post as Solved? -------------------------------------------------------- -
[SOLVED] Cannot boot from raid1 after upgrade
My system cannot boot from software raid(1) after upgrading the kernel to version 3.2.13-1. I realized then, that mkinitcpio.conf was overwritten (probably missed that in a previous upgrade). So I put back "mdadm" to HOOKS and "raid1" to MODULES. Unfortunately it didn't help. This is the boot-up screen:
Any ideas?
Last edited by dito (2012-03-28 13:10:52)Thank you for your answer. I replaced the mdadm hook with mdadm_udev and updated my mdadm.conf. Removing the hd configuration stuff from grub then finally did the trick. Works again!
-
Curve 8320 corrupts OS periodically and then cannot boot (blinking LED only)
I have a T-Mobile BB Curve 8320 that I've had for about 9 months, and I have what appears to be a recurring problem.
Three times now, the phone has corrupted its OS, and it will not boot. Each time it does it, the symptoms are first the phone is non responsive, and just shows the spinning hourglass cursor. The last time it did it while in the Mail app, which is the one I use almost exclusively. The phone appears to lock up, showing the wait cursor indefinitely. This time I waited a half hour, and it was clear that it wasn't coming back. So I pushed the power button, and it shut down the phone. But then when I tried to turn it back on, the screen never came up, and it just blinked the red LED "forever." (It was about 18-20 hours before I got around to trying to reload it.) The first time this happened was when the phone was running the OS version it shipped with, which I think was 4.3, but I don't recall. But now it has done it twice while running 4.5.0.81, which is the OS distribution T-Mobile makes available for the Curve.
The first two times it did it, I used the application loader to wipe the device and reload the OS. When in this state, BB desktop manager doesn't see the device since it can't boot. But if you click through to the application loader, you can get it to load. (Or you can run the application loader outside of BB desktop manager)
This time, the application loader started up, offered the choice of what to load, and then proceeded into the next phases. Erasing the device succeeds, as does the next phase where it loads the OS. But then it gets to where it is loading application modules, with a progress bar for each module and one for the overall progress. It got halfway through the overall progress, and failed with an "unspecified error", suggesting to try again. I tried it three times, and it failed the same way each time.
After calling T-Mobile, they bounced me over to RIM, and the first guy had me go through the app loader again with the same result. When he started pursuing USB connectivity issues, I asked to speak to someone else. (There are other devices on this system, both mass storage and input, and none of them ever show connectivity issues. )
The second tech had me rerun the application loader, but this time only select the core OS, leaving out all the apps. This succeeded, and then he had me rerun it, loading the rest of the applications. This also succeeded.
But the problem I still have is this. There is no explanation why the phone corrupts itself every couple of months, or why loading the OS and the applications in one step failed to work _repeatedly_. I believe the device has a bad memory address, and the two step OS load simply danced around it. And it is that which is causing the phone to corrupt its own OS to the point that it cannot boot.
The tech tried to pass of the corruption due to loading third party applications, and while I can accept that a rogue application can corrupt memory locations that it has the ability to write to, I don't know if the BB OS/device uses any form of protected memory, or if apps are essentially unrestrained. The only third party applications I load on this are the Google app, with Gmail, and Opera Mini.
To be honest, if the BB OS is that fragile that I can't even load these two applications on it, I'll be trading it for a different email capable phone.
Anyway, I'm looking to find if anyone else has a phone that repeatedly gets corrupted so it can't boot, and requires a complete reload. Also, is there anyway to test the memory on the phone? I'm going to call T-Mobile back and try to get them to swap my phone, because I can't afford to spend three hours on the phone with tech support every couple of months when my phone dies.
thanks!Thanks for the reply. Our cases sound a bit different. I seldom use Desktop Manager, as I sync through BES. I do use it for backup though.
But over the time my phone corrupting itself has happened, I've upgraded from BB OS 4.3 to 4.5, which required an update to Desktop Manager, and following that I upgraded to a new computer. So I've changed computers, BB Desktop software, and BB OS software, and the problem has happened across all of those changes.
You should have been able to restore the OS even if it was corrupt. Desktop Manager won't recognize the device if it won't boot, but application loader will still find it. The first two times I did it, I used instructions basically like this: http://crackberry.com/blackberry-101-lecture-12-how-reload-operating-system-nuked-blackberry?page=4
But since then I've found I can just access application loader via BB Desktop Manager and do the same thing. I did notice when my OS reload kept failing this last time, that using application loader directly showed more of the failure message. It still wasn't anything useful, but when I reran the reload via Desktop Manager, I recognized the error was the same, but noted that I didn't see all of the output of the standalone application loader. -
A library on my hard drive became corrupted, so I over-wrote it from an external hard drive. When I now access the library on my hard drive, many of the images are vertical, and cannot be rotated other than one at a time. Ideas to correct this?
You had already done "Repair" and "Rebuild"? These usually takes scores of minutes or hours.
Does the Library on your external drive work from the external drive? Navigate to it in Finder and double-click the name.
If it does, delete the problem Library, empty the System Trash, reboot, Verify your system disk using Disk Utility (and might as well repair permissions while you're at it), reboot, test the external drive Library once more to confirm it works properly, then close it and copy the Library to your system drive. When the copying is done, double-click the Library (now on the system drive) and see what you get. -
MOVED: Windows cannot boot because of missing/corrupt hal.dll! Help!
This topic has been moved to Operating Systems.
Windows cannot boot because of missing/corrupt hal.dll! Help!Hi,
make sure you have disconnected all non-essential external devices (printers, scanners, external harddisk) prior to installing BootCamp Windows.
Leave only mouse, keyboard and display connected.
Make sure that your XP CD is either retail or OEM/systemBuilder version and not a manufacturer-bundled one.
Also make sure that the CD is 'clean' (no dust, no scratches, etc.).
Use the BootCamp Assistant to revert back to one single OSX volume.
Use OSX Disk Utility to Verify your harddisk and repair permissions.
Retry the XP installation from scratch.
Generally using NTFS is more likely to not getting the 'missing hal.dll' error.
Stefan -
Cannot boot....BIOS Corrupted ?
I have a lenovo 3000 Q, machine type 10003 Model Number 57054161 S/N SSxxxxxxxx M701W07, previously I change the motherboard and when it boot up it has this message invalid cpu serial number and error 00 something, but pressing enter to continue boot seem ok. But now I cannot boot the pc and cannot enter BIOS setup.
After the message usually I just press enter to continue, and it will boot up. Now it seem to stuck forever. Even pressing F1 to go to the BIOS also stuck at entering setup forever. Is the BIOS corrupted? I try to clear the BIOS by jumper pin, did not solved the problem. Searching for BIOS update / firmware for this type of PC on all over the internet did not find any BIOS firmware. It quite difficult to get info for this PC type with all the jumble up info at IBM and lenovo site.
Is there anyway to get this PC alive again ?
Moderator Note; s/n edited for members own protectionAlready done that , I take out the battery for more than 3 days, and jump the clear CMOS jumper, but still when pressing F1, it stuck at Entering setup.
More detail on the boot up.
It come up with the ThinkCenter logo, Intel and Phoneix logo, then
ERROR 00CE Machine Type and Serial Number are Invalid!
Update the BIOS to correct this problem
System is starting
(To interrupt normal startup, press ENTER)
-- Usually this will boot up to the operating system, but not it stuck forever.
-- Pressing ESC will bring the boot up screen. It shows the :-
Phoenix TrustedCore(tm) Desktop SP2 for ThinkCenter.U
Copyright......
Lenovo Copyright.....
CPU Information
RAM Infromation
L2 cache info
There is no info regarding the hard disk or the cdrom drive although both of them are there and connected.
At the lower leff bottom stated Press F1 for Setup
Pressing F1 will change it to Entering Setup..... and stuck there forever.
Is there any way to fixed this ? Can I update the bios for this PC ? If can how, coz I cannot access the OS and where in the world that I can get the current BIOS for this PC, searching on the intenet did not found one. and to change the motherboard
is like buying a new computer.
Is there a reason that the boot up sequence did not detect the hard disk and the cdrom. the hard disk is sata 500GB and the cdrom is an ide cdrom that come with the PC.
Hopefully someone can shade a light on this problem.
Rgds
Din -
System Image Utility fails to create boot image
I am not able to successfully build a boot image with the System Image Utility. The build starts and runs for about 1 minute and then I get 100's of ditto messages saying "No space left on device". There's plenty of space left on the device. Eventually I get a GUI message stating the there was an error creating the image. The image is of course unusable. This only happens on a Boot image. I have no problem making an install image from the same source. Is it just me??
Xserve G5 Dual Mac OS X (10.4.5)I had simililar problems with much headscratching as the result.
I found that whenever I tried to create a boot image with System Image Utility (SIU) using an image file of my existing system as the source SIU would fail with the annoying "No space left on device" message everytime. I did a little investigating and found that SIU always created a 400 MB disk image file to copy to. So the error message was correct as my source was way over 4 GB.
I checked the manual and found the embarrasingly simple solution. It's not mentioned directly, rather it is stated that when you want to create an boot image from an existing system you should boot the machine containing the desired system on disk from an alternate source and the run SIU on that machine. The "trick" is that you're running SIU with the existing system mounted as a disk.
So I went back to my Xserve, mounted the image so it appeared on the desktop. Ran SIU and chose the mounted volume as the source instead of the image file, and hey presto!
MacBook Pro, Xserve, eMac, iMac... any Mac I can get my hands on Mac OS X (10.4.6) -
Lucreate - Cannot make file systems for boot environment
Hello!
I'm trying to use LiveUpgrade to upgrade one "my" Sparc servers from Solaris 10 U5 to Solaris 10 U6. To do that, I first installed the patches listed on [Infodoc 72099|http://sunsolve.sun.com/search/document.do?assetkey=1-9-72099-1] and then installed SUNWlucfg, SUNWlur and SUNWluufrom the S10U6 sparc DVD iso. I then did:
--($ ~)-- time sudo env LC_ALL=C LANG=C PATH=/usr/bin:/bin:/sbin:/usr/sbin:$PATH lucreate -n S10U6_20081207 -m /:/dev/md/dsk/d200:ufs
Discovering physical storage devices
Discovering logical storage devices
Cross referencing storage devices with boot environment configurations
Determining types of file systems supported
Validating file system requests
Preparing logical storage devices
Preparing physical storage devices
Configuring physical storage devices
Configuring logical storage devices
Analyzing system configuration.
Comparing source boot environment <d100> file systems with the file
system(s) you specified for the new boot environment. Determining which
file systems should be in the new boot environment.
Updating boot environment description database on all BEs.
Searching /dev for possible boot environment filesystem devices
Updating system configuration files.
The device </dev/dsk/c1t1d0s0> is not a root device for any boot environment; cannot get BE ID.
Creating configuration for boot environment <S10U6_20081207>.
Source boot environment is <d100>.
Creating boot environment <S10U6_20081207>.
Creating file systems on boot environment <S10U6_20081207>.
Creating <ufs> file system for </> in zone <global> on </dev/md/dsk/d200>.
Mounting file systems for boot environment <S10U6_20081207>.
Calculating required sizes of file systems for boot environment <S10U6_20081207>.
ERROR: Cannot make file systems for boot environment <S10U6_20081207>.So the problem is:
ERROR: Cannot make file systems for boot environment <S10U6_20081207>.
Well - why's that?
I can do a "newfs /dev/md/dsk/d200" just fine.
When I try to remove the incomplete S10U6_20081207 BE, I get yet another error :(
/bin/nawk: can't open file /etc/lu/ICF.2
Quellcodezeilennummer 1
Boot environment <S10U6_20081207> deleted.I get this error consistently (I ran the lucreate many times now).
lucreate used to work fine, "once upon a time", when I brought the system from S10U4 to S10U5.
Would anyone maybe have an idea about what's broken there?
--($ ~)-- LC_ALL=C metastat
d200: Mirror
Submirror 0: d20
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 31458321 blocks (15 GB)
d20: Submirror of d200
State: Okay
Size: 31458321 blocks (15 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c1t1d0s0 0 No Okay Yes
d100: Mirror
Submirror 0: d10
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 31458321 blocks (15 GB)
d10: Submirror of d100
State: Okay
Size: 31458321 blocks (15 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c1t0d0s0 0 No Okay Yes
d201: Mirror
Submirror 0: d21
State: Okay
Submirror 1: d11
State: Okay
Pass: 1
Read option: roundrobin (default)
Write option: parallel (default)
Size: 2097414 blocks (1.0 GB)
d21: Submirror of d201
State: Okay
Size: 2097414 blocks (1.0 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c1t1d0s1 0 No Okay Yes
d11: Submirror of d201
State: Okay
Size: 2097414 blocks (1.0 GB)
Stripe 0:
Device Start Block Dbase State Reloc Hot Spare
c1t0d0s1 0 No Okay Yes
hsp001: is empty
Device Relocation Information:
Device Reloc Device ID
c1t1d0 Yes id1,sd@THITACHI_DK32EJ-36NC_____434N5641
c1t0d0 Yes id1,sd@SSEAGATE_ST336607LSUN36G_3JA659W600007412LQFN
--($ ~)-- /bin/df -k | grep md
/dev/md/dsk/d100 15490539 10772770 4562864 71% /Thanks,
MichaelHello.
(sys01)root# devfsadm -Cv
(sys01)root# To be on the safe side, I even rebooted after having run devfsadm.
--($ ~)-- sudo env LC_ALL=C LANG=C lustatus
Boot Environment Is Active Active Can Copy
Name Complete Now On Reboot Delete Status
d100 yes yes yes no -
--($ ~)-- sudo env LC_ALL=C LANG=C lufslist d100
boot environment name: d100
This boot environment is currently active.
This boot environment will be active on next system boot.
Filesystem fstype device size Mounted on Mount Options
/dev/md/dsk/d100 ufs 16106660352 / logging
/dev/md/dsk/d201 swap 1073875968 - -In the rebooted system, I re-did the original lucreate:
<code>--($ ~)-- time sudo env LC_ALL=C LANG=C PATH=/usr/bin:/bin:/sbin:/usr/sbin:$PATH lucreate -n S10U6_20081207 -m /:/dev/md/dsk/d200:ufs</code>
Copying.
*{color:#ff0000}Excellent! It now works!{color}*
Thanks a lot,
Michael -
Cannot boot in Windows 8.1 anymore (after making some changes in both systems)
Problem: I cannot boot in the Windows 8.1 partition created with Bootcamp anymore. When I try to do that, the system displays the grey screen then goes into a command line mode similar with MS-DOS and asks for inserting a disk (it reports no bootable drive).
Possible causes:
- I disabled the Bootcamp process in the Notification area in the Windows 8.1 systray
- I created a new partition in OS X on which I installed an older OS X version I still need to use (Mt Lion)BroFlav wrote:
Can you tell me what exactly I should do in gdisk after merging the OS X partitions with their respective Recovery partitions?
Thanks, in advance.
Once you have EFI, Yosemite HD, Lion HD and Bootcamp, use the following steps. Your values will be different then this example. Use defaults except the boot ability flag for the last Bootcamp partitions to be 'y'.
sudo gdisk /dev/disk0
GPT fdisk (gdisk) version 0.8.10
Warning: Devices opened with shared lock will not have their
partition table automatically reloaded!
Partition table scan:
MBR: hybrid
BSD: not present
APM: not present
GPT: present
Found valid GPT with hybrid MBR; using GPT.
Command (? for help): p
Disk /dev/disk0: 490234752 sectors, 233.8 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 59BDFEEB-1EB4-4529-94FE-3CBC2C3CD513
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 490234718
Partitions will be aligned on 8-sector boundaries
Total free space is 2604 sectors (1.3 MiB)
Number Start (sector) End (sector) Size Code Name
1 40 409639 200.0 MiB EF00 EF
2 409640 401060383 191.0 GiB AF05 Macintosh HD
3 401060384 402329919 619.9 MiB AB00 Re
4 402331648 490233848 41.9 GiB 0700 Microsoft basic data
Command (? for help): r
Recovery/transformation command (? for help): h
WARNING! Hybrid MBRs are flaky and dangerous! If you decide not to use one,
just hit the Enter key at the below prompt and your MBR partition table will
be untouched.
Type from one to three GPT partition numbers, separated by spaces, to be
added to the hybrid MBR, in sequence: 2 3 4
Place EFI GPT (0xEE) partition first in MBR (good for GRUB)? (Y/N): y
Creating entry for GPT partition #2 (MBR partition #2)
Enter an MBR hex code (default AF): AF
Set the bootable flag? (Y/N): n
Creating entry for GPT partition #3 (MBR partition #3)
Enter an MBR hex code (default AB): AB
Set the bootable flag? (Y/N): n
Creating entry for GPT partition #4 (MBR partition #4)
Enter an MBR hex code (default 07): 07
Set the bootable flag? (Y/N): y
Recovery/transformation command (? for help): w
Final checks complete. About to write GPT data. THIS WILL OVERWRITE EXISTING
PARTITIONS!!
Do you want to proceed? (Y/N): y
OK; writing new GUID partition table (GPT) to /dev/disk0.
Warning: Devices opened with shared lock will not have their
partition table automatically reloaded!
Warning: The kernel may continue to use old or deleted partitions.
You should reboot or remove the drive.
The operation has completed successfully.
Now Reboot and verify the output of fdisk again. -
W540 BIOS update to 2.18 cannot boot to any operating system
i try to update the BIOS of thinkpad w540 to BIOS version 2.18.
Everything seems to work fine and it says to me the update is flashed.
But now, when my w540 boots, it does everything as normal but when starting to load the operatig system it power off and reboot and do this again and again.
I can enter the BIOS setup and the version is the updated one (2.18)
I can change in the BIOS options and i can choose from where my w540 boots. i try to boot from the HD, a CD, a flash but no use (using Windows 7 on HD and Linux from flash and ESXi from CD).
My Problem, i cannot boot to any operating system now.
Any one can help please, Thanks.
Solved!
Go to Solution.Thank U ALOT Richk, i do what U say and also before that i restore the default bios setting and restor the keys to the factory settings. i write this as it may help some one another.
Again Thank U ALOT Richk. -
MDT2012 - Deployment failed, the system cannot find the file specified
Hi everybody.
First, excuse me for my english, i think it's not the best thing I'm able to do, but now, I REALLY need help.
I encounter issues with my MDT 2012 Update 1 platform.
I have 5 systems to capture. All systems have 3 partitions (System, softwares, data). Capture is working fine for all parts.
In my Task Sequence, to deploy these images (C, D and E parts), I use a script after the "Install Operating System" which runs imagex to deploy the WIM images for D: and E:.
The script is the following :
"%DeployRoot%\Tools\x64\imagex" /apply "%DeployRoot%\Operating Systems\D_Drive\D_Drive.wim" 1 %DDrive%"
But, for some images, the task fails on the "D" drive deployement. The wizard shows the following error :
Litetouch deployment dailed, return code = -214767259 0x80004005
Failed to run the action: InstallD (ie : the script above)
The system cannot find the file specified. (Error: 00000002; Source: Windows)
The error is on my task which uses imagex to deploy my D and E WIM.
So I looked to see if the file's path was the good one.
And it is !!!
Wizard says that the file couldn't be find, but the file is existing, and in the good path.
For your information, there is no problem when I don't use multicast. Everything is working fine on unicast, not on multicast.
I even encounter this issue if I use my MDT server and my computers on the same switch.
Any help would be gratefull, my client gives me the week to resolve the issue.
ThanksBDD.LOG
<![LOG[Microsoft Deployment Toolkit version: 6.1.2373.0]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log.]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Write all logging text to \\192.168.36.208\Logs$]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Validating connection to \\192.168.36.208\Logs$]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Already connected to server 192.168.36.208 as that is where this script is running from.]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Will boot into Windows PE architecture x64 to match OS being deployed.]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[OSDTargetDriveCache was determined earlier : V:]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Property OSDTargetDriveCache is now = V:]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Property OSDisk is now = V:]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Open Control File: OperatingSystems]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[------ Applying Windows image using ImageX.exe ------]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[LTI applying image \\192.168.36.208\MDT$\Operating Systems\Master 3 avec Sysprep\CAPT.wim using ImageX]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Event 41023 sent: LTI applying image \\192.168.36.208\MDT$\Operating Systems\Master 3 avec Sysprep\CAPT.wim using ImageX]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Property SourcePath is now = \\192.168.36.208\MDT$\Operating Systems\Master 3 avec Sysprep]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Multicast transfer to directory: C:\MININT\Operating Systems\Master 3 avec Sysprep]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[<Message containing password has been suppressed>]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Command has been started (process ID 1348)]LOG]!><time="16:53:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ZTI Heartbeat: command has been running for 0 minutes (process ID 1348)]LOG]!><time="16:53:57.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Event 41003 sent: ZTI Heartbeat: command has been running for 0 minutes (process ID 1348)]LOG]!><time="16:53:57.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console >
]LOG]!><time="16:53:57.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Transfer Started.
]LOG]!><time="16:53:57.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ZTI Heartbeat: command has been running for 5 minutes (process ID 1348)]LOG]!><time="16:58:01.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Event 41003 sent: ZTI Heartbeat: command has been running for 5 minutes (process ID 1348)]LOG]!><time="16:58:01.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console >
]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Transfer Complete [0x0].]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Return code from command = 0]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Multicast transfer of "\\192.168.36.208\MDT$\Operating Systems\Master 3 avec Sysprep\CAPT.wim" to "C:\MININT\Operating Systems\Master 3 avec Sysprep\CAPT.wim" completed successfully.]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply"
context="" type="1" thread="" file="LTIApply">
<![LOG[Cleaning off old operating system]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Skipping V:\Drivers]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[New ZTIDiskPartition : \\MININT-1H9O4H6\root\cimv2:Win32_LogicalDisk.DeviceID="V:" \\MININT-1H9O4H6\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0"]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply"
context="" type="1" thread="" file="LTIApply">
<![LOG[Enabling 8dot3 name support on volume V:]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[About to run command: "\\192.168.36.208\MDT$\Tools\X64\imagex.exe" /apply "C:\MININT\Operating Systems\Master 3 avec Sysprep\CAPT.wim" 1 V:]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread=""
file="LTIApply">
<![LOG[Command has been started (process ID 536)]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > ImageX Tool for Windows]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Copyright (C) Microsoft Corp. All rights reserved.]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Version: 6.1.7600.16385]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ 0% ] Applying progress ]LOG]!><time="17:00:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ 0% ] Applying progress ]LOG]!><time="17:00:49.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ 1% ] Applying progress ]LOG]!><time="17:00:49.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ 2% ] Applying progress ]LOG]!><time="17:00:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ 3% ] Applying progress ]LOG]!><time="17:00:58.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ 4% ] Applying progress: 5:28 mins remaining ]LOG]!><time="17:01:03.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ 5% ] Applying progress: 5:33 mins remaining ]LOG]!><time="17:01:07.000+000"
<![LOG[ Console > [ 99% ] Applying progress: 3 secs remaining ]LOG]!><time="17:06:43.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > [ 100% ] Applying progress ]LOG]!><time="17:06:50.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Successfully applied image.]LOG]!><time="17:06:51.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Total elapsed time: 6 min 7 sec]LOG]!><time="17:06:51.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Return code from command = 0]LOG]!><time="17:06:51.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Property LTIDirtyOS is now = TRUE]LOG]!><time="17:06:51.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[The image C:\MININT\Operating Systems\Master 3 avec Sysprep\CAPT.wim was applied successfully.]LOG]!><time="17:06:51.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Event 5625 sent: The image C:\MININT\Operating Systems\Master 3 avec Sysprep\CAPT.wim was applied successfully.]LOG]!><time="17:06:51.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[About to run command: "\\192.168.36.208\MDT$\Tools\X64\bootsect.exe" /nt60 V:]LOG]!><time="17:06:52.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Command has been started (process ID 1252)]LOG]!><time="17:06:52.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Target volumes will be updated with BOOTMGR compatible bootcode.
]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console >
]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > V: (\\?\Volume{2ab15dec-99c9-19e3-baf6-94de80bab573})
]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console >
]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Successfully updated NTFS filesystem bootcode.
]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console >
]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Bootcode was successfully updated on all targeted volumes.
]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Return code from command = 0]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Find the boot drive (if any) [True] [6.1.7601.18229] [False]]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[New ZTIDiskPartition : \\MININT-1H9O4H6\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0" \\MININT-1H9O4H6\root\cimv2:Win32_LogicalDisk.DeviceID="V:"]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply"
context="" type="1" thread="" file="LTIApply">
<![LOG[New ZTIDisk : \\MININT-1H9O4H6\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Found bootable drive (No Boot File Test) [ V: ]: \\MININT-1H9O4H6\root\cimv2:Win32_LogicalDisk.DeviceID="V:"]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Ready to Prepare boot partition: V:]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[About to run command: cscript.exe //nologo "\\192.168.36.208\MDT$\Scripts\ztiRunCommandHidden.wsf" ""\\192.168.36.208\MDT$\Tools\X64\BCDBoot.exe" V:\windows /l fr-fr /s V:"]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="LTIApply"
context="" type="1" thread="" file="LTIApply">
<![LOG[Microsoft Deployment Toolkit version: 6.1.2373.0]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
<![LOG[The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG. For task sequence failures, please consult this log.]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="ztiRunCommandHidden" context="" type="1" thread=""
file="ztiRunCommandHidden">
<![LOG[Write all logging text to \\192.168.36.208\Logs$]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
<![LOG[Validating connection to \\192.168.36.208\Logs$]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
<![LOG[Already connected to server 192.168.36.208 as that is where this script is running from.]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
<![LOG[About to run command: \\192.168.36.208\MDT$\Tools\X64\BCDBoot.exe V:\windows /l fr-fr /s V:]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
<![LOG[Command has been started (process ID 1984)]LOG]!><time="17:06:54.000+000" date="02-19-2014" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
<![LOG[ Console > Boot files successfully created.]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
<![LOG[Return code from command = 0]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="ztiRunCommandHidden" context="" type="1" thread="" file="ztiRunCommandHidden">
<![LOG[Command has returned: 0]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Run Command: X:\WINDOWS\SYSTEM32\bcdedit.exe /Store "V:\boot\bcd" /timeout 0]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[BCD> The operation completed successfully.]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[BCDEdit returned ErrorLevel = 0]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Created scratch folder.]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Copy File: C:\MININT\unattend.xml to V:\Windows\Panther\Unattend.xml]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Copied unattend.xml to V:\Windows\Panther for image apply.]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[About to run command: dism.exe /Image:V:\ /Apply-Unattend:V:\Windows\Panther\Unattend.xml /ScratchDir:C:\MININT\Scratch]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Command has been started (process ID 1516)]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Deployment Image Servicing and Management tool]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Version: 6.1.7600.16385]LOG]!><time="17:06:55.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > Image Version: 6.1.7600.16385]LOG]!><time="17:06:56.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[ Console > The operation completed successfully.]LOG]!><time="17:06:57.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Return code from command = 0]LOG]!><time="17:06:57.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[LTIApply processing completed successfully.]LOG]!><time="17:06:57.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Event 41001 sent: LTIApply processing completed successfully.]LOG]!><time="17:06:57.000+000" date="02-19-2014" component="LTIApply" context="" type="1" thread="" file="LTIApply">
<![LOG[Command completed, return code = -2147467259]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Litetouch deployment failed, Return Code = -2147467259 0x80004005]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">
<![LOG[Event 41014 sent: Litetouch deployment failed, Return Code = -2147467259 0x80004005]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[For more information, consult the task sequencer log ...\SMSTS.LOG.]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property RetVal is now = -2147467259]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Validating connection to \\192.168.36.208\Logs$]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Already connected to server 192.168.36.208]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[OSDTargetDriveCache was determined earlier : V:]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property OSDTargetDriveCache is now = V:]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property OSDisk is now = V:]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\LiteTouch.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\LiteTouch.log]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\LTIApply.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\LTIApply.log]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\LTICopyScripts.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\LTICopyScripts.log]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\PnpEnum.xml to \\192.168.36.208\Logs$\MININT-1H9O4H6\PnpEnum.xml]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\Wizard.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\Wizard.log]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\ZTIBDE.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\ZTIBDE.log]LOG]!><time="17:10:54.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\ZTIConfigure.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\ZTIConfigure.log]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\ZTIDiskpart.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\ZTIDiskpart.log]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\ZTIDrivers.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\ZTIDrivers.log]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\ZTIGather.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\ZTIGather.log]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\ZTINextPhase.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\ZTINextPhase.log]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\ZTIPatches.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\ZTIPatches.log]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\ztiRunCommandHidden.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\ztiRunCommandHidden.log]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying C:\MININT\SMSOSD\OSDLOGS\ZTIValidate.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\ZTIValidate.log]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG to \\192.168.36.208\Logs$\MININT-1H9O4H6\SMSTS.LOG]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying X:\WINDOWS\Debug\Netsetup.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying X:\WINDOWS\System32\wpeinit.log to \\192.168.36.208\Logs$\MININT-1H9O4H6\]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Copying log C:\MININT\SMSOSD\OSDLOGS\BDD.log contents to \\192.168.36.208\Logs$\MININT-1H9O4H6\BDD.LOG]LOG]!><time="17:10:55.000+000" date="02-19-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
Maybe you are looking for
-
Goods receipt by using Vl31N for production order.
Hi we can do Goods receipt by using inbound delivery VL31N, with confirmation control key in PO, for purchase orders. I want to do Goods receipt using Inbound delivery( VL31N), this is my requirement. how to do it.
-
I can't get my volume to work and have tried everything! Anyone know anything else I can try I really don't want to send it in if I don't have 2!
-
Download mangers not working in firefox 4
I tried both download managers and neither works. I tried downloading different things, like software and videos, and both times they went straight to desktop. Am I supposed to change something to get the download manager to automatically download al
-
How can I output audio to a different output than video?
I am using STP to do some ADR work and I am having the following issue: Whenever I play back my material which has a 720p video track, both the audio and the video go out of my Kona LHe. I want to be able to separate the audio to go to a different ha
-
After watching a movie from tunes i can not watch a second one without restart apple tv
After I have watched a movie played via Itunes on my computer I have to restart the Aplle tv because the second movie would not load. Spinning wheel!