NUC Overheating Trying to Add 2 Files to Library

Roon Core Machine

Intel NUC NUC8i7BEH Mini PC/HTPC, QUAD-Core i7-8559U Up to 4.5GHz, 32GB RAM, 1TB NVMe SSD, WiFi, BT 5.0 Thunderbolt 3, 4k Support, Triple Monitor Capable, Win 10 Pro (32GB RAM + 1TB NVMe SSD)

Data Stored on Asustor LOCKERSTOR 10 (AS6510T)

Tidal, Qobuz scriptions.

Ethernet Connected.

Networking Gear & Setup Details

Netgear throughout.

Connected Audio Devices

NODE2

Number of Tracks in Library

800k

Description of Issue

When I start Roon or add new files Roon continues to look for 2 files to add to my library. The problem is it takes hours to “find” these 2 files. Now my issue is my NUC shuts down because of overheating. I’ve search for these files and I’m not sure what they are. I’ve checked skipped files and see no real issues. There are a few that are I/O errors or unable to read Image file message but these have been listed since I began using Roon 14 months ago. The overheating doesn’t affect the normal library load or the adding of new files. It only overheats spending hours looking for these 2 rogue files. My feeling is that if I can identify and delete these files the overheating issue will be solved as it only occurs hours after new files are added.

BTW I’ve opened and cleaned the NUC.

Also disabled both Tidal and Qobuz in case they were the issue. They weren’t.

Now I’m without Roon until this is solved since every time I launch Roon it starts looking for the 2 files. Can the support team help me?

The “rogue” files may be the symptom, rather than the disease. Your 800,000 track library may be too large for a mobile processor and 32 GB RAM.

AJ

When you say “data stored on Assustor…” is that your music files?
If so, have you tried disabling the storage (temporarily) to see if the files Roon is looking or are on that drive?

Do you have a good DB backup file from before this issue started?
If support can look at the fault they might be able to identify the files, however, I suspect that you may be heading for a re-install and restore of DB.

Worst case would be that the files are corrupt due to a failing drive? How old are the drives involved?

Thanks for your reply. I could agree but I’m not sure if that’s the case. I’ve been running Roon for 14 months w/o this issue. All I’d like to do is determine which files (even if ghost files) are causing the issue.

Thanks for you reply. I have two full backups. If I’m headed in a full restore so be it but I don’t think the NUC will handle it. I don’t see any corrupt files listed in Skipped Files. I did have one listed a while back and deleted it and replaced it. It didn’t show in skipped files again.

EDIT: the only thing on the Asustor are music files. The only app running on the NUC other than a few utilities is Roon.

Drives are WD Red and less than a year old. Asustor shows no issues with the drives.

As an aside I have an identical NUC running Logictech Media Server and have zero issues with it.

I would think that support would offer help since I’m paying to use their product.

Yes, I think support should chime in here.

I have seen something similar to this on the forum, in their case the library got hung on several files and never seemed to finish analyzing (their device did not overheat due to the issue, though). They were able to identify approximately when the issue started and what albums they added to Roon around that time and methodically removed the albums and ultimately identified the problem files.

Thanks for your reply.

Is there anyway I can be assured support will see this thread?

I’ve read that placing #support will somewhere in this thread will alert support then somewhere else said that’s not necessary since the Support topic is monitored by the Support Team and that wasn’t neccessary.

I’ve search for large files and other types of files I may have left in my library that may cause the issue. I found 2 large FLAC files and a few ISOs, I deleted them and that didn’t solve my issue.

It’s already in the support section, but they are backlogged with tickets so it might not get a response before the end of the weekend (not sure if today and Monday are holidays in the US either)

I will have to agree with some other posts here that no NUC is really able to support 800,000 track’s even with 32GB of memory. The two files maybe a symptom that it has been struggling but managed just about to keep up before now.

I am not sure what the best spec machine for your library size is, but I imagine a full desktop processor with high single core performance

Thanks!

Very helpful to know.

Sometimes it “finds” those 2 files in a short amount of time. Other times it runs all night.

Depending on Support’s analyzing my situation I may have to upgrade or downsize my library for Roon and let my LMS NUC handle the rest. I do have some options.

Good to know that options are available.
I imagine that Support will turn on enhanced logging for you which will hopefully help to pin point the problem and get you back to working again

Assuming it’s possible given the size of your library, I’d look at a single usb connected large capacity drive rather than a NAS. This might fix the latency problem you’re experiencing. You can then set up an rsync cronjob to back everything up to the NAS.

if you’d like to test this now, one way to go at it might be to temporarily add a directly connected smaller drive, and adding your files to that.

One other option (perhaps) is to buy a new NUC with a larger memory capacity. I see Intel now has NUCs that handle up to 64. Not sure that would solve the issue if the culprit is the number of files. I know I’m up there in number files probably 99.8% or so. I’ve read other posts about number of files other users have so I know I’m in a tiny majority but after 20 years of doing this what would one expect? :grin:

And it’s an expensive option for sure.

1 Like

Thanks for your suggestion.

I need to think about less time consuming testing until I hear what support has to say.

I have 6 folders on the NAS. One thing I had thought about was installing Roon on the other identaical NAS and making that the core. Then I could scan the smallest of the 6 folders and see if those 2 files appear there. If not then scan a different folder.

Not sure if that would be helpful, however.

I don’t think it would be.

You also need to keep in mind that LMS isn’t Roon in terms of how demanding it is of the underlying hardware. If anything, and given the size of your library, I’d install ROCK on the NUC you’re currently using for Roon, import my current database from a backup, and see what happens.

My hunch is that spinning up the NAS / searching on a remote filesystem could be part of the issue you’re seeing, so I’d start by following @danny’s general recommendation and try something directly attached.

Want not time consuming ? Plug a USB flashdrive into the NUC, add it in Roon, then dump the two problematic files on it. It’s a temporary solution, but it might tell you if the issue is with the NAS / networking / whatever.

While I’d guess your issue has more to do with networked filesystem issues, you’re still probably in the top percentile in terms of library sizes, and while a million + tracks is within the realm of possibility on Nucleus+ equivalent hardware (so an i7 NUC), it’s still pushing it, so you should really aim for lean and mean there: ROCK, so nothing else running on it, directly attached drives, the works.

I think you might want to move up to a full size processor instead of mobile and the 8th Gen is one of the better options in what you already have.

I think some people are having a good run with the mini intel Ryzen CPU buit it’s worth waiting to see what support say.

I would say you are probably in about the top 1%-2% of owners in term’s of Library size. And pretty impressive that is as well. I have about 68k local tracks and I have been collecting for about 43 years. Much respect to you :+1:

Thanks. I’m begining to a better insight on my issue.

I’ve tried ROCK…twice. It was a huge disappoint. It was slower than one could imagine. I ditched it for my current setup.

I’ve always known that LMS wasn’t a huge resource hog but didn’t have a deep knowledge of what Roon did and what the hardware aspects were when I started using it. If I had a clearer understand I doubt I would have tried it. If I hadn’t renewed my subscription 2 months ago I doubt if I’d be here posting at all. I like Roon and hope (somehow) I can get it to work for me.

Thanks, Micheal.

I’ve been collecting since 1964. Once the world became digital it did change things but I found (at times) there are many tracks that just aren’t available on streaming service. And I’m too lazy to dig out an album be it on vinyl or cd when I can just click from here and away I go! :smile:

If I have to upgrade I may be asking you for some advice!

1 Like

Hi @mudbone,

Thank you for your patience as we worked through an unusual uptick in our queue to reach your report.

We’ve attempted to pull diagnostic reports from the affected NUC, but found the device as offline. At your convenience, please boot up the affected Core for at least a few hours to the reports have a chance to reach our server. Alternatively, you can use the directions found here and send over a set of logs to our File Uploader?

This topic was automatically closed 45 days after the last reply. New replies are no longer allowed.