Dase

Members
  • Posts

    56
  • Joined

  • Last visited

Everything posted by Dase

  1. I'm having the same problem where the cron job isn't running this automatically, so I have to run it manually. Anybody found a fix for this yet?
  2. I initially had this problem too. I fixed it by making plexWatch.pl executable in the container. For some reason it isn't by default and so the cron job doesn't run it. docker exec -it plexWatch bash chmod +x /plexWatch/plexWatch.pl exit
  3. Check this post on configuring Windows 7 for NFS. Perhaps it will help: http://lime-technology.com/forum/index.php?topic=13022.0
  4. See this post for info on accessing NFS shares from Windows 7: http://lime-technology.com/forum/index.php?action=printpage;topic=13022.0
  5. I'm not sure how to do it from the GUI. From the command prompt, do something similar to the following. 1. On your Ubuntu box create a directory to hold your unRAID shares. I created one at the root called tower. sudo mkdir /tower sudo mkdir /tower/disk1 2. Let's mount the unRAID disk1 inside your Ubuntu /tower/disk1 (my unRAID is at 192.168.0.10, change this to match yours): sudo mount -t cifs -o noperm,user=<unraid user>,password=,uid=nobody,gid=users //192.168.0.10/disk1 /tower/disk1 3. Check to make sure it worked: cd /tower/disk1 ls You should see your unRAID disk1 directories.
  6. You can check this post for some additional info: http://lime-technology.com/forum/index.php?topic=13317.0. I use a line like this in my Ubuntu fstab to mount my unRAID shares: //192.168.0.10/disk1 /mnt/disk1 cifs username=<unRAID user>,password=<unRAID user password>,noperms,uid=nobody,gid=users 0 0
  7. Did you install the php upgrade package: php-upgrade+unraid-0.0.2-i386-bubba.tgz (http://lime-technology.com/forum/index.php?topic=7274.0)? I only had to install this once. It seems to reinstall on boot. I couldn't get the phpVirtualBox Web page to load without it. Try doing that, rebooting, and rerunning your VirtualBox commands.
  8. I didn't see a final solution in this thread so I thought I'd post one. I did more troubleshooting on my Ubuntu 11.04 fstab and this is the final line I ended up using that allows read/write access and creates files with the correct unRAID permissions. From what I could tell, I pared it down to the minimum parameters required to make things work. It's also much cleaner than the line I posted earlier in this thread. //192.168.0.10/disk1 /mnt/disk1 cifs username=<unRAID user>,password=<unRAID user password>,noperms,uid=nobody,gid=users 0 0 Replace 192.168.0.10 with your unRAID IP address Replace "disk1" with the unRAID share name that you're mounting My unRAID shares were read-only until I added "noperms" For unRAID 5, you want to make sure your files are owned by the "users" group (gid=users). That's the group that all unRAID users are a member of, and it makes sure your other users can move/delete files you create through your Linux computer. I set the user to nobody (uid=nobody) though you could replace that with your actual unRAID user. To quote limetech on permissions: I won't say how many hours I spent on my Ubuntu server figuring this out...
  9. Oh, and one more note. By default the guest additions are installed to /opt/VirtualBox/additions/. You shouldn't have to download those separately. Just point the CD drive in phpvirtualbox to the right file in that folder.
  10. I had alignment problems with the VirtualBox remote desktop too. I made do with the VirtualBox remote desktop just long enough to enable real remote desktop in my Windows install. Once I switched to direct remote desktop, the alignment problems went away.
  11. I think I read in the VirtualBox docs that to get 64-bit working you've got to enable IO APIC (under System > Motherboard in phpvirtualbox). Glad you got phpvirtualbox working though. On my motherboard I couldn't assign more than 1 core to a VM, even though my processor supposedly supports it. So some of that stuff is hit or miss.
  12. I couldn't get the unmenu versions to work. I installed the two packages I linked to, as I described. I didn't try the combined web package.
  13. Are the results any different when you add index.html to the phpvirtualbox path in your URL? Just confirming that you aren't trying to load config.php directly.
  14. I have a few years of experience with Linux but I'm far from an expert. I spent about 20 hours finding out these things that I wish someone had told me up front about getting VirtualBox running on unRAID. Really though, it should be less than a couple hours work getting this going if you have enough info up front. Huge credit of course goes to the wiki page author for getting the less-experienced of us 95% there at: http://lime-technology.com/wiki/index.php?title=Installing_VirtualBox_in_unRAID This is on unRAID 5.0 b14. Installation tips Don't run the installation scripts on your flash! I did it on my cache drive in some folders that begin with a period so they won't get moved. If the script screws up, any changes to the virtual filesystem will be removed when you reboot and you'll be back to normal. The only change left over after the reboot should be the symlink from /root/.VirtualBox. If something fails, reboot, fix, and try again. Don't break up the installation scripts. I was nervous about running so many commands at once, but my attempts to do things incrementally failed hard. As the wiki says, first double-check the links, then I suggest you run the scripts as is. The only link that didn't work was the kernel download. I had to change the version from 2.6 to 3.0. Don't forget to do the manual steps between the first and second scripts. After building the headers, you have to create the symlink I mentioned above and install VirtualBox. These two steps are in the manual part of the wiki. I still had to point the installer to a temp folder with 4 GB ram: mkdir -p /boot/custom/vbox && ln -sf /boot/custom/vbox /root/.VirtualBox export TMPDIR=/mnt/cache/.tmp && sh VirtualBox-4.1.8-75467-Linux_x86.run When creating the VirtualBox package after installing VirtualBox, accept the option to remove symlinks (press y). And say no to changing all the permissions. phpvirtualbox tips Run this command once to allow phpvirtualbox to talk to virtualbox: VBoxManage setproperty websrvauthlibrary null To install phpvirtualbox, just copy it somewhere and copy config.php.example to config.php. You don't have to make any changes. The PHP version that unRAID 5 uses doesn't work with phpvirtualbox. I got a SOAP not enabled error. I couldn't get the PHP or lighttpd versions that you can install from unMenu to work with phpvirtualbox. At all. It was cake with bubba's versions: http://lime-technology.com/forum/index.php?topic=7274.0 http://lime-technology.com/forum/index.php?topic=7267.0 Install his PHP package, which auto-reinstalled for me. I have to rerun his httpd package each boot. For httpd configuration, go to the main unRAID Utils page and you'll see the lighttpd user application. Change the directory to wherever you installed phpvirtualbox. Make sure you start lightttpd. Hit it on port 89 and the main phpvirtualbox page should load. The default phpvirtualbox authentication is admin and admin. You can disable authentication in config.php. VirtualBox tips VirtualBox supports VM remote desktop (this even works through VM post and boot). But you have to install the VirtualBox extension pack each boot to use this: VBoxManage extpack install Oracle_VM_VirtualBox_Extension_Pack-4.1.8-75467.vbox-extpack After installing the extension pack and before installing a VM from scratch, enable remote desktop for your new VM in phpvirtualbox under Display > Remote Display. You can turn this on even after a VM boots. Your default remote desktop port is 3389 on your unRAID box, not the VM IP address. This port increments for each VM you have running. And use the standard Windows Remote Desktop app to access it. VNC doesn't work. I use these lines to install VirtualBox and phpvirtualbox after unRAID boots: installpkg VirtualBox-4.1.8-unRAID.tgz installpkg lighttpd+unraid-0.2.01-i386-bubba.tgz vboxwebsrv -H 0.0.0.0 >/dev/null 2>&1 & VBoxManage extpack install Oracle_VM_VirtualBox_Extension_Pack-4.1.8-75467.vbox-extpack Hope this helps someone.
  15. I upgraded from beta 12a to beta 13 without any problems. My onboard Realtek 8111E NIC works fine with both versions. I have 5 or so drives running off an SASLP-MV8. My motherboard is a Biostar TH67B (http://www.newegg.com/Product/Product.aspx?Item=N82E16813138308). I'm planning on running two SAASLP-MV8 boards on this but only have one plugged in so far.
  16. I had the same problem with unRAID shares on an Ubuntu installation. After several hours of google-fu and many tests I finally found a combination of parameters that gave me write access. Here's a sample that's working for me from my fstab: //tower/Downloads /mnt/tower/Downloads cifs username=<username>,uid=<username>,gid=users,dir_mask=0777,file_mask=0755,password=,rw 0 0 You may not need all those parameters. I can't remember which one finally made the difference. I was just relieved to finally have it working.
  17. You've probably already checked this, but have you looked in your CMOS setup and made sure the BIOS is managing your CPU fan speed correctly? Depending on the BIOS, you may have to try a few settings to get this working.
  18. I don't have NFS enabled right now, but I believe once you select secure or private and apply the change, a dropdown appears for each unRAID account where you can select the type of access you want.
  19. Have you tried rebooting your unRAID after enabling NFS? I couldn't get NFS shares to work until I did that. NFS permissions are set in drop-down lists inside each share configuration. You don't manually specify *(rw) any more. Instead, you can use the UI to give each unRAID user account the permissions you want.
  20. I'm passing this info along to hopefully save someone else the hours of googling it took me to figure this out. NFS support in Windows is very poorly documented. First of all, you need Windows 7 Ultimate for this to work. Lesser versions of Windows 7 don't include NFS support. My main roadblock was that every share I mapped resulted in "Access denied" errors. It turns out you need an obscure registry hack to allow Windows to authenticate properly. Here's what you need to do. 1. In Control Panel, open Programs and Features. 2. Click "Turn Windows features on or off." 3. Enable "Services for NFS" and click OK. Wait for it to install. 4. Start the registry editor. 5. Locate HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default. 6. Create two DWORD values: AnonymousUid and AnonymousGid. They both need to be set to the number zero (0). 7. Reboot. 8. Activate NFS in unRAID 5 (Settings tab) and on the Main tab click the shares you want to export. Set "Export" to Yes. I used Public security. I had to reboot my unRAID server for NFS shares to work after enabling NFS support the first time. 8. In Windows 7, map your drives with the "Map network drive" feature by using this format for the path: tower:/mnt/user/Video You can also do this from the command line: mount tower:/mnt/user/Video z: Note that for NFS shares you have to provide the full unRAID folder path, not just the final shared folder. Alas, after doing all this work I found out that my NFS transfers in Windows topped out at about 30 MB/sec. I get up to 120 MB/sec in Samba. Oh well.
  21. It looks fine for me on the beta build (11.0.696.57 beta).
  22. I had to stop unmenu from installing the PHP package for my 5.0 upgrade. The unraid web UI was all garbled with it active.
  23. Are you specifying the IP addresses you want to access the NFS shares? I have this on the shares page at the top in the "Disk shares (NFS):" field: 192.168.0.1(rw) 192.168.0.2(rw) You have to do the same thing in each share's "Export (NFS):" field too. Here's the wiki topic on this: http://www.lime-technology.com/wiki/index.php?title=FAQ#How_do_I_configure_NFS_mounts.3F
  24. That's a good question. I hope the kernel would consistently assign USB posts based on the motherboard's USB port order rather than power-on order, but I don't know for sure. Messages appear in the syslog as devices connect so you could see how that's being handled. From what I can tell, p910nd doesn't have any clue what it's connected to, other than the USB post.
  25. It should. You can run an instance for each printer and each instance has its own port. The first is port 9100, the second port 9101, etc. Since the print drivers will be pointing to different ports there shouldn't be any conflicts.