Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

After upgrade from 4.7 to 5.0-rc12 my BoxeeBox devices lose access to NFS shares

Featured Replies

Hello.  I have been running Unraid 4.7 for quite a while now.  I recently upgraded to 5.0rc10 and upgraded each time a new version has come out and am currently running 5.0rc12. 

 

I use NFS for sharing media on my network for Boxee Box.  BD, DVD, and TV shares which are mapped to boxee box as sources.

 

I noticed that after the upgrade to 5.0 my boxee box devices would stop automatically updating media on their hourly scans.  They would work for a while and then at some point would no longer add new media.  A boxee box power cycle will temporarily fix the problem but it comes back within two days.  While investigating I noticed that if I select the boxee box menu "Files" and browse my sources I would sometimes get a boxee box error when selecting a source to browse.  This same source would show no data when boxee box would do it's scan.  I found one other work around out side of the power cycle;  selecting a media file from that source (movie list or tv list) would actually play and then if I went back to browse the source I would get a file listing and media would be found on the next scan but it reverts back to being inaccessible after a while (1-2 days).

 

 

After experiencing this issue for a few weeks I decided to downgrade back to Unraid 4.7 to make sure this was not an issue with the 4.7 version.  After the downgrade I was able to browse sources/shares with no issues and media is automatically being found on the hourly scans.  I tested for a while and it has been working solidly as I am used to.  Last night I took the jump back to 5.0-rc12 and in less than a day I am having the same issue again.

 

So it seems that there is some difference with how the NFS shares are being handled that boxee box has difficulties with.  I would very much like to be on the 5.0 version of code since it has features that I will want to take advantage of, but this issue I am seeing with boxee box is preventing that.  I would be very grateful if someone could take a look into this and offer any suggestions outside of replacing boxee box :)

 

I have attached some logs from unraid and boxee.

 

In the logs below, I try to access the file source bd on boxee and get the access error screen. 

 

I see this error in the boxee syslog.

 

4/7/2013 5:31:55 PM [224858] From: (192.168.100.81) Fac:16 Sev:7 Msg >>> Apr 7 18:31:50 boxee GetDirectory - Error getting nfs://tower.brittonfamily.net/mnt/user/BD/

 

I then go to my movie listing and play 3:10 to Yuma which I know is in that share path.  The movie plays fine.  At the same time I played the movie I see this in the unraid syslog

 

Apr  7 17:32:43 Tower mountd[1739]: authenticated mount request from 192.168.100.81:1011 for /mnt/user/BD (/mnt/user/BD)

 

That is the IP for the boxee box in question.  I then go back to the file | sources screen and I can access the BD share with no issues.

 

Thanks.

unraid-syslog.zip

boxeebox-syslog.zip

I can't help you, but it looks like the issue is effecting more than yourself. There is several entries in your system log that look like this  -async,no_subtree_check,fsid=102 *(rw,insecure,anongid=100,anonuid=99,all_squash)' >>/etc/exports

 

I googled it and found several posts having the same message. It may at least start you in the right direction.

 

 

 

 

 

Edited for spelling error

I think that you may be falling foul of the stale nfs file handle problem.  Try reverting to 5.0rc10 - for me this version is much better in this respect.

  • Author

I changed my exports to this and it seems to be working all day today.  I don't have anything that actually does any writing over NFS.  I tried just sync, but it seemed to cause a different issue.  I will give it a few days and report back.

 

# See exports(5) for a description.

# This file contains a list of all directories exported to other computers.

# It is used by rpc.nfsd and rpc.mountd.

 

#"/mnt/user/BD" -async,no_subtree_check,fsid=100 *(rw,insecure,anongid=100,anonuid=99,all_squash)

"/mnt/user/BD" -async,no_subtree_check,fsid=100 *(rw)

#"/mnt/user/DVD" -async,no_subtree_check,fsid=101 *(rw,insecure,anongid=100,anonuid=99,all_squash)

"/mnt/user/DVD" -async,no_subtree_check,fsid=101 *(rw)

#"/mnt/user/TV" -async,no_subtree_check,fsid=102 *(rw,insecure,anongid=100,anonuid=99,all_squash)

"/mnt/user/TV" -async,no_subtree_check,fsid=102 *(rw)

 

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.