Library lost/rebuild if NFS not mounted

[joelvazquez 0]

Hello everyone,

Got a question.  I have a two computers setup with ubuntu, one as emby-server the other as NFS server.  The NFS server, if it looses power it does not come back up on its own, the emby-server does come back on by itself.  There will be no media at all on the mounting folders before mounting the NFS shares, as I have restricted by file attribute to avoid files been written.  Now the problems is that if emby-server scans the library folder without the NFS been mounted, the library gets empty as it assumes the media got deleted, then when I turn on the other node and mount the NFS mounts, I have to scan everything again and it can take a while.

The question, what options I have on emby to avoid this situation?  Does emby have a way to detect if the mount is mounted or not and adjust based on that?  I mean I dont expect Emby to mount it, but at least wait for them to be mounted, that would be enough...

 

Comments/suggestions?

 

Thanks!

[chowbok 132]

Do the servers go down independently, or both at once? Because if it's the latter, you could make the Emby service's starting dependent on the NFS mount being there. I can help you with this if you want.

 

I gotta ask, though... how often do you lose power, for goodness sake? If it's happening to you so much that you're posting about it here, you should probably consider buying a battery backup. It's not really good for computers to have their power cut constantly.

[mastrmind11 722]

Hello everyone,

Got a question.  I have a two computers setup with ubuntu, one as emby-server the other as NFS server.  The NFS server, if it looses power it does not come back up on its own, the emby-server does come back on by itself.  There will be no media at all on the mounting folders before mounting the NFS shares, as I have restricted by file attribute to avoid files been written.  Now the problems is that if emby-server scans the library folder without the NFS been mounted, the library gets empty as it assumes the media got deleted, then when I turn on the other node and mount the NFS mounts, I have to scan everything again and it can take a while.

 

The question, what options I have on emby to avoid this situation?  Does emby have a way to detect if the mount is mounted or not and adjust based on that?  I mean I dont expect Emby to mount it, but at least wait for them to be mounted, that would be enough...

 

Comments/suggestions?

 

Thanks!

This issue was addressed over a year ago.  @@Luke

[joelvazquez 0]

Thanks for the reply guys.  @mastermind11, how it was addressed before?  Was it a workaround or a configuration on Emby itself?  Can you link the post for it?

@chowbok:  Yeah I planning getting some UPS for each one, getting the budget set to do it as soon as possible.  So far power has been stable, but lately with all thunderstorms power has flicker couple of times in last few weeks.  It would be awesome to make Emby depend on NFS, I would appreciate if you could help me with that if that's the best solution/alternative for it.

 

Thanks again.

[Luke 42079]

Hi, yes this isn't normal. Can you please attach the emby server log from when this happened? Thanks !

 

@@joelvazquez

[chowbok 132]

Okay, I'm not sure what the Emby service is called on Ubuntu, so I'll assume it's "emby-server". First, create the directory "/etc/systemd/system/emby-server.service.d". Inside that folder, you'll need to create a file called "custom.conf" (actually, it can be named anything, as long as it ends in .conf). If your NFS file system is mounted at "/mnt/nfs", the file should look like the following:

[Unit]
After=mnt-nfs.mount
Requires=mnt-nfs.mount

Then do "systemctl daemon-reload" and Emby should depend on that mount being present to start.