Skip to content

Commit aac4e99

Browse files
authored
Merge pull request #79214 from alkohli/tsg
Add validation & copy errors, interpret log files
2 parents 1620f28 + c1fc900 commit aac4e99

10 files changed

+364
-157
lines changed

articles/databox/TOC.yml

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -112,8 +112,16 @@
112112
items:
113113
- name: Manage via Azure portal
114114
href: data-box-portal-ui-admin.md
115-
- name: Troubleshoot Data Box Disk issues
116-
href: data-box-disk-troubleshoot.md
115+
- name: Troubleshoot
116+
items:
117+
- name: Unlock issues
118+
href: data-box-disk-troubleshoot-unlock.md
119+
- name: Data copy issues
120+
href: data-box-disk-troubleshoot-data-copy.md
121+
- name: Validation issues
122+
href: data-box-disk-troubleshoot.md
123+
- name: Upload issues
124+
href: data-box-disk-troubleshoot-upload.md
117125
- name: Contact Support
118126
href: data-box-disk-contact-microsoft-support.md
119127

articles/databox/data-box-disk-deploy-copy-data.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -245,6 +245,8 @@ This optional procedure may be used when you are using multiple disks and have a
245245
246246
`DataBoxDiskSplitCopy.exe PrepImport /config:<configFile.json> /ResumeSession`
247247
248+
If you see errors using the Split Copy tool, go to how to [troubleshoot Split Copy tool errors](data-box-disk-troubleshoot-data-copy.md).
249+
248250
After the data copy is complete, you can proceed to validate your data. If you used the Split Copy tool, skip the validation (Split Copy tool validates as well) and advance to the next tutorial.
249251
250252
@@ -266,6 +268,8 @@ If you did not use the Split Copy tool to copy data, you will need to validate y
266268
267269
3. If using multiple disks, run the command for each disk.
268270
271+
If you see errors during validation, see [troubleshoot validation errors](data-box-disk-troubleshoot.md).
272+
269273
## Next steps
270274
271275
In this tutorial, you learned about Azure Data Box Disk topics such as:

articles/databox/data-box-disk-deploy-picked-up.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: alkohli
77
ms.service: databox
88
ms.subservice: disk
99
ms.topic: tutorial
10-
ms.date: 05/06/2019
10+
ms.date: 06/13/2019
1111
ms.author: alkohli
1212
Customer intent: As an IT admin, I need to be able to order Data Box Disk to upload on-premises data from my server onto Azure.
1313
---
@@ -153,6 +153,8 @@ Once the copy is complete, order status updates to **Completed**.
153153
154154
![Data copy completed](media/data-box-disk-deploy-picked-up/data-box-portal-completed.png)
155155
156+
If the copy completes with errors, see [troubleshoot upload errors](data-box-disk-troubleshoot-upload.md).
157+
156158
Verify that your data is in the storage account(s) before you delete it from the source. Your data can be in:
157159
158160
- Your Azure Storage account(s). When you copy the data to Data Box, depending on the type, the data is uploaded to one of the following paths in your Azure Storage account.

articles/databox/data-box-disk-deploy-set-up.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ author: alkohli
77
ms.service: databox
88
ms.subservice: disk
99
ms.topic: tutorial
10-
ms.date: 10/31/2018
10+
ms.date: 06/13/2019
1111
ms.author: alkohli
1212
Customer intent: As an IT admin, I need to be able to order Data Box Disk to upload on-premises data from my server onto Azure.
1313
---
@@ -118,7 +118,9 @@ Perform the following steps to connect and unlock your disks.
118118
```
119119
8. Once the disk is unlocked, you can view the contents of the disk.
120120
121-
![Data Box Disk contents](media/data-box-disk-deploy-set-up/data-box-disk-content.png)
121+
![Data Box Disk contents](media/data-box-disk-deploy-set-up/data-box-disk-content.png)
122+
123+
If you run into any issues while unlocking the disks, see how to [troubleshoot unlock issues](data-box-disk-troubleshoot-unlock.md).
122124
123125
## Unlock disks on Linux client
124126
@@ -249,6 +251,9 @@ Perform the following steps to connect and unlock your disks.
249251
250252
![Data Box Disk contents](media/data-box-disk-deploy-set-up/data-box-disk-content-linux.png)
251253
254+
255+
If you run into any issues while unlocking the disks, see how to [troubleshoot unlock issues](data-box-disk-troubleshoot-unlock.md).
256+
252257
## Next steps
253258
254259
In this tutorial, you learned about Azure Data Box Disk topics such as:
Lines changed: 98 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,98 @@
1+
---
2+
title: Azure Data Box Disk troubleshooting data copy issues| Microsoft Docs
3+
description: Describes how to troubleshoot issues seen during data copy in Azure Data Box Disk using logs.
4+
services: databox
5+
author: alkohli
6+
7+
ms.service: databox
8+
ms.subservice: disk
9+
ms.topic: article
10+
ms.date: 06/13/2019
11+
ms.author: alkohli
12+
---
13+
14+
# Troubleshoot data copy issues in Azure Data Box Disk
15+
16+
This article applies to Microsoft Azure Data Box Disk and describes how to troubleshoot any issues you see when copying the data to disks. The article also covers issues when using the split copy tool.
17+
18+
19+
## Data copy issues when using a Linux system
20+
21+
This section details some of the top issues faced when using a Linux client to copy data to disks.
22+
23+
### Issue: Drive getting mounted as read-only
24+
25+
**Cause**
26+
27+
This could be due to an unclean file system.
28+
29+
Remounting a drive as read-write does not work with Data Box Disks. This scenario is not supported with drives decrypted by dislocker. You may have successfully remounted the device using the following command:
30+
31+
`# mount -o remount, rw /mnt/DataBoxDisk/mountVol1`
32+
33+
Though the remounting was successful, the data will not persist.
34+
35+
**Resolution**
36+
37+
Take the following steps on your Linux system:
38+
39+
1. Install the `ntfsprogs` package for the ntfsfix utility.
40+
2. Unmount the mount points provided for the drive by the unlock tool. The number of mount points will vary for drives.
41+
42+
```
43+
unmount /mnt/DataBoxDisk/mountVol1
44+
```
45+
46+
3. Run `ntfsfix` on the corresponding path. The highlighted number should be same as Step 2.
47+
48+
```
49+
ntfsfix /mnt/DataBoxDisk/bitlockerVol1/dislocker-file
50+
```
51+
52+
4. Run the following command to remove the hibernation metadata that may cause the mount issue.
53+
54+
```
55+
ntfs-3g -o remove_hiberfile /mnt/DataBoxDisk/bitlockerVol1/dislocker-file /mnt/DataBoxDisk/mountVol1
56+
```
57+
58+
5. Do a clean unmount.
59+
60+
```
61+
./DataBoxDiskUnlock_x86_64 /unmount
62+
```
63+
64+
6. Do a clean unlock and mount.
65+
7. Test the mount point by writing a file.
66+
8. Unmount and remount to validate the file persistence.
67+
9. Continue with the data copy.
68+
69+
### Issue: Error with data not persisting after copy
70+
71+
**Cause**
72+
73+
If you see that your drive does not have data after it was unmounted (though data was copied to it), then it is possible that you remounted a drive as read-write after the drive was mounted as read-only.
74+
75+
**Resolution**
76+
77+
If that is the case, see the resolution for [drives getting mounted as read-only](#issue-drive-getting-mounted-as-read-only).
78+
79+
If that was not the case, copy the logs from the folder that has the Data Box Disk Unlock tool and [contact Microsoft Support](data-box-disk-contact-microsoft-support.md).
80+
81+
82+
## Data Box Disk Split Copy tool errors
83+
84+
The issues seen when using a Split Copy tool to split the data over multiple disks are summarized in the following table.
85+
86+
|Error message/Warnings |Recommendations |
87+
|---------|---------|
88+
|[Info] Retrieving BitLocker password for volume: m <br>[Error] Exception caught while retrieving BitLocker key for volume m:<br> Sequence contains no elements.|This error is thrown if the destination Data Box Disk are offline. <br> Use `diskmgmt.msc` tool to online disks.|
89+
|[Error] Exception thrown: WMI operation failed:<br> Method=UnlockWithNumericalPassword, ReturnValue=2150694965, <br>Win32Message=The format of the recovery password provided is invalid. <br>BitLocker recovery passwords are 48 digits. <br>Verify that the recovery password is in the correct format and then try again.|Use Data Box Disk Unlock tool to first unlock the disks and retry the command. For more information, go to <li> [Unlock Data Box Disk for Windows clients](data-box-disk-deploy-set-up.md#unlock-disks-on-windows-client). </li><li> [Unlock Data Box Disk for Linux clients.](data-box-disk-deploy-set-up.md#unlock-disks-on-linux-client) </li>|
90+
|[Error] Exception thrown: A DriveManifest.xml file exists on the target drive. <br> This indicates the target drive may have been prepared with a different journal file. <br>To add more data to the same drive, use the previous journal file. To delete existing data and reuse target drive for a new import job, delete the *DriveManifest.xml* on the drive. Rerun this command with a new journal file.| This error is received when you attempt to use the same set of drives for multiple import session. <br> Use one set of drives only for one split and copy session only.|
91+
|[Error] Exception thrown: CopySessionId importdata-sept-test-1 refers to a previous copy session and cannot be reused for a new copy session.|This error is reported when trying to use the same job name for a new job as a previous successfully completed job.<br> Assign a unique name for your new job.|
92+
|[Info] Destination file or directory name exceeds the NTFS length limit. |This message is reported when the destination file was renamed because of long file path.<br> Modify the disposition option in `config.json` file to control this behavior.|
93+
|[Error] Exception thrown: Bad JSON escape sequence. |This message is reported when the config.json has format that is not valid. <br> Validate your `config.json` using [JSONlint](https://jsonlint.com/) before you save the file.|
94+
95+
96+
## Next steps
97+
98+
- Learn how to [troubleshoot validation tool issues](data-box-disk-troubleshoot.md).
Lines changed: 71 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,71 @@
1+
---
2+
title: Azure Data Box Disk troubleshooting disk unlocking issues | Microsoft Docs
3+
description: Describes how to troubleshoot issues seen in Azure Data Box Disk.
4+
services: databox
5+
author: alkohli
6+
7+
ms.service: databox
8+
ms.subservice: disk
9+
ms.topic: article
10+
ms.date: 06/14/2019
11+
ms.author: alkohli
12+
---
13+
# Troubleshoot disk unlocking issues in Azure Data Box Disk
14+
15+
This article applies to Microsoft Azure Data Box Disk and describes the workflows used to troubleshoot any issues when using the unlock tool.
16+
17+
18+
<!--## Query activity logs
19+
20+
Use the activity logs to find who unlocked and accessed the disks. Your Data Box Disk arrive on your premises in a locked state. You can use the device credentials available in the Azure portal for your order to unlock them.
21+
22+
To figure out who accessed the **Device credentials** blade, you can query the Activity logs.  Any action that involves accessing **Device details > Credentials** blade is logged into the activity logs as `ListCredentials` action.
23+
24+
![Query Activity logs](media/data-box-logs/query-activity-log-1.png)-->
25+
26+
27+
## Data Box Disk Unlock tool errors
28+
29+
30+
| Error message/Tool behavior | Recommendations |
31+
|-------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------|
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. |
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. |
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. |
35+
| Could not find locked volumes. Verify disk received from Microsoft is connected properly and is in locked state. | The tool fails to find any locked drives. Either the drives are already unlocked or not detected. Ensure that the drives are connected and are locked. |
36+
| Fatal error: Invalid parameter<br>Parameter name: invalid_arg<br>USAGE:<br>DataBoxDiskUnlock /PassKeys:<passkey_list_separated_by_semicolon><br><br>Example: DataBoxDiskUnlock /PassKeys:passkey1;passkey2;passkey3<br>Example: DataBoxDiskUnlock /SystemCheck<br>Example: DataBoxDiskUnlock /Help<br><br>/PassKeys: Get this passkey from Azure DataBox Disk order. The passkey unlocks your disks.<br>/Help: This option provides help on cmdlet usage and examples.<br>/SystemCheck: This option checks if your system meets the requirements to run the tool.<br><br>Press any key to exit. | Invalid parameter entered. The only allowed parameters are /SystemCheck, /PassKey, and /Help.|
37+
38+
39+
## Unlock issues for disks when using a Windows client
40+
41+
This section details some of the top issues faced during deployment of Data Box Disk when using a Windows client for data copy.
42+
43+
### Issue: Could not unlock drive from BitLocker
44+
45+
**Cause**
46+
47+
You have used the password in the BitLocker dialog and trying to unlock the disk via the BitLocker unlock drives dialog. This would not work.
48+
49+
**Resolution**
50+
51+
To unlock the Data Box Disks, you need to use the Data Box Disk Unlock tool and provide the password from the Azure portal. For more information, go to [Tutorial: Unpack, connect, and unlock Azure Data Box Disk](data-box-disk-deploy-set-up.md#connect-to-disks-and-get-the-passkey).
52+
53+
### Issue: Could not unlock or verify some volumes. Contact Microsoft Support.
54+
55+
**Cause**
56+
57+
You may see the following error in the error log and are not able to unlock or verify some volumes.
58+
59+
`Exception System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.Management.Infrastructure, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.`
60+
61+
This indicates that you are likely missing the appropriate version of Windows PowerShell on your Windows client.
62+
63+
**Resolution**
64+
65+
You can install [Windows PowerShell v 5.0](https://www.microsoft.com/download/details.aspx?id=54616) and retry the operation.
66+
67+
If you are still not able to unlock the volumes, copy the logs from the folder that has the Data Box Disk Unlock tool and [contact Microsoft Support](data-box-disk-contact-microsoft-support.md).
68+
69+
## Next steps
70+
71+
- Learn how to [troubleshoot validation issues](data-box-disk-troubleshoot.md).

0 commit comments

Comments
 (0)