Roon Server not booting some times and takes too long

Core Machine (Operating system/System info/Roon build number)
Ubuntu 12.04
Kernel 5.10.0
CPU Intel® Atom™ x5-E8000
Memory 4GB
Storage 256 GB (SSD)

Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
1 Wired ethernet / DHCP / 1G

Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)
None / Just Roon Ready device

Description Of Issue
Roon server does not boot sometime.
When I check systemctl status message

Initializing --> Started --> Not Responding --> Error forever loop.

Roon Server Logs always same as follows when it restart

  1 01/15 04:30:41 Info: Starting RoonServer v1.7 (build 710) stable on linuxx64
  2 01/15 04:30:42 Trace: Checking if we are already running
  3 01/15 04:30:42 Warn: get lock file path: /tmp/.rnsems0-roon
  4 01/15 04:30:42 Trace: Nope, we are the only one running
  5 01/15 04:30:42 Info: Is 64 bit? True
  6 01/15 04:30:43 Trace: [orbit] init seq=37, pending=2, spcount=7, uidcount=2
  7 01/15 04:30:44 Info: Command Line Argument: -watchdogport=38423
  8 01/15 04:30:44 Trace: [childprocess] using .NET child process
  9 01/15 04:30:45 Trace: [realtime] fetching time from NTP server
 10 01/15 04:30:45 Info: [stats] 424mb Virtual, 34mb Physical, 16mb Managed, 0 Handles, 7 Threads
 11 01/15 04:30:47 Info: [broker] starting ad707ddd-338a-4769-8de5-1d4f9671f3d4
 12 01/15 04:30:48 Trace: [httpcache] loaded 1186 cache entries from /var/roon/RoonServer/Cache/httpcache_2.db, current: 82mb / 128mb
 13 01/15 04:30:50 Debug: [broker/filebrowser/nassharemaker] rebuildsymlinks
 14 01/15 04:30:50 Debug: [broker/filebrowser/volumeattached] initial listing found drive mounted at /
 15 01/15 04:30:50 Debug: [broker/filebrowser/volumeattached] initial listing found drive mounted at /mnt/RoonStorage_b657a3dc4a3cdd9ac8fad950a133a7d97fadf70d
 16 01/15 04:30:50 Debug: [broker/filebrowser/volumeattached] skipping /mnt/RoonStorage_b657a3dc4a3cdd9ac8fad950a133a7d97fadf70d because it is not a /dev/sd[0-9]* (mountline: //19    2.168.0.87/Slot4 /mnt/RoonStorage_b657a3dc4a3cdd9ac8fad950a133a7d97fadf70d cifs rw,relatime,vers=2.1,cache=strict,username=root,domain=WORKGROUP,uid=0,noforceuid,gid=0,noforce    gid,addr=192.168.0.87,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=1048576,wsize=1048576,bsize=1048576,echo_interval=60,actimeo=1 0 0)
 17 01/15 04:30:51 Warn: [realtime] failed to get time: Operation on non-blocking socket would block

A lot depends on your library size, but I would check your PC spec against Roon’s minimum requirement,

As far as I see the Atom is a 1 ghz clock and is probably underpowered for Roon , but I am no expert on CPU’s

Hi @hobeom_park,

As Mike suggested above, your Core machine doesn’t quite meet our requirements. How many tracks total are in your library?

Do you have any machine that meets our requirements that you could try temporarily?

Hi @hobeom_park
It may not that relevant for this support request, but Audio Device includes Roon Ready devices, basically anything the Roon is using (or attempting to use) as a audio zone. Roon ask this to get a full picture of your setup which aid them to diagnose the issue.

Thanks for your help.

All other systems run without problems.
Yes, it has to do with system performance.
I am wondering if there is a parameter increment timeout parameter, etc.

Hello @hobeom_park,

Thanks for confirming other systems work without issue.

Since the Core you wish to use does not meet our minimum requirements, we suggest using another Roon Core. You will very likely run into performance issues on an Atom CPU as you’ve seen.

Also, since you are using Ubuntu as a Roon Core, I would check to make sure it isn’t by any chance related to this issue:

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