You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| None<br><br>Data Box Disk unlock tool crashes. | BitLocker not installed. Ensure that the host computer that is running the Data Box Disk unlock tool has BitLocker installed. |
33
32
| The current .NET Framework is not supported. The supported versions are 4.5 and later.<br><br>Tool exits with a message. | .NET 4.5 is not installed. Install .NET 4.5 or later on the host computer that runs the Data Box Disk unlock tool. |
34
33
| Could not unlock or verify any volumes. Contact Microsoft Support. <br><br>The tool fails to unlock or verify any locked drive. | The tool could not unlock any of the locked drives with the supplied passkey. Contact Microsoft Support for next steps. |
35
34
| Following volumes are unlocked and verified. <br>Volume drive letters: E:<br>Could not unlock any volumes with the following passkeys: werwerqomnf, qwerwerqwdfda <br><br>The tool unlocks some drives and lists the successful and failed drive letters.| Partially succeeded. Could not unlock some of the drives with the supplied passkey. Contact Microsoft Support for next steps. |
|None | Completed successfully. | No errors encountered. No action is required. |
78
-
|Completed | Completed successfully. | No errors encountered. No action is required. |
79
-
|Created | Successfully uploaded the blob. | For import disposition, means the blob was created as new. |
80
-
|Renamed | Successfully renamed the blob. ||
81
-
|CompletedWithErrors | Upload completed with errors.| There were some errors during upload. The errors are written to *copylog* file in the storage account where the data was uploaded. |
|LeasePresent | Lease is already present on the item. ||
85
-
|StorageRequestForbidden |||
86
-
|Canceled | {0} was canceled. | For the blob status in user logs; never used in recovery logs. |
87
-
|ManagedDiskCreationTerminalFailure | Could not convert to managed disks. The data was uploaded as page blobs. | Managed disk creation failed. This is a terminal failure. You can manually convert the data in the page blobs in the staging account to managed disks. |
88
-
|DiskConversionNotStartedTierInfoMissing | Could not convert to managed disk as the data was uploaded outside of the precreated folders on the Data Box Disk. | Since the VHD file was copied outside of the precreated tier folders, a managed disk wasn't created. The file is uploaded as page blob to the staging storage account as specified during order creation. You can convert it manually to a managed disk.|
89
-
|InvalidWorkitem | Could not upload the data as it does not conform to Azure naming and limits conventions. |These are files that didn't conform to Azure naming conventions and could not be uploaded as block blob. They are marked as invalid work item.|
90
-
|InvalidPageBlobUploadAsBlockBlob | The invalid page blobs are uploaded as block blobs in a container with prefix `databoxdisk-invalid-pb-`. ||
91
-
|InvalidAzureFileUploadAsBlockBlob | The invalid Azure Files are uploaded as block blobs in a container with prefix `databoxdisk-invalid-af-`. ||
92
-
|InvalidManagedDiskUploadAsBlockBlob | The invalid managed disk files are uploaded as block blobs in a container with prefix `databoxdisk-invalid-md-`.||
75
+
| Error code | Description |
76
+
|-------------|------------------------------|
77
+
|`None`| Completed successfully. |
78
+
|`Renamed`| Successfully renamed the blob. ||
79
+
|`CompletedWithErrors`| Upload completed with errors. The details of the files in error are included in the log file. |
80
+
|`Corrupted`|CRC computed during data ingestion doesn’t match the CRC computed during upload. |
|`LeasePresent`| This item is leased and is being used by another user. |
83
+
|`StorageRequestForbidden`|Could not upload due to authentication issues. |
84
+
|`ManagedDiskCreationTerminalFailure`| Could not upload as managed disks. The files are available in the staging storage account as page blobs. You can manually convert page blobs to managed disks. |
85
+
|`DiskConversionNotStartedTierInfoMissing`| Since the VHD file was copied outside of the precreated tier folders, a managed disk wasn't created. The file is uploaded as page blob to the staging storage account as specified during order creation. You can convert it manually to a managed disk.|
86
+
|`InvalidWorkitem`| Could not upload the data as it does not conform to Azure naming and limits conventions.|
87
+
|`InvalidPageBlobUploadAsBlockBlob`| Uploaded as block blobs in a container with prefix `databoxdisk-invalid-pb-`.|
88
+
|`InvalidAzureFileUploadAsBlockBlob`| Uploaded as block blobs in a container with prefix `databoxdisk-invalid-af`-.|
89
+
|`InvalidManagedDiskUploadAsBlockBlob`| Uploaded as block blobs in a container with prefix `databoxdisk-invalid-md`-.|
90
+
|`InvalidManagedDiskUploadAsPageBlob`|Uploaded as page blobs in a container with prefix `databoxdisk-invalid-md-`. |
91
+
|`MovedToOverflowShare`|Uploaded files to a new share as the original share size exceeded the maximum Azure size limit. The new file share name has the original name suffixed with `-2`. |
92
+
|`MovedToDefaultAzureShare`|Uploaded files that weren’t a part of any folder to a default share. The share name starts with `databox-`. |
93
+
|`ContainerRenamed`|The container for these files didn’t conform to Azure naming conventions and is renamed. The new name starts with `databox-` and is suffixed with the SHA1 hash of the original name |
94
+
|`ShareRenamed`|The share for these files didn’t conform to Azure naming conventions and is renamed. The new name starts with `databox-` and is suffixed with the SHA1 hash of the original name. |
95
+
|`BlobRenamed`|These files didn’t conform to Azure naming conventions and were renamed. Check the `BlobPath` field for the new name. |
96
+
|`FileRenamed`|These files didn’t conform to Azure naming conventions and were renamed. Check the `FileStoragePath` field for the new name. |
97
+
|`DiskRenamed`|These files didn’t conform to Azure naming conventions and were renamed. Check the `BlobPath` field for the new name. |
Copy file name to clipboardExpand all lines: articles/databox/data-box-disk-troubleshoot.md
+21-20Lines changed: 21 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,13 +7,13 @@ author: alkohli
7
7
ms.service: databox
8
8
ms.subservice: disk
9
9
ms.topic: article
10
-
ms.date: 06/13/2019
10
+
ms.date: 06/14/2019
11
11
ms.author: alkohli
12
12
---
13
13
14
-
# Troubleshoot validation issues in Azure Data Box Disk
14
+
# Use logs to troubleshoot validation issues in Azure Data Box Disk
15
15
16
-
This article applies to Microsoft Azure Data Box Disk and describes the validation issues you see when you deploy this solution.
16
+
This article applies to Microsoft Azure Data Box Disk. The article describes how to use the logs to troubleshoot the validation issues you could see when you deploy this solution.
17
17
18
18
## Validation tool log files
19
19
@@ -72,24 +72,25 @@ The errors contained in the *error.xml* with the corresponding recommended actio
| `None` | Successfully validated the data. | No action is required. |
75
-
| `InvalidXmlCharsInPath` | Could not create the path as the file path has characters that are not valid.| Having characters that are not valid in the file path will result in the failure of manifest file creation. Remove these characters to proceed. |
76
-
| `OpenFileForReadFailed`| Could not open the file.|File read failed due to an error. Details for the error should be in the exception. |
77
-
| `Not512Aligned` | Could not upload the data as it is not 512 bytes aligned.| Remove the file and retry the validation. Only upload data that is 512 bytes aligned to this folder. |
78
-
| `InvalidBlobPath` | Could not upload the data as the upload path is not valid.| |
79
-
| `EnumerationError` | Could not enumerate the files. | |
80
-
| `ShareSizeExceeded` | Could not upload the file as it exceeds the available space in the share.|Reduce the size of the data in the share so that it conforms to the [Azure object size limits](data-box-disk-limits.md#azure-object-size-limits). Retry the validation. |
81
-
| `AzureFileSizeExceeded` | Could not upload the file as it exceeds the maximum size allowed for Azure Files.| Reduce the size of the file or the data so that it conforms to the [Azure object size limits](data-box-disk-limits.md#azure-object-size-limits). Retry the validation.|
82
-
| `BlockBlobSizeExceeded` | Could not upload the data as it exceeds the maximum size allowed for a block blob. | Reduce the size of the file or the data so that it conforms to the [Azure object size limits](data-box-disk-limits.md#azure-object-size-limits). Retry the validation. |
83
-
| `ManagedDiskSizeExceeded` | Could not upload the data as it exceeds the maximum size allowed for a managed disk. | Reduce the size of the file or the data so that it conforms to the [Azure object size limits](data-box-disk-limits.md#azure-object-size-limits). Retry the validation. |
84
-
| `PageBlobSizeExceeded` | Could not upload the data as it exceeds the maximum size allowed for a page blob. | Reduce the size of the file or the data so that it conforms to the [Azure object size limits](data-box-disk-limits.md#azure-object-size-limits). Retry the validation. |
85
-
| `InvalidShareContainerFormat` | |The first folder created under the pre-existing folders on the disk becomes a container in your storage account. This share or container name does not conform to the Azure naming conventions. Rename the file so that it conforms to [Azure naming conventions](data-box-disk-limits.md#azure-block-blob-page-blob-and-file-naming-conventions). Retry the validation. |
86
-
| `InvalidBlobNameFormat` | Could not upload the data as it does not follow the Azure naming conventions.|Rename the file so that it conforms to [Azure naming conventions](data-box-disk-limits.md#azure-block-blob-page-blob-and-file-naming-conventions). Retry the validation. |
87
-
| `InvalidFileNameFormat` | Could not upload the data as it does not follow the Azure naming conventions. |Rename the file so that it conforms to [Azure naming conventions](data-box-disk-limits.md#azure-block-blob-page-blob-and-file-naming-conventions). Retry the validation. |
88
-
| `InvalidDiskNameFormat` | Could not upload the data as it does not follow the Azure naming conventions. |Rename the file so that it conforms to [Azure naming conventions](data-box-disk-limits.md#azure-block-blob-page-blob-and-file-naming-conventions). Retry the validation. |
75
+
| `InvalidXmlCharsInPath` |Could not create a manifest file as the file path has characters that are not valid. | Remove these characters to proceed. |
76
+
| `OpenFileForReadFailed`| Could not process the file. This could be due to an access issue or file system corruption.|Could not read the file due to an error. The error details are in the exception. |
77
+
| `Not512Aligned` | This file is not in a valid format for PageBlob folder.| Only upload data that is 512 bytes aligned to `PageBlob` folder.
78
+
Remove the file from the PageBlob folder or move it to the BlockBlob folder. Retry the validation.
79
+
|
80
+
| `InvalidBlobPath` | File path doesn’t map to a valid blob path in cloud as per the Azure Blob naming conventions.|Follow the Azure naming guidelines to rename the file path. |
81
+
| `EnumerationError` | Could not enumerate the file for validation. |There could be multiple reasons for this error. A most likely reason is access to the file. |
82
+
| `ShareSizeExceeded` | This file caused the Azure file share size to exceed the Azure limit of 5 TB.|Reduce the size of the data in the share so that it conforms to the [Azure object size limits](data-box-disk-limits.md#azure-object-size-limits). Retry the validation. |
83
+
| `AzureFileSizeExceeded` | File size exceeds the Azure File size limits.| Reduce the size of the file or the data so that it conforms to the [Azure object size limits](data-box-disk-limits.md#azure-object-size-limits). Retry the validation.|
84
+
| `BlockBlobSizeExceeded` | File size exceeds the Azure Block Blob size limits. | Reduce the size of the file or the data so that it conforms to the [Azure object size limits](data-box-disk-limits.md#azure-object-size-limits). Retry the validation. |
85
+
| `ManagedDiskSizeExceeded` | File size exceeds the Azure Managed Disk size limits. | Reduce the size of the file or the data so that it conforms to the [Azure object size limits](data-box-disk-limits.md#azure-object-size-limits). Retry the validation. |
86
+
| `PageBlobSizeExceeded` | File size exceeds the Azure Managed Disk size limits. | Reduce the size of the file or the data so that it conforms to the [Azure object size limits](data-box-disk-limits.md#azure-object-size-limits). Retry the validation. |
87
+
| `InvalidShareContainerFormat` |The directory names do not conform to Azure naming conventions for containers or shares. |The first folder created under the pre-existing folders on the disk becomes a container in your storage account. This share or container name does not conform to the Azure naming conventions. Rename the file so that it conforms to [Azure naming conventions](data-box-disk-limits.md#azure-block-blob-page-blob-and-file-naming-conventions). Retry the validation. |
88
+
| `InvalidBlobNameFormat` | File path doesn’t map to a valid blob path in cloud as per the Azure Blob naming conventions.|Rename the file so that it conforms to [Azure naming conventions](data-box-disk-limits.md#azure-block-blob-page-blob-and-file-naming-conventions). Retry the validation. |
89
+
| `InvalidFileNameFormat` | File path doesn’t map to a valid file path in cloud as per the Azure File naming conventions. |Rename the file so that it conforms to [Azure naming conventions](data-box-disk-limits.md#azure-block-blob-page-blob-and-file-naming-conventions). Retry the validation. |
90
+
| `InvalidDiskNameFormat` | File path doesn’t map to a valid disk name in cloud as per the Azure Managed Disk naming conventions. |Rename the file so that it conforms to [Azure naming conventions](data-box-disk-limits.md#azure-block-blob-page-blob-and-file-naming-conventions). Retry the validation. |
89
91
| `NotPartOfFileShare` | Could not upload the files as the upload path is not valid. Upload the files to a folder in Azure Files. | Remove the files in error and upload those files to a precreated folder. Retry the validation. |
90
-
| `NotFixedVhd` | Could not upload as managed disks. The differencing VHDs are not supported.|Remove the differencing VHDs as these are not supported. Retry the validation. |
91
-
| `NonVhdFileNotSupportedForManagedDisk` | Could not upload as managed disks. The non-VHD files are not supported. |Remove the non-VHD files as these are not supported. Retry the validation. |
92
-
| `VhdAsBlockBlob` | Could not upload as managed disk. The VHD file is not valid.|Remove the VHDs that are not valid. Retry the validation. |
92
+
| `NonVhdFileNotSupportedForManagedDisk` | A non-VHD file can’t be uploaded as a managed disk. |Remove the non-VHD files as these are not supported. Retry the validation. |
0 commit comments