After the Core service starts, the repository does not mount automatically with the repository check job. The UI shows a similar error message as your repository configuration may differ:
Error mounting the volume [VolumeDescriptor{RepositoryId=64f1d83a-c46e-47d1-bfe4-9c2f5ea29340,DeviceId=1,AllocationPolicy=Striped,FileSystems='[FileSystem{RepositoryId=64f1d83a-c46e-47d1-bfe4-9c2f5ea29340,DeviceId=1,DataPath=E:\RR\repo1\data,MetadataPath=E:\RR\repo1\meta,WriteCachingPolicy=On}]','[FileSystem{RepositoryId=64f1d83a-c46e-47d1-bfe4-9c2f5ea29340,DeviceId=2,DataPath=F:\RR\Repo1\data,MetadataPath=F:\RR\Repo1\meta,WriteCachingPolicy=On}]','[FileSystem{RepositoryId=64f1d83a-c46e-47d1-bfe4-9c2f5ea29340,DeviceId=3,DataPath=G:\RR\Repo1\data,MetadataPath=G:\RR\Repo1\meta,WriteCachingPolicy=On}]','[FileSystem{RepositoryId=64f1d83a-c46e-47d1-bfe4-9c2f5ea29340,DeviceId=4,DataPath=H:\RR\Repo1\data,MetadataPath=H:\RR\Repo1\meta,WriteCachingPolicy=On}]'}] - Error(s) 'DvmMountFailed' (0x80131500)
The AppRecoveryLog.txt file also shows a similar event as your repository metadata configuration may differ:
ERROR 2017-02-14T10:12:51 [38] - unmanagedDvm.storageSubsystem (Job Id = e362a7c0-16d1-4adb-b7a9-ec0b1dd13ce8:MaintainRepositoryJob 210044bd-33b6-4990-ac23-dde5daf6da8b:MountRepositoryJob)
<03:12:51 PM> 02/14/2017: filesystem <1>: file size 2296633096704 in the master boot record for device id 1 does not match actual filesystem size 2296633098240. aborting mount
This error event is caused by the dfs.records_ids (repository index) file not aligned correctly and only is only detected during a repository mount operation.
WORKAROUND:
To resolve the issue, a full repository check needs to be performed. Please complete the following steps:
This operation will automatically realign your repository files to the correct size. Once the job completes, your repository should mount correctly.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center