Endpoint 1.1 - Partition exceeds disk layout by X bytes

[chris.childerhose]

Upgraded to version 1.1 yesterday and server back ran but gives the following warning -

Partition 1 exceeds disk 1 layout by 1024000 bytes

What does this mean and can it be fixed? Never got this on Version 1.0 of Endpoint.

[Vitaliy S.]

Chris, do you have a support case opened on this?

[chris.childerhose]

No I don't but I can open one. Seems to be persistent since yesterday after the 1.1 upgrade.

I will open a case and post back the Case #.

UPDATE -- Case # 00994597

[Dima P.]

Hi Chris,
Checking with QA - thanks for the case!

[rodo]

I have this warning after upgrading to version 1.1 too:
13. 8. 2015 7:23:22 :: Partition 1 exceeds disk 0 layout by 16384 bytes

[Dima P.]

Folks,
Please check if this helps: Partition exceeds disk layout

[rodo]

Yes, it helps, problem solved, case closed. Ttnx.

[Dima P.]

I am glad you nailed it and additional thanks for confirmation! By the way, we have reworked the KB a little bit, so now it looks more “friendly"

[hgrams]

Hi there,

On a physical Windows 2012 server backup via VEP, the console logs: "Partition 2 exceeds disk 0 layout by 105170944 bytes"
And some GB later the tasks breaks with error:

Code: Select all

[14.04.2016 16:24:56] <  8960>      ERR |Asynchronous data reader has failed.
[14.04.2016 16:24:56] <  8960>      ERR |Das Laufwerk kann den angeforderten Sektor nicht finden. Error code: 27
[14.04.2016 16:24:56] <  8960>      >>  |Failed to read data from the file [\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1].
[14.04.2016 16:24:56] <  8960>      >>  |--tr:Storage device: failed to read 622592 bytes, offset 299965513728.
[14.04.2016 16:24:56] <  8960>      >>  |--tr:Failed to read the next block from the disk. Disk: [Disk Emulator]. Current offset: [300,070,993,920]. Disk size: [300,071,616,512]. CBT tracker: [Incremental multi-tracker { bitmap_tracker:// , bitmap_tracker:// ,  }].
[14.04.2016 16:24:56] <  8960>      >>  |--tr:Next asynchronous read request cannot be processed.

I already uninstalled VEP and installed it new. The windows partition tools mean all partitions healthy and everything's Ok.

Does anybody know this error.

I would be grateful for a little input.

Thanks Harald

[hgrams]

Thanks for re-routing my problem. The KB article made me happy again

[Mike Resseler]

Thanks for letting us know your problem is solved Hgrams!

[CraigL2112]

Bringing this issue back from the dead.. seeing it on v2.1.0.423.

"Partition 1 exceeds disk 0 layout by 425984 bytes"
and
"Error: The drive cannot find the sector requested. Asynchronous read operation failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}......"

Assuming the second error is because of the first. Went to try the shrink fix and no dice, there is no space to shrink.

Tried reducing the size via Diskpart as well, and no dice. "The specified shrink size is too big and will cause the volume to be smaller than the minimum volume size."

Any ideas, anyone?

[Mike Resseler]

Hi Craig,

Looking at the error you state, I think it might be different. Please open a support call because our engineers would need to look into the entire log to learn more what is happening.

Thanks
Mike

[team Emira]

Hello team,

We are installing a POC and we make a backup in a physical server windows server 2008 SP1 (With MS SQL), but I am having problems with the backup. the mistake is:

Code: Select all

Partition 2 exceeds disk 1 layout by 98068480 bytes Error: The drive cannot find the sector requested. Asynchronous read operation failed Failed to upload disk. Agent failed to process method {DataTransfer.SyncDisk}. 

Exception from server: The drive cannot find the sector requested. Asynchronous read operation failed Unable to retrieve next block transmission command. Number of already processed blocks: [79434]. Failed to download disk 'CCE40834'.

I see the log too and show the following:

Code: Select all

[21.07.2022 21:24:01] Info <2e3c> C:\ 
[21.07.2022 21:24:01] Info <2e3c> Extents: 
[21.07.2022 21:24:01] Info <2e3c> Disk 1, offset105906176, length 146770847744 
[21.07.2022 21:24:01] Error <2e3c> Failed to check whether volume '\\?\Volume{c79a4d77-5a43-11ea-b62f-2c44fd807d60}' is alive and removable. 
[21.07.2022 21:24:01] Warning <2e3c> Failed to check whether volume '\\?\Volume{c79a4d77-5a43-11ea-b62f-2c44fd807d60}' is mounted. 
[21.07.2022 21:24:01] Warning <2e3c> Failed to open volume '\\?\Volume{c79a4d77-5a43-11ea-b62f-2c44fd807d60}'. [21.07.2022 21:24:01] Warning <2e3c> Win32 error:The device is not ready.

I have version 11a of veeam and the agent is version 5

My number case is 05554856.

Thanks and regards!!!
Miguel J.

[Dima P.]

Hello Miguel,

Have you tried the solution described in this KB article: Veeam Agent for Microsoft Windows job displays warning: Partition exceeds disk layout. Thanks!

[team Emira]

Hello Dima,

We test a different software for the backup and the Cobian software does not have a problem with to backup all disk. Do you know if this problem we can fix with another steps, because the client doesn't like to shrink the disk, in this moment is a POC and the uses software cobian for the backup.

thanks and regards!!!
Miguel J.

[Dima P.]

Miguel,

Unfortunately there is no workaround except the mentioned one. I'd recommend to fix it despite the backup application you are about to use because it may cause issues for other applications too (logical volume exceeding boundaries of the allocated disk size is not a normal practice ).