scottmbritton

I changed my exports to this and it seems to be working all day today. I don't have anything that actually does any writing over NFS. I tried just sync, but it seemed to cause a different issue. I will give it a few days and report back. # See exports(5) for a description. # This file contains a list of all directories exported to other computers. # It is used by rpc.nfsd and rpc.mountd. #"/mnt/user/BD" -async,no_subtree_check,fsid=100 *(rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/BD" -async,no_subtree_check,fsid=100 *(rw) #"/mnt/user/DVD" -async,no_subtree_check,fsid=101 *(rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/DVD" -async,no_subtree_check,fsid=101 *(rw) #"/mnt/user/TV" -async,no_subtree_check,fsid=102 *(rw,insecure,anongid=100,anonuid=99,all_squash) "/mnt/user/TV" -async,no_subtree_check,fsid=102 *(rw)

Hello. I have been running Unraid 4.7 for quite a while now. I recently upgraded to 5.0rc10 and upgraded each time a new version has come out and am currently running 5.0rc12. I use NFS for sharing media on my network for Boxee Box. BD, DVD, and TV shares which are mapped to boxee box as sources. I noticed that after the upgrade to 5.0 my boxee box devices would stop automatically updating media on their hourly scans. They would work for a while and then at some point would no longer add new media. A boxee box power cycle will temporarily fix the problem but it comes back within two days. While investigating I noticed that if I select the boxee box menu "Files" and browse my sources I would sometimes get a boxee box error when selecting a source to browse. This same source would show no data when boxee box would do it's scan. I found one other work around out side of the power cycle; selecting a media file from that source (movie list or tv list) would actually play and then if I went back to browse the source I would get a file listing and media would be found on the next scan but it reverts back to being inaccessible after a while (1-2 days). After experiencing this issue for a few weeks I decided to downgrade back to Unraid 4.7 to make sure this was not an issue with the 4.7 version. After the downgrade I was able to browse sources/shares with no issues and media is automatically being found on the hourly scans. I tested for a while and it has been working solidly as I am used to. Last night I took the jump back to 5.0-rc12 and in less than a day I am having the same issue again. So it seems that there is some difference with how the NFS shares are being handled that boxee box has difficulties with. I would very much like to be on the 5.0 version of code since it has features that I will want to take advantage of, but this issue I am seeing with boxee box is preventing that. I would be very grateful if someone could take a look into this and offer any suggestions outside of replacing boxee box I have attached some logs from unraid and boxee. In the logs below, I try to access the file source bd on boxee and get the access error screen. I see this error in the boxee syslog. 4/7/2013 5:31:55 PM [224858] From: (192.168.100.81) Fac:16 Sev:7 Msg >>> Apr 7 18:31:50 boxee GetDirectory - Error getting nfs://tower.brittonfamily.net/mnt/user/BD/ I then go to my movie listing and play 3:10 to Yuma which I know is in that share path. The movie plays fine. At the same time I played the movie I see this in the unraid syslog Apr 7 17:32:43 Tower mountd[1739]: authenticated mount request from 192.168.100.81:1011 for /mnt/user/BD (/mnt/user/BD) That is the IP for the boxee box in question. I then go back to the file | sources screen and I can access the BD share with no issues. Thanks. unraid-syslog.zip boxeebox-syslog.zip

Thanks. That worked.

No. I am using 2TB as the largest drives. I was running 4.7 previously with all the same drives and upgraded a few months ago. I can not locate my 4.7 flash drive backup. So I backed up and removed the 5.0 passwd, smbpasswd, and shadow files. I then put the 4.7 bzroot and bzimage files on the flash drive and rebooted.

Hello. I am trying to go back to 4.7 but after booting up unraid tells me that I have an invalid configuration. To many wrong and/or missing disks. I am trying to go back to 4.7 because of a specific issue that I have noticed with the 5.0 releases that I don't remember being an issue with 4.7. I want to verify this by going back to 4.7 for a while. Can anyone help me get my array back up and running? I took a screenshot of the disk placement in 5.0 and have matched it up in 4.7 but I am still getting the message that the disks are wrong. Thanks unraid_syslog.txt

Yeah, I can understand that, but I think if you are not watching the GUI to see how fast it is going it is actually going normal speed. Every time I open the GUI I see that it is going as fast as I am used to and it slowly drops. I am fine with that until it is fixed since I don't access the GUI that much and rarely when a parity check is running. Is there a way to see what the parity check speed is from command line?

Could this be something to do with the 'blinking activity lights' that others report when the SF 1.0.11 gui is open? Sounds like something is polling the disks, which as I understand it could effect parity check speed. Perhaps a more experienced user can chime in... I'm only going on what I recall reading here and there I think you are on to something. I am also noticing slow parity checks with 5.0.rc11 and SF 1.0.11. I was watching from the GUI and would only see 20 - 25MB/s and I could hear drives thrashing. When I closed the GUI the drive thrashing stopped. I reopened the GUI and saw that parity check was back up to 96MB/s and slowly decreased back to the 20-25 MB/s range. So on my system it appears to only be an issue when a parity check is running and you are watching the GUI.

Finally got my server indexing. Still a few tweaks needed. This will be something I do later on. Thanks for sharing your theme.

THANKS! This fixed the problem!

I was running SABnzbd 0.6.14 without issues. I tried to upgrade to 0.6.15 and am getting this error when trying to start SABnzbd. I even installed unMenu and SABnzbd through that thinking they might have a fix for this, but I am still getting the same error. Does anyone have an solution to fix this? Thanks. root@Tower:/mnt/cache/.sabnzbd# /mnt/cache/.sabnzbd/SABnzbd.py Traceback (most recent call last): File "/mnt/cache/.sabnzbd/SABnzbd.py", line 65, in <module> import sabnzbd File "/mnt/cache/.sabnzbd/sabnzbd/__init__.py", line 85, in <module> import sabnzbd.api File "/mnt/cache/.sabnzbd/sabnzbd/api.py", line 29, in <module> locale.setlocale(locale.LC_ALL, "") File "/usr/lib/python2.6/locale.py", line 513, in setlocale return _setlocale(category, locale) locale.Error: unsupported locale setting Python 2.6.4 (r264:75706, Dec 5 2009, 21:18:28) [GCC 4.3.3] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> locale.setlocale(locale.LC_ALL, "") Traceback (most recent call last): File "<stdin>", line 1, in <module> File "locale.py", line 513, in setlocale return _setlocale(category, locale) locale.Error: unsupported locale setting

Disconnected the Mapped drive on my Win7 PC and changed the spin down to 15 minutes so I didn't have to wait that long to see. The drives spun down after 15 minutes. Fun stuff.

Yes that appeared to be the case. Now.. after having it this way for a few days I am not getting the stutters/freeze like I was before, but I am pretty sure my drives are never spinning down. Before I would only find disk 1 spun down when I checked, but after putting them all in the same group I haven't seen them ever spun down. Which I guess would make sense since they are in the same group. I am curious why they will not spin down though. Will mapping a network drive from a windows 7 PC that never shuts down keep the drives up? I'm disconnecting it tonight to see if that makes a difference. I may answer my own question. Thanks

If you still need this info.. On the main screen.. far left of the screen next to the green status ball.. click on each disk (for example.. parity, disk1, disk2, disk3) and in the Spinup group(s): section put the same name for each disk.

Thanks for the responses. I now have them all in a spinup group and they all spinup at the same time. No more pauses when accessing the shares while watching a movie.

Hello. I am running version: 4.5.3, spinup groups is enabled I have 4 drives and they are all connected to 4 of the motherboards 6 sata ports. When I watch a movie parity disk, disk2, and disk3 spinup. Disk 1 does not spin up. If I access SMB shares on the server while watching the movie and disk1 spins up I will get a pause in the movie for about 2 to 3 seconds. In searching I see that this has to do with spinup and spinup groups were added to prevent this, but I think my disks are not in the same spinup group. Is there a way to add/force all the disks in the same group? Thanks. parity device: pci-0000:00:11.0-scsi-0:0:0:0 host1 (sda) WDC_WD10EACS-00ZJB0_WD-WCASJ1239364 disk1 device: pci-0000:00:11.0-scsi-1:0:0:0 host2 (sdb) WDC_WD10EACS-00ZJB0_WD-WCASJ1236063 disk2 device: pci-0000:00:11.0-scsi-2:0:0:0 host3 (sdc) WDC_WD10EADS-00L5B1_WD-WCAU45615899 disk3 device: pci-0000:00:11.0-scsi-3:0:0:0 host4 (sdd) WDC_WD10EADS-00L5B1_WD-WCAU45888872