Windows - Drive Not Ready : Exception Processing

[antivir]

netmonkey
Try to remove network interface and add it again.

[robertson]

I am faced with the same issue as above with the "windows - drive not ready :exception processing" message appearing on the screen. Very Frustrating!
There is a ticket open with support who are currently looking into the issue. I tried removing the Network card from the Veeam VM as suggested above and thought this had resolved the issue as it worked for a couple of days. However the message reappeared and seems to be random. I have two replica jobs that are of VM'S created from the same template as the Veeam server however the message does not seem to appear when replicating these servers.

The search for a fix continues because at the moment the software solution is unreliable

[meier]

hello,
i have the same error (Windows. drive not ready Exception Processing message c000000a3 Parameters .....). Are there any solutions?
Thanks.

[Alexey D.]

Hello Holger,

Have you tried the suggestions in the posts above?

[antivir]

I have this error again. Removing network interface is not solution

[Alexey D.]

Andrew, please contact our support team for assistance.

[Jamo]

Its been too long and too many projects ago but i think the fix was regedit here in "last resort" paragraph.

http://www.consumingexperience.com/2007 ... ssing.html

Not 100% sure though.

[robertson]

I made contact with Veeam support and went through various troubleshooting but was still recieving the error. Support suggested spreading out the jobs so not to overlap replica creation which I have done. However, since introducing a scheduled reboot of the Veeam server outwith my replica window I have not seen the error return (touch wood!).
My Recommendations:
- spread out the jobs
- try to keep any replicas that could be conflicting well apart
- scheduled a daily reboot (This seems to work for me)

[Alexey D.]

Paul, thanks for posting back the findings.

[virtualwatts]

[merged]

Greetings,
I've spent all morning in a perfect storm of multiple-dozens of Windows - No Disk error messages.
vSphere 4.1/B&R 5.0.1 on VM using Appliance mode.

So - I'm posting to see if my observations and resolution seem on point.

It is the combination of the Windows No Disk together with the hotadd failover to NBD that has me concerned - I don't expect to get error messages simply from a Hotadd to NBD failover with halted processing and the locks that come along with that.

The backup processes observed in realtime look like this:
Start VM backup
Hotadd/NBD without changed block tracking
Hotadd/NBD with changed block tracking
** Windows NO DISK exception error (processing stops until acknowledged)
-- acknowledge, cancel or continue doesn't seem to make a difference
Hot Add is not supported for this disk failing over to Network Mode.
Backup (eventually) completes.
I watched this play out for 40 - 50 VMs this morning, like clockwork.

Less concerned about the NBD failover - very concerned with the Windows No Disk exception error because it holds up processing for the Veeam server. Which leaves locks, which then causes other downstream problems in our batch processing.


There is an old (v 4.x) FAQ post that says you can only use 8 devices per controller and Hotadd will need slots.
It looks like I have allocated 7 scsi devices on my second controller in the Veeam VM guest. That would leave one remaining if 8 is indeed the limit.
I currently have two controllers, boot disk on 0:0, the rest on 1:xx for paravirtual.
I thought "simple solution - I'll drop and then add some existing disks onto a second paravirtual as 2:xx"

Then I had a whoa moment - Why?
I already have a scsi controller (LSI 0:xx) that has 7 slots free plus the 1 slot free on the para controller.

So before I go re-distributing my 8 Veem disks -
Is the HotAdd scsi controller limit still valid in v5.0.1?
How does Veeam decide which scsi controller to use for the Hotadd when there are multiple (assuming it ever leaves 0:xx)?
Why the Windows No Disk error message on a Hotadd failover to NBD? What is the specific cause of that?

As the Windows No Disk and HotAdd - separately - are older issues I'm posting for insights.

Rick

[virtualwatts]

Additionally - I did look at the post here http://www.veeam.com/forums/viewtopic.php?f=2&t=5735&p=25554&hilit=no+disk+windows#p23013 and followed the steps to show hidden storage volumes.

I have perhaps 600 hidden/disconnected Generic storage volumes. But the aforementioned thread didn't indicate if that is a problem or simply a consequence of HotAdd.

[Gostev]

Let's keep everything on this Windows error in the same topic instead of creating multiple.

Is the HotAdd scsi controller limit still valid in v5.0.1?

It's not a Veeam limit, but VMware iSCSI controller's limit, so it does not depend on Veeam version.

How does Veeam decide which scsi controller to use for the Hotadd when there are multiple (assuming it ever leaves 0:xx)?

Veeam doesn't decide this, it happens under the hood in the vStorage API for Data Protection (or, possibly, in vSphere).

Why the Windows No Disk error message on a Hotadd failover to NBD? What is the specific cause of that?

I don't really understand what you are asking here. But the cause of this Windows error is currently unknown (aside of what is already written above in this topic). And NBD failover is caused by the fact that primary transpost mode (Hot Add) fails because of this error.

In your case I would suggest removing paravirtual iSCSI controller from Veeam Backup VM, as I've seen reports of this one causing various issues before.

Thanks.