Skip to content

Commit 4f29d7c

Browse files
authored
Update data-box-troubleshoot.md
1 parent 169678e commit 4f29d7c

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

articles/databox/data-box-troubleshoot.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -25,13 +25,13 @@ The errors in Data Box and Data Box Heavy are summarized as follows:
2525

2626
| Error category | Description | Recommended action |
2727
|----------------------------------------------|---------|--------------------------------------|
28-
| Container or share names<sup>*</sup> | The container or share names do not follow the Azure naming rules. |Download the error lists. <br> Rename the containers or shares. [Learn more](#container-or-share-name-errors). |
28+
| Container or share names<sup>*</sup> | The container or share names don't follow the Azure naming rules. |Download the error lists. <br> Rename the containers or shares. [Learn more](#container-or-share-name-errors). |
2929
| Container or share size limit<sup>*</sup> | The total data in containers or shares exceeds the Azure limit. |Download the error lists. <br> Reduce the overall data in the container or share. [Learn more](#container-or-share-size-limit-errors).|
3030
| Object or file size limit<sup>*</sup> | The object or files in containers or shares exceeds the Azure limit.|Download the error lists. <br> Reduce the file size in the container or share. [Learn more](#object-or-file-size-limit-errors). |
31-
| Data or file type<sup>*</sup> | The data format or the file type is not supported. |Download the error lists. <br> For page blobs or managed disks, ensure the data is 512-bytes aligned and copied to the pre-created folders. [Learn more](#data-or-file-type-errors). |
31+
| Data or file type<sup>*</sup> | The data format or the file type isn't supported. |Download the error lists. <br> For page blobs or managed disks, ensure the data is 512-bytes aligned and copied to the pre-created folders. [Learn more](#data-or-file-type-errors). |
3232
| Folder or file internal errors<sup>*</sup> | The file or folder have an internal error. |Download the error lists. <br> Remove the file and copy again. For a folder, modify it by renaming or adding or deleting a file. The error should go away in 30 minutes. [Learn more](#folder-or-file-internal-errors). |
3333
| General error<sup>*</sup> | Internal exceptions or error paths in the code caused a critical error. | Reboot the device and rerun the **Prepare to Ship** operation. If the error doesn't go away, contact Microsoft Support. [Learn more](#general-errors). |
34-
| Non-critical blob or file errors | The blob or file names do not follow the Azure naming rules or the file type is not supported. | These blob or files may not be copied or the names may be changed. [Learn how to fix these errors](#non-critical-blob-or-file-errors). |
34+
| Non-critical blob or file errors | The blob or file names don't follow the Azure naming rules or the file type isn't supported. | These blob or files may not be copied or the names may be changed. [Learn how to fix these errors](#non-critical-blob-or-file-errors). |
3535

3636
<sup>*</sup> Errors in this category are critical errors that must be fixed before you can proceed to **Prepare to Ship**.
3737

@@ -140,7 +140,7 @@ These errors are related to data exceeding the maximum size of object or the fil
140140
**Suggested resolution:** The blob or the file sizes exceed the maximum limit allowed for upload.
141141

142142
- On the **Connect and copy** page of the local web UI, download, and review the error files.
143-
- Make sure that the blob and file sizes do not exceed the Azure object size limits.
143+
- Make sure that the blob and file sizes don't exceed the Azure object size limits.
144144

145145
## Data or file type errors
146146

@@ -167,12 +167,12 @@ For more information, see [Overview of Page blobs](../storage/blobs/storage-blob
167167

168168
### ERROR_DIRECTORY_DISALLOWED_FOR_TYPE
169169

170-
**Error description:** A directory is not allowed in any of the pre-existing folders for the managed disks. Only fixed VHDs are allowed in these folders.
170+
**Error description:** A directory isn't allowed in any of the pre-existing folders for the managed disks. Only fixed VHDs are allowed in these folders.
171171

172172
**Suggested resolution:** For managed disks, within each share, the following three folders are created which correspond to containers in your storage account: Premium SSD, Standard HDD, and Standard SSD. These folders correspond to the performance tier for the managed disk.
173173

174174
- Make sure that you copy your page blob data (VHDs) into one of these existing folders.
175-
- A folder or directory is not allowed in these existing folders. Remove any folders that you have created inside the pre-existing folders.
175+
- A folder or directory isn't allowed in these existing folders. Remove any folders that you have created inside the pre-existing folders.
176176

177177
For more information, see [Copy to managed disks](data-box-deploy-copy-data-from-vhds.md#connect-to-data-box).
178178

0 commit comments

Comments
 (0)