Disk error?

richie43 · 06-17-2020, 07:01 PM

has anyone seen this before? It's happened twice randomly recently, specifically doing a "save as".. Hard drives are good, and I am not finding any errors.

"error: one or more disk writes failed during project save! A disk could be failing or have become disconnected.

You may wish to try saving to a different disk before diagnosing the error"

karbomusic · 06-17-2020, 07:12 PM

Does the "System" Log in Windows Event Viewer show any errors or warnings for disk? If there were errors that serious happening, there's a chance the OS logged it there. No guarantee but it's useful enough that I check it about once a month because if there are disk issues on the horizon, it often has early warning signs.

The error verbiage sort of reads like the OS told Reaper that the device was no longer there for a moment but I can't be sure.

richie43 · 06-17-2020, 07:26 PM

Huh....a zillion of them in the system log. Starting on the 15th. On my C drive, supposedly. Most of them are errors, but today there are warnings as well.
Errors are "The default transaction resource manager on volume C: encountered a non-retryable error and could not start. The data contains the error code."

Warning reads "The default transaction resource manager on volume C: encountered an error while starting and its metadata was reset. The data contains the error code."

karbomusic · 06-17-2020, 07:32 PM

Whats the "Source" of that error. In the list, each column has a name, what is listed under the Source column? And the EventID Number?

richie43 · 06-17-2020, 07:33 PM

Why is it doing this only when I do a "save as" in Reaper? I have never seen this message before besides Reaper related...happened years ago and mysteriously stopped.

richie43 · 06-17-2020, 07:34 PM

Source is "Ntfs (Ntfs"
Event ID for error is 137, warning is 136

karbomusic · 06-17-2020, 07:36 PM

OK, that's the NTFS transaction log database - If you search for that error text you'll see some steps to fix. I'm not sure it's 100% related to the Reaper error but could be. Are there any other disk related errors other than those?

richie43 · 06-17-2020, 07:37 PM

No others.... but there are over 79,000 since June 15th!

richie43 · 06-17-2020, 07:38 PM

What error text am I searching for?
\

karbomusic · 06-17-2020, 07:43 PM

https://answers.microsoft.com/en-us/...c-68b599b31bf5

I know little about the issue but I'd make sure you have your stuff backed up just as a precaution. Not 100% sure this is related to the reaper error but could be.

I can say those transaction logs are what allow the OS to fix corruption on the fly as they are backups of the real sectors (likely only recent writes), but here those transaction logs themselves are corrupt. Sounds dangerous so probably should be addressed unless is some false alarm I'm not aware of.

Of course if you are saving your project to something other than C:, that may remove reaper from the picture a littler further.

richie43 · 06-17-2020, 07:45 PM

So the error that I posted the screenshot of is generated by Reaper, or the OS?

richie43 · 06-17-2020, 07:46 PM

The system log says it's on my C drive, which is OS and programs only for me. All of my audio is on a separate physical drive.

Jae.Thomas · 06-17-2020, 08:00 PM

this just happened to me a bunch of times today.

are you using a pre?

richie43 · 06-17-2020, 08:47 PM

Quote:

Originally Posted by Jason Brian Merrill

this just happened to me a bunch of times today.

are you using a pre?

Yes!

I am going to install the latest stable and see what happens.

richie43 · 06-17-2020, 08:47 PM

Quote:

Originally Posted by Jason Brian Merrill

this just happened to me a bunch of times today.

are you using a pre?

Same error code?

karbomusic · 06-17-2020, 08:48 PM

Quote:

Originally Posted by richie43

So the error that I posted the screenshot of is generated by Reaper, or the OS?

The error in the screen shot is from reaper, it reads as if Reaper got some type of bad news back from the OS while trying save the project.

The error we found in the system log may or may not be related to that, but I'd keep an eye on it because if it isn't a false alarm it's probably prudent to fix, whether it's related to Reaper or not. And they are filling up the Event log which we don't want.

Are both of you on the same build or some new pre? It sounds more like the disk wasn't happy but might as well start eliminating the obvious just in case it's reaper.

richie43 · 06-17-2020, 08:49 PM

Quote:

Originally Posted by karbomusic

The error in the screen shot is from reaper, Reaper got some type of bad news back from the OS while trying save the project.

The error we found in the system log may or may not be related to that, but I'd keep an eye on it because if it isn't a false alarm it's probably prudent to fix, whether it's related to Reaper or not.

Are both of you on the same build or some new pre? It sounds more like the disk wasn't happy but might as well start eliminating the obvious.

I followed the fix from the link you sent already. I am going to fire up Reaper right now and see.

karbomusic · 06-17-2020, 08:52 PM

There is also a pretty clear instruction in the screenshot so you do need to see if you can save to a different disk platter and still repro:

"You may wish to try saving to a different disk before diagnosing the error"

richie43 · 06-17-2020, 08:54 PM

Quote:

Originally Posted by karbomusic

There is also a pretty clear instruction in the screenshot so you do need to see if you can save to a different disk platter and still repro:

"You may wish to try saving to a different disk before diagnosing the error"

Does this mean save the project file, the rpp? I can change it in preferences and do that,...but it didn't error every time, so....?

richie43 · 06-17-2020, 08:55 PM

I have done a few "save as", so far no errors
.

karbomusic · 06-17-2020, 08:56 PM

Quote:

Originally Posted by richie43

Does this mean save the project file, the rpp? I can change it in preferences and do that,...but it didn't error every time, so....?

Yea, just Save As then browse to another disk drive and save there if there is another one to browse to. Yea, if it doesn't do it every time then you Save As to another drive, and just work with it there until... Guess it all depends on how often/predictable the repro is.

richie43 · 06-17-2020, 08:56 PM

Quote:

Originally Posted by karbomusic

There is also a pretty clear instruction in the screenshot so you do need to see if you can save to a different disk platter and still repro:

"You may wish to try saving to a different disk before diagnosing the error"

Um...I am a language nut (poet, editor, writer...)...
Those are not clear instructions to save to a different disk before diagnosing..."You may wish to try..."
I did not wish to try.

Next?

richie43 · 06-17-2020, 08:57 PM

Quote:

Originally Posted by karbomusic

Yea, just Save As then browse to another disk drive and save there if there is another one to browse to.

I have 5 installed hard drives in this computer...ha ha. maybe someday I will upgrade to ssd's.....

karbomusic · 06-17-2020, 08:58 PM

Quote:

Originally Posted by richie43

I have done a few "save as", so far no errors
.

Fingers crossed but sometime those little varmints know we are looking and stop reproing.

richie43 · 06-17-2020, 09:04 PM

Quote:

Originally Posted by karbomusic

Fingers crossed but sometime those little varmints know we are looking and stop reproing.

Did you see Jason Brian Merrill's post? Same issue since using a pre. Weird.

varmints indeed!

karbomusic · 06-17-2020, 09:06 PM

Quote:

Originally Posted by richie43

Did you see Jason Brian Merrill's post? Same issue since using a pre. Weird.

varmints indeed!

Yea compare pre build numbers and he should confirm if he has those same errors or not in the windows system log.

richie43 · 06-17-2020, 09:15 PM

Quote:

Originally Posted by karbomusic

Yea compare pre build numbers and he should confirm if he has those same errors or not in the windows system log.

Yup.
Thanks again for your expertise.

Jae.Thomas · 06-18-2020, 06:22 AM

I recently updated to 6.12 dev0617 so maybe we should take this to the pre forum?

Justin · 06-18-2020, 06:29 AM

This is a new thing in 6.12+dev (as JBM noted), so I moved this to the pre-release forum.

Interesting, it's very likely that this error is being mis-reported (and you can ignore for now). Any steps to reproduce?

Edit: ah I think I see why it might be, hopefully fixing for the next build!

richie43 · 06-18-2020, 06:30 AM

Quote:

Originally Posted by Jason Brian Merrill

I recently updated to 6.12 dev0617 so maybe we should take this to the pre forum?

We should.
For now I am using the last stable release, did the steps described in the Microsoft link Karbo posted, and am having zero problems.I will reinstall the pre as a portable and see if it happens again

Jae.Thomas · 06-18-2020, 06:32 AM

Quote:

Originally Posted by Justin

This is a new thing in 6.12+dev (as JBM noted), so I moved this to the pre-release forum.

Interesting, it's possible that this error is being mis-reported. Any steps to reproduce?

im going to open the exact project I had, but I forgot exactly what dev I was on before, unless nothing changed in the last few. Def a 6.12 dev

Justin · 06-18-2020, 06:54 AM

I can't duplicate but I have a pretty good idea of what it probably is, today's +dev build should hopefully fix!

Jae.Thomas · 06-18-2020, 06:59 AM

just got it simply by leaving that project open

Jae.Thomas · 06-18-2020, 07:01 AM

happened again by hitting save. Didn't happen on the other project.

no associated event viewer entry

well, there's some complaining about TLS and network stuff but that's all over the place