Corrupted tag issue after backup migration (ref#OTME8X)

What’s happening?

· Something else

How can we help?

· None of the above

Other options

· Other

Describe the issue

Had to migrate to a new computer. When I restored my backup on the new computer, one large tag (4000-5000 albums) was corrupted and had about half the albums it should. I have tried doing a new backup on the old computer but that did not work.

Describe your network setup

Intel(R) Core(TM) i9-14900K 3.20 GHz, Actiontec MI424WR

I would really love some help with this. I don’t seem to have lost any albums but I am not eager to retag 2000-3000 missing tags. I wish Roon was like Firefox where you can just copy your profile in appdata and everything is restored.

Hi @cass_fisher,

Thanks for taking the time to write in!

Corruption is tough in that the only real option would be to attempt to restore from a previous backup that pre-dates the corruption. If you have any additional backups saved before migrating to a new computer, that would be your best bet.

@benjamin I store backups on dropbox but it is not clear to me how to recover deleted backups. The ten backups that I have access to are all corrupted. I have to say that this is very disappointing. I rely heavily on tags but the backup/recovery is really inadequate. It shouldn’t happen that you lose thousands of tags. Also, I don’t know why I am still having memory issues on my new installation. Can you give me some guidance about that?

Any idea why I have continued buffering after doing a backup?
Screenshot 2024-05-29 094310

Hi @cass_fisher,

While this certainly works, I would highly suggest setting up a second backup location more local to your setup. For example, setting up an additional hard drive or over a network share to a dedicated folder on a computer.

This is likely a result of the backup being corrupt. Restoring from a healthy backup restores all library edits and customizations including tags.

This could happen for a variety of reasons, can you provide more insight into what is going on in Roon during this event? How much meta data grooming are you performing? Are you using any third party programs to work your metadata and tags?

From your Roon Server logs, I see Roon having a hard time with a handful of Grateful Dead albums, for example:

Warn: [storage] [directory] Failed to extract tags from 'B:\Grateful Dead\Dick's Picks, Vol. 6; Hartford Civic Center 10-14-83\03 Grateful Dead - The Other One.flac': UnsupportedFormat
Warn: [tagextractionservice] possibly corrupt file (UnsupportedFormat): B:\Grateful Dead\Dick's Picks, Vol. 6; Hartford Civic Center 10-14-83\02 Grateful Dead - Fire on the Mountain.flac

If you remove these issue albums and perform a library clean up, do you still experience issues? Be sure to make a fresh backup before making any edits to your database. :+1:

@benjamin thanks for the reply. I appreciate the suggestion about backups. I do store to my computer as well. Although, I have to say customer service at Dropbox was excellent in recovering lost backups. I moved the files with the bad meta data and will watch what happens. I am hesitant about doing the library cleanup because I don’t know what is being referred to regarding deleted files and disabled storage locations. I suppose I could just restore a backup if something goes wrong. Thanks for the help.

Ok, Library Cleanup seems to have gone well. I’ll keep an eye on memory usage. Thanks.

Still seems to be using a lot of memory.

Hi @cass_fisher,

Thanks for the update.

We’ll need a fresh set of Roon Server logs as well for additional inspection, if you could please use the directions found here and send over a set of logs to our File Uploader?

Thanks!

Thanks @benjamin. I uploaded the logs. I appreciate your taking a deeper look.

Thanks @cass_fisher, can you also provide more information based on my previous request:

@benjamin sorry about that. I am experiencing high memory usage under normal circumstances. There is no metadata grooming or anything like that going on. Thanks again.

1 Like

Thanks for the info @cass_fisher, what are your background and on-demand analysis speeds set to? If you disable both, do you experience the same issues with memory?

@benjamin I have never really adjusted those settings. Currently, they are set at “Fast (8 cores)”/“Fast.” This is where memory usage is at the moment:

@benjamin, just checked what happens if I turn off “Background audio analysis speed” and “On-demand audio analysis speed.” Memory usage stays the same.

Hi @cass_fisher,

Thanks for the report. Unfortunately, I don’t have any additional troubleshooting steps for you to try at this time. Were you ever able to restore from a healthy backup?

If you fully remove Roon from the PC, and create a fresh instance of Roon (not restoring from a backup yet) and only sign in/ sync your Tidal content to this fresh account, do you still experience memory pressure?

We have a ticket in with our dev team for further investigation, but I’m unable to speak on any specific timelines.

@benjamin, just to be clear, you do think Roon is using too much memory on my system? How much memory should it be using (6500 albums)? I will try reinstalling but I am in the middle of a month long work project, so it may not be immediately. I appreciate your help.

Hey @cass_fisher,

It’s not completely out of the ordinary, our team has seen 2-3GB of memory usage happen in Roon sometimes.

As a next step, could you try to increase the virtual memory on the device? Here’s more helpful info:

@benjamin that link was not really clear about what value I should set for 32gb of memory. Apparently, Microsoft recommends against manually setting virtual memory in Windows 11. Since it’s a new install and I am not having any problems (other than my tag corruption, which I will have to fix manually), I think I will hold off on manually setting the virtual memory. Thanks for the help. Let me know if anyone else takes a look at my logs.

https://answers.microsoft.com/en-us/windows/forum/all/how-much-virtual-memory-should-i-get-for-16gb-of/21340fe1-6d86-4d0e-b2f6-5382f8edfacb