Event 12289 Volume Shadow Copy Service error: Unexpected error DeviceIoControl

[isdepartment]

Hi,

Can someone help me with this error message.

Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\fdc#generic_floppy_drive#5&3aa3947e&0&0#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b} - 000000000000046C,0x00560000,0000000000000000,0,00000000001432E0,4096,[0]). hr = 0x80070001, Incorrect function.

This happens during a backup with snapmanager for hyper-v

thx

ruud

[isdepartment]

Does nobody have the same error message or a solution?

[barve]

This seems to be an error for the floppy drive and not a NetApp LUN. Is the backup failing when you get this error?

Thanks,

Anagha

[isdepartment]

hi,

the backup is not failing, this error occurs at the start of the backup.

This is also the only virtual machine with this error message.

there is no floppy image loaded.

[barve]

If the backup is not failing, I would think this is not caused by SnapManager for Hyper-V.

Microsoft may be able to provide a better answer on the significance of this message.

Thanks,

Anagha

[pauli]

Hi,

Have the same error. We see this in a ESX environment when backing up with SMVI:

VSS Error:

Log Name:      Application
Source:        VSS
Date:          17.04.2011 21:34:32
Event ID:      12289
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      EJDSA6944
Description:
Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\fdc#generic_floppy_drive#6&2bc13940&0&0#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b} - 000000000000046C,0x00560000,0000000000000000,0,000000000017D0D0,4096,[0]).  hr = 0x80070001, Incorrect function.

.

Operation:
    Exposing Recovered Volumes
    Locating shadow-copy LUNs
    PostSnapshot Event
    Executing Asynchronous Operation

Context:
    Device: \\?\fdc#generic_floppy_drive#6&2bc13940&0&0#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
    Examining Detected Volume: Existing - \\?\fdc#generic_floppy_drive#6&2bc13940&0&0#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}

   Execution Context: Provider
    Provider Name: VMware Snapshot Provider
    Provider Version: 1.0.0
    Provider ID: {564d7761-7265-2056-5353-2050726f7669}
    Current State: DoSnapshotSet
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
   <System>
     <Provider Name="VSS" />
     <EventID Qualifiers="0">12289</EventID>
     <Level>2</Level>
     <Task>0</Task>
     <Keywords>0x80000000000000</Keywords>
     <TimeCreated SystemTime="2011-04-17T19:34:32.000000000Z" />
     <EventRecordID>1422</EventRecordID>
     <Channel>Application</Channel>
     <Computer>EJDSA6944</Computer>
     <Security />
   </System>
   <EventData>
     <Data>DeviceIoControl(\\?\fdc#generic_floppy_drive#6&amp;2bc13940&amp;0&amp;0#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b} - 000000000000046C,0x00560000,0000000000000000,0,000000000017D0D0,4096,[0])</Data>

    <Data>0x80070001, Incorrect function.
</Data>
     <Data>

Operation:
    Exposing Recovered Volumes
    Locating shadow-copy LUNs
    PostSnapshot Event
    Executing Asynchronous Operation

Context:
    Device: \\?\fdc#generic_floppy_drive#6&amp;2bc13940&amp;0&amp;0#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}
    Examining Detected Volume: Existing - \\?\fdc#generic_floppy_drive#6&amp;2bc13940&amp;0&amp;0#{53f5630d-b6bf-11d0-94f2-00a0c91efb8b}

   Execution Context: Provider
    Provider Name: VMware Snapshot Provider
    Provider Version: 1.0.0
    Provider ID: {564d7761-7265-2056-5353-2050726f7669}
    Current State: DoSnapshotSet</Data>
     <Binary>2D20436F64653A20494E434943484C4830303030303532312D2043616C6C3A20434F52485755544330303030303131372D205049443A202030303030333934342D205449443A202030303030313533362D20434D443A2020433A5C57696E646F77735C73797374656D33325C76737376632E6578652020202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820</Binary>

  </EventData>
</Event>

My customer is having that error only with Windows 2008 R2 Server and VMWare Tools 4.1 u1

If we downgrade to VMWare Tools 4.1 it works.

we found the following vmware communitiy entry:

http://communities.vmware.com/message/1735358#1735358

So what kind of error/burt/problem we are having, when you have it with hyper-v and I with a ESX environment?

Customer is having a lot of such VM's. So downgrading is not realy a fancy option... 😉

Any ideas?

Thanks,

Horst

[dailyfresh]

Did you, by any change, create a VM with a floppy drive, installed Windows and then one day removed the floppy drive from the VM?

In that case disable the floppy drive in the Device Manager of Windows and see if the error goes away.

[jason_woerner]

I was seeing the same Event Log error in the same type of environment (ESXi 4.1 + Win2k8 R2). I followed the above suggestion, also thinking it odd that such a device even existed in Windows. The Event Log errors goes away on subsequent snapshots, but the snapshot still fails claiming it timed out trying to suspend I/O.

I'm seeing this on any VM I have SQL installed on. Does this match others experiences?

[awells]

Hello.  Was there a resolution to this?  Or this is expected behavior?  I am seeing similar Windows event logs for two brand new vSphere 5 virtual machines where one is running MS SQL 2008 R2 and the other is Exchange 2010 SP1.  Both of these virtual machines have RDMs (created via SnapDrive and used by SnapManager for backups) and a dedicated VMDK (independent disk) for the Windows page file.  NetApp Virtual Storage Console reports that it fails to backup the virtual machines because the resulting VMware snapshot fails along with these errors within Windows.  No virtual floppy drive or controller was part of the virtual machine hardware, however, one is seen within Windows.  Disabling the virtual floppy device controller and drive seems to address the event viewer issue but VMware snapshots still fail due to independent disks and/or RDMs.  Related KB article:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1007532

You may also experience this issue with RDMs in the physical compatibility mode, because they are always independent.

How other folks are working around these issues?

Thank you,

-Adrian

[pauli]

Hi Adrian,

I will be next week at customer site. will ask them what the actuall status is...

Thanks

Horst

[steve_hummel]

I am having the same problem with smvi and protection manager.  Working with ESXi 5.0U1 and smvi v4.1.  I see this with machines that run SQL or Web services.

I found an interesting artifact from this.  If you go to the VM that is failing, and look at the device manager's hidden devices:

To work around this behavior and display devices when you click Show hidden devices: 

1. Click Start, point to All Programs, point to Accessories, and then click Command Prompt.
2. At a command prompt, type the following command , and then press ENTER: 

   set devmgr_show_nonpresent_devices=1

3. Type the following command a command prompt, and then press ENTER: 

   start devmgmt.msc

4. Troubleshoot the devices and drivers in Device Manager.
   
   NOTE: Click Show hidden devices on the View menu in Device Manager before you can see devices that are not connected to the computer.

You will see hidden disk drives, hidden storage volumes, and possibly hidden ShadowStorage devices.

If you clear all of these devices, you should get a good snapshot.  But, in my test so far, they come right back and then the snapshot fails again.

My thought is that these extra devices represent the snapshot process creating shadows and that they aren't closing out properly and get left behind.  Haven't gotten any further than that yet, but I am continuing to look and test.

Thanks,

Steve