Roon 1.8 does not see local folders on Linux ZFS drive [Resolved]

Steef_de_Bruijn · February 9, 2021, 11:39pm

Core Machine (Operating system/System info/Roon build number)

Core on Ubuntu 18.04.05, normally in docker container but have same problem running native. Machine runs all the way on ZFS including the root FS.

Description Of Issue

I have a server running Ubuntu 18 for years on ZFS filesystems (also root file system is ZFS). On this machine I have running docker containers all the time. I never had a problem running Roon server.

After the 1.8 update all runs fine but I do not have access to any local folder. So no music files and no backup locations.

To rule out docker I ran Roon native on this server as a test resulting in exactly the same problem. The only folder I can select is a network share. Nothing else.

Can running my system with root on ZFS be the problem? (Core can’t find the / folder from where to browse to other locations hence this suggestion for the root cause).

For the time being I mounted the local folder as a network share. This works for music but not for backups.

noris · February 10, 2021, 4:53am

Hi @Steef_de_Bruijn ,

Can you please use these instructions to access your Roon logs and upload them for review? If you notice any errors regarding storage in the logs and can post a snippet here that would help, but if not, we can review the logs on our end, thanks!

Bernardo_Meurer_Cost · February 10, 2021, 5:16am

I have the exact same issue as you, and my music is on ZFS too.

I submitted them my logs earlier today, but haven’t heard back.

Steef_de_Bruijn · February 10, 2021, 6:32am

Hi,

Thanks for replying.

I sent a download link for the logs by DM.

Tried different things yesterday evening. Originally ran on docker, now runs native. This pollutes the logs but I guess you will find your way

Please let me know if I should provide more info or should try an isolated scenario.

Steef

Jan_Kuhnemund · February 10, 2021, 7:16am

Exactly the same problem. Core runs on Debian Buster in an LXC Container which is stored on a ZFS ZRaid 1. Roon can’t access any local folder. So I’m stuck with listening to radio.

Bernardo_Meurer_Cost · February 10, 2021, 10:39am

@Jonathon_Wiebe Are you using ZFS as well? I know you’re having the same problem.

Jonathon_Wiebe · February 10, 2021, 4:07pm

I’m using roon in an lxc/d container, I think ZFS is the underlying storage of the container system, but my music is located at a lxd mount point (/mnt/music), which points to an nfs share on the host. Possible ZFS is the shared culprit. I could try it on another machine without ZFS pretty easily. I’ll test today and verify.

Jonathon_Wiebe · February 10, 2021, 4:42pm

Confirmed that roon can see local storage in a VM (not container) backed by different storage. Looks like ZFS breaks roon 1.8 but worked on 1.7.

Dean_Bailey · February 10, 2021, 7:30pm

Misery loves company it seems. I’m experiencing the exact same problem. 25T ZRAID10 backed Docker install of Roon on Xeon D-2146NT with 128G ECC. Getting a message in the Roon UI saying it can’t access the paths. docker exec -it roon /bin/bash followed by a ls of the paths shows the data is where it is supposed to be. x_X

Totally learns me to NOT jump on these big updates at day one.

noris · February 10, 2021, 8:22pm

Hi @Jonathon_Wiebe / @Jan_Kuhnemund / @Dean_Bailey ,

Can you please upload a set of your Roon Core logs for review to Dropbox / Google Drive / etc and send me a link via private message or on this thread? Thanks!

Dean_Bailey · February 10, 2021, 8:33pm

@noris You’re just looking for the RoonServer_log files, yes?

Edit: Logs sent with system details.

Bernard_Languillier · February 10, 2021, 9:48pm

Same problem on a brand new Mojo Dejavu Evo with a custom version of Linux. Not sure what flavor of Linux they are using nor what file system type it’s relying on.

No local folders can be browsed.

It was working fine in 1.7.

Cheers,
Bernard

Robert_Dura · February 10, 2021, 11:09pm

Same issue on Ubuntu 20.10 (zfs-on-root and running Roon in a lxc container - music is stored on separate zfs pool connected to host). Went down with the upgrade.

For local storage settings, the usual breadcrumb and folder selection is missing

Steef_de_Bruijn · February 11, 2021, 12:44am

This was exactly what I was seeing. For now I use network mount to same ZFS dataset exported over smb.

But hope this will be an easy fix. Backups are also a no-no now.

Dean_Bailey · February 11, 2021, 2:01am

@noris I think I found yer problem while seeing if I could get this working using a docker controlled NFS mount. Which I couldn’t, and not because the data wasn’t available in container, the same as with the ZFS.

From log while trying to get NFS mounted data working:

02/10 17:35:40 Info: [broker/locations/directorystoragelocation] initializing FileBrowser.Entry:  / : /music/lossless, drive availability is: False
02/10 17:35:40 Info: [broker/locations/directorystoragelocation] drive is not available so disposing resources (if they exist): FileBrowser.Entry:  / : /music/lossless
02/10 17:35:40 Info: [broker/locations] storage location backend (Folder:Name=:Location=FileBrowser.Entry:  / : /music/lossless:Id=5a91d8f5-8083-4511-9fda-7a2e1977e997) offline reason changed to: DriveNotReady
02/10 17:35:40 Info: [broker/locations/directorystoragelocation] we'd like to keep this volume mounted: LINUXROOT
02/10 17:35:40 Info: [broker/locations] created enabled location, FileBrowser.Entry:  / : /music/lossless
02/10 17:35:40 Info: [broker/locations] adding storage location: Folder:Name=:Location=FileBrowser.Entry:  / : /music/lossless:Id=5a91d8f5-8083-4511-9fda-7a2e1977e997
02/10 17:35:40 Info: [broker/locations/directorystoragelocation] initializing FileBrowser.Entry:  / : /music/lossy, drive availability is: False
02/10 17:35:40 Info: [broker/locations/directorystoragelocation] drive is not available so disposing resources (if they exist): FileBrowser.Entry:  / : /music/lossy
02/10 17:35:40 Info: [broker/locations] storage location backend (Folder:Name=:Location=FileBrowser.Entry:  / : /music/lossy:Id=20c7e543-c594-4b63-ad7c-cb4f856a59c5) offline reason changed to: DriveNotReady
02/10 17:35:40 Info: [broker/locations/directorystoragelocation] we'd like to keep this volume mounted: LINUXROOT
02/10 17:35:40 Info: [broker/locations] created enabled location, FileBrowser.Entry:  / : /music/lossy
02/10 17:35:40 Info: [broker/locations] adding storage location: Folder:Name=:Location=FileBrowser.Entry:  / : /music/lossy:Id=20c7e543-c594-4b63-ad7c-cb4f856a59c5
02/10 17:35:40 Debug: [broker/locations] write pre 1.3 automounts, strlist:
02/10 17:35:41 Debug: [broker/filebrowser/volumeattached] initial listing found drive mounted at /music
02/10 17:35:41 Debug: [broker/filebrowser/nassharemaker] rebuildsymlinks
02/10 17:35:41 Debug: [broker/filebrowser/volumeattached] skipping /music because it is not a /dev/sd[0-9]* (mountline: :/media/music /music nfs ro,noatime,vers=3,rsize=8192,wsize=8192,namlen=255,hard,proto=tcp,timeo=14,retrans=2,sec=sys,mountaddr=10.0.120.7,mountvers=3,mountproto=tcp,local_lock=none,addr=10.0.120.7 0 0)

Then going back to the previous logs from 1.8 while on ZFS:

02/10 10:57:52 Info: [broker/locations/directorystoragelocation] initializing FileBrowser.Entry:  / : /music/lossless, drive availability is: False
02/10 10:57:52 Info: [broker/locations/directorystoragelocation] drive is not available so disposing resources (if they exist): FileBrowser.Entry:  / : /music/lossless
02/10 10:57:52 Info: [broker/locations] storage location backend (Folder:Name=:Location=FileBrowser.Entry:  / : /music/lossless:Id=5a91d8f5-8083-4511-9fda-7a2e1977e997) offline reason changed to: DriveNotReady
02/10 10:57:52 Info: [broker/locations/directorystoragelocation] we'd like to keep this volume mounted: LINUXROOT
02/10 10:57:52 Info: [broker/locations] created enabled location, FileBrowser.Entry:  / : /music/lossless
02/10 10:57:52 Info: [broker/locations] adding storage location: Folder:Name=:Location=FileBrowser.Entry:  / : /music/lossless:Id=5a91d8f5-8083-4511-9fda-7a2e1977e997
02/10 10:57:52 Info: [broker/locations/directorystoragelocation] initializing FileBrowser.Entry:  / : /music/lossy, drive availability is: False
02/10 10:57:52 Info: [broker/locations/directorystoragelocation] drive is not available so disposing resources (if they exist): FileBrowser.Entry:  / : /music/lossy
02/10 10:57:52 Info: [broker/locations] storage location backend (Folder:Name=:Location=FileBrowser.Entry:  / : /music/lossy:Id=20c7e543-c594-4b63-ad7c-cb4f856a59c5) offline reason changed to: DriveNotReady
02/10 10:57:52 Info: [broker/locations/directorystoragelocation] we'd like to keep this volume mounted: LINUXROOT
02/10 10:57:52 Info: [broker/locations] created enabled location, FileBrowser.Entry:  / : /music/lossy
02/10 10:57:52 Info: [broker/locations] adding storage location: Folder:Name=:Location=FileBrowser.Entry:  / : /music/lossy:Id=20c7e543-c594-4b63-ad7c-cb4f856a59c5
02/10 10:57:52 Debug: [broker/locations] write pre 1.3 automounts, strlist:
02/10 10:57:53 Debug: [broker/filebrowser/volumeattached] initial listing found drive mounted at
02/10 10:57:53 Debug: [broker/filebrowser/nassharemaker] rebuildsymlinks
02/10 10:57:53 Debug: [broker/filebrowser/volumeattached] skipping  because it is not mounted

It is looking like y’all are doing some funny-bunny checks for the mount status of the volumes associated with the music, and I’m not entirely sure why. Wouldn’t it just be easier to check to see if the data was there instead of putting wacky restrictions based on the hardware or mountpoint associated with the data?

To put it another way, how can you be sure that everyone will have controllers or storage that fits into the low-end style of /dev/sd* or able to have the mount point manipulated by software in a container? If the software is going to support operation on Linux, you best expect people will do things different.

Bernardo_Meurer_Cost · February 11, 2021, 2:50am

This probably explains why it can’t see my /dev/nvme* drives either

Bernardo_Meurer_Cost · February 11, 2021, 2:59am

I wonder if you bind-mount the /music to /dev/sdz it will fool it into working

Dean_Bailey · February 11, 2021, 3:16am

Pure postulation on my part, but yeah, that is my take on it. But I could be very wrong.

Compare that to the log from the previous version:

01/28 18:21:23 Info: [broker/locations/directorystoragelocation] initializing FileBrowser.Entry:  / : /music/lossless, drive availability is: False
01/28 18:21:23 Info: [broker/locations/directorystoragelocation] drive is not available so disposing resources (if they exist): FileBrowser.Entry:  / : /music/lossless
01/28 18:21:23 Info: [broker/locations] storage location backend (Folder:Name=:Location=FileBrowser.Entry:  / : /music/lossless:Id=5a91d8f5-8083-4511-9fda-7a2e1977e997) offline reason changed to: DriveNotReady
01/28 18:21:23 Info: [broker/locations/directorystoragelocation] we'd like to keep this volume mounted: LINUXROOT
01/28 18:21:23 Info: [broker/locations] created enabled location, FileBrowser.Entry:  / : /music/lossless
01/28 18:21:23 Info: [broker/locations] adding storage location: Folder:Name=:Location=FileBrowser.Entry:  / : /music/lossless:Id=5a91d8f5-8083-4511-9fda-7a2e1977e997
01/28 18:21:23 Info: [broker/locations/directorystoragelocation] initializing FileBrowser.Entry:  / : /music/lossy, drive availability is: False
01/28 18:21:23 Info: [broker/locations/directorystoragelocation] drive is not available so disposing resources (if they exist): FileBrowser.Entry:  / : /music/lossy
01/28 18:21:23 Info: [broker/locations] storage location backend (Folder:Name=:Location=FileBrowser.Entry:  / : /music/lossy:Id=20c7e543-c594-4b63-ad7c-cb4f856a59c5) offline reason changed to: DriveNotReady
01/28 18:21:23 Info: [broker/locations/directorystoragelocation] we'd like to keep this volume mounted: LINUXROOT
01/28 18:21:23 Info: [broker/locations] created enabled location, FileBrowser.Entry:  / : /music/lossy
01/28 18:21:23 Info: [broker/locations] adding storage location: Folder:Name=:Location=FileBrowser.Entry:  / : /music/lossy:Id=20c7e543-c594-4b63-ad7c-cb4f856a59c5
01/28 18:21:23 Debug: [broker/locations] write pre 1.3 automounts, strlist:
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] loading from mount, and volume exists already with UUID "LINUXROOT". updating values /: |/| => /|/|
01/28 18:21:24 Info: [broker/filebrowser/volumeattached] Volume's availability changed: True
01/28 18:21:24 Debug: [broker/filebrowser/drive] availability on drive's volume changed: True: VolumeAttached[id:LINUXROOT,title: /,subtitle:<null>,mountdir:/]
01/28 18:21:24 Info: [broker/locations/directorystoragelocation] drive availabilitychanged: True, FileBrowser.Entry:  / : /music/lossless (it was False)
01/28 18:21:24 Info: [broker/locations/directorystoragelocation] drive is available checking to referencing fs provider and setting up dirwatcher: FileBrowser.Entry:  / : /music/lossless
01/28 18:21:24 Debug: [broker/locations/directorystoragelocation] drive path lookup took 3ms: FileBrowser.Entry:  / : /music/lossless
01/28 18:21:24 Debug: [broker/locations/directorystoragelocation] dirwatcher init took 0ms: FileBrowser.Entry:  / : /music/lossless
01/28 18:21:24 Info: [broker/locations/directorystoragelocation] attaching backend: FileBrowser.Entry:  / : /music/lossless
01/28 18:21:24 Info: [broker/locations] storage location backend created and attached (Folder:Name=:Location=FileBrowser.Entry:  / : /music/lossless:Id=5a91d8f5-8083-4511-9fda-7a2e1977e997)
01/28 18:21:24 Info: [broker/locations] media availability: Folder:Name=:Location=FileBrowser.Entry:  / : /music/lossless:Id=5a91d8f5-8083-4511-9fda-7a2e1977e997 is online
01/28 18:21:24 Info: [broker/locations/directorystoragelocation] drive availabilitychanged: True, FileBrowser.Entry:  / : /music/lossy (it was False)
01/28 18:21:24 Info: [broker/locations/directorystoragelocation] drive is available checking to referencing fs provider and setting up dirwatcher: FileBrowser.Entry:  / : /music/lossy
01/28 18:21:24 Debug: [broker/locations/directorystoragelocation] drive path lookup took 0ms: FileBrowser.Entry:  / : /music/lossy
01/28 18:21:24 Debug: [broker/locations/directorystoragelocation] dirwatcher init took 0ms: FileBrowser.Entry:  / : /music/lossy
01/28 18:21:24 Info: [broker/locations/directorystoragelocation] attaching backend: FileBrowser.Entry:  / : /music/lossy
01/28 18:21:24 Info: [broker/locations] storage location backend created and attached (Folder:Name=:Location=FileBrowser.Entry:  / : /music/lossy:Id=20c7e543-c594-4b63-ad7c-cb4f856a59c5)
01/28 18:21:24 Info: [broker/locations] media availability: Folder:Name=:Location=FileBrowser.Entry:  / : /music/lossy:Id=20c7e543-c594-4b63-ad7c-cb4f856a59c5 is online
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /proc
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /proc because it is not a /dev/sd[0-9]* (mountline: proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /dev
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /dev/pts
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /dev because it is not a /dev/sd[0-9]* (mountline: tmpfs /dev tmpfs rw,nosuid,size=65536k,mode=755 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /sys
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /sys/fs/cgroup
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /dev/pts because it is not a /dev/sd[0-9]* (mountline: devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=666 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /sys because it is not a /dev/sd[0-9]* (mountline: sysfs /sys sysfs ro,nosuid,nodev,noexec,relatime 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /sys/fs/cgroup/systemd
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /sys/fs/cgroup/net_cls,net_prio
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /sys/fs/cgroup/systemd because it is not a /dev/sd[0-9]* (mountline: cgroup /sys/fs/cgroup/systemd cgroup ro,nosuid,nodev,noexec,relatime,xattr,name=systemd 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /sys/fs/cgroup/net_cls,net_prio because it is not a /dev/sd[0-9]* (mountline: cgroup /sys/fs/cgroup/net_cls,net_prio cgroup ro,nosuid,nodev,noexec,relatime,net_cls,net_prio 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /sys/fs/cgroup/memory
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /sys/fs/cgroup because it is not a /dev/sd[0-9]* (mountline: tmpfs /sys/fs/cgroup tmpfs ro,nosuid,nodev,noexec,relatime,mode=755 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /sys/fs/cgroup/memory because it is not a /dev/sd[0-9]* (mountline: cgroup /sys/fs/cgroup/memory cgroup ro,nosuid,nodev,noexec,relatime,memory 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /sys/fs/cgroup/pids
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /sys/fs/cgroup/perf_event
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /sys/fs/cgroup/pids because it is not a /dev/sd[0-9]* (mountline: cgroup /sys/fs/cgroup/pids cgroup ro,nosuid,nodev,noexec,relatime,pids 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /sys/fs/cgroup/hugetlb
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /sys/fs/cgroup/perf_event because it is not a /dev/sd[0-9]* (mountline: cgroup /sys/fs/cgroup/perf_event cgroup ro,nosuid,nodev,noexec,relatime,perf_event 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /sys/fs/cgroup/hugetlb because it is not a /dev/sd[0-9]* (mountline: cgroup /sys/fs/cgroup/hugetlb cgroup ro,nosuid,nodev,noexec,relatime,hugetlb 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /sys/fs/cgroup/cpuset
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /sys/fs/cgroup/rdma
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /sys/fs/cgroup/cpuset because it is not a /dev/sd[0-9]* (mountline: cgroup /sys/fs/cgroup/cpuset cgroup ro,nosuid,nodev,noexec,relatime,cpuset 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /sys/fs/cgroup/cpu,cpuacct
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /sys/fs/cgroup/devices
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /sys/fs/cgroup/rdma because it is not a /dev/sd[0-9]* (mountline: cgroup /sys/fs/cgroup/rdma cgroup ro,nosuid,nodev,noexec,relatime,rdma 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /sys/fs/cgroup/cpu,cpuacct because it is not a /dev/sd[0-9]* (mountline: cgroup /sys/fs/cgroup/cpu,cpuacct cgroup ro,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /sys/fs/cgroup/freezer
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /sys/fs/cgroup/devices because it is not a /dev/sd[0-9]* (mountline: cgroup /sys/fs/cgroup/devices cgroup ro,nosuid,nodev,noexec,relatime,devices 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /sys/fs/cgroup/freezer because it is not a /dev/sd[0-9]* (mountline: cgroup /sys/fs/cgroup/freezer cgroup ro,nosuid,nodev,noexec,relatime,freezer 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /sys/fs/cgroup/blkio
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /dev/mqueue
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /sys/fs/cgroup/blkio because it is not a /dev/sd[0-9]* (mountline: cgroup /sys/fs/cgroup/blkio cgroup ro,nosuid,nodev,noexec,relatime,blkio 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /dev/mqueue because it is not a /dev/sd[0-9]* (mountline: mqueue /dev/mqueue mqueue rw,nosuid,nodev,noexec,relatime 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /dev/shm
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /data
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /dev/shm because it is not a /dev/sd[0-9]* (mountline: shm /dev/shm tmpfs rw,nosuid,nodev,noexec,relatime,size=65536k 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /backup
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /data because it is not a /dev/sd[0-9]* (mountline: rpool/docker /data zfs rw,nodev,noatime,xattr,posixacl 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /app
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /backup because it is not a /dev/sd[0-9]* (mountline: stardom3/roon /backup zfs rw,noatime,xattr,posixacl 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /app because it is not a /dev/sd[0-9]* (mountline: rpool/docker /app zfs rw,nodev,noatime,xattr,posixacl 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /music
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /music because it is not a /dev/sd[0-9]* (mountline: stardom3/music /music zfs ro,noatime,xattr,posixacl 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /etc/resolv.conf
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /etc/hostname
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /etc/resolv.conf because it is not a /dev/sd[0-9]* (mountline: rpool/docker /etc/resolv.conf zfs rw,nodev,noatime,xattr,posixacl 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /etc/hostname because it is not a /dev/sd[0-9]* (mountline: rpool/docker /etc/hostname zfs rw,nodev,noatime,xattr,posixacl 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /etc/hosts
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /etc/hosts because it is not a /dev/sd[0-9]* (mountline: rpool/docker /etc/hosts zfs rw,nodev,noatime,xattr,posixacl 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /proc/bus
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /proc/fs
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /proc/bus because it is not a /dev/sd[0-9]* (mountline: proc /proc/bus proc ro,relatime 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /proc/irq
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /proc/fs because it is not a /dev/sd[0-9]* (mountline: proc /proc/fs proc ro,relatime 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /proc/irq because it is not a /dev/sd[0-9]* (mountline: proc /proc/irq proc ro,relatime 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /proc/sys
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /proc/sys because it is not a /dev/sd[0-9]* (mountline: proc /proc/sys proc ro,relatime 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /proc/sysrq-trigger
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /proc/sysrq-trigger because it is not a /dev/sd[0-9]* (mountline: proc /proc/sysrq-trigger proc ro,relatime 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /proc/acpi
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /proc/kcore
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /proc/acpi because it is not a /dev/sd[0-9]* (mountline: tmpfs /proc/acpi tmpfs ro,relatime 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /proc/keys
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /proc/kcore because it is not a /dev/sd[0-9]* (mountline: tmpfs /proc/kcore tmpfs rw,nosuid,size=65536k,mode=755 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /proc/timer_list
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /proc/keys because it is not a /dev/sd[0-9]* (mountline: tmpfs /proc/keys tmpfs rw,nosuid,size=65536k,mode=755 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /proc/timer_list because it is not a /dev/sd[0-9]* (mountline: tmpfs /proc/timer_list tmpfs rw,nosuid,size=65536k,mode=755 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /proc/sched_debug
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /proc/sched_debug because it is not a /dev/sd[0-9]* (mountline: tmpfs /proc/sched_debug tmpfs rw,nosuid,size=65536k,mode=755 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /proc/scsi
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /proc/scsi because it is not a /dev/sd[0-9]* (mountline: tmpfs /proc/scsi tmpfs ro,relatime 0 0)
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] found newly mounted drive at /sys/firmware
01/28 18:21:24 Debug: [broker/filebrowser/volumeattached] skipping /sys/firmware because it is not a /dev/sd[0-9]* (mountline: tmpfs /sys/firmware tmpfs ro,relatime 0 0)

The filtering based on /dev/sd* is apparently used to keep roon out of other non-data locations. We also see a bunch of the same mountpoint errors, probably related to checking to see if the folders in /music/ are mountpoints. But, it also continues on finding / and enabling stuff in /music.

Dean_Bailey · February 11, 2021, 3:20am

Probably not on the /dev/sdz thing, but I could be wrong there.

I’ll just wait until they provide a fix, I’ve done my casual inspections and hopeful quick fixes.

Bernardo_Meurer_Cost · February 11, 2021, 4:26am

To confirm, I can see the same behavior in the logs:

02/10 20:20:25 Info: [broker/locations] adding storage location: Internet:Name=Internet Media:Id=e268f098-04c4-4e65-af3f-38ba3c3fcecb                                                                                                                                     02/10 20:20:25 Info: [broker/locations] media availability: Internet:Name=Internet Media:Id=e268f098-04c4-4e65-af3f-38ba3c3fcecb is online
02/10 20:20:25 Info: [broker/locations] adding storage location: MetadataService:Name=Metadata Service:Id=13769258-b70b-4243-b1d6-bd46e8257ba8
02/10 20:20:25 Info: [broker/locations] media availability: MetadataService:Name=Metadata Service:Id=13769258-b70b-4243-b1d6-bd46e8257ba8 is online                                                                                                                       02/10 20:20:25 Info: [broker/locations] adding storage location: Offline:Name=Offline:Id=f1e4b43f-f643-47ba-b875-fd93b32a6006
02/10 20:20:25 Debug: [broker/locations/migration] start, propname: loc_c609af3911be4aebabfa404906865a1a
02/10 20:20:25 Debug: [broker/locations] Migrating UUID based storage location, id: loc_c609af3911be4aebabfa404906865a1a, version: 2                                                                                                                                      02/10 20:20:25 Debug: [broker/locations/migration] start, propname: location_automounts                                                                                                                                                                                   02/10 20:20:25 Debug: [broker/locations] load pre 1.3 automounts, strlist:
02/10 20:20:25 Info: [broker/locations/directorystoragelocation] initializing FileBrowser.Entry:  / : /srv/music, drive availability is: False
02/10 20:20:25 Info: [broker/locations/directorystoragelocation] drive is not available so disposing resources (if they exist): FileBrowser.Entry:  / : /srv/music
02/10 20:20:25 Info: [broker/locations] storage location backend (Folder:Name=:Location=FileBrowser.Entry:  / : /srv/music:Id=c609af39-11be-4aeb-abfa-404906865a1a) offline reason changed to: DriveNotReady
02/10 20:20:25 Info: [broker/locations/directorystoragelocation] we'd like to keep this volume mounted: LINUXROOT
02/10 20:20:25 Info: [broker/locations] created enabled location, FileBrowser.Entry:  / : /srv/music
02/10 20:20:25 Info: [broker/locations] adding storage location: Folder:Name=:Location=FileBrowser.Entry:  / : /srv/music:Id=c609af39-11be-4aeb-abfa-404906865a1a
02/10 20:20:25 Debug: [broker/locations] write pre 1.3 automounts, strlist: