This is where the difference between Raspberry and other distros has me at a disadvantage.
I don’t own one to become familiar with.
I already have a QNAP TVS-1282 (QTS), Synology DS1815+ (DSM), NUC (Ubuntu 16.04), Fedora 27 Desktop (my workstation).
Additional development systems here at the moment are: Thecus, Synology, and QNAP
I have a 24 port main switch and it’s almost full. I added 10 GbE and a moved the backbone to it to free up gigabit ports on the 24 (HPE switch).
In a nutshell… no more room! haha
For now, again, please do the manual mount,
Once you have Plex scanning, go into Settings - Server - Library. Uncheck the box Empty Trash after every scan and save.
By doing this, should you reboot the Pi, PMS will turn your scanned media Red until you remount the share and Rescan. that’s it… No actual data will be lost.
Wow, that sounds impressive but is mostly over my head. Setting up this NAS/Pi/PMS has been about all of my experience with Linux and servers. Tutorials work great until something doesn’t go right. Then it’s down the rabbit hole to find an answer.
Doing a manual mount until uglymagoo responds works great. I’ve been troubleshooting this on and off for more time than I’ll admit. Just happy to have it seeing my files again! Thanks for all the help with this.
I’m looking at my system to see if we can manually trigger what you need.
# systemctl list-units
What it will present to you is a scrolling text window with all the defined units (each mount point is a unit).
Here you see my NFS mounts. You might need to reboot to have the service created for you… again, I forget how this is done. I know it is based on the current contents of fstab at start.
here’s how mine looks. Note the ‘jellyfish’ service isn’t running. (it’s not currently mounted)
vie-bin.mount loaded active mounted /vie/bin
vie-cakewalk.mount loaded active mounted /vie/cakewalk
vie-channels.mount loaded active mounted /vie/channels
vie-classical.mount loaded active mounted /vie/classical
vie-devel.mount loaded active mounted /vie/devel
vie-download.mount loaded active mounted /vie/download
vie-dvr.mount loaded active mounted /vie/dvr
vie-gdrive.mount loaded active mounted /vie/gdrive
vie-git.mount loaded active mounted /vie/git
vie-hp.mount loaded active mounted /vie/hp
vie-jazz.mount loaded active mounted /vie/jazz
● vie-jellyfish.mount loaded failed failed /vie/jellyfish
vie-mmg.mount loaded active mounted /vie/mmg
vie-movies.mount loaded active mounted /vie/movies
vie-movies2.mount loaded active mounted /vie/movies2
vie-music.mount loaded active mounted /vie/music
vie-mymovies.mount loaded active mounted /vie/mymovies
vie-mytv.mount loaded active mounted /vie/mytv
vie-nuc.mount loaded active mounted /vie/nuc
vie-nzbdrone.mount loaded active mounted /vie/nzbdrone
vie-o\x2dmusic.mount loaded active mounted /vie/o-music
vie-oldmusic.mount loaded active mounted /vie/oldmusic
vie-pfsense.mount loaded active mounted /vie/pfsense
lines 79-102
Yep, it returned 139 lines. I can see the home/plex mount failed but that’s not what you’re looking for. Want me to paste it all in here? Not really sure what I’m looking at and it’s a lot.
@savenelroy As mentioned a thousand times in this forum, the guide you have used is completely broken and a bad start for setting up PMS on your Pi. Your PMS is still running as user plex on your Pi, regardless what’s told in the above tutorial.
I just skipped over the above posts and I understand that you are now able to manually mount your NAS share correctly at /home/plex, correct? It just does not mount on reboot? So that’s most likely a network issue, i.e. network not available on restart. That’s usually an issue if you use Wi-Fi. What’s your network setup?
Citing @ChuckPa:
Please take a look at the directory /run/systemd/generator with ls /run/systemd/generator or take the name from the unit list as @ChuckPa has told you. There should be a *.mount file for your nfs mount. I suspect it begins with the IP.
You can then check the status of the mount after reboot with systemctl status foo-bar.mount. Replace foo-bar.mount with the correct file. Thus, we can get the error that’s stopping your nfs share from being mounted correctly at reboot.
● home-plex.mount - /home/plex
Loaded: loaded (/etc/fstab; generated; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2019-01-06 11:27:24 EST; 4min 31s ago
Where: /home/plex
What: 192.168.0.27:/volume1/video
Docs: man:fstab(5)
man:systemd-fstab-generator(8)
Process: 418 ExecMount=/bin/mount 192.168.0.27:/volume1/video /home/plex -t nfs -o defaults,rw,bg,x-systemd.after=network-
Jan 06 11:27:24 raspberrypi systemd[1]: Mounting /home/plex…
Jan 06 11:27:24 raspberrypi systemd[1]: home-plex.mount: Mount process exited, code=exited status=32
Jan 06 11:27:24 raspberrypi systemd[1]: Failed to mount /home/plex.
Jan 06 11:27:24 raspberrypi systemd[1]: home-plex.mount: Unit entered failed state.
Yes, manually mounting works great. I did a reboot. No access to media. Once I manually mount, it works great again.
For network configuration, I found my ip address of the pi and defined it in the cmdline.txt. I believe that’s all I did (just followed the steps in the tutorial mentioned earlier).
