After installing a plugin then restarting the computer plugins wont start. FreeNAS 9.10 STABLE
Just for grins, can we hop over to the Storage menu and make sure that your jails are showing up there?
After that, I'd go to System -> Advanced, and enable Show Console Messages In The Footer. Just in case there are better error messages popping up there.
Nov 12 19:25:55 freenas manage.py: [freeadmin.navtree:577] Couldn't retrieve http://192.168.1.54/plugins/emby/1/_s/treemenu: timed out
Nov 12 19:26:15 freenas manage.py: [freeadmin.navtree:577] Couldn't retrieve http://192.168.1.54/plugins/emby/1/_s/treemenu: HTTP Error 503: OK
Nov 12 19:26:19 freenas manage.py: [plugins.utils:91] Couldn't retrieve http://192.168.1.54/plugins/emby/1/_s/status: HTTP Error 503: OK
Nov 12 19:26:43 freenas manage.py: [middleware.exceptions:37] [MiddlewareError: The path could not be mounted /mnt/vol1/jails/emby_1: Mount failed 64 -> , mount_nullfs: /mnt/vol1/jails/emby_1 (/mnt/vol1/jails/emby_1) and /mnt/vol1/jails/emby_1/media are not distinct paths
]
Nov 12 19:26:44 freenas manage.py: [freeadmin.navtree:577] Couldn't retrieve http://192.168.1.54/plugins/emby/1/_s/treemenu: HTTP Error 503: OK
Nov 12 19:26:49 freenas manage.py: [freeadmin.navtree:577] Couldn't retrieve http://192.168.1.54/plugins/emby/1/_s/treemenu: HTTP Error 503: OK
Nov 12 19:27:19 freenas manage.py: [freeadmin.navtree:577] Couldn't retrieve http://192.168.1.54/plugins/emby/1/_s/treemenu: timed out
Nov 12 19:27:23 freenas manage.py: [freeadmin.navtree:577] Couldn't retrieve http://192.168.1.54/plugins/emby/1/_s/treemenu: timed out
Nov 12 19:27:44 freenas manage.py: [common.pipesubr:66] Popen()ing: /sbin/zfs list -H -o name '/mnt/vol1/jails/.warden-template-pluginjail'
Nov 12 19:27:44 freenas manage.py: [common.pipesubr:66] Popen()ing: /sbin/zfs get -H origin '/mnt/vol1/jails/emby_1'
Nov 12 19:27:44 freenas manage.py: [common.pipesubr:66] Popen()ing: /sbin/zfs list -H -o name '/mnt/vol1/jails/.warden-template-pluginjail'
Nov 12 19:27:44 freenas manage.py: [common.pipesubr:66] Popen()ing: /sbin/zfs get -H origin '/mnt/vol1/jails/emby_1'
Nov 12 19:27:50 freenas manage.py: [freeadmin.navtree:577] Couldn't retrieve http://192.168.1.54/plugins/emby/1/_s/treemenu: HTTP Error 503: OK
Nov 12 19:27:58 freenas manage.py: [plugins.utils:91] Couldn't retrieve http://192.168.1.54/plugins/emby/1/_s/status: HTTP Error 503: OK
Nov 12 19:27:44 freenas manage.py: [common.pipesubr:66] Popen()ing: /sbin/zfs get -H origin '/mnt/vol1/jails/emby_1'
Nov 12 19:27:50 freenas manage.py: [freeadmin.navtree:577] Couldn't retrieve
Nov 12 19:27:50 freenas manage.py: [freeadmin.navtree:577] Couldn't retrieve http://192.168.1.54/plugins/emby/1/_s/treemenu: HTTP Error 503: OK
Nov 12 19:27:58 freenas manage.py: [plugins.utils:91] Couldn't retrieve
That looks pretty damning to me. Does the jails dataset not exist?
it does exist
im going to do a fresh install of a different version of freenas see if I have any luck.
Oh here. I missed this little gem. Do you have storage attached to the jail currently? If so, could you remove that storage entry and try to start it again?
edit:
Oops. Looks like I missed the re-OS boat. Well definitely come back if it keeps giving you trouble.
Ok I'm new to freenas how do I check if there is storage attached and if not how do I attach storage?
Easiest way is to go to Jails, then Storage, and see if you have any entries there. This is the section that allows you to tie a directory in your dataset to a directory inside the jail. So in the screenshot above I've got 2 directories inside of the jail plexmediaserver_1, and 1 directory for clonedeploy_1.
If you see an entry for your emby_1 jail, go ahead and delete it.
okay well for some reason it is working now ty for the help anyway if I have any other problems ill ask you. :)
wait why should I delete emby_1 jail?
for emby 1 what source am I meant to put there and what destination? I think this could be why I cant start up the plugin.
* I have made I new data set in the emby jail storage called source and I am using it as destination and now the storage should be working but the plugin is still not working
This seems like something that should work, but best I can tell is absolutely not how FreeNAS wants you to do it. Let's say you've got your zpool tank. Because all ZFS documentation loves the Matrix. FreeNAS automatically creates jails as its own dataset within tank, and you might have NASStorage as where you put the carefully collected, useless junk you find around the Internet.
So now you have:
tank/NASStorage
tank/jails
You create the emby_1 jail. FreeNAS creates a new dataset for its files to live in. Now you have
tank/NASStorage
tank/jails
tank/jails/emby_1
Now you've created a new dataset. Emby is a media server, so let's say you created the dataset Videos. And from what I gather is that you created it in the emby_1 dataset. So you have tank/jails/emby_1/Videos. Is that accurate? My whole response hinges on that being the thing that you've done.
If it is what you've done, undo it. Don't put any datasets within the jails dataset. In order to provide emby_1 with whatever you want to put in the Videos dataset, what you would do is create the Videos dataset in NASStorage.
tank/NASStorage
tank/NASStorage/Videos
tank/jails
tank/jails/emby_1
Then, after Videos is populated with everything you want, you need to link storage from your zpool somewhere, into your jail. You do this by expanding Jails in the left menu, expand emby_1, expand storage, and select add storage.
In the configuration page that pops up:
Jail should already been on emby_1.
Source in our current example will be the Videos dataset, so you would browse to /mnt/tank/NASStorage/Videos.
Destination will be the directory inside your jail where the Videos dataset will be linked.
Read-only can be enabled if you want to make sure that nothing in your jail can come back and screw with your data (this can jack with multimedia servers, so best to leave this unchecked until you get things working, then experiment)
Create directory can be checked if the directory inside your jail doesn't exist yet. For example, jails have a /media directory. If you wanted to mount it /media/Videos, you could select his box and it would create the Videos directory for you.
Mounted needs to be checked in order for the software running in the jail to see the data in tank/NASStorage/Videos
This isn't the most straight forward thing to understand. Here's my FreeNAS box using the Plex media server.
My storage setup. I have 2 zpools, CheetahZFS and Sarth1. Ignore CheetahZFS and focus on Sarth1. About half way down you'll see a Media dataset, followed by a dataset for Audio and a dataset for Video. Finally at the bottom, you'll see jails, and plexmediaserver_1. There are no datasets inside plexmediaserver_1.
Moving on to storage for jails. In this picture you see I've expanded everything for plexmediaserver_1. The source is /mnt/Sarth1/Media/Videos/Movies, and inside my jail it's mounted at /media/Movies. Movies is simply a plain jane directory within Videos, there's also a TV directory, which you can see there is linked storage for that as well.
Does this help?
This does help and I have fixed all those other problems but for some reason now my transfer speeds are inconsistent. Right now I'm trying to transfer 700GB of data from my pc to the NAS and I was getting around 100MB/s and suddenly its dropped to 0 bytes/s.
NAS:
CPU: AMD A8-5600K
Storage: HGST Deskstar NAS 3TB 0S03662
8GB of ram
Even when I was getting 100 mbp/s it was dropping down to 20-50 like 20% of the time.
But I can also watch videos from my nas ands its flawless but the transfer is still 0 bytes/s
Usually when you have fast speeds for a period of time, and then they tank, it's because the ZFS Intent Log (ZIL, which resides memory) gets filled up first, and then you're transferring about as quickly as things can be written to the drive (check the memory reports page to see if your memory usage increases sharply when your data transfer started). This should be faster than 12MB/s even with only 1 NAS drive, so this probably isn't the only problem.
First and foremost, do you have deduplication on? If yes, turn it off. Turn it the hell off. This will chew up RAM and CPU like you wouldn't believe. The more memory your system uses, the less it has for the ZIL. And CPU being busy is bad for obvious reasons. ZFS needs CPU time to calculate checksums and such. In short, lz4 compression good, deduplication bad.
The solutions to this are:
1. More memory
2. A dedicate ZIL device (which could be a 64GB SSD, for example). But be careful with this one. If your ZIL goes down, your zpool goes down.
Another piece to this issue may be CIFS/SMB, which is likely how you're transferring everything to your NAS. There is a LOT of wiggle room for performance tuning with CIFS, and unfortunately there aren't a whole lot of silver bullets out there. You'll need to Google this one and start tuning until you get things right for your environment. I'd highly recommend starting with setting the minimum and maximum server protocol levels.
What would be the best way to transfer files ftp or something?
FTP would be good for a test to see how well your FreeNAS box is performing. It's about as seamless a transfer protocol as you can get. Obviously not the easiest thing to use long term. But just to get a bunch of data transferred so that you can use your system now and troubleshoot later, FTP works.
If ever you have to do transfers over the Filthy Unwashed Internet, FTP is never the right option. SFTP or go home. This is my standard disclaimer because I see far too many people still using FTP these days, even for business usage.
I have been trying to change the protocols but it seems to not change at all im stuck at 12MB/s ...