Discussions specific to the VMware vSphere hypervisor
Post Reply
twistedwrister
Lurker
Posts: 2
Liked: never
Joined: Jul 25, 2016 3:34 pm
Full Name: Ryan
Contact:

The drive cannot find the sector requested. SUSE Linux

Post by twistedwrister » Jul 25, 2016 5:18 pm

Hello,

While attempting to run a backup job on a VM, Veeam continually stops processing at about 7% (so I believe that rules out permissions as a cause), with the following error:

Processing <server name> Error: The drive cannot find the sector requested. Failed to read data from the file [\\.\PhysicalDrive1]. Failed to upload disk. Agent failed to process method {DataTransfer.DiskSync}.

VMware version: ESXi 6.0
Veeam version: 9.0.0.1491
VM OS: SUSE Linux Enterprise 11 64-bit.

Has anyone seen this before? I've seen some other solutions on other forums regarding Windows Server running chkdsk, and/or re-sizing the disk, but this is a Linux box.

Any suggestions or insight would be appreciated!

Thanks.

PTide
Veeam Software
Posts: 4526
Liked: 371 times
Joined: May 19, 2015 1:46 pm
Contact:

Re: The drive cannot find the sector requested. SUSE Linux

Post by PTide » Jul 25, 2016 5:28 pm

Hi,

It is required by forum rules to post support case ID when one posts about a technical issue. Please open a support case and let me know the ID.

Thanks!

twistedwrister
Lurker
Posts: 2
Liked: never
Joined: Jul 25, 2016 3:34 pm
Full Name: Ryan
Contact:

Re: The drive cannot find the sector requested. SUSE Linux

Post by twistedwrister » Jul 25, 2016 6:06 pm

Case ID 01862117

Thanks.

jmmarton
Veeam Software
Posts: 1273
Liked: 144 times
Joined: Nov 17, 2015 2:38 am
Full Name: Joe Marton
Location: Chicago, IL
Contact:

Re: The drive cannot find the sector requested. SUSE Linux

Post by jmmarton » Jul 25, 2016 10:49 pm

Have you tried running fsck?

Joe

alanbolte
Expert
Posts: 635
Liked: 172 times
Joined: Jun 18, 2012 8:58 pm
Full Name: Alan Bolte
Contact:

Re: The drive cannot find the sector requested. SUSE Linux

Post by alanbolte » Jul 27, 2016 5:52 am 1 person likes this post

I doubt it'd be anything in-guest, since the failure message indicates that reading the VM disk was what failed (not guest processing). The thing that's failing to be read sounds like a disk hot-added to a proxy. First isolation step would be to try a different transport mode; on the other hand, if you can storage vMotion this VM (other otherwise migrate it to another datastore), I have a hunch that that would be a workaround.

Post Reply

Who is online

Users browsing this forum: No registered users and 11 guests