Jump to content

Library Scan Failing


mekevinb

Recommended Posts

I'm pretty comfortable with Arch, but Emby has put me to the test. After two days and several 6-packs of Coke, I finally got it installed and configuration up and running in Chrome. I even somehow got two forms of media added to the library from my WD MyCloud NAS. But the folder scanning is failing. In the Library section, under the Scan Library button it just always says "Last result: (failed)". Really, really not sure what is going on. Anyone have any thoughts? My latest log file is attached but it's all greek to me.

emby-Log-2015.09.20.txt

Link to comment
Share on other sites

Well, I'm not sure what's going on. I've tried seeking out answers to why I can't get Emby to scan my library. The instructions here - http://emby.media/downloads/linux-server/ - appear to show that Emby is relatively straight-forward in setting up but that couldn't be further from the truth. I've spent 4 days just on the server. I would certainly hope the client apps are much easier to setup and use.

Link to comment
Share on other sites

Since you're on Arch, I've just updated the website with our new instructions that are based on the community repository. The install process is now a single-line command.

 

As for your path issues - just a little bit of background. Mono does not have native smb support which is why the server cannot see your unc shares and instead you need to mount them to a local share first. I am working to revamp our file system access to add this support ourselves but it will take time. In the meantime, it's probably best you start again with the new repo and this new information, then if you're still having problems we can go from there.

  • Like 1
Link to comment
Share on other sites

Luke, thank you for responding.

 

I see the new one-line command for installing but the terminal does not "provide additional instructions for accessing the dashboard to complete configuration", as the statement on the download page suggests. I had to fish through this forum to find out how to get the configuration up in a browser. It's http://localhost:8096/web/index.html if I'm not mistaken, correct?

Edited by mekevinb
Link to comment
Share on other sites

Luke, thank you for responding.

 

I see the new one-line command for installing but the terminal does not "provide additional instructions for accessing the dashboard to complete configuration", as the statement on the download page suggests. I had to fish through this forum to find out how to get the configuration up in a browser. It's http://localhost:8096/web/index.html if I'm not mistaken, correct?

I'm not an Arch user but yet I'm running Emby on Linux, feeding it with media from NFS shares on a dedicated file server. As far as the network shares are locally mounted on your Emby server you will be fine. If you are comfortable with NFS go ahead but keep in mind that you can use CIFS aswell which tends to be less tricky.

 

 

Sent from my iPhone using Tapatalk

Link to comment
Share on other sites

I'm not an Arch user but yet I'm running Emby on Linux, feeding it with media from NFS shares on a dedicated file server. As far as the network shares are locally mounted on your Emby server you will be fine. If you are comfortable with NFS go ahead but keep in mind that you can use CIFS aswell which tends to be less tricky.

 

 

Sent from my iPhone using Tapatalk

 

The only mention I see of CIFS in the Arch wiki is when SMB is mentioned, and Luke says that SMB is not supported in Mono. How do you suggest I proceed? Either way I'll be having to teach myself how to do something (either mounting network shares using NFS or CIFS).

Link to comment
Share on other sites

Well mono doesn't support cifs natively but neither supports nfs for that matters. You will need to mount them externally either using fstab or like myself using autofs.

 

 

Sent from my iPhone using Tapatalk

Link to comment
Share on other sites

I'm looking at https://wiki.archlinux.org/index.php/Autofs and it's just overwhelming. I don't even know where to begin. I'm not sure if the entire article is relevant to my situation. At this point, I think I need to see a visual demo with the WD MyCloud in mind because I'm not even sure if the WD MyCloud can even be treated as a traditional NAS like Synology devices and such.

Link to comment
Share on other sites

As far as I could see it behaves as a regular NAS. Meaning you can share files and folder at least over CIFS but I think also over NFS.

Regarding using autofs or fstab to automatically mount the network shares on your Linux box I would say that the main difference is that using fstab the network shares must be available on system boot and if they don't then you need to manually mount them. On the other hand autofs will mount the network share automatically on access instead of on boot. This is convenient if you need to bring the NAS offline at any moment since the shares will be automatically remounted when they are available again. With fstab you will need to manually unmount and mount them except on boot.

 

My advice start by manually mounting your network resources once your comfortable with doing manually just move on and have a look at fstab or autofs. You will be fine. :)

 

 

Sent from my iPad using Tapatalk

Link to comment
Share on other sites

fc7 - You're good people, thanks. I didn't realize that setting up a media server would become a rabbit hole of mount points, fstab, and conf files. Starting simple is good advice as I just wanted to "kick the tires" on Emby before I implement it 100%.

Link to comment
Share on other sites

Yea, sorry, this is one limitation we're not really happy about and hope to resolve soon by adding our own smb support.

  • Like 1
Link to comment
Share on other sites

fc7 - You're good people, thanks. I didn't realize that setting up a media server would become a rabbit hole of mount points, fstab, and conf files. Starting simple is good advice as I just wanted to "kick the tires" on Emby before I implement it 100%.

We are here to help man. Regarding complexity it's not really Emby but the platform you choosed but look at the bright side, you will learn a few new things. And if things get too complicated you can always try Emby on Windows that will be more straight forward to setup.

 

Just post here if you need help mounting the network shares.

 

 

Sent from my iPad using Tapatalk

Link to comment
Share on other sites

Haha you're being very helpful but now you're also being funny! Emby on Windows? I agree that the install would be straight forward but, as stated, I wouldn't learn anything. That was one of the things I got tired of with Windows. I started using Linux casually about a year ago. I stepped it up a few weeks ago when I discovered the Evo/Lution (Architect) Arch installer. I'll stick with learning how to mount network shares to get Emby up and running. And thanks for the assist.

Link to comment
Share on other sites

We are here to help man. Regarding complexity it's not really Emby but the platform you choosed but look at the bright side, you will learn a few new things. And if things get too complicated you can always try Emby on Windows that will be more straight forward to setup.

 

Just post here if you need help mounting the network shares.

 

 

Sent from my iPad using Tapatalk

 

Okay, officially overwhelmed. So much Google searching and it just confuses one after awhile. The one thing I did manage to find is that the WD MyCloud supports CIFS (Samba) and NFS. I just don't know where to begin. I don't know how to refer to my MyCloud in fstab. I know its IP address. I know the paths to the folders on the MyCloud that I want as shares in Emby. I just don't know how to translate all of that to auto-mounting these shares every time I boot this Linux machine for the sake of Emby. It feels like I'm tackling too much at the same time while I'm in the glorious learning curve of Linux.

Edited by mekevinb
Link to comment
Share on other sites

Again. Start by simply mounting the shared folder with the mount command. Once you master that move on to fstab or autofs.

And start with CIFS since NFS is more tricky.

 

 

Sent from my iPhone using Tapatalk

Edited by fc7
Link to comment
Share on other sites

Again. Start by simply mounting the shared folder with the mount command. Once you master that move on to fstab or autofs.

And start with CIFS since NFS is more tricky.

 

 

Sent from my iPhone using Tapatalk

Yep, forgot to mention that I've been looking through the man page for 'mount' and I can't see how to refer to my network-attached device. I know enough to feel confident that it's not going to be 'sda' or 'sr0' or anything like 'sdx'.

 

I'll have to revisit this all later.

Link to comment
Share on other sites

Yep, forgot to mention that I've been looking through the man page for 'mount' and I can't see how to refer to my network-attached device. I know enough to feel confident that it's not going to be 'sda' or 'sr0' or anything like 'sdx'.

 

I'll have to revisit this all later.

 

This is just a hint and you will need to adapt it to your environment but something like:

# mount -t cifs -o username=mycloud_share_user,password=mycloud_share_user_password //mycloud_ip/shared_folder /local_path

should work. Where:

 

mycloud_share_user = a user valid in your MyCloud NAS with access to the shared folder

mycloud_share_user_password = the password for the mycloud_share_user

mycloud_ip = the IP of your MyCloud NAS device

shared_folder = the name of the network shared resource on the MyCloud NAS device

local_path = the local path on your Linux box where you want to mount the network shared folder

 

You will need the cifsutils package installed for this to work, of course.

Edited by fc7
Link to comment
Share on other sites

The media shares on my MyCloud are not password protected, so I tried widdling it down to this......

sudo mount -t cifs -o guest //192.168.xxx.xxx/public/Movies /home/xxxxxxxx/server

...but I get...

mount error(16): Device or resource busy

Thanks for your help. Tomorrow will be another day.

Link to comment
Share on other sites

Okay, I'm almost convinced it's not me at this point. I managed to get my Movies share mounted with the mount command. I can see it in my file manager. It's all there. When I try to add this share to Emby it won't take it. I even copy and paste the path from my file manager to Emby, in the path field and it doesn't like it.

 

The saga continues.....

 

UPDATE: Yeah, it's not me. I'm successfully mounting my Movies share on the MyCloud and Emby just will not see it. I don't see this documented anywhere.

Edited by mekevinb
Link to comment
Share on other sites

Under which user is Emby server running and which file permissions do you see for your files and directories?

Keep in mind that Emby must have at least read access for files are read+execute access for directories.

 

 

Sent from my iPad using Tapatalk

Link to comment
Share on other sites

thefirstofthe300

I am glad to hear that you have taken the dive into learning about the core of Linux. :)

 

I agree with fc7 that it sounds like you have permissions issues.  The CIFS share 

 

I remember when I first got started with learning how to use Arch that I was so overwhelmed it took me weeks to get a computer to the point that it was semi-usable in everyday life.  The fstab file is actually fairly simple once you understand what it is doing.  The first part of a line is the filesystem that you want to mount (in this case the SMB share).  The second part is the location to mount it.  The third is the type of filesystem you are mounting (cifs for SMB shares).  The fourth option is all of the mount options that you want to use.  The last two should be left as zeros for SMB shares but you can read about them here.

 

You will probably end up with an fstab entry similar to

//Server-IP/share-name /path/to/mount/point cifs /path/to/credentials/file,uid=username,gid=groupname 0 0

You can read about the credentials file here.  The catch to an fstab entry is the filesystem must be present for the system to boot.  In other words, using this method on a laptop you take with you to work will cause the laptop to not boot.  If the computer is never going to leave the LAN with the file server, this method is the way to go.

 

Before the above will work, you will need to decide what the permissions scheme for your media should look like.  I would make the gid above a group that the Emby user is a part of.  You should avoid permissions issues that way.  I think.

 

This stuff is a lot of trial and error and googling your problems.  I have found the Arch forums and the askubuntu forums to be amazing resources since you are almost guaranteed to find someone who has the exact problem you are facing.  To be honest, I haven't read the documentation nearly as much as I should have but I have managed to get most of my problems solved.

  • Like 1
Link to comment
Share on other sites

brett_1968

Since your using Arch I'd suggest you use a systemd unit file for the mount rather than fstab, that way you can ensure that networking is up before you create the mount point.

 

The Arch wiki has good info on systemd.

 

With systemd and fstab the default for continuing the boot process if an mount fails has changed ie. the boot fails, you can control it by the 'nofail' option in fstab.

  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...