Recreating /boot?

I have two Arch linux installations, and /boot was on a separate partition. Unfortunately my sister installed Ubuntu on the computer and over-wrote the /boot partition, and now the GRUB menu is messed up, with several duplicate entries that all end up booting Ubuntu (even though they say /dev/sda3, /dev/sda4 where my arch installs exist.)
I've been configuring GRUB for a while now and can't get back into Arch. It appears that I need copies of the vmlinuz and init files, which have been over-written. How do I restore my precious Arch installs?

*Uh* idiot moment. I was trying to chroot with the ubuntu live disc.
Ok, I'm at the stage where I'm chrooted into Arch and I'm ready to run mkinitcpio. Obviously I need to get the kernel images from somewhere. I don't know what I need to mount under /boot/ to give appropriate images for the mkinitcpio command to work (damn, I don't even know where the Live CD is in /dev/)
At the moment I get "ERROR invalid kernel specifier: 'boot/vmlinuz-linux'"
Last edited by Bardwise (2012-07-01 16:49:44)

Similar Messages

How to "Recreate Boot Camp"?

I have just upgraded Snow Leopard to Mountain Lion.
I also had to upgrade VM Ware Fusion to 5.0.
Now, when I attempt to run VM Ware Fusion I get the following message:
Your Boot Camp installation has been modified since you last accessed it.
Move the Boot Camp virtual machine to the trash then select "Run Boot Camp" to recreate it. This will not affect the Windows applications or data on your Boot Camp partition.
I have dragged the Boot Camp virtual machine to the trash but I don't understand what is meant by "...select "Run Boot Camp" to recreate it".
Select "Run Boot Camp" from where?
I have tried shutting down the computer and booting from the Boot Camp partition, shutting down again, restarting normally and attempting to run VM Ware Fusion again but I get the same message (above).

I had the same problem upgrading from VMware 5.0.0 to 5.0.4 with Mavericks. I found the message from Fussion a long way short of helpful and this forum much more so.
I would add that witn VMware Fussion running choose Virtual Machine Library from the Window menu tab and from there delte the Boot Campl viritual machine and create (add) a new one. I did not have to reinstall windows or any applications.
I'm sure VMware could make this more obvious in their upgrade process.

Upgrade to SCCM R2 have to recreate boot image and TS

Wanna ask, I have upgraded from my SCCM from SP1 CU3 to R2. But i noticed that in boot image, the WinPE tab is missing thus i cannot include the network driver. Anyway that i can make the tab reappear again? Net says have to recreate the boot image and TS...
http://www.deploymentresearch.com/Research/tabid/62/EntryId/117/A-Geeks-Guide-for-upgrading-to-ConfigMgr-2012-R2-and-MDT-2013.aspx

This often happens after R2 upgrade. If your boot image does not have 6.3.9600 version then you will not be able to manipulate it using the R2 console. You don't need MDT to create a new one though (this new version).
You can use dism. See here. It's very easy. I had to do it yesterday.
http://www.niallbrady.com/2013/10/09/how-can-i-manually-add-winpe-5-boot-images-to-system-center-2012-configuration-manager-sp1-cu3/
http://myitforum.com/myitforumwp/2013/08/01/how-to-create-configmgr-2012-boot-images-from-scratch/
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Boot Image properties...tabs missing

I updated our SCCM system to R2 yesterday...today when I went in to edit a boot image I no longer see the "drivers" tab...it seems like there are other tabs missing as well, just can't remember. Don't know how to add drivers to a boot image
now.
Server 2008 R2
SCCM 2012 R2

This is a common problem. It came up on the forum yesterday as well.
http://social.technet.microsoft.com/Forums/en-US/a42ab116-63f1-431b-a42c-f31f2bdf0896/upgrade-to-sccm-r2-have-to-recreate-boot-image-and-ts?forum=configmanagergeneral
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Dell Laptops E7440 & E7240 - Issues with connecting to MDT 2012 deployment share

Hi,
Good afternoon.Need help on this please
-Test laptops Iam using are 2 * E7440 and 1*E7240. One laptop of model E7440 has our image installed and other two (1*E7440 & 1*E7240) are shipped from Dell with default Win 7 64 bit OS.
-Test desktops Iam using are Dell Optiplex 3020 & Dell 3010 . Both models have our own images of Win 7 64 Bit.
-Laptops and desktops are on same network .
-For OS deployments we have MDT 2012.
-While there are no issues with desktops, all the laptops mentioned above don’t connect to MDT deployments share . The detailed error message I get when I run a litetouch ISO is ‘A connection to the deployment share could not be made. Connection OJ.Possible
cause:invalid credentials. Retry : Try again to connect to the deployment share.’
-Have injected all possible network & storage drivers mentioned by Dell & Intel into MDT boot image but the problem still persists. Still WinPE doesn’t detect network adapter wherein IPaddresses are not picked in WinPE mode.
-Have been testing each and every driver by manually loading them into Winpe mode to see if they pick up the IP addresses and I finally found one driver by name ‘e1d63x64.inf ‘ which I downloaded directly from Intel website. This one is picking IP Address
in WinPE mode when loaded manually. Also have tested the connectivity to MDT server in WinPE mode with net use command and it was successful.
Have injected this driver into MDT Laptop deployment share, regenerated the ISO and tried again however Iam still unable to connect to the deployment share with litetouch ISO.
The above driver is very much part of set of network drivers on Dell website too.But it doesn’t work.
-Have also tried combination of network & storage drivers from Dell website (along with the above one mentioned ) injecting them into the MDT laptop boot image but no luck.
-Every time I make changes to drivers in boot image,I update deployment share & recreate boot image .
-This very litetouch iso connects to MDT deployments share for Dell desktop models 3010 & 3020 but have issues with laptop models E7440 & E7240. This means any connectivity or access issues can be ruled out. Also no problem with our image cause
this happens even with brand new shipped laptops with your inbuild win 7 OS.
-Have tried all options suggested on internet,tested all the drivers suggested but no luck.
-For example I tried latest E7440 netwrok & storage drivers ,Dell Win PE drivers,drivers from Intel website,etc individually as well as in combinations but the issue persists.
-If you google many express similar issues with these laptop models.
Though I used the drivers suggested by various bloggers,nothing worked for me.
Any help on this is appreciated.Thanks in advance.

Hi,
I have several E6420, O3010 and since a week also some E7440 and E7240 on site.
I never had issues using the current Dell PE package for MDT.
At the moment my PE contains only the drivers from the Dell PE 3.0 package (WinPE3.0-Drivers-A13-D67JC)
and all my systems mentioned abobe have no issues connecting to the deployment share.
(btw: I have also some older E6400, E6410 and O390 I do no longer support, they
are supported by the pack Dell-WinPE-Drivers-A05.CAB according
to the Dell site, but I just started a deplymenst on a E6410 and is is also workign with just the latest PE pack)
I'd
suggest you start over with your deplyoment share using at least MDT2012 Update 1.
Create a folder "PE" under "Out-of-Box Drivers" and extract latest Dell PE pack and import he drivers there
Create a selection profile e.g. "PE Drivers" and include just the "PE" folder created above
When configuring the Windows PE settings of your deployment share select "PE
Drivers" selection profile for the driver injection in the "Drivers and Patches" to keep the PE image free of not needed drives.

OSD Task Sequence fails with "There are no task sequences available for this computer"

Let me preface this by saying that I have read at least 100 forum posts with people having similar issues. However, none of the solutions in those
posts have worked for me.
The Problem: SCCM 2012 R2 will not image unknown computers.
The task sequence gives the error "There are no task sequences available for this computer." As soon as that error occurs, SCCM places an Unknown entry into the All Systems collection. I have been imaging unknown computers, without fail, for
4 months and no environmental changes have been made. NOTE: I am using USB media, not PXE.
What I've Tried:
Checked for duplicate SMSBIOS GUIDS in the console, none.
Checked for duplicate MAC Addresses in the console, none.
Checked for expired certificates, none.
Recreated Boot Media, twice.
Deleted the Unknown entry and retried, SCCM just recreates the Unknown entry.
Deleted all of my task sequence deployments, and then redeployed them each to All Systems (Only Boot Media and PXE) and to Unknown Systems (Only Boot Media and PXE)
I have also ran the following in the SQL Server Management Studio;
SELECT
* FROM
ResPolicyMap WHERE
machineid = 0 and
PADBID IN
(SELECT
PADBID FROM PolicyAssignment
WHERE BodyHash
IS NULL)
No result
Select
* From
vMacAddresses Where
MacAddresses = '00:00:00:00:00:00'
This displays an entry for every time that I have tried to image the unknown machine attached to the MAC Address with a different ItemKey and SMS_Unique_Identifier for each entry.
Added the machine manually using Import Computer Information, immediately recognized the Task Sequences that I have advertised to the All Systems collection.
Any and all assistance is welcome, I am going on the third straight day of dead ends. Below I have tried my best to post the entire SMSTS Log;

LOGGING: Finalize process ID set to 744
==============================[ TSBootShell.exe ]==============================
Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL'
Debug shell is enabled
Waiting for PNP initialization...
RAM Disk Boot Path: MULTI(0)DISK(0)RDISK(0)PARTITION(1)\SOURCES\BOOT.WIM
WinPE boot path: C:\SOURCES\BOOT.WIM
Booted from removable device
Found config path C:\
Booting from removable media, not restoring bootloaders on hard drive
C:\WinPE does not exist.
C:\_SmsTsWinPE\WinPE does not exist.
Executing command line: wpeinit.exe -winpe
The command completed successfully.
Starting DNS client service.
Executing command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:C:\
The command completed successfully.
==============================[ TSMBootStrap.exe ]==============================
Command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:C:\
Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL'
Succeeded loading resource DLL 'X:\sms\bin\x64\TSRESNLC.DLL'
Current OS version is 6.2.9200.0
Adding SMS bin folder "X:\sms\bin\x64" to the system environment PATH
Failed to open PXE registry key. Not a PXE boot.
Media Root = C:\
WinPE boot type: 'Ramdisk:SourceIdentified'
Failed to find the source drive where WinPE was booted from
Executing from Media in WinPE
Verifying Media Layout.
MediaType = BootMedia
PasswordRequired = false
Found network adapter "Intel(R) Ethernet Connection I217-LM" with IP Address XXX.XX.XXX.XXX.
Running Wizard in Interactive mode
Loading Media Variables from "C:\sms\data\variables.dat"
no password for vars file
Activating Welcome Page.
Loading bitmap
WelcomePage::OnWizardNext()
Loading Media Variables from "C:\sms\data\variables.dat"
no password for vars file
Spawned thread 1008 to download policy.
Entering TSMediaWizardControl::GetPolicy.
Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00350031004100300031003600420036002D0046003000440045002D0034003700350032002D0042003900370043002D003500340045003600460033003800360041003900310032007D00'
Environment scope successfully created: Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}
Creating key 'Software\Microsoft\SMS\47006C006F00620061006C005C007B00420041003300410033003900300030002D0043004100360044002D0034006100630031002D0038004300320038002D003500300037003300410046004300320032004200300033007D00'
Environment scope successfully created: Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}
Setting LogMaxSize to 1000000
Setting LogMaxHistory to 1
Setting LogLevel to 0
Setting LogEnabled to 1
Setting LogDebug to 1
UEFI: false
Loading variables from the Task Sequencing Removable Media.
Loading Media Variables from "C:\sms\data\variables.dat"
Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL'
Setting SMSTSMP TS environment variable
Setting _SMSMediaGuid TS environment variable
Setting _SMSTSBootMediaPackageID TS environment variable
Setting _SMSTSBootMediaSourceVersion TS environment variable
Setting _SMSTSBrandingTitle TS environment variable
Setting _SMSTSCertSelection TS environment variable
Setting _SMSTSCertStoreName TS environment variable
Setting _SMSTSDiskLabel1 TS environment variable
Setting _SMSTSHTTPPort TS environment variable
Setting _SMSTSHTTPSPort TS environment variable
Setting _SMSTSIISSSLState TS environment variable
Setting _SMSTSMediaCreatedOnCAS TS environment variable
Setting _SMSTSMediaPFX TS environment variable
Setting _SMSTSMediaSetID TS environment variable
Setting _SMSTSMediaType TS environment variable
Setting _SMSTSPublicRootKey TS environment variable
Setting _SMSTSRootCACerts TS environment variable
Setting _SMSTSSiteCode TS environment variable
Setting _SMSTSSiteSigningCertificate TS environment variable
Setting _SMSTSStandAloneMedia TS environment variable
Setting _SMSTSSupportUnknownMachines TS environment variable
Setting _SMSTSTimezone TS environment variable
Setting _SMSTSUseFirstCert TS environment variable
Setting _SMSTSx64UnknownMachineGUID TS environment variable
Setting _SMSTSx86UnknownMachineGUID TS environment variable
Root CA Public Certs=
Missing root CA environment variable from variables file
Support Unknown Machines: 1
Custom hook from X:\\TSConfig.INI is
No hook is found to be executed before downloading policy
Authenticator from the environment is empty.
Need to create Authenticator Info using PFX
Initialized CStringStream object with string: 1F53C44B-1AE9-4CAF-8ADA-5ED28DC8FF9A;2014-07-16T18:15:39Z.
Set media certificate in transport
Set authenticator in transport
CLibSMSMessageWinHttpTransport::Send: URL: XXXXXXXXX.XXXXXX.com:80 GET /SMS_MP/.sms_aut?MPKEYINFORMATIONMEDIA
Request was successful.
Default CSP is Microsoft Enhanced RSA and AES Cryptographic Provider
Default CSP Type is 24
New settings:
site=XXX,XXX, MP=http://XXXX.XXXX.com, ports: http=80,https=443
certificates are received from MP.
Unknown machine GUIDs: 774b17a2-6eeb-44bc-9c94-ce9081f5fe4c 74f16942-dd75-437f-8c4b-2a5de4d0e5e5
MP specific X86 unknown machine GUID is received at run time
MP specific X64 unknown machine GUID is received at run time
Getting MP time information
Set authenticator in transport
Requesting client identity
Setting message signatures.
Setting the authenticator.
CLibSMSMessageWinHttpTransport::Send: URL: XXXX.XXXX.com:80 CCM_POST /ccm_system/request
Request was successful.
::DecompressBuffer(65536)
Decompression (zlib) succeeded: original size 406, uncompressed size 2460.
-120
Server time zone info: 300, , [0 11 0 1 2 0 0 0], 0, , [0 3 0 2 2 0 0 0], -60
Client Identity:
Netbios name:
Current time: 2014-07-16 18:15:39.787 TZ:Pacific Standard Time Bias:0480
Current time zone info: 480, Pacific Standard Time, [0 0 0 0 0 0 0 0], 0, , [0 0 0 0 0 0 0 0], 0
Adjusting the system time: -14400.551 seconds
Time zone info set to: 300, , [0 11 0 1 2 0 0 0], 0, , [0 3 0 2 2 0 0 0], -60
New time: 2014-07-16 14:15:39.235
Current time: 2014-07-16 14:15:39.231 TZ: Bias:0300
Downloading policy from http://XXXX.XXXX.com.
Initializing HTTP transport.
Setting URL = http://XXXX.XXXX.com.
Setting Ports = 80,443.
Setting CRL = false.
Setting Server Certificates.
Set authenticator in transport
Setting Media Certificate.
Preparing Client Identity Request.
Setting transport.
Setting SourceID = 1F53C44B-1AE9-4CAF-8ADA-5ED28DC8FF9A.
Setting site code = XXX.
Can not find DeploymentType in file TsmBootstrap.ini or the file doesn't exist. This is not running on Windows To Go.
Setting SMBIOS GUID = XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX.
Adding MAC Address XX:XX:XX:XX:XX:XX.
Executing Client Identity Request.
Requesting client identity
Setting message signatures.
Setting the authenticator.
CLibSMSMessageWinHttpTransport::Send: URL: XXXX.XXXX.com:80 CCM_POST /ccm_system/request
Request was successful.
::DecompressBuffer(65536)
Decompression (zlib) succeeded: original size 415, uncompressed size 2460.
-120
Server time zone info: 300, , [0 11 0 1 2 0 0 0], 0, , [0 3 0 2 2 0 0 0], -60
Client Identity:
Netbios name:
Client GUID = , Netbios name = , State = Known
Using unknown machine GUID: 74f16942-dd75-437f-8c4b-2a5de4d0e5e5
GetSystemEnclosureChassisInfo: IsFixed=TRUE, IsLaptop=TRUE
Hash computed from CSP: Microsoft Enhanced RSA and AES Cryptographic Provider, AlgID: 32772, HashSize: 20
Computed HardwareID=2:4AC96CD5003991BC201B7AC01FBC88E592C3E2BE
Hardware ID: 2:4AC96CD5003991BC201B7AC01FBC88E592C3E2BE
Preparing the Client DDR Message
Setting SourceID = 1F53C44B-1AE9-4CAF-8ADA-5ED28DC8FF9A.
Sending the Client DDR message.
Sending Report
<Report><ReportHeader><Identification><Machine><ClientInstalled>0</ClientInstalled><ClientType>1</ClientType><Unknown>1</Unknown><ClientID>GUID:26717327-194f-4cd6-90ba-309998c058f2</ClientID><ClientVersion>5.00.0000.0000</ClientVersion><NetBIOSName>Unknown</NetBIOSName><CodePage>437</CodePage><SystemDefaultLCID>1033</SystemDefaultLCID></Machine></Identification><ReportDetails><ReportContent>Inventory
Data</ReportContent><ReportType>Full</ReportType><Date>20140716141539.000000+000</Date><Version>1.0</Version><Format>1.1</Format></ReportDetails><InventoryAction ActionType="Predefined"><InventoryActionID>{00000000-0000-0000-0000-000000000003}</InventoryActionID><Description>Discovery</Description><InventoryAc
Setting message signatures.
Setting the authenticator.
CLibSMSMessageWinHttpTransport::Send: URL: XXXX.XXXX.com:80 CCM_POST /ccm_system/request
Request was successful.
Submitted new client identity: GUID:26717327-194f-4cd6-90ba-309998c058f2
Preparing Policy Assignment Request.
Setting transport.
Setting site code = XXX.
Setting client ID = 74f16942-dd75-437f-8c4b-2a5de4d0e5e5.
Setting site signing Certificate.
Setting SiteSigningCertificateContext
Executing Policy Assignment Request.
Sending RequestAssignments
Setting message signatures.
Setting the authenticator.
CLibSMSMessageWinHttpTransport::Send: URL: XXXX.XXXX.com:80 CCM_POST /ccm_system/request
Request was successful.
::DecompressBuffer(65536)
Decompression (zlib) succeeded: original size 274, uncompressed size 662.
Request client ID: 74f16942-dd75-437f-8c4b-2a5de4d0e5e5
Response client ID: 74f16942-dd75-437f-8c4b-2a5de4d0e5e5
Retrieving Policy Assignments:
Successfully read 0 policy assignments.
Retrieving collection variable policy.
Found 0 collection variables.
Retrieving machine variable policy.
Found 0 machine variables.
Setting collection variables in the task sequencing environment.
Setting machine variables in the task sequencing environment.
Exiting TSMediaWizardControl::GetPolicy.
WelcomePage::OnWizardNext()
Loading Media Variables from "C:\sms\data\variables.dat"
no password for vars file
No assigned task sequence.
Setting wizard error: There are no task sequences available for this computer.
Skipping Confirmation Page.
Skipping Task Sequence Selection Page.
Skipping Variables Selection Page.
Skipping Resolve Progress Page.
Activating Finish Page.
Loading bitmap
Executing command line: X:\windows\system32\cmd.exe /k
The command completed successfully.
Successfully launched command shell.

[SOLVED] GRUB 2 - "error: file not found" after Clonezilla Restore

Hello,
I backed up my Arch Install which is one root partition covering the entire SDD with Clonezilla, to play around with Gentoo and FreeBSD on my Laptop.
Now I restored the image and when GRUB 2 loads I see "error: file not found" three times for a short momemt before I'm in the GRUB 2 menu.
When I boot my I also see these 3 messages (probably the once from the early loading process) and "Loading Linux ck kernel...." "Loading initrafms...." "Press any key to continue..." When I wait for a short time or press enter it boots like expected (fsck message appears for a short time since I'm using quite boot and I'm in KDM after that).
Grub loading...
error: file not found
error: file not found
error: file not found
Loading Linux ck kernel...
Loading initramfs...
Press any key to continue...
I did not have this when I backed it up. It booted into the menu and when I booted the menu entry it would go black to show me the fsck message and seconds later I was in KDM.
I tried $ sudo grub-mkconfig but it did not change anything.
This is my current /boot/grub/grub.cfg
# DO NOT EDIT THIS FILE
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="0"
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 a93fa938-f74f-477d-9573-678340bb2940
else
search --no-floppy --fs-uuid --set=root a93fa938-f74f-477d-9573-678340bb2940
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_input console
terminal_output gfxterm
set timeout=5
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Arch GNU/Linux, with Linux ck kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-ck kernel-true-a93fa938-f74f-477d-9573-678340bb2940' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 a93fa938-f74f-477d-9573-678340bb2940
else
search --no-floppy --fs-uuid --set=root a93fa938-f74f-477d-9573-678340bb2940
fi
echo 'Loading Linux ck kernel ...'
linux /boot/vmlinuz-linux-ck root=/dev/sda1 elevator=noop ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux-ck.img
menuentry 'Arch GNU/Linux, with Linux ck kernel (Fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-ck kernel-fallback-a93fa938-f74f-477d-9573-678340bb2940' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 a93fa938-f74f-477d-9573-678340bb2940
else
search --no-floppy --fs-uuid --set=root a93fa938-f74f-477d-9573-678340bb2940
fi
echo 'Loading Linux ck kernel ...'
linux /boot/vmlinuz-linux-ck root=/dev/sda1 elevator=noop ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux-ck-fallback.img
menuentry 'Arch GNU/Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-a93fa938-f74f-477d-9573-678340bb2940' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 a93fa938-f74f-477d-9573-678340bb2940
else
search --no-floppy --fs-uuid --set=root a93fa938-f74f-477d-9573-678340bb2940
fi
echo 'Loading Linux core repo kernel ...'
linux /boot/vmlinuz-linux root=/dev/sda1 elevator=noop ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux.img
menuentry 'Arch GNU/Linux, with Linux core repo kernel (Fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-fallback-a93fa938-f74f-477d-9573-678340bb2940' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 a93fa938-f74f-477d-9573-678340bb2940
else
search --no-floppy --fs-uuid --set=root a93fa938-f74f-477d-9573-678340bb2940
fi
echo 'Loading Linux core repo kernel ...'
linux /boot/vmlinuz-linux root=/dev/sda1 elevator=noop ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux-fallback.img
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/20_memtest86+ ###
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
Anyone has a clue what files it is looking for? And why it doesn't boot straight away, when there is nothing that keeps it from booting up normal anyway?
Last edited by blackout23 (2013-03-21 16:16:59)

the.ridikulus.rat wrote:Upgrade to grub 2.00, that will give info on which file is actually missing. And then recreate /boot/grub/grub.cfg and check whether that error is gone.
I think I'm already on Grub 2.0.0 otherwise I wouldn't have this cryptic menu configuration file.
local/grub-bios 2.00-1
GNU GRand Unified Bootloader - i386 PC BIOS Modules
local/grub-common 2.00-1
GNU GRand Unified Bootloader - Utilities and Common Files

SCCM 2012 _ PXE error (no advertisement found)

Hi
i have an error, always happen with PXE deployment on SCCM 2012 SP1_CU4
i tray to uninstall DP ,WDS and delete Reminstall, recreate Boot images
nothing no advertisements found
save me
Mahmoud

Hi,
Quote: i import computer info in to Device collection
So could you pxe boot successfully after deploy the task sequence to the device?
Best Regards,
Joyce
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.

Unable to get SCCM to install operating system

I am unable to get the operating system to install via SCCM. Here is a list of the steps I have taken so far with no luck:
- Uninstalled WDS and reinstalled
- Removed distribution point and reinstalled
- Recreated boot image, Windows 7 image and driver packages
- Unchecked PXE and checked again
I can get it to boot into PXE and after the password is put in, the packages fail. It starts at the winpe and after recreating the package from scratch it will error at the next package(win 7 image, then driver package). I recreated each package
to get to the next step but it never installs the OS. Is there anything else I can do?
Processing DST00007 SMS_DISTRIBUTION_MANAGER
8/6/2014 3:27:29 PM 5232 (0x1470)
Library path mismatch: \\?\D:\SCCMContentLib, D:\SCCMContentLib
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:27:29 PM
5232 (0x1470)
Removing DST00007 from D:\RemoteInstall\SMSImages
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:27:29 PM
5232 (0x1470)
Removing D:\RemoteInstall\SMSTempBootFiles\DST00007
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:27:29 PM
5232 (0x1470)
Processing DST00031 SMS_DISTRIBUTION_MANAGER
8/6/2014 3:27:29 PM 5232 (0x1470)
Library path mismatch: \\?\D:\SCCMContentLib, D:\SCCMContentLib
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:27:29 PM
5232 (0x1470)
Removing DST00031 from D:\RemoteInstall\SMSImages
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:27:29 PM
5232 (0x1470)
Removing D:\RemoteInstall\SMSTempBootFiles\DST00031
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:27:29 PM
5232 (0x1470)
RegQueryValueExW failed for Software\Microsoft\SMS\DP, INST_WDSAUTO
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:27:30 PM
5232 (0x1470)
RegReadDWord failed; 0x80070002 SMS_DISTRIBUTION_MANAGER
8/6/2014 3:27:30 PM 5232 (0x1470)
Machine is running Windows Server. (NTVersion=0X601, ServicePack=1)
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:27:30 PM
5232 (0x1470)
WDS is INSTALLED SMS_DISTRIBUTION_MANAGER
8/6/2014 3:27:30 PM 5232 (0x1470)
CcmUnregisterWDS SMS_DISTRIBUTION_MANAGER
8/6/2014 3:27:30 PM 5232 (0x1470)
Removing SMSPXE provider. Performing an uninstall
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:27:30 PM
5232 (0x1470)
No need to reset the firewall. SMS_DISTRIBUTION_MANAGER
8/6/2014 3:27:32 PM 5232 (0x1470)
PXE performance counters have been uninstalled
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:27:33 PM
5232 (0x1470)
RegOpenKeyExW failed for SYSTEM\CurrentControlSet\services\WDSServer\Providers\WDSMC\Providers\SMSProvider
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:27:33 PM
5232 (0x1470)
RegReadString failed; 0x80070002 SMS_DISTRIBUTION_MANAGER
8/6/2014 3:27:33 PM 5232 (0x1470)
SMS multicast provider is not installed. SMS_DISTRIBUTION_MANAGER
8/6/2014 3:27:33 PM 5232 (0x1470)
Running: ServerManagerCmd.exe -r WDS SMS_DISTRIBUTION_MANAGER
8/6/2014 3:27:33 PM 5232 (0x1470)
Waiting for the completion of: ServerManagerCmd.exe -r WDS
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:27:33 PM
5232 (0x1470)
Failed to run: ServerManagerCmd.exe -r WDS. Program returned 000003e9
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:27:35 PM
5232 (0x1470)
Running: PowerShell.exe -Command Import-Module ServerManager; Get-WindowsFeature WDS; Remove-WindowsFeature WDS
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:27:35 PM
5232 (0x1470)
Waiting for the completion of: PowerShell.exe -Command Import-Module ServerManager; Get-WindowsFeature WDS; Remove-WindowsFeature WDS
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:27:35 PM
5232 (0x1470)
Failed to run: PowerShell.exe -Command Import-Module ServerManager; Get-WindowsFeature WDS; Remove-WindowsFeature WDS. Program returned 00000001
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:27:44 PM
5232 (0x1470)
Failed to remove WDS. SMS_DISTRIBUTION_MANAGER
8/6/2014 3:27:44 PM 5232 (0x1470)
DP monitoring task is disabed on server DST-SCMP4A.dst.local
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:27:44 PM
5232 (0x1470)
No need to initialize monitoring task on DST-SCMP4A.dst.local
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:27:44 PM
5232 (0x1470)
DP settings have been updated to DST-SCMP4A.dst.local.
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:27:44 PM
5232 (0x1470)
Initialize usage gathering task on DST-SCMP4A.dst.local
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:27:44 PM
5232 (0x1470)
IIS Version 7 SMS_DISTRIBUTION_MANAGER
8/6/2014 3:27:44 PM 5232 (0x1470)
Successfully saved iis settings. SMS_DISTRIBUTION_MANAGER
8/6/2014 3:27:45 PM 5232 (0x1470)
Log Location C:\inetpub\logs\LogFiles\W3SVC1
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:27:45 PM
5232 (0x1470)
Successfully enabled usage gathering on the local distribution point.
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:27:45 PM
5232 (0x1470)
1998-01-01T00:00:00 SMS_DISTRIBUTION_MANAGER
8/6/2014 3:27:45 PM 5232 (0x1470)
DP settings have been updated to DST-SCMP4A.dst.local.
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:27:45 PM
5232 (0x1470)
OS information for the server - 6.1.7601 SMS_DISTRIBUTION_MANAGER
8/6/2014 3:27:46 PM 5232 (0x1470)
for ["Display=\\DST-SCMP4A.dst.local\"]MSWNET:["SMS_SITE=DST"]\\DST-SCMP4A.dst.local\, failed to get a copy of master SCF
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:27:46 PM
5232 (0x1470)
Failed to find the share info for share SMSSIG$ on the DP machine DST-SCMP4A.DST.LOCAL. Error code = 2310
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:27:58 PM
5636 (0x1604)
ConfigurePXE SMS_DISTRIBUTION_MANAGER
8/6/2014 3:28:59 PM 6424 (0x1918)
CcmInstallPXE SMS_DISTRIBUTION_MANAGER
8/6/2014 3:28:59 PM 6424 (0x1918)
RegQueryValueExW failed for Software\Microsoft\SMS\DP, PxeInstalled
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:28:59 PM
6424 (0x1918)
RegReadDWord failed; 0x80070002 SMS_DISTRIBUTION_MANAGER
8/6/2014 3:28:59 PM 6424 (0x1918)
Running: D:\Program Files\Microsoft Configuration Manager\bin\x64\vcredist_x64.exe /q /log "D:\Program Files\Microsoft Configuration Manager\bin\x64\vcredist.log"
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:28:59 PM
6424 (0x1918)
Waiting for the completion of: D:\Program Files\Microsoft Configuration Manager\bin\x64\vcredist_x64.exe /q /log "D:\Program Files\Microsoft Configuration Manager\bin\x64\vcredist.log"
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:28:59 PM
6424 (0x1918)
Found notification for package 'DST00002' SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:03 PM 5232 (0x1470)
Found notification for package 'DST00003' SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:03 PM 5232 (0x1470)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:03 PM 5644 (0x160C)
Package Thread Limit: 3 SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:03 PM 5232 (0x1470)
Per package Thread Limit: 5 SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:03 PM 5232 (0x1470)
Retry interval: 30 SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:03 PM 5232 (0x1470)
DP upgrade thread Limit: 5 SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:03 PM 5232 (0x1470)
DP upgrade retry interval: 20 SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:03 PM 5232 (0x1470)
Used 0 out of 3 allowed processing threads.
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:29:03 PM
5232 (0x1470)
Starting package processing thread, thread ID = 0x17D0 (6096)
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:29:03 PM
5232 (0x1470)
Starting package processing thread, thread ID = 0x181C (6172)
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:29:04 PM
5232 (0x1470)
Run completed for: D:\Program Files\Microsoft Configuration Manager\bin\x64\vcredist_x64.exe /q /log "D:\Program Files\Microsoft Configuration Manager\bin\x64\vcredist.log"
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:29:04 PM
6424 (0x1918)
Created the DP mutex key for WDS. SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:04 PM 6424 (0x1918)
Finding Wimgapi.Dll SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:04 PM 6424 (0x1918)
MsiEnumRelatedProducts failed SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:04 PM 6424 (0x1918)
FindProduct failed; 0x80070103 SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:04 PM 6424 (0x1918)
MsiEnumRelatedProducts failed SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:04 PM 6424 (0x1918)
FindProduct failed; 0x80070103 SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:04 PM 6424 (0x1918)
Found C:\Windows\system32\wimgapi.dll SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:04 PM 6424 (0x1918)
Wimgapi.dll is already installed. SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:04 PM 6424 (0x1918)
Path to smsdp.dll is 'D:\Program Files\Microsoft Configuration Manager\bin\x64\SMSDP.DLL'
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:29:04 PM
6424 (0x1918)
STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=DST-SCMP4A.dst.local SITE=DST PID=2552 TID=6172 GMTDATE=Wed Aug 06 19:29:04.421 2014 ISTR0="Configuration Manager Client Upgrade Package" ISTR1="DST00003"
ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="DST00003"
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:29:04 PM
6172 (0x181C)
No action specified for the package DST00003.
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:29:04 PM
6172 (0x181C)
Start adding package to server ["Display=\\DST-SCMP4A.dst.local\"]MSWNET:["SMS_SITE=DST"]\\DST-SCMP4A.dst.local\...
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:29:04 PM
6172 (0x181C)
Will wait for 1 threads to end. SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:04 PM 6172 (0x181C)
The distribution point is on the siteserver and the package is a content type package. There is nothing to be copied over.
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:29:04 PM
2752 (0x0AC0)
The distribution point ["Display=\\DST-SCMP4A.dst.local\"]MSWNET:["SMS_SITE=DST"]\\DST-SCMP4A.dst.local\ is not installed or upgraded yet.
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:29:04 PM
2752 (0x0AC0)
Error occurred. Performing error cleanup prior to returning.
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:29:04 PM
2752 (0x0AC0)
DP thread with array index 0 ended. SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:04 PM 6172 (0x181C)
DP thread with thread handle 0000000000002750 and thread ID 2752 ended.
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:29:04 PM
6172 (0x181C)
PXE performance counters have been initialized
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:29:04 PM
6424 (0x1918)
Machine is running Windows Server. (NTVersion=0X601, ServicePack=1)
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:29:04 PM
6424 (0x1918)
WDS is INSTALLED SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:04 PM 6424 (0x1918)
WDS service is already installed. SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:04 PM 6424 (0x1918)
Machine is running Windows Server. (NTVersion=0X601, ServicePack=1)
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:29:04 PM
6424 (0x1918)
WDS is INSTALLED SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:04 PM 6424 (0x1918)
Machine is running Windows Server. (NTVersion=0X601, ServicePack=1)
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:29:04 PM
6424 (0x1918)
Setting TFTP config key as: System\CurrentControlSet\Services\WDSSERVER\Providers\WDSTFTP
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:29:04 PM
6424 (0x1918)
Configuring TFTP read filters SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:04 PM 6424 (0x1918)
SetupComplete is set to 1 SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:04 PM 6424 (0x1918)
RegQueryValueExW failed for Software\Microsoft\Windows\CurrentVersion\Setup, REMINST
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:29:04 PM
6424 (0x1918)
RegReadDWord failed; 0x80070002 SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:04 PM 6424 (0x1918)
REMINST not set in WDS SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:04 PM 6424 (0x1918)
WDS is Configured SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:04 PM 6424 (0x1918)
WDSServer is STARTED SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:25 PM 6424 (0x1918)
Running: WDSUTIL.exe /Initialize-Server /REMINST:"D:\RemoteInstall"
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:29:25 PM
6424 (0x1918)
Waiting for the completion of: WDSUTIL.exe /Initialize-Server /REMINST:"D:\RemoteInstall"
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:29:25 PM
6424 (0x1918)
Failed to run: WDSUTIL.exe /Initialize-Server /REMINST:"D:\RemoteInstall". Program returned c1030105
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:29:26 PM
6424 (0x1918)
Machine is running Windows Server. (NTVersion=0X601, ServicePack=1)
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:29:26 PM
6424 (0x1918)
No need to configure the firewall SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:26 PM 6424 (0x1918)
Processing DST00007 SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:26 PM 6424 (0x1918)
Library path mismatch: \\?\D:\SCCMContentLib, D:\SCCMContentLib
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:29:26 PM
6424 (0x1918)
Expanding D:\SCCMContentLib\FileLib\B9BE\B9BE214D055D8D5B1C11ABC1844028CB8FB5888F731799BE4374C4189C691394 from package DST00007
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:29:26 PM
6424 (0x1918)
Finding Wimgapi.Dll SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:26 PM 6424 (0x1918)
MsiEnumRelatedProducts failed SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:26 PM 6424 (0x1918)
FindProduct failed; 0x80070103 SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:26 PM 6424 (0x1918)
MsiEnumRelatedProducts failed SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:26 PM 6424 (0x1918)
FindProduct failed; 0x80070103 SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:26 PM 6424 (0x1918)
Found C:\Windows\system32\wimgapi.dll SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:26 PM 6424 (0x1918)
SetNamedSecurityInfo() failed. SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:26 PM 6424 (0x1918)
SetObjectOwner() failed. 0x80070003. SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:26 PM 6424 (0x1918)
SetFileSecurity() failed. SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:26 PM 6424 (0x1918)
Expanding DST00007 to D:\RemoteInstall\SMSImages
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:29:26 PM
6424 (0x1918)
Processing DST00031 SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:32 PM 6424 (0x1918)
Library path mismatch: \\?\D:\SCCMContentLib, D:\SCCMContentLib
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:29:32 PM
6424 (0x1918)
Expanding D:\SCCMContentLib\FileLib\9E37\9E37D6A7AAF833CBE9C391243489E8A2C6FD2870747480417D4FF66F1980B07D from package DST00031
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:29:32 PM
6424 (0x1918)
Finding Wimgapi.Dll SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:32 PM 6424 (0x1918)
MsiEnumRelatedProducts failed SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:32 PM 6424 (0x1918)
FindProduct failed; 0x80070103 SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:32 PM 6424 (0x1918)
MsiEnumRelatedProducts failed SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:32 PM 6424 (0x1918)
FindProduct failed; 0x80070103 SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:32 PM 6424 (0x1918)
Found C:\Windows\system32\wimgapi.dll SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:32 PM 6424 (0x1918)
SetNamedSecurityInfo() failed. SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:32 PM 6424 (0x1918)
SetObjectOwner() failed. 0x80070002. SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:32 PM 6424 (0x1918)
SetFileSecurity() failed. SMS_DISTRIBUTION_MANAGER
8/6/2014 3:29:32 PM 6424 (0x1918)
Expanding DST00031 to D:\RemoteInstall\SMSImages
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:29:32 PM
6424 (0x1918)
CcmInstallPXE: Deleting the DP mutex key for WDS.
SMS_DISTRIBUTION_MANAGER 8/6/2014 3:29:40 PM
6424 (0x1918)

Hi,
Have you verified WDS service is running?
According to the log, please check the registry "SYSTEM\CurrentControlSet\services\WDSServer\Providers\WDSMC\Providers\SMSProvider" on the DP.
Please make sure all the prerequisites for DP have met.
A similar thread:
http://social.technet.microsoft.com/Forums/en-US/cea6e674-962b-427a-841e-a91b5e68136f/issue-setting-up-pxe-enabled-distribution-point-for-sccm-2012?forum=configmanagerdeployment
Best Regards,
Joyce
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.

MDT 2012 Toggle Multicast On And Off At Will?

Since multicast is so much slower than our normal deployment, it is more of a problem than it is worth unless we are doing more than a handful of computers simultaneously.
Can we disable it without having to update the deployment share and recreate boot media each time?
We would rather just keep it off normally and when we have many to do and then turn it off again when the large group of PCs is complete.

How many do you image at a time? You might not need multicast at all, but if you do need it try:
Scheduled-Cast. This option sets the start criteria for the transmission based on the number of clients that are requesting an image and/or a specific day and time.
Then you can have multicast only kick in when enough clients at once are requesting an image.
If this post is helpful please vote it as Helpful or click Mark for answer.
Won't that just cause the machines to sit doing nothing until the required number of clients connect before the deployment starts?
I don't see how it would automatically change between unicast and multicast on the fly.
If it can do that, that would be great, but I can't find anything that says that is part of the functionality..

/boot Partition was Deleted! What is the best way to recreate?

My /boot Partition was somehow deleted.
How can I recreate it?
I've been trying to boot from a LiveCD then un-archive the Grub and Kernel26 pkgs from a flash drive.
Then run:
mkinitcpio -c /mnt/sda3/etc/mkinitcpio.conf -k 2.6.31-ARCH -b /mnt/sda3/ -g /mnt/sda3/boot/kernel26.img
Everything seems to work except it fails to detect /dev/sda3.
Error Log:
:: Loding udev.../init: 11: /sbin/udevd: not found
/init: 11: /sbin/udevadm: not found
/init: 11: /sbin/udevadm: not found
Waiting 10 seconds for device /dev/sda3 ...
Root device '/dev/sda3' doesn't exist, attempting to create it
ERROR: Failed to parse block device ids for '/dev/sda3'
ERROR: Unable to detect or create root device '/dev/sda3'
You are being dropped to a recovery shell
And no /dev/* devices show up, except for console, mem, null, and zero.

Hello o/
1) Boot on your live CD
2) Launch fdisk on your boot disk and create a new partition
3) mkfs.ext3 your new partition
mkfs.ext3 /dev/your_boot_partition
4) mount your / partition and /boot
mkdir /mnt/my_system
mount /dev/your_system_partition /mnt/my_system
mount /dev/your_boot_partition /mnt/my_system/boot
5) Chroot into your system :
chroot /mnt/my_system /bin/bash
6) Install grub and kernel26
pacman -S grub kernel26
7) Edit your /mnt/my_system/boot/menu.lst to reflect the change
8) Exit your chroot and umount yours partitions and reboot
Sorry for my english

Editing boot.msg, recreating .iso

Hi. I'm trying to unpack/repack an .iso for the fun of doing it. It *almost* works fine, I'm using syslinux/isolinux, I
manage to unpack the isolinux/initram.img and do some simple editing (I'm editing arch linux' .iso). However the command:
find . | cpio -o -H newc > initrd.img
(from within the directory isolinux/initrd/) does not generate a bootable initram.
What am I missing ?
I really didn't edit anytihng special, only the boot.msg, yet bochs restarts after displaying "loading initramfs" (or whatever the message was, can't recall) but it works with the original arch iso, so it's not bochs' fault.

Hi and thanks,
I don't have a external drive and if feels lika too much of a long-shot to go and buy one to be honest.
Also, the error with copying comes after making an iso of the original DVD, its occurring during the boot camp process as it can't be the optical drive thats the problem. Or well, it might be brokan and thats why it can't find any Win7 dvd however, it doesn't seem to work with iso files either so I'm lost.
One thing though, if you guys insert a win7 install disc into the mac, does it show any content in the finder? Mine shows absolutely nothing but when I insert it on a PC it boots just fine.

Boot partition wiped out - how to recreate grub's files [SOLVED]

Boot partition got wiped out on my system.
/dev/sda1 #root
/dev/sda2 #boot
/dev/sda3 #swap
/dev/sda4 #home
I'm in an ubuntu live CD and doing this via VNC. I am chrooted into /dev/sda1 (arch) and I have mounted /boot and regenerated the kernel images. There is a /boot/grub/menu.lst and a /boot/grub/system.map but that's it. If I look at my functional system (another pc) I see a ton of extra grub files:
$ ls /boot/grub
fat_stage1_5 stage1 xfs_stage1_5
ffs_stage1_5 minix_stage1_5 stage2
default iso9660_stage1_5 more.lst stage2_eltorito
device.map jfs_stage1_5 reiserfs_stage1_5 ufs2_stage1_5
e2fs_stage1_5 menu.lst splash.xpm.gz vstafs_stage1_5
How can I get them back? I thought that a pacman -S grub would do it, but nothing...??
Last edited by graysky (2010-05-16 16:51:10)

*!@* I must have read that page 3 times over and missed that 3 times over. Thank you!
EDIT: made the wiki article a little more obvious!
Last edited by graysky (2010-05-16 16:55:41)

A guide to dual/multi boot (No BootCamp)

I am making this because of all the trouble I went through before I successfully multibooted my mac. I figured out the process is SOO much easier than described in all the walkthroughs I had read. I am assuming if you are reading this, you have some sense of what you're doing. WARNING: This could seriously mess your system up if you delete, format, or install on the wrong partition. So, here is my multibooting walkthrough.
First off, I am running Snow Leopard 10.6.8 on a Macbook Pro 7.1, but I'm pretty sure the process is not much different in other Mac OS versions. I was multibooting with Windows 7 and Ubuntu, but had another Linux OS when I was trying to figure this out. I currently am not multibooting, becuase I picked up a few desktops to run Windows and Linux on. Lets begin:
FORGET ABOUT BOOT CAMP ENTIRELY. Boot Camp allows you to install only one Microsoft OS, and offers no support for a Linux based OS. It really isn't that hard to do this without Boot Camp, and Boot Camp can hinder the process. (Unless you are only interested in installing one Windows OS, then Boot Camp is good. It is harder, however, to use Boot Camp and decide later on to multiboot.)
Open Disk Utility. It can be found in the Utilities folder, which is in Applications.
Locate your hard drive, and highlight it. It should be the top most disk in the box on the left.
Find the "Partition" tab, and click it. Your hard drive SHOULD be the only disk with a "Partition" tab.
Press the "+" button to add a partition. (Note: If you are multibooting, it's probably easier to do this process for each OS one at a time. It is easier to keep track of the partitions when there is only one blank one. Also, creating distinct sizes for each partition will help you differentiate the partitions, when you get to the installing step. In example, 27GB & 23GB is easier to tell apart than two 25GB partitions.)
Select the desired partition size, by either typing it in the "Size" field, or dragging the slider on the blue and white rectangle. (Note: You cannot slide into the blue area, because this is space currently being used. If you somehow do, you WILL mess something up.) You can name it if you'd like, but I dont think you will see the name again, the new OS will rename the partition.
Once you have your partition the desired size, click "Apply". A progress bar will appear, let it finish completely before moving on.
Now put your OS disk in, restart your computer, and boot from the disk. To boot from a disk with the Macbook Pro, hold down the "c" key while it's starting up.
(Skip to 9 if you have a bootable disk already.)
Note: If you are like me, (or using a free Linux) you probably have the OS disk somewhere on your computer in a ".iso" (or ".dmg") file. (be sure you do not break copyright laws obtaining the iso). If you are having trouble making the iso file into a bootable disk, this can be done in Disk Utility also.
Drag the UNMOUNTED iso into the list of disks, on the left side of the Disk Utility window (where you found your hard drive in step 3). DO NOT MOUNT OR OPEN THE DISK IMAGE.
Highlight the UNMOUNTED iso, and click burn.
Another progress bar will pop up, again let it finish completely.
After you boot up from the disk, it's time to dictate where/how to install the OS (sorry, I have no screenshots). BE CAREFUL WHICH OPTIOINS YOU CHOOSE ON THIS STEP. YOU CAN ALWAYS DO A HARD REBOOT IF YOU AREN'T SURE WHICH SELECTION TO MAKE. REBOOT IS LESS RISKY THAN MESSING UP THE WRONG PARTITION. There will be an option to erese everything and install the new OS, don't do that. There should be another option to configure the partitions manually, do that. Also, be careful which partition you choose (this is where the specific sizes come in handy, and that 27GB partition will be easy to find). You want to be sure not to install the OS over your original partition, or any of the (very small) system partitioins.
Find the desired partition in the manual configuration section, and click to edit it. This will probably open a seperate, partition editing window.
There will be a dropdown list, whose default setting will say something like, "Do nothing with this partition," Change that. I always pick the top most option, but any will do as long as a box, allowing you to choose what folder to mount the file system to, appears. Also, your selection should allow you to check a box to format the partition, which is probably in the first window, the one where you selected what partition to edit.
Still in that second window, change the folder it mounts to, to " / " (just the slash) and click "Apply".
Then check the box, "Format Partition" before clicking continue. WARNING: If you format the wrong partition, it's game over.
It will ask about a "Swap Space Partition", but I have never made one. I just continue without it.
After step 9, the rest should be a normal install. Select the preferances you favor.
If I made that clear enough, your system should now be partitioned and multibooted. Just repeat the process as many times as you need.
To switch between partitions, hold down the "option" key during startup, and a menu with the available partitions will be shown. I don't know if there is an option to always show the partition menu at startup, or not. If you do want to see a menu every time, rEFIt is the program I was using. You can download it here. Mount this disk image, then open the file "rEFIt.mpkg" inside it. Follow the installation menu (I'm pretty sure you need to be logged into an admin account to install rEFIt).
You can remove a partition entirely in Disk Utility, by clicking the " - " (next to the "+" from step 5), while highlighting the partition you want to delete inside the blue and white rectangle. Drag the slider as you please to fill the space leftover from the removal, then click apply (if you dont do this you will have unusable hard drive space the size of the deleted partition. if you forget you can resize later, no big deal). There are instructions on removing rEFIt on the rEFIt website.
It sounds harder typed out than it really is. I spent some time on this, so I really hope it helps at least one person.

Your hope is fulfilled. Thank you for taking the time to prepare this. Your clear explanation allowed me to repartition my disk. All through the process it kept reassuring me that it was not erasing the top portion of the main partition. I created several partitions a number of times, deleting and recreating as needed. The originak main partition was shortened, then lengthened several times. The occupied area, denoted by the light blue tint, was never close to being affected. Upon completion, I shut it down, and the next day it powered up beautifully.
The other explanations that I had read omitted use of + for creating new partitions, and - for deleting them. That was key to making the story complete.
Thanks again
Daniel B. Davis

Efibootmgr & gummiboot replaced UEFI entry for Windows Boot Manager

TLDR
I am now in Windows 7 and dual boot with Arch is working fine.
But before I update Arch, I would like to understand what happened, as in why adding an efibootmgr entry for Arch replaced/deleted the Windows Boot Manager entry although I followed the BG.
The status of my UEFI boot menu was, before the installation of Arch:
Windows Boot Manager
AHCI HDJ... (hard drive 1)
AHCI ST... (hard drive 2)
While working through the BG, I decided to use gummiboot=> https://wiki.archlinux.org/index.php/Be … #Gummiboot. So:
pacman -S gummiboot
gummiboot install
pacman -S efibootmgr
gummiboot install
[some error ocurred, as mentioned in red box]
efibootmgr -c -L "Gummiboot" -l /EFI/gummiboot/gummibootx64.efi
nano /boot/loader/entries/arch.conf
title Arch Linux
linux /vmlinuz-linux
initrd /initramfs-linux.img
options root=/dev/sdb3 ro
[CTRL + X, Y, Enter]
exit
umount /mnt/{boot,home,}
reboot
I then saw a new list of the UEFI boot order:
Gummiboot
AHCI HDJ... (hard drive 1)
AHCI ST... (hard drive 2)
Chose Gummiboot and it brought up a gummiboot menu with entries
Arch Linux
Windows Boot Manager
EFI Shell something
Selected Arch Linux and it went to a message something along "boot device ' ' not found" and I was in a shell which was, I think, rootfs.
I rebooted via the button on my desktop and out the Arch Linux USB drive back. After mounting the partitions:
gummiboot remove
efibootmgr
[0000: Windows Boot Manager
[0001: Arch Linux
[0002: AHCI HDJ...
[0003: AHCI ST...
exit
umount /mnt/{boot,home,}
reboot
Now I booted into a black screen with white text which said something "Reboot and select proper Boot device"
=> Inserted Win 7 64-bit DVD, repaired the boot sector. Rebooted, saw I had these entries again:
Windows Boot Manager
AHCI HDJ... (hard drive 1)
AHCI ST... (hard drive 2)
The boot into Windows worked fine. Rebooted, chrooted into my install again and:
efibootmgr
[0000: Arch Linux
[0001: Windows Boot Manager
[0003: AHCI HDJ...
[0003: AHCI ST...
efibootmogr -b 0 -B
Then I used the EFISTUB method:
efibootmgr -c -L "Arch Linux" -l /vmlinuz-linux -u "root=/dev/sdb3 ro initrd=/initramfs-linux.img"
efibootmgr
[0000: Windows Boot Manager
[0001: Arch Linux
[0002: AHCI HDJ...
[0003: AHCI ST...
exit
umount /mnt/{boot,home,}
reboot
On reboot, 'Windows Boot Manager' was again replaced by 'Arch Linux'.
=> Inserted Win 7 64-bit DVD, repaired the boot sector.
Rebooted, I have now Windows Boot Manager + Arch Linux and dual boot works now.
My questions:
What is going on with efibootmgr replacing/deleting the Windows entry? Is there something wrong with my UEFI menu?
In connection with 1., I would like to sync the EFISTUB Kernel (wiki entry) before I run pacman -Syu. Can I do that now?
Can I uninstall gummiboot now?
Last edited by jones (2013-07-11 12:30:55)

henrik wrote:So in light of your post, I decided to ditch EFISTUB + gummiboot and try out GRUB. Thanks for clearing it up a bit. Which is what confuses me a great deal more, as GRUB/gummiboot obviously do not meddle with Microsoft's EFI files. Right?
EFI relies on two things to boot:
Boot loader program files on the ESP (or occasionally elsewhere).
NVRAM entries pointing to the boot loader files.
Your own problems seem to be with the NVRAM entries, not with the boot loader files themselves. Unfortunately, managing those NVRAM entries has proven to be problematic because of bugs in specific EFI implementations, bugs in efibootmgr and other tools that manipulate the NVRAM entries, poor documentation, and other factors.
To answer your question, though, no boot loader should mess with another's files. Such things can happen, though. The number of bugs that cause Microsoft's boot loader (EFI/Microsoft/Boot/bootmgfw.efi) to be treated deferentially have provoked some tools to use it as a target location for other boot loaders. (Ubuntu's Boot Repair tool does this in a rather overzealous way. So does my own rEFInd installer script, but only under certain narrow circumstances.) Also, the EFI/BOOT/bootx64.efi file is a special case; it's the fallback bootloader that's used when NVRAM entries are missing or don't work, and various boot loader installation procedures place copies in that location, so it can be overwritten and could contain just about anything.
However, the whole thing happened again with GRUB. So I did the whole "repairing Boot problems" with the Windows DVD rescue thingy again and deleted all non-Microsoft files from the EFI partition, /dev/sda1.
Then I formatted / (root) and installed arch again and followed the Beginners' Guide which suggest mounting /dev/sda1/ to /mnt/boot (in contrast to the GRUB entry where the ESP should be mounted to /mnt/boot/efi).
I strongly advise against doing a complete re-installation just to overcome a boot loader problem. Instead, figure out what the problem is and fix it. Doing a complete re-installation is not likely to fix anything, and depending on precisely how you do it, you could end up with a more complex problem. The reason is that the re-installation is not likely to erase the NVRAM entries from the old installation, so you could find that you've got additional stray NVRAM entries. If you do happen to fix the problem by re-installing (say, because you selected a different installation option), you're not likely to know what changed to fix the problem, so you could end up in the same boat should you need to re-install again in the future.
But it did not show this line
Found Windows 7 (loader) on /dev/sda1
... how come??
I've given up trying to understand GRUB's configuration scripts. You could try creating an entry manually by editing /etc/grub.d/40_custom; or you could forget about using the GRUB scripts and create a hand-crafted grub.cfg; or you could forget about using GRUB at all. I'm not a fan of GRUB, so my personal choice is the final one.
So for all the headache and time ... should I delete the EFI partition and recreate it maybe? I think it's possible using the Windows 7 DVD.
But somehow using efibootmgr on my UEFI list somehow invalidated the Windows entry.
Reviewing your posts, it seems that you want to use the EFI stub loader directly, but you're having problems with that because when you add it to the NVRAM entries, Windows drops off your boot manager's boot options. The obvious solution to this problem is to forget about adding the EFI stub loader directly to the NVRAM entries, and instead add a boot manager that can handle either a Linux kernel or the Windows boot loader. (IMHO, this is the superior solution anyhow; I disagree with the Arch wiki's emphasis on using the EFI stub loader "raw.") It seems you were trying to do this with GRUB but had problems booting Windows. Earlier you tried gummiboot but had problems booting Linux. My suggestion is to either go back to gummiboot and fix its problem or try rEFInd. The "device not found" error you reported with gummiboot is usually caused by either a missing (or incorrectly-specified) initrd file or by an incorrectly-specified "root=" option passed to the kernel. Check those possitilities, and if you need help, report what happens in more detail. If necessary, take a digital photo of the screen and post it here. (Make sure it's legible, though!)
You can try rEFInd with minimal disk by using a CD-R or USB flash drive image. Boot with that and your NVRAM and ESP won't be affected at all. If you can get rEFInd working from the flash drive, you can then install it to your hard disk and it should continue working. Note that you probably won't be able to boot Linux directly from rEFInd with your current configuration without adding a "root=" specification to the kernel command line. You can do this by hitting F2 or Insert twice rather than launching Linux by pressing Enter. Alternatively, you can create a refind_linux.conf file in the directory that holds your kernel. That file's contents are described in the rEFInd documentation.

Recreating /boot?

Similar Messages

Maybe you are looking for