Hi all, we have recently built 5 servers from the same template and installed Snapdrive for Windows 6.3 onto 3 of these servers.
When I have tried to install the server 2008 service pack 1 onto theses servers they keep failing with an error code of 800F0A12.
I have tried installing this from the Windows update site and from an iso that I have downloaded but still the same problem.
What makes me think its Snapdrive is the other 2 servers which didn't have Snapdrive installed both took SP1 without any problems.
I have also rebuilt one of the servers and installed SP1 first and then installed Snapdrive and that has worked without any problems.
I have tried removing Snapdrive from the 2 servers and tried to install SP1 but still get the same error.
As you can see it seems to be when Snapdrive is installed on the servers I am getting this issue.
I can try building another server and installing Snapdrive again and then try SP1 to see if the problems occurs yet again but I wanted to see if anyone has came across this issue themselves before I proceed with anything else.
Any help or info would be appreciated!
I don't feel that snapdrive is causing this issue.
i did some google around the error code you mentioned found others not using snapdrive also face this.
please see the below links.Hope this helps
i feel this resoution should work
"Had the same problem - assign a drive letter to the 100MB partition before the C: drive using Computer Management/Disk Management and then set the partition active by right clicking on the partition. Then try to reinstall. Worked for me!
Oh, then delete the drive letter if you want to."
Did some google again
This is what i got now.
hv a look.
We've got the same problem with some VMs at a customer. The workaround (Set drive letter to 100MB partition) did work on a new installed Windows Server 2008 R2 with SnapDrive 6.3P2 in our LAB envoirement.
is this the only way to "solve" the problem? has somebody got any other experiences?
Ok, I have created another virtual server.
I've done no extra Window updates from the clone I used the other day that worked when installing SP1 first then Snapdrive.
With this server I installed Snapdrive 6.3 first before any updates or SP1, tried installing SP1 and it wouldn't install and came back with the same error.
So to me that is conclusive evidence that their is a problem when trying to install SP1 after Snapdrive has already been installed.
We're seeing the exact same issue here; a Server 2008 R2 server that has SnapDrive 6.2P1 installed is unable to install SP1, and gives the exact same error code. Every other server we have that does not have SnapDrive installed, installs SP1 fine. It's only this server with SnapDrive on that is seeing the issue. Nothing in the links help or solve the problem.
We are also facing the same problem, when we try to upgrade an existing Windows Server 2008 Datacenter Edition x64 R2 with SnapDrive 6.3 to R2 SP1. We have to uninstall SnapDrive, before we can successfully upgrade to R2 SP1.
According to the NetApp Interoperability Matrix, Windows 2008 Datacenter Edition x64 R2 SP1 and SnapDrive 6.3 is supported.
Anybody know the status on fixing this issue ?
Applying Windows 2008 R2 Service Pack 1
and eliminate error: 0x800f0a12
I am running Windows Server 2008 R2 Standard edition with SnapDrive 6.3.1 and experienced the same issue. These instructions worked for me, but I'd like to make 2 notes:
1) I did not find it necessary to reset the service start mode, as it was already set back to Automatic following the reinstall.
2) I don't know whether this is related to SP1, but on the two 2008R2 machines that I have upgraded, SnapDrive no longer displays NFS drives following the SP1 installation.
Does anyone know whether this issue is exclusively related to the automount setting and the fact that SnapDrive appears to disable it whenever it is manually enabled? If so, would it be possible to temporarily prevent SnapDrive from disabling automount long enough to install SP1 and therefore avoid the hassle of uninstalling and reinstalling SnapDrive?
Nevermind on point 2. If you can't see the VMDK disks on the guest VM SnapDrive, double check in VMWare vSphere client - check that your Virtual Storage Console, Backup and Recovery, Setup settings are set right:
- If the account used for vCenter server has an expired password - you won't see drives in your VM guest SnapDrive.
- Also, check the registration of the SAN storage systems - if the network is not accessible from the guest OS, you may not see the drives either.
This fixed my problem with not seeing the VMDK's.
I have the same problem with SP1 not installing on 2008 R2 + snapdrive 6.3, giving error 0x800F0A12. After tryed to do a Mountvol /e´and then a restart, the sp1 installs, but fails in one of the final steps, and roles back, after the roleback i get the error E_FAIL 0x80004005. If i try to install again i again get the error 0x800F0A12. I cannot help thinking that snapdrive sets some mount volume options that conficts with the SP1 install.
There is a burt open for this and is currently being tracked internally.
There is also some discussion that this may be related to the following kb from Microsoft.
If you're hitting the burt above, please open a ngs case and have them collect the proper logs.
I was able to resolve this issue by enabling automount. http://blogs.technet.com/b/joscon/archive/2011/02/17/windows-7-2008-r2-service-pack-1-fails-with-0x800f0a12.aspx
run cmd as administrator
I had the same problem. I resolved without uninstalling snapdrive.
This is the solution. We patched our 2 Windows 2008 R2 servers with Service Pack 1 and it would install but after the reboot it would roll back and uninstall SP1.
So to cover the problems and make sure the Service Pack would install I followed Marco Polci's advice:
Marco Polci wrote:
I had the same problem. I resolved without uninstalling snapdrive.
- Changed the "startup type" from Automatic to Disabled for services "SnapDrive" and "SnapDrive Management Service"
- enabled automount: "mountvol /E"
- installed the SP 1
- Changed the "startup type" from Disabled to Automatic for services "SnapDrive" and "SnapDrive Management Service"
- enabled automount "mountvol /N"
And I also assigned a letter to the System Reserve partition:
Open Computer Management > Storage > Disk Management > Right-click System Reserve (100MB partition) and assigned it any random letter.
I re-ran the Service Pack and it worked. Needless to say, I jumped for joy Thanks Marco!
I don't feel that snapdrive is causing this issue. i did some google around the error code you mentioned found others not using snapdrive also face this. please see the below links.Hope this helps http://blogs.technet.com/b/joscon/archive/2011/02/ 17/windows-7-2008-r2-service-pack-1-fails-with-0x8 00f0a12.aspx http://answers.microsoft.com/en-us/windows/forum/w indows_other-windows_...
*TRUE FRIENDSHIP "NEVER" ENDS, Friends are FOREVER*