Unable to upgrade basic disk to an Infoscale Dynamic Diskgroup.
book
Article ID: 100060857
calendar_today
Updated On:
Description
Error Message
Warning V-47-1-46
Only the empty disks you chose will be upgraded.
At least one disk does not have 16 MB unpartitioned space at the end of the disk, which is needed for upgrade.

Cause
This message can come on either MBR or GPT disks.
MBR disks will require at least 16 MBs of free unpartitioned space at the end of the drive to be converted to an InfoScale Dynamic Diskgroup.
GPT disks will need to have the MSFT_RESERVED_PARTITION size of at least 32 MB in order to fit the 16 MB InfoScale private region inside it. Use the OS diskpart.exe utility to confirm the incompatible size of the reserved region as follows.

Resolution
For disks initialized as MBR, shrink the partition by 16 MB using Windows Disk Management and retry the upgrade basic disk to InfoScale Dynamic Diskgroup operation.
For disks initialized as GPT with a reserved too small region, do one of the following options.
Option 1 - Backup and restore data
- Backup the data on the partition(s) that currently exists on the disk(s).
- Using Windows Disk Management (diskmgmt.msc),
- Delete all partitions from the disk.
- Convert the disk to MBR.
- Using Veritas Enterprise Administrator,
- Convert the disk to GPT.
The GPT size should now be either 32 MB or 128 MB depending on the size of the disk. Use the steps from the Cause section above to validate the GPT reserved region size.
- Create a new InfoScale Dynamic Diskgroup with the newly initialized disk.
- Create a new volume(s) in the InfoScale Dynamic Diskgroup and assign the drive letter(s) as needed.
- Restore the data to the volume(s) from the backup that was done in step 1.
Option 2 - Mirror the partition to a new disk using a Windows Dynamic Diskgroup.
- Add a new disk(s) to the server that is at least 128 MB larger than the original disk(s). This larger size is needed to allow room for a larger GPT region.
- The maximum size is 128 MB for the GPT reserved region.
- The same size disk can be used. However, the partition(s) must be shrunk by 128 MB to allow space for a larger GPT reserved region
.
- Using Veritas Enterprise Administrator,
- Online the new disk(s).
- Write a new signature to the new disk(s).
- Click "GUID Partition Table (GPT)"
- Select the new disk(s) from step 1.
The GPT size should now be either 32 MB or 128 MB depending on the size of the disk. Use the steps from the Cause section above to validate the GPT reserved region size.
- Using Windows Disk Management (diskmgmt.msc),
- Right click on the disk and select "Convert to Dynamic Disk..."
- In the pop-up, select the disks to be converted, select the original disk(s) and the newly added disk(s)
- Using Veritas Enterprise Administrator,
- Select the windows compatible Diskgroup and go to the volumes tab on the right.
- Right click on the volume and select Mirror > Add
- Select the new disk to mirror the volume to.
- After the volume has finished the resynching process then continue with the next steps.
- Using Windows Disk Management (diskmgmt.msc),
- Right click on the original disk and select "Convert to Basic"
- Right click on the original disk and select "Convert to MBR"
The original disk can now be reclaimed by the storage array or it can be converted to GPT using Veritas Enterprise Administrator and used for other purposes on this server as needed.
- Using Veritas Enterprise Administrator,
- Right click on the Windows Compatible Diskgroup and select "Convert to SFW Dynamic Disk Group".
- Answer the questions in the two pop-ups. A reboot may be needed to complete the conversion to SFW/InfoScale Dynamic Diskgroup. Please plan accordingly for possible downtime.
- After the reboot, the Diskgroup may need to be imported with the "Clear Host ID" checked.
- The Diskgroup will show as Type: (Secondary, Windows Compatible). Right click on the Diskgroup and select "Upgrade Dynamic Disk Group Version" to remove the "Windows Compatible" type from the diskgroup. Now all advanced features of the InfoScale version being used will be available to this InfoScale Dynamic Diskgroup.
Issue/Introduction
Unable to upgrade basic disks to an InfoScale Dynamic Diskgroup.
Was this article helpful?
thumb_up
Yes
thumb_down
No