Quantcast
Channel: File Services and Storage forum
Viewing all articles
Browse latest Browse all 13565

NTFS warnings and errors - ID 57 and 137

$
0
0

Hi! since the 4th of january I've seen NTFS errors 57 and 137 in the event log of one of our servers.
Saying:
57 - The system failed to flush data to the transaction log. Corruption may occur
137 - The default transaction resource manager on volume \\?\Volume{da4147bc-b6e1-11e5-aea0-005056af0080} encountered a non-retryable error and could not start.  The data contains the error code.

I've seen other have the issue here in the forums, and I found an article saying this can be ignored.

But does anyone know why they suddenly can appear? Everything was fine until the fourth at 6 PM

The volumes mentioned in the 137 warning, cannot be found on the server.

Why is a volume mentioned that is not on the server? How is the value created for a volume that is not there?

Is there no solution to this?


Freddy


Viewing all articles
Browse latest Browse all 13565

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>