Any Way to Recover "Orphaned Files"?

[machineghost]

Linux Version: Linux Mint 18.2
Audacity Version: 2.3.2 (the latest in the repository)
Source: Distribution Repository

I have never, in my entire life, simultaneously loved and hated a single piece of software more than I love/hate Audacity

When it's working, Audacity is perfect. It's exactly the tool I need, and no other tool can even seem to compare (especially now that I have a few Nyquist scripts/plug-ins that generous people on this forum have shared with me).

The problem is, it crashes several times per hour. It crashes by freezing, so even if I run it from the command line there is absolutely no output indicating what went wrong. But even that is really just an annoyance, because usually it recovers my file. Even if I choose not to recover it, I usually only lose my work from that session: I still have my original file.

However, twice in the past week Audacity has crashed in a way that it loses all the track info. When I come back to the file it tells me that everything has been orphaned, and nothing I've tried doing afterwards fixes things. I then have a file with tracks of the exact right length ... but no audio in them.

I did change the name of a different project in the same folder recently, but I did not rename that particular project. I also didn't do anything else that I've read could cause this.

So two questions:

A) Is there any way to recover this entire file's worth of work? The data seems like it's all still there, just "orphaned" (which I assume means not associated with any track). Is there any way I can listen to the tracks (I tried listening to the files in the data folder but that didn't work) and somehow tell Audacity "this file is track #1, that file is track #2, ..."? Or better yet, any way to have Audacity figure it out for me?

B) What can I do to prevent this in the future? Again, I <3 Audacity, and I don't want to change to a different program! But obviously crashing multiple times per hour and losing an entire file (for me 15-20 minutes of audio, which takes several hours of effort) on a weekly basis is no bueno.

[kozikowski]

So two questions:

Only one:

How do I keep Audacity from crashing?

Did you build your machine? Is there an exhaustive Linux memory checker? The one that loops and you leave running all night?

Video and audio production programs take lots of elbow room. Creating a spreadsheet may not take up lots of memory, but if you're trying to create a multi-hour, multi-channel stereo production, you're going to go right out to the extremes of memory in a heartbeat. Any memory problems waiting out there have the signature of "only failing every other day or so."

usually it recovers my file.

I have never needed Audacity to recover my files on multiple machines in all three operating systems. Your machine is broken.

This is where the Linux forum elves step in and start you with diagnostics and repair before you create any more damage.

Start with the memory checker. That can turn up a whole raft of problems.

Are you using Cloud Storage or Network Connected Drives? You should probably stop. Audacity doesn't always get along with those.

Koz

[kozikowski]

Screen Shot 2019-06-25 at 17.24.51.png (51.51 KiB) Viewed 750 times

Adapt that to your machine.

Koz

[machineghost]

First off, thanks so much for responding.

Second, Ubuntu no longer provides a memory tester on their live CD (which of course, Murphy's Law, I had to download, make a live USB boot disk, and boot to actually discover). For future reference I would suggest you refer people (including anyone reading this later on) to download the (free version of) MemTest https://www.memtest86.com/download.htm. That will give you a zip file with a "memtest86-usb.img" image file in it. You can burn that to a DVD ... or you can use the package usb-creator-gtk (or usb-creator-kde, whichever floats your boat) to make a bootable USB stick out of it.

I did that, booted up mem test, and got 91% through it before I had to reboot for work. Tonight after I'm done I'll boot up into it again and run the full test suite ... but given that it got 91% through without finding anything, and given that this is a professionally built laptop and not a home-built desktop (I've built plenty of desktops myself, this just happens not to be one of them) I don't think my memory is the problem.

But I will try to confirm that 100% tonight. Thanks again.

[kozikowski]

I don't think my memory is the problem.

I don't either, but I've had enough of those fail to want to make sure before galloping off with exotic tests and odd assumptions.

but given that it got 91% through without finding anything

Doesn't count.

Memcheck "Charging Rhinoceros" test failed memory location: bank 4 element 37. Pass 26, 04:36 hours.

I'm making up the details, but not the event. Memcheck requires that the rest of the machine be in top condition, too. If it's not you get migrating errors.

There is no reason for Memcheck to ever fail.

I do wonder why Steve isn't here yet. He's the Linux Practitioner.

Koz

[kozikowski]

Charging Rhinoceros

Did you look at the test suite? The individual tests all have adorable names like "Rippling Checkerboard" and "Wandering Digits."

Koz

[machineghost]

I don't think my memory is the problem.

I don't either, but I've had enough of those fail to want to make sure before galloping off with exotic tests and odd assumptions.

but given that it got 91% through without finding anything

Doesn't count.

Memcheck "Charging Rhinoceros" test failed memory location: bank 4 element 37. Pass 26, 04:36 hours.

I'm making up the details, but not the event. Memcheck requires that the rest of the machine be in top condition, too. If it's not you get migrating errors.

There is no reason for Memcheck to ever fail.

I do wonder why Steve isn't here yet. He's the Linux Practitioner.

Koz

Sorry for not responding sooner. I completed a scan (100%) and it found nothing. Any other suggestions would be welcome.

[machineghost]

Just to recap:

Your machine is broken.

It's not, it's working just fine with every other program I use. Furthermore:

Start with the memory checker. That can turn up a whole raft of problems.

Did that, it passed with flying colors. Machine != broken.

Are you using Cloud Storage or Network Connected Drives? You should probably stop. Audacity doesn't always get along with those.

Not using those.

So is there anything I can do except wait for this mythical Steve? Is there nothing at all in-between "your computer is broken" and "your computer is possessed by the devil and can't run Audacity"? Like anything else I can try that might help?

As I said, I've tried other programs and they're all a nightmare compared to Audacity. I'm willing to try anything, but I just don't know what to do with software that crashes frequently without giving any debug info whatsoever that I could use to figure out what's wrong.

[steve]

Have you said what you're trying to do (specifically)?
What are your settings in the device toolbar?

[kozikowski]

Like anything else I can try that might help?

You're having an odd/serious problem with Audacity on Linux and the only real support is the forum. We would normally be waiting for someone to arrive that has the same machine config that you do to compare notes. This isn't a help desk although it can seem like one because of the resident Elves Who Have Seen Everything.

But if this fails......

All most of us can do is shoot for generic concepts such as:

I tried listening to the files in the data folder but that didn't work

That could be the Kiss Of Death. The snippets in the _data folder are 6 second actual sound files (except for some graphic files) If they don't play, that's not good news.

And that snaps us back to why your machine and Audacity are unstable. Question 1.

Koz