MS Azure Recovery Services Agent was unable to create a snapshot - 0x186C2

Hello in the Azure Backup forum,
We use Microsoft Azure Backup on a VM in Azure. We have scheduled a backup for everyday. However, so far it has not been able to backup anything it fails with:
"Microsoft Azure Recovery Services Agent was unable to create a snapshot of the selected volume. Please try the operation again. If the issue persists, contact Microsoft Support. (0x186C2) "
and in the Windows event log it is found that:
Event ID 20 - volsnap:
" a volume snapshot of C:\ was interrupted - free space could not be calculated " - this has been translated from Danish.
Furthermore when I try doing a manual backup via volume shadow copy services I get the following error:
When troubleshooting and researching I find hotfixes for this type of error for Windows 2003 Server but none for Windows 2012 R2 or specifically for Microsoft Azure Backup.
Any suggestions and help will be highly appreciated :-)
Looking forward to hear from you.
Red Baron

Hi,
Please change the Shadow Copy Storage limit for the System drive to NO LIMIT and check. You may refer:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/e8cac987-e3b9-4ac1-9247-a72e1f953036/was-unable-to-create-a-snapshot-of-the-selected-volume-0x186c2?forum=windowsbackup
Also, I see that in that error message it states about Free space could not be calculated. Please make sure that you have enough free space (atleast equivalent to that size of snapshot).
Regards,
Manu

Similar Messages

Error : -2145124329 Installing Microsoft Azure Recovery Services Agent on SBS Standard 2011

When installing the Microsoft Azure Recovery Services Agent on Windows SBS 2011 Standard I receive error code - Error : -2145124329. When looking at the file OBManagedlog.LOGCurr.errlog located here: C:\Windows\Temp extract below it appears to be failing on
the Windows Powershell 3.0 prerequisite which is apart of the .NET 3 Framework. I have tried to install this manually but it does not appear to be compatible with SBS 2011 standard. Anyone have any ideas? MS Azure cannot help until we have a paid subscription,
I have only a trial at the moment as I wanted to test the product first but have been unable to do so as i can't install the agent.

Hi,
I searched and it seems that Windows SBS 2011 is not in the support list. Only Windows Server 2012 Essentials (and later versions) are available.
Windows Server Essentials Integration Module for Windows Azure Backup is Now Available
http://blogs.technet.com/b/sbs/archive/2013/04/19/windows-server-essentials-integration-module-for-windows-azure-backup-is-now-available.aspx
Edit on May.2: I've heard that it was supported in trial version so I'm now trying to contact related team about whether or not it is supported. Will update when getting any response.

Azure recovery Services (Backup Vault)

Hi
I'm trying to test Azure Recovery Services and have established a Backup Vault and connected a new server to it using the Azure generated certificate. The set-up seemed to be very simple and the installation of the agent went like a dream.
Unfortunately it does not work as after I start a backup I get the error "Engine encountered an unexpected error. Please ....." The corresponding event log entry is:
Faulting application name: cbengine.exe, version: 2.0.8694.0, time stamp: 0x54816461
Faulting module name: KERNELBASE.dll, version: 6.3.9600.17415, time stamp: 0x54505737
Exception code: 0xe0434352
Fault offset: 0x0000000000008b9c
Faulting process id: 0x12fc
Faulting application start time: 0x01d03016883f6a46
Faulting application path: C:\Program Files\Microsoft Azure Recovery Services Agent\bin\cbengine.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 72d16f21-9c0a-11e4-80e6-00155d800f3f
Faulting package full name:
Faulting package-relative application ID:
The server is a Windows 2012 R2 Domain controller and is patched with all latest Windows Updates. The latest Azure agent was installed from the web site
I have tried it on a second server built at the same time and it fails there with the same error

Please find the note on the supported drives by Azure Backup.
https://msdn.microsoft.com/en-us/library/azure/jj573031.aspx?f=255&MSPPError=-2147217396#BKMK_faq_4

Azure Recovery Service

Hello,
We are using the Azure Recovery Service to backup data from our server (Windows Server 2012).
This has been done since almost 1 year now.
Since last October we experience problems in backuping data, jobs keep failing without any additional details.
I have totally reinstalled the Azure Agent on the server yesterday to see if it would change, but we still have issues.
It is quite hard to identify the issue and I would need help i that. Moreover, the backups are still billed as if data was consumed but our last recovery points is from 09.10.2014!
Thank you in advance for your help and support.

Hello and thank you for your answer.
Looking at the log I could extract the part where the backup fails.
3EE4 477C 01/07 12:42:28.813 75 OMUtils.cs(59) 246C08FC-FE67-4664-890F-D3C7FBF03D44 NORMAL GetFQDNForServer = sdw-srvbu.
3EE4 341C 01/07 12:42:29.469 32 metadatastream.cpp(537) [000000001C2AC8B0] 65853539-E59E-4732-AFD0-C5D1F0393B3A NORMAL CMetadataStream::WaitForCompletion Waiting for MetadataStream [4].
3EE4 341C 01/07 12:42:29.797 32 metadatastream.cpp(562) [000000001C2AC8B0] 65853539-E59E-4732-AFD0-C5D1F0393B3A NORMAL CMetadataStream::WaitForCompletion Wait complete for MetadataStream [4]. Bytes read = [11574181888]
3EE4 341C 01/07 12:42:30.770 32 metadatastream.cpp(537) [000000001C2AC8B0] 65853539-E59E-4732-AFD0-C5D1F0393B3A NORMAL CMetadataStream::WaitForCompletion Waiting for MetadataStream [4].
3EE4 341C 01/07 12:42:31.212 32 metadatastream.cpp(562) [000000001C2AC8B0] 65853539-E59E-4732-AFD0-C5D1F0393B3A NORMAL CMetadataStream::WaitForCompletion Wait complete for MetadataStream [4]. Bytes read = [11575230464]
3EE4 192C 01/07 12:42:31.837 75 OMUtils.cs(59) FBAF663B-ABA3-48FB-BAFA-E3FA9EB4E55F NORMAL GetFQDNForServer = sdw-srvbu.
3EE4 341C 01/07 12:42:32.087 32 metadatastream.cpp(537) [000000001C2AC8B0] 65853539-E59E-4732-AFD0-C5D1F0393B3A NORMAL CMetadataStream::WaitForCompletion Waiting for MetadataStream [4].
3EE4 42B0 01/07 12:42:32.540 32 msfstream.cpp(133) [000000001C2AC8B0] 65853539-E59E-4732-AFD0-C5D1F0393B3A NORMAL CMSFStream Download of Metadata stream [4] complete! Bytes downloaded = [11577056256].
3EE4 341C 01/07 12:42:32.540 32 metadatastream.cpp(562) [000000001C2AC8B0] 65853539-E59E-4732-AFD0-C5D1F0393B3A NORMAL CMetadataStream::WaitForCompletion Wait complete for MetadataStream [4]. Bytes read = [11576143360]
3EE4 341C 01/07 12:42:33.353 32 msfparser.cpp(114) [000000001C3DE5A0] 65853539-E59E-4732-AFD0-C5D1F0393B3A NORMAL Copying real boot sector3EE4 341C 01/07 12:42:33.399 32 metadatastream.cpp(618) [000000001C2AC8B0] 65853539-E59E-4732-AFD0-C5D1F0393B3A NORMAL CMetadataStream::Close Closing metadata stream [4]
3EE4 341C 01/07 12:42:33.399 32 metadatastream.cpp(629) [000000001C2AC8B0] 65853539-E59E-4732-AFD0-C5D1F0393B3A WARNING Failed: Hr: = [0x80070003] Failed to delete metadata file []
3EE4 341C 01/07 12:42:33.399 32 vhdhelper.cpp(15) 65853539-E59E-4732-AFD0-C5D1F0393B3A NORMAL pVhdHelper:[1a2ab3900x, Type:[1]]
3EE4 3140 01/07 12:42:34.853 75 OMUtils.cs(59) EA4AB5E8-FAD7-4306-A38A-09260439943A NORMAL GetFQDNForServer = sdw-srvbu.
3EE4 3140 01/07 12:42:37.874 75 OMUtils.cs(59) 1953CED7-9413-47F0-BB81-59BEB03022D4 NORMAL GetFQDNForServer = sdw-srvbu.
3EE4 341C 01/07 12:42:37.936 71 replica.cpp(126) 65853539-E59E-4732-AFD0-C5D1F0393B3A NORMAL ErrorMapper: Set Dls error [DLS - 32505]
3EE4 341C 01/07 12:42:37.936 71 dscontext.cpp(152) [000000001A2FCEF0] 65853539-E59E-4732-AFD0-C5D1F0393B3A WARNING Last completed state for Ds Id (1801510221167250988) is 4
3EE4 341C 01/07 12:42:37.936 71 dscontext.cpp(158) [000000001A2FCEF0] 65853539-E59E-4732-AFD0-C5D1F0393B3A WARNING Ds Id (1801510221167250988) failed. DLS: 32505 HRESULT: 0x80070005
3EE4 341C 01/07 12:42:37.936 71 storageasyncworker.cpp(227) [000000001A42C078] 65853539-E59E-4732-AFD0-C5D1F0393B3A WARNING Failed: Hr: = [0x80070005] Initialize unsuccessful for replica id ({DED9EF60-259A-49EE-9422-81782CE7427B})
3EE4 341C 01/07 12:42:37.936 71 backupasync.cpp(1016) [000000001A42C070] 65853539-E59E-4732-AFD0-C5D1F0393B3A NORMAL Backup Progress: Initialize Storage finished.
3EE4 341C 01/07 12:42:37.936 71 backupasync.cpp(1045) [000000001A42C070] 65853539-E59E-4732-AFD0-C5D1F0393B3A WARNING Failed: Hr: = [0x80070005] Backup Progress: Failed
Tell me if it helps, otherwise I will attach the whole log file
Thank you

[URGENT HELP] Why is cannot install Windows 7 on my X120e? ERROR : Setup was unable to create..

i have got X120e from my college with ubuntu 11.04 installed. But my half of softwares dont work on this Lunix OS so decided to install windows 7, downloaded officially as i have keys for activation.
I used USB drive to install, Windows 7 setup sucessfully started on boot up but its getting error
"Setup was unable to create a new system partition or locate an existing system partition. See the Setup log files for more information"
I have not connected any other devices.
My Hard disk is NOT dynamic, its basic.
I have contacted lenovo service centre, but this are taking up calls.
I am fed up of this, please help me..
I have exams coming and i need this urgently.
Solved!
Go to Solution.

Hello,
Do you just want to delete the Ubuntu partition? If so, you may be able to do by booting from the Microsoft Windows 7 installation disc, pressing Shift+F10 to get to a Command Prompt, and then using the DISKPART.EXE program to erase the hard disk drive.
Regards,
Aryeh Goretsky
I am a volunteer and neither a Lenovo nor a Microsoft employee. • Dexter is a good dog • Dexter je dobrý pes
S230u (3347-4HU) • X220 (4286-CTO) • W510 (4318-CTO) • W530 (2441-4R3) • X100e (3508-CTO) • X120e (0596-CTO) • T61p (6459-CTO) • T43p (2678-H7U) • T42 (2378-R4U) • T23 (2648-LU7)
Deutsche Community Comunidad en Español Русскоязычное Сообщество

Error Code 0x80070005 "Windows was unable to create a required installation folder" when trying to upgrade XP to Windows

While trying to upgrade Windows XP to Windows 7 in Boot Camp after (performing a satisfactory compatibility check) the process aborted with error message "Windows was unable to create a required installation folder." Do I need to have a full version Windows 7 disk instead of the Upgrade version? Any other ideas??

Your suggestion to do Bing/Google search helped. It turns out there was interference from Boot Camp Services. I found two work-arounds that others had used that were stated to have worked. One was to temporarily delete Boot Camp Services and then reinstall it after the XP to 7 update, the other was to create a DVD of the downloaded installer files created by the updater and use the startup application from that DVD.
I had previously tried to update XP in a Parallel Virtual Machine but but XP didn't recognise the Updater disk as a DVD. That led me to try updating in BootCamp. I decided to try using Parallels again and was able to fix the device problem and update t&. I am going to keep Windows XP in the BootCamp partition as an alternate "machine". When I update to Lion I'll keep that partitition since BootCamp 4 that comes with Lion does not support XP.

Alienware M17x R2 Install issue "Setup was unable to create or locate a system partition"

Hi, I have recently gotten a new alienware laptop for x-mas. I tried to set up Windows 7 64-bit Premium edition. and it comes to the spot that says "Where do you want to install Windows"? and when i try to click next (because it shows one of
my drive partions there) it gives me some lame error that says it was unable to create or locate a partition... any help?

Sounds like:
1) the hard drive has a problem. Try booting into the BIOS and see if the drive is recognized
or
2) the drive adapter is unknown to W7. You may need to download the driver onto a floppy and press "F6" when prompted to provide drivers
Regards,
Hank Arnold
Microsoft MVP
Windows Server - Directory Services
http://it.toolbox.com/blogs/personal-pc-assistant/
On 12/25/2010 2:14 PM, vickydimarino wrote:
Hi, I have recently gotten a new alienware laptop for x-mas. I tried to set up Windows 7 64-bit Premium edition. and it comes to the spot that says "Where do you want to install Windows"? and when i try to click next (because it shows one of my
drive partions there) it gives me some lame error that says it was unable to create or locate a partition... any help?
Regards, Hank Arnold (MVP - DS)

Error message: Warning 20225. Adobe Acrobat 7.0 Setup was unable to create a new item: Adobe PDF Por

Error message: Warning 20225. Adobe Acrobat 7.0 Setup was unable to create a new item: Adobe PDF Port-Printer. The Adobe PDF Printer may be unavailable. I'm using the original CD to set up

And on what system? Acrobat 7 is not compatible with Windows 7, if that's what you are using. You need to upgrade then.
Mylenium

Windows 7 Ultimate isn't installing on my iMac. Setup was unable to create a new system partition or locate an existing system partition

I have a 21.5" iMac (Late 2012) running OS X Mavericks. I'm trying to install Windows 7 Ultimate via Bootcamp but whenever i get to the setup part it goes wrong
These are the steps I followed
I selected all the options since I didn't have the drivers or an install disk
it copied the Windows 7 iso image, downloaded the support software, and saved the support software to the flash drive (8GB)
I selected a partition size - I gave windows roughly 100GB
and I let it install
Right now I'm at the part where it says " where do you want to install windows? I selected the bootcamp partition and formatted it. It now says
"Setup was unable to create a new system partition or locate an existing system partition. See the Setup log files for more information"
WHAT DO I DO?

I had to read the apple instructions several times before they started to make sense. I burned my iso onto a DVD and had the required USB for support software. Are you trying to use the single USB method?
This article has a lot of info on the single usb method

Boot Camp - Setup was unable to create a new system partition....from Windows install

Hi folks. So I ran the boot camp wizard and made a USB install key for windows from that. I boot to it and everything works until I get to the install. I format the Boot Camp partition as indicated in the walkthrough and then I get "Setup was unable to create a new system partition or locate an existing system partition. See the Setup log files for more information." from the Windows installer. What do I do? Thanks.

just to add to the mix. . . i just got a new macbook retina.
Originally used a USB flash drive. Hit the same barrier described here.
Spent a few hours with drive unplugging / replugging silliness. No progress. Went back into OSX to attempt using an external DVD drive. There is no option for that in Bootcamp assistant now - must use USB.
Grabbed a different USB stick and started again. This time I used the other USB port on the macbook (the one on the left). Everything worked fine this time!?
You still have to go into "advanced options" and hit "format" when you get to the partition screen.
Moral of the story: different stick, different port. Sounds random. If that doesn't work, try changing your socks and putting on a hat.
Good luck!

Windows 7 Setup was unable to create a new system partition

I had windows 7 ultimate installed on a raid striping configuration and one of the hard drives crashed. I bought a new hard drive (WD Caviar Black 1TB) and when I went to reinstall windows 7, I got an error message saying Setup was unable to create
a new system partition blah blah blah. I did a lot of searching around for an answer, wondering if 1TB was too big of a hard drive to do a fresh install on, whether it was formated correctly, etc...
What I eventually found to be the solution was to go into the BIOS and change a setting. Somehow when my old hard drive crashed, the boot priority for hard drives automatically changed so that the first boot priority was one of my external hard drives.
After I changed the boot priority so that the first priority was the hard drive I wanted to install windows 7 on, the installation went smoothly. I think that's why other people had success after removing all external hard drives. After a
couple of reboots the boot priority most likely automatically updated to reflect which hard drives were actually connected.
Anyway, I had a hard time finding this answer, it was frustrating beyond all belief, and I wanted to make it easily available in case it helps anybody else out in the future.
Andy Mykrantz

Hi.
Thanks for sharing the information here.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

Bootcamp windows 7 setup was unable to create a new system partition

I've been trying to load Win 7 sp1 64 for a week. Tried 4 versions, all 64b, made a new USB drive each time, I always get stuck in the same place:
"setup was unable to create a new system partition or locate existing system partition". I've tried everything, read MANY forums.
I read format in set-up many times, but it matters not! HELP!

Restart your machine and do a pram reset (google)
Open disk utility and repair permissions twice, also you should only have 1 partition
Then try boot camp assistant again
If this doesn't work, you'll need to either clean install OSX or have a terminal disk wizard from here try and help

Visual Studio cannot remote debug Azure cloud service: There was a failure to launch the remote debugger

I am trying to invoke remote debugger on an Azure worker role cloud service, following the example of
http://msdn.microsoft.com/en-us/library/azure/ff683670.aspx
But on attaching the remote debugger for the cloud service instance
Microsoft Visual Studio
There was a failure to launch the remote debugger.
OK
According to somebody else's extra coverage on the topic, there are extra ports 4016/4017 that need to be taken care of (but do they have to be exposed externally)?
http://developers.de/blogs/damir_dobric/archive/2014/02/04/behind-windows-azure-remote-debugger.aspx
So servicedefinition.csdef gets
    <Endpoints>
      <InputEndpoint name="Endpoint1" protocol="http" port="80" />
      <InputEndpoint name="RemoteDebugger" protocol="tcp" port="4016" localPort="4016" />
      <InputEndpoint name="RemoteDebugger2" protocol="tcp" port="4017" localPort="4017" />
      <InstanceInputEndpoint name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Connector" protocol="tcp" localPort="30398">
        <AllocatePublicPortFrom>
          <FixedPortRange min="30400" max="30424" />
        </AllocatePublicPortFrom>
      </InstanceInputEndpoint>
      <InstanceInputEndpoint name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Forwarder" protocol="tcp" localPort="31398">
        <AllocatePublicPortFrom>
          <FixedPortRange min="31400" max="31424" />
        </AllocatePublicPortFrom>
      </InstanceInputEndpoint>
    </Endpoints>
Serviceconfiguration.cscfg gets
      <Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Connector.Enabled" value="true" />
      <Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Connector.Version" value="2.3" />
      <Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.ClientThumbprint" value="THUMBNAIL" />
      <Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.ServerThumbprint" value="THUMBNAIL" />
    </ConfigurationSettings>
    <Certificates>
      <Certificate name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.TransportValidation" thumbprint="THUMBNAIL" thumbprintAlgorithm="sha1"
/>
    </Certificates>
But all these are to no avail; the same error still pops for Visual Studio 2013 Update 4; Azure SDK 2.3
Anybody regularly perform remote debugging for Azure cloud services?
The melody of logic will always play out the truth. ~ Narumi Ayumu, Spiral

And, how do I control that in Visual Studio?
All I get is the Attach Debugger... context menu option in the Azure cloud service nodes in Server Explorer. That is where it is failing. There are no customisable options.
Because of that, the Attach to Process dialog box is unable to retrieve the list of processes (to debug) in the remote worker role instance server.
I tested a blank-template worker role project and published to a new cloud project, and this simplistic copy had no problems with the Remote debugger.
Now the question is, what is it about this real-world project/cloud service that is different from blank sample? From what I compare between what I think are the relevant settings, there are none.
ServiceDefinition.csdef
<Imports>
<Import moduleName="Diagnostics" />
<Import moduleName="RemoteAccess" />
<Import moduleName="RemoteForwarder" />
<Import moduleName="RemoteDebuggerConnector" />
</Imports>
<Contents>
<Content destination=".\">
<SourceDirectory path="D:\Projects\experiments\workerrole1\workerrole1\rcf\Debug\RemoteDebuggerContent\" />
</Content>
</Contents>
<Endpoints>
<InstanceInputEndpoint name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Connector" protocol="tcp" localPort="30398">
<AllocatePublicPortFrom>
<FixedPortRange min="30400" max="30424" />
</AllocatePublicPortFrom>
</InstanceInputEndpoint>
<InstanceInputEndpoint name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Forwarder" protocol="tcp" localPort="31398">
<AllocatePublicPortFrom>
<FixedPortRange min="31400" max="31424" />
</AllocatePublicPortFrom>
</InstanceInputEndpoint>
</Endpoints>
ServiceConfiguration.cscfg
<ConfigurationSettings>
<Setting name="Microsoft.WindowsAzure.Plugins.Diagnostics.ConnectionString" value="DefaultEndpointsProtocol=https;AccountName=storage;AccountKey=" />
<Setting name="Microsoft.WindowsAzure.Plugins.RemoteAccess.Enabled" value="true" />
<Setting name="Microsoft.WindowsAzure.Plugins.RemoteAccess.AccountUsername" value="" />
<Setting name="Microsoft.WindowsAzure.Plugins.RemoteAccess.AccountEncryptedPassword" value="" />
<Setting name="Microsoft.WindowsAzure.Plugins.RemoteAccess.AccountExpiration" value="2015-12-31T23:59:59.0000000+08:00" />
<Setting name="Microsoft.WindowsAzure.Plugins.RemoteForwarder.Enabled" value="true" />
<Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Connector.Enabled" value="true" />
<Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.Connector.Version" value="2.4" />
<Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.ClientThumbprint" value="" />
<Setting name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.ServerThumbprint" value="" />
</ConfigurationSettings>
<Certificates>
<Certificate name="Microsoft.WindowsAzure.Plugins.RemoteAccess.PasswordEncryption" thumbprint="" thumbprintAlgorithm="sha1" />
<Certificate name="Microsoft.WindowsAzure.Plugins.RemoteDebugger.TransportValidation" thumbprint="" thumbprintAlgorithm="sha1" />
</Certificates>
The melody of logic will always play out the truth. ~ Narumi Ayumu, Spiral

[SOLVED] defect dbus service, systemd is unable to create socket

Hi,
I am experiencing serious problems with systemd & dbus.
I want to setup a gateway in a KVM VM, all was working fine till i applied my shorewall config & set to autostart (systemctl enable shorewall).
If I reboot the machine after this step one or two times, then I get a broken dbus service.
What I did than: reinstalled archlinux again (x86_x64) and setup same -> got issue again.
installed arch linux as x86 and setup same -> issue again
installed arch as x86 and configured nothing else shorewall and got this issue again after maximum of two reboots.
i found in log:
Feb 13 15:45:56 pactor systemd[1]: Failed to open private bus connection: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
I've checked this directory by hand and found that only /var/run is existing. /var/run/dbus is already not existing.
logs:
journalctl -b: http://nopaste.info/685f4c6192.html
-be aware of systemd-logind, this needs dbus and i experience same problem with other services which require dbus as dnsmasq
root@pactor ~]# systemctl status dbus
dbus.service - D-Bus System Message Bus
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
Active: active (running) since Mi 2013-02-13 15:45:56 CET; 9min ago
Main PID: 169 (dbus-daemon)
CGroup: name=systemd:/system/dbus.service
└─169 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
[root@pactor ~]# systemctl status dbus.socket
dbus.socket - D-Bus System Message Bus Socket
Loaded: loaded (/usr/lib/systemd/system/dbus.socket; static)
Active: active (running) since Mi 2013-02-13 15:45:56 CET; 9min ago
Feb 13 15:45:56 pactor systemd[1]: Listening on D-Bus System Message Bus Socket.
systemd-logind.service - Login Service
Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static)
Active: activating (start) since Mi 2013-02-13 16:00:56 CET; 48s ago
Docs: man:systemd-logind.service(8)
man:logind.conf(5)
http://www.freedesktop.org/wiki/Software/systemd/multiseat
Main PID: 338 (systemd-logind)
CGroup: name=systemd:/system/systemd-logind.service
└─338 /usr/lib/systemd/systemd-logind
Feb 13 16:00:56 pactor systemd[1]: Failed to start Login Service.
Feb 13 16:00:56 pactor systemd[1]: Unit systemd-logind.service entered failed state
Feb 13 16:00:56 pactor systemd[1]: systemd-logind.service holdoff time over, scheduling restart.
Feb 13 16:00:56 pactor systemd[1]: Stopping Login Service...
Feb 13 16:00:56 pactor systemd[1]: Starting Login Service...
installed packages: http://nopaste.info/1d1be9adad.html
shorewall config: shorewall_conf.tar
Last edited by debijan (2013-02-20 20:13:47)

oh man... found the reason due to help of some guys on systemd irc... big thx to falconindy and alxchk.
shorewall's SUBSYSLOCK option in shorewall.conf is by default set to /var/lock/shorewall.
but the arch wiki point that it should be set to /var/run: https://wiki.archlinux.org/index.php/Router
definitely wrong! that deletes the /var/run symlink and created a directory intstead.
to set the SUBSYSLOCK on default is working like a charm.
look also for this: https://bbs.archlinux.org/viewtopic.php?id=151285
could somebody modify the wiki in the meantime, i will hold this thread on -not-solved in the meantime
edit:/ oh man this wrong info in wiki did cost me a lot of time :-/
Last edited by debijan (2013-02-13 22:09:35)

Boot Camp - Setup was unable to create a new system partition

I'm getting this problem installing windows 7 via bootcamp on the macbook pro retina 13 using an usb drive. I looked up solutions online, and they involved unplugging other usb ports or moving the usb drive from one port to the other. I don't have any other usb drives connected when doing the windows installation, and I tried moving the usb drive with windows setup from one port to the other, but I'm still getting this error message. Are there any other solutions to the problem? Do I have a problem with the USB drive?

Hi Pharotek,
I had the same issue, trying to install Windows 7 on my new iMac yesterday and this morning. I couldn't ever get it to work in any configuration of usb port plugging but I read a lot of those suggestions too. Ultimately, I borrowed an external dvd drive and burned the Windows 7 iso to a dvd. Booting from the external dvd did the trick. To summarize, so hopefully I help others with this terribly-frustrating problem:
Use the Bootcamp Assistant to remove any half-finished windows partition (that should be checking the last checkbox only, to "remove").
Plug in an external dvd drive with a Windows 7 install disk. (Use the Disk Utility to burn the ISO to the DVD if needed.)
Plug in a USB thumb drive, which we will use to hold the Apple support files.Because order seems to matter, on my iMac with 4 usb ports at the back, facing the back of the iMac from right to left I had: external DVD drive, thumb drive, blank, apple keyboard w/ non-apple mouse plugged into keyboard.
Use Bootcamp Assistant:
uncheck option one (we don't need to copy the iso to the thumb drive, since we're using dvd)
check option two (we do want to copy the support files to the thumb drive)
check option three (we do want to install Windows! )
During the install process, if you've been booting from USB thumb drive, you'll likely get a message about making the thumb not bootable. Yes, we want to make the USB thumb drive not bootable now, as we are booting from the DVD and just using the thumb for support files.
Now the installation should work. Select the bootcamp partition, choose advanced, choose to format the BOOTCAMP partition as usual.
Dance around the office (optional.)
I believe the core issue is a unhappy melding of USB 3.0 issues and having a bootable USB thumb drive be the source of installation.
My external DVD drive was an Apple USB SuperDrive.

MS Azure Recovery Services Agent was unable to create a snapshot - 0x186C2

Similar Messages

Maybe you are looking for