Diagnosing mount order and jail startup issue

[MarkEWaite]

I have a plex jail running on my FreeNAS Mini XL running FreeNAS-11.1-U6.

When I restart the hardware (after an operating system upgrade, etc.), the plex server is unable to find the media that I had previously uploaded.

When I restart the plex jail, without restarting the hardware, the plex server is able to find the media that I have previously uploaded.

I lack FreeNAS skills and have been unable to diagnose the problem. The workaround (restart the plex jail once after each hardware restart) is easy and simple. I would like to understand why the problem occurs and how to resolve it. It is not a rush to understand it, but I would like to understand it.

When the plex server is able to find the media, the output of df run from the root shell opened from the FreeNAS web interface is:

Code:

[root@freenas ~]# df
Filesystem											   512-blocks	   Used	   Avail Capacity  Mounted on
freenas-boot/ROOT/11.1-U6								  20317840	2324776	17993064	11%	/
devfs															 2		  2		   0   100%	/dev
tmpfs														 65536	  21288	   44248	32%	/etc
tmpfs														  8192		 16		8176	 0%	/mnt
tmpfs													  22325328	 166632	22158696	 1%	/var
freenas-boot/grub										  18009072	  16008	17993064	 0%	/boot/grub
fdescfs														   2		  2		   0   100%	/dev/fd
pool-a												  11158025864  317261088 10840764776	 3%	/mnt/pool-a
pool-a/Data											 10840765024		248 10840764776	 0%	/mnt/pool-a/Data
pool-a/jails											10840800392	  35616 10840764776	 0%	/mnt/pool-a/jails
pool-a/jails/.warden-template-pluginjail-10.3-x64	   10841725552	 960776 10840764776	 0%	/mnt/pool-a/jails/.warden-template-pluginjail-10.3-x64
pool-a/jails/.warden-template-standard-10.3-x64		 10844145720	3380944 10840764776	 0%	/mnt/pool-a/jails/.warden-template-standard-10.3-x64
pool-a/jails/git-server								 10911555272   70790496 10840764776	 1%	/mnt/pool-a/jails/git-server
pool-a/jails/plexmediaserver_1						  14498222456 3657457680 10840764776	25%	/mnt/pool-a/jails/plexmediaserver_1
pool-a/.system										  10840764968		192 10840764776	 0%	/var/db/system
pool-a/.system/cores									10840768120	   3344 10840764776	 0%	/var/db/system/cores
pool-a/.system/samba4								   10840766136	   1360 10840764776	 0%	/var/db/system/samba4
pool-a/.system/syslog-618a7bc26f3c409faab2b82ca8892702  10840775616	  10840 10840764776	 0%	/var/db/system/syslog-618a7bc26f3c409faab2b82ca8892702
pool-a/.system/rrd-618a7bc26f3c409faab2b82ca8892702	 10840815520	  50744 10840764776	 0%	/var/db/system/rrd-618a7bc26f3c409faab2b82ca8892702
pool-a/.system/configs-618a7bc26f3c409faab2b82ca8892702 10840865552	 100776 10840764776	 0%	/var/db/system/configs-618a7bc26f3c409faab2b82ca8892702
devfs															 2		  2		   0   100%	/mnt/pool-a/jails/git-server/dev
procfs															8		  8		   0   100%	/mnt/pool-a/jails/git-server/proc
devfs															 2		  2		   0   100%	/mnt/pool-a/jails/plexmediaserver_1/dev
procfs															8		  8		   0   100%	/mnt/pool-a/jails/plexmediaserver_1/proc
/mnt/pool-a/jails/plexmediaserver_1/plex-media		  14498222456 3657457680 10840764776	25%	/mnt/pool-a/jails/plexmediaserver_1/home/plex-media
[root@freenas ~]#

When the plex server is not able to find the media, the output of df run from the root shell opened from the FreeNAS web interface is:

Code:

[root@freenas ~]# df
Filesystem											   512-blocks	   Used	   Avail Capacity  Mounted on
freenas-boot/ROOT/11.1-U6								  20317888	2324776	17993112	11%	/
devfs															 2		  2		   0   100%	/dev
tmpfs														 65536	  21288	   44248	32%	/etc
tmpfs														  8192		 16		8176	 0%	/mnt
tmpfs													  22325328	  50976	22274352	 0%	/var
freenas-boot/grub										  18009120	  16008	17993112	 0%	/boot/grub
fdescfs														   2		  2		   0   100%	/dev/fd
pool-a												  11204306800  317261088 10887045712	 3%	/mnt/pool-a
pool-a/Data											 10887045960		248 10887045712	 0%	/mnt/pool-a/Data
pool-a/jails											10887081328	  35616 10887045712	 0%	/mnt/pool-a/jails
pool-a/jails/.warden-template-pluginjail-10.3-x64	   10888006488	 960776 10887045712	 0%	/mnt/pool-a/jails/.warden-template-pluginjail-10.3-x64
pool-a/jails/.warden-template-standard-10.3-x64		 10890426656	3380944 10887045712	 0%	/mnt/pool-a/jails/.warden-template-standard-10.3-x64
pool-a/jails/git-server								 10957836064   70790352 10887045712	 1%	/mnt/pool-a/jails/git-server
pool-a/jails/plexmediaserver_1						  14498196416 3611150704 10887045712	25%	/mnt/pool-a/jails/plexmediaserver_1
pool-a/jails/plexmediaserver_1/plex-media			   11018447720  131402008 10887045712	 1%	/mnt/pool-a/jails/plexmediaserver_1/plex-media
pool-a/.system										  10887045904		192 10887045712	 0%	/var/db/system
pool-a/.system/cores									10887074152	  28440 10887045712	 0%	/var/db/system/cores
pool-a/.system/samba4								   10887047032	   1320 10887045712	 0%	/var/db/system/samba4
pool-a/.system/syslog-618a7bc26f3c409faab2b82ca8892702  10887056616	  10904 10887045712	 0%	/var/db/system/syslog-618a7bc26f3c409faab2b82ca8892702
pool-a/.system/rrd-618a7bc26f3c409faab2b82ca8892702	 10887096464	  50752 10887045712	 0%	/var/db/system/rrd-618a7bc26f3c409faab2b82ca8892702
pool-a/.system/configs-618a7bc26f3c409faab2b82ca8892702 10887146488	 100776 10887045712	 0%	/var/db/system/configs-618a7bc26f3c409faab2b82ca8892702
devfs															 2		  2		   0   100%	/mnt/pool-a/jails/git-server/dev
procfs															8		  8		   0   100%	/mnt/pool-a/jails/git-server/proc
devfs															 2		  2		   0   100%	/mnt/pool-a/jails/plexmediaserver_1/dev
procfs															8		  8		   0   100%	/mnt/pool-a/jails/plexmediaserver_1/proc
/mnt/pool-a/jails/plexmediaserver_1/plex-media		  11018447720  131402008 10887045712	 1%	/mnt/pool-a/jails/plexmediaserver_1/home/plex-media
[root@freenas ~]#

In the failing case, there is an extra mount point pool-a/jails/plexmediaserver_1/plex-media. Could that be hiding the real data behind that incorrect mount point?

Where should I look to find the definition of that mount point so that I can try removing the mount point?

Are there other things I should check?

Mark Waite

 

[dlavigne]

Were you able to figure this out?

 

[MarkEWaite]

I have not found a solution yet.

The "Storage" -> "Volumes" page looks like this:

I assume the problem file system is the highlighted one. It contains far too little information (62.7 GiB is too small for the media files that should be there), while its parent contains the right amount of information (1.8 TiB).

Unfortunately, I haven't found a way to remove the incorrect "plex-media" volume.

If that hunch is correct it may also explain that I'm wasting effort applying lz4 compression to media files that are already compressed in one form or another.