mac4685

Members
  • Posts

    15
  • Joined

  • Last visited

Everything posted by mac4685

  1. If anyone is having issues with this with Windows 10, I was able to find a solution. I basically just created a user in Unraid and when I tried to connect to my unraid tower from my Windows computer, I put in my username and password for the user I just created in Unraid and selected "Remember my credentials" and it worked. It connects to my mapped network drives even after a reboot now. I'm not sure why all of a sudden this was necessary, I've never done that before until now. Hopefully this helps anyone else out using SMB on Windows 10.
  2. Having the issue with smb on 6.7.2 as well. Downgrading for now.
  3. Yes it's basically the same thing. The main theme of both threads is to have a dedicated drive to dockers and VMs rather than use the cache or data drives. Sent from my SM-N910V using Tapatalk
  4. I'm not using protected samba shares but I tried directing the version to Jarvis by using "linuxserver/kodi-headless:Jarvis" in the repository directory and that seems to have fixed the log spamming.
  5. I'm get this spammed in the log. Any ideas? mkdir failed on directory /var/cache/samba: Permission denied mkdir failed on directory /var/cache/samba: Permission denied mkdir failed on directory /var/cache/samba: Permission denied mkdir failed on directory /var/cache/samba: Permission denied mkdir failed on directory /var/cache/samba: Permission denied mkdir failed on directory /var/cache/samba: Permission denied mkdir failed on directory /var/cache/samba: Permission denied mkdir failed on directory /var/cache/samba: Permission denied mkdir failed on directory /var/cache/samba: Permission denied mkdir failed on directory /var/cache/samba: Permission denied mkdir failed on directory /var/cache/samba: Permission denied mkdir failed on directory /var/cache/samba: Permission denied mkdir failed on directory /var/cache/samba: Permission denied
  6. I wholeheartedly agree with this request. I've been an unraid user for about 6 years now and I really love it. I usually don't write much in the forums, mostly just read what everyone else posts. In 6.1.9 I've been using Unassigned Devices to mount my 250GB ssd for 2 vms and about 12 or so dockers. After upgrading to 6.2, I have to say I was really disappointed that I could no longer use my UD ssd and instead would have to either use my HD cache or my small ssd as a cache. Since buying a new ssd cache drive isn't really in my budget right now, I'm forced to go back to 6.1.9. It would really be nice if there was another drive class implemented with unraid.
  7. Rebooted the server and I started getting this segfault error in my syslog. I've tried removing the docker completely and reinstalling but still get the error. Any ideas? Aug 28 01:06:29 Tower kernel: JobWorker[12434]: segfault at 4c0 ip 00000000009c0cc7 sp 00002b02f0a02730 error 4 in kodi.bin[400000+1da6000] Aug 28 01:06:49 Tower kernel: JobWorker[12723]: segfault at 4c0 ip 00000000009c0cc7 sp 00002b77623db730 error 4 in kodi.bin[400000+1da6000] Aug 28 01:07:09 Tower kernel: JobWorker[12997]: segfault at 4c0 ip 00000000009c0cc7 sp 00002b8ff9d1b730 error 4 in kodi.bin[400000+1da6000] Aug 28 01:07:29 Tower kernel: JobWorker[13202]: segfault at 4c0 ip 00000000009c0cc7 sp 00002b226d412730 error 4 in kodi.bin[400000+1da6000] Aug 28 01:07:48 Tower kernel: JobWorker[13476]: segfault at 4c0 ip 00000000009c0cc7 sp 00002b9537901730 error 4 in kodi.bin[400000+1da6000]
  8. I use JSON and cURL to trigger updates, from this guide http://kodi.wiki/view/HOW-TO:Remotely_update_library I just have my sync program run a .bat file (the specific string for update library) after sync, and it works perfectly. Sync program monitors the folder (Allway Sync) and UTorrent does its thing. I used the kodi-send update command with Sparklyballs' version of this docker, but since moving over to this one I get a "exec: "kodi-send": executable file not found in $PATH" error. Any idea on what I need to do to get the kodi-send command to work? docker exec kodi-headless kodi-send --action="UpdateLibrary(video)" I wasn't ever able to get kodi-send to work on this docker so I am now using JSON and cURL to trigger updates. I setup a script with this: curl --silent -H "Content-Type: application/json" -u user:pass -d '{"jsonrpc":"2.0","method":"VideoLibrary.Scan","id":"scan"}' http://hostname:port/jsonrpc > /dev/null I have a crontab setup that runs this script every so often throughout the day so when I open up Kodi on my VM, all of my recently added shows show up and I don't have to manually update and wait . The --silent part is optional but you will get an email every time this runs if you don't include that. Hopefully this helps others that need a way to send updates remotely without using kodi-send.
  9. I use JSON and cURL to trigger updates, from this guide http://kodi.wiki/view/HOW-TO:Remotely_update_library I just have my sync program run a .bat file (the specific string for update library) after sync, and it works perfectly. Sync program monitors the folder (Allway Sync) and UTorrent does its thing. I used the kodi-send update command with Sparklyballs' version of this docker, but since moving over to this one I get a "exec: "kodi-send": executable file not found in $PATH" error. Any idea on what I need to do to get the kodi-send command to work? docker exec kodi-headless kodi-send --action="UpdateLibrary(video)"
  10. They are usually pretty easy to extract but it might void the warranty of the drive? I'm assuming the internal drive is the Toshiba X300 Desktop Internal.
  11. I was having the same problem before i upgraded my hardware when I had 4GB of RAM. I just enabled a paging file on my cache drive with another 4gb. Problem solved for me.
  12. I've already tried all of the usb settings. My mobo gives the option of usb-hdd, usb-fdd, and usb-zip. All of which boot the same to boot unraid. I also have my boot priorities all set to boot from usb.
  13. Ok I just figured out that the key file doesn't have anything to do with it. I first realized if I just plug my flash drive into another computer and then back into my server it boots fine without moving any files. Then I tried just removing the flash drive from the server after it has shutdown and plugging it right back in and oddly enough it boots correctly. I also tried flipping the switch on the PSU after shutting down to off then back on and rebooting and that seems to be working too. So maybe the flash drive has to lose all power first before it can boot again correctly At least I know now that I don't have to plug it into another computer and swap a file around. It must just be this samsung flash drive. I guess if it keeps bothering me I'll just try a new one then.
  14. So I've been having this issue for quite some time now. Anytime I have to reboot my server, if I don't move the Pro.key file to or from the config folder it doesn't boot. Instead it sits on a "loading operating system" message. Once I move it though, it boots fine and normally. I am using a Gigabyte MA74GM-S2 motherboard with my boot settings set to boot only on the USB drive. I am also running 4.7. It's been this way since 4.5 I think. I've done everything to make my USB drive bootable too and that hasn't done anything. It hasn't really been a big deal because I rarely reboot but it is getting a little annoying and I've looked EVERYWHERE on the forums to try and fix this and there hasn't been any topics on moving a key file before it will reboot. Hope you can help. Thanks.