Share via

Storage Replica Error 3004

Anonymous
2024-02-02T10:13:44+00:00

I'm using storage replica on server 2019 datacenter. There is an error in the logs

Unable to read record from the log.
ReplicationGroupName: Group
ReplicationGroupId: {afdee3c5-f38b-4cd3-82ee-876bdb53e477}
ReplicaName: f:\
LogFile: LOG:\Device\Harddisk5\ClusterPartition2\System Volume Information\StorageReplicaLogs\{afdee3c5-f38b-4cd3-82ee-876bdb53e477}\{6234fb5e-c484-4229-963d-23bce468cf7c}19
Record LSN: 0x12DCD000
Status: The object was not found.

Guidance: Possible causes include inaccessible log volume or log corruption. Storage Replica will not replicate corresponding data volumes until the issue is resolved. Make sure the log volume is accessible and there is nothing preventing access to the log files such as filesystem filter drivers. Once the condition is resolved try to bring the Replication Group online.

Re-creating the replica and the disk with logs will not solve the problem.
Windows Server High availability Clustering and high availability

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

5 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-02-05T02:08:01+00:00

    Hi EvgeniySibenkov,

    Hope you're doing well.

    1. Ensure that the log volume is accessible. Check for any issues related to permissions, connectivity, or disk failures.
    2. Corruption in the log files can lead to this error. Verify the integrity of the log files.
    3. Check all VMs status.
    4. Check whether there exists 3rd party software (like anti-virus). If so, please try to disable it.

    Best Regards

    0 comments
  2. Anonymous
    2024-02-06T14:21:47+00:00

    I checked all the listed items and found no problems. The error appears periodically.

    0 comments
  3. Anonymous
    2024-02-07T02:37:51+00:00

    Hi EvgeniySibenkov,

    Thanks for your update.

    Please provide me the following information:

    Please open PowerShell as an administrator and input the following commands and send me the results:

    (1) Get-SRPartnership

    (2) Get-SRGroup

    (3) Test-SRTopology -SourceComputerName xxx -SourceVolumeName xxx -DestinationComputerName xxx -DestinationVolumeName xxx

    In addition, please check whether exist errors in Event logs.

    Best Regards

    0 comments
  4. Anonymous
    2024-02-07T07:55:33+00:00

    my logs

    0 comments
  5. Anonymous
    2024-08-08T21:49:09+00:00

    Same exact issue here and it appears to be causing read/write issues with the application using the volume. Any luck finding a resolution?

    0 comments