kl0wn

Members
  • Posts

    69
  • Joined

  • Last visited

Everything posted by kl0wn

  1. I forgot to mention I did login to check TOP and nothing was jumping out at me as unusually high, which makes this thing even more confusing. I did notice that there was an IOWAIT the first time I had to bounce the box, which leads me to believe that there are some IO Operations hanging, thus causing the Kernel to go crazy. This did not happen prior to 6.6 so I'm wondering what changes were made that could cause this. Here is a screen of TOP when everything is normal, which is basically a mirror image of what it looks like when things are going haywire...
  2. Ever morning my processor goes to 100% and just hangs there for hours until I reboot the server. This was never an issue before and is now a daily thing....the logs are giving me jack for troubleshooting Any thoughts?: Oct 22 20:00:16 Tower crond[1673]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Oct 22 20:53:04 Tower sshd[13608]: SSH: Server;Ltype: Kex;Remote: 192.168.2.109-10539;Enc: [email protected];MAC: <implicit>;Comp: [email protected] Oct 22 21:00:01 Tower crond[1673]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Oct 22 22:00:16 Tower crond[1673]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Oct 22 23:00:10 Tower crond[1673]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Oct 23 00:00:01 Tower Plugin Auto Update: Checking for available plugin updates Oct 23 00:00:07 Tower crond[1673]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Oct 23 00:00:28 Tower Plugin Auto Update: Community Applications Plugin Auto Update finished Oct 23 01:00:07 Tower crond[1673]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Oct 23 02:00:16 Tower crond[1673]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Oct 23 03:00:07 Tower crond[1673]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Oct 23 04:00:14 Tower root: /mnt/cache: 8 GiB (8576638976 bytes) trimmed Oct 23 04:00:14 Tower crond[1673]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Oct 23 05:00:16 Tower crond[1673]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Oct 23 06:00:07 Tower crond[1673]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Oct 23 07:00:16 Tower crond[1673]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Oct 23 08:00:16 Tower crond[1673]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Oct 23 09:00:16 Tower crond[1673]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null Oct 23 10:00:07 Tower crond[1673]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null
  3. Howdy, I have scripts setup to reboot my docker containers nightly be running 'docker restart <container id goes here>'. I noticed that this wasn't occurring nightly so I dug a little deeper. I compared my scripts to the Container ID's and found that they had changed. I saw some orphaned images, and thought it was a fluke and that's what caused the container ID to change. However, I just checked again and found that my Container ID's have again changed with no orphaned images in site. Am I wrong to assume that the Container ID's should remain the same or is something wonky going on? NOTE: I also have my Docker's set to auto-update at 6AM every day. Thanks
  4. I got it figured out and cut my transfer time in half. Here is what I did: Stop any and ALL automation that reads the shares in real-time or any dockers that may look at the directories. (ie Sab, CP, Sonarr etc.) Stop the array and unassig the parity disk. This took my write speed from 30MB/s to 50MB/s (WARNING: This will leave your array unprotected during the next steps!) Setup a movies_temp and tv_temp share with the split-level you want. This will be the shares you move your files to so they can be re-split and balance across the drives. (NOTE: DISABLE YOUR CACHE DRIVE) Create a Windows VM on unraid or dedicate a standalone box in your environment for the transfer. I'd recommend a VM as you get a 10GbE connection and the transfer times should be better. In your Windows VM, map the original movies and tv folders along with the temp ones you created. Download and install Teracopy. Initiate a move from the original to the temp directories. (NOTE: Teracopy may or may not say you don't have enough space to complete the operation. While in my case I only have 4TB free and I'm "Moving" 16TB, we can safely ignore this error. Why? Because we are simply moving files from the array and back. This means the free sapce that Teracopy is seeing is irrelevant to this procedure. Grab a case of beer and wait a few days for the data to finish transferring.
  5. Yeah - sorry for the incorrectly representing what I did. Yes I moved in MC rather than copied, would that trigger different behavior? The difference I saw was when moving in MC the files were not even touching the new drive, even though Most-Free is enabled. I'm guessing this is due to the fact I'm transferring to /mnt/user/movies_temp and not a samba share. However, In the Windows VM I'm moving files between mapped shares, so this in turn triggers Most-Free and Split-Level as expected. In short, I'm just trying to get my Movies share to a different split-level and rebalance the files across all drives. If there is a more efficient way of achieving this, please let me know. Thanks for the assistance.
  6. I want to add another 4TB HDD and rebalance all data across, all of my drives. During this process I will be changing my split-level as well so I can keep my movie directories and their album art, etc, etc on the same drive. Now I've read I can copy files to a new temp share and then rename the temp share back to Movies. I tried to accomplish this via MC so I can get the best throughput but sadly MC doesn't trigger any share level attributes (split level, Most-Free, etc.) I tried to do the transfer via VM but with 16TB worth of data that will take close to a week to complete (50MB/s transfer speed). Has anyone else tried this? Any suggestions? My main goal is to rebalance and spread the love across all my drives. Rather than all new content hitting my new 4TB HDD, which will in turn cause it to get flooded when users are streaming content.
  7. I installed the plugin, plugged in my external and UNRAID recognizes the device: Aug 19 00:08:58 Tower kernel: usb 7-2: new SuperSpeed USB device number 15 using xhci_hcd Aug 19 00:08:58 Tower kernel: usb-storage 7-2:1.0: USB Mass Storage device detected Aug 19 00:08:58 Tower kernel: scsi host24: usb-storage 7-2:1.0 But both SNAP and Unassigned Devices do not show it listed. Any help would be greatly appreciated. Thanks!
  8. Docker won't start and my logs are spammed with these messages. Been like this for hours. Any help would be greatly appreciated. Mar 24 11:08:33 Tower root: starting docker ... Mar 24 11:08:34 Tower emhttp: shcmd (240): /etc/rc.d/rc.libvirt start |& logger Mar 24 11:08:34 Tower root: no image mounted at /etc/libvirt Mar 24 11:08:36 Tower root: mount: /mnt/cache/docker.img is already mounted Mar 24 11:08:36 Tower root: mount error Mar 24 11:08:36 Tower emhttp: shcmd (250): /etc/rc.d/rc.docker start |& logger Mar 24 11:08:36 Tower root: starting docker ... Mar 24 11:08:36 Tower emhttp: shcmd (253): /etc/rc.d/rc.libvirt start |& logger Mar 24 11:08:36 Tower root: no image mounted at /etc/libvirt Mar 24 11:09:01 Tower root: mount: /mnt/cache/docker.img is already mounted Mar 24 11:09:01 Tower root: mount error Mar 24 11:09:01 Tower emhttp: shcmd (263): /etc/rc.d/rc.docker start |& logger Mar 24 11:09:01 Tower root: starting docker ... Mar 24 11:09:01 Tower emhttp: shcmd (266): /etc/rc.d/rc.libvirt start |& logger Mar 24 11:09:01 Tower root: no image mounted at /etc/libvirt Mar 24 11:10:01 Tower root: mount: /mnt/cache/docker.img is already mounted Mar 24 11:10:01 Tower root: mount error Mar 24 11:10:01 Tower emhttp: shcmd (276): /etc/rc.d/rc.docker start |& logger Mar 24 11:10:02 Tower root: starting docker ... Mar 24 11:10:02 Tower emhttp: shcmd (279): /etc/rc.d/rc.libvirt start |& logger Mar 24 11:10:02 Tower root: no image mounted at /etc/libvirt Mar 24 11:11:01 Tower root: mount: /mnt/cache/docker.img is already mounted Mar 24 11:11:01 Tower root: mount error Mar 24 11:11:01 Tower emhttp: shcmd (289): /etc/rc.d/rc.docker start |& logger Mar 24 11:11:01 Tower root: starting docker ... Mar 24 11:11:01 Tower emhttp: shcmd (292): /etc/rc.d/rc.libvirt start |& logger Mar 24 11:11:01 Tower root: no image mounted at /etc/libvirt Mar 24 11:12:01 Tower root: mount: /mnt/cache/docker.img is already mounted Mar 24 11:12:01 Tower root: mount error Mar 24 11:12:01 Tower emhttp: shcmd (302): /etc/rc.d/rc.docker start |& logger Mar 24 11:12:01 Tower root: starting docker ... Mar 24 11:12:01 Tower emhttp: shcmd (305): /etc/rc.d/rc.libvirt start |& logger Mar 24 11:12:01 Tower root: no image mounted at /etc/libvirt Mar 24 11:12:10 Tower root: mount: /mnt/cache/docker.img is already mounted Mar 24 11:12:10 Tower root: mount error Mar 24 11:12:10 Tower emhttp: shcmd (315): /etc/rc.d/rc.docker start |& logger Mar 24 11:12:10 Tower root: starting docker ... Mar 24 11:12:10 Tower emhttp: shcmd (318): /etc/rc.d/rc.libvirt start |& logger Mar 24 11:12:10 Tower root: no image mounted at /etc/libvirt
  9. Same deal under windows 8. I am able to pass the "AMD Trinity HDMI" but I believe that is the one associated with the APU and onboard (shows it's passed but disconnected). I have another controller that references the AMD 5000 series...so I believe that's the one that is supposed to be passed. Sadly that is the one that shows it cannot start in device manager. Any logs I can yank to narow down what's going on?
  10. Howdy, I am currently passing a 5450 to a windows 7 VM without issues EXCEPT the HDMI Audio. I have it selected, I'm able to start the VM but in Device Manager it is showing HDMI Audio Controller failed to start. I tried going to Update Driver but it says it's already up-to-date. I'm getting no errors on start, so I'm hoping someone can shed some light. Thanks!
  11. I'm currently running OpenVPN on the router itself but I could easily migrate that to the unraid box if necessary. What routing rules do you have in place to have plex bypass the VPN? I would just open ports with the provider but I'd like to not go that route due to security.
  12. I have spent the past few days looking at multiple threads about having plex either A. run over the vpn or B. bypass it. The problem I see is every thread pretty much ends in the same thing, "it worked for a bit but now it doesn't". I am currently running unRAID 6 for my OS and have a rt-n66u as my router. I want to know if there is a way I can setup plex to bypass the OpenVPN interface? Thanks!
  13. Looks like a couple reboots and the addition of a cache drive got disk3 in the mix. Thanks for all the help guys!
  14. Nope. I'm now on pro and it still won't write to the 3rd drive when copying files to the array...
  15. Lol yeah just figured that out. I figured there would be an error or something. *shrugs* purchasing now.
  16. Thst could be the problem as well. I thought you could use 3 drives whether they were all data or 2 data and 1 parity.
  17. I rebooted the box remotely and I'm not seeing any mention of read only in the syslog. http://pastebin.com/iaz6cvjL
  18. Wonderful. Just headed out of town haha. I'll check it when I get home. Thanks man
  19. Thanks guys it was due to me not specifying the partition. All is well now. Thanks!
  20. Hello, I have unRAID basic with 3 data drives. I was able to move existing data over to the user share after enabling sharing for the first 2 drives. When I added the third and attempted to move data it kept saying the array was out of space. Even though I had a fresh 3TB drive showing 33.7MB used in the array. So now I decided to just move the data to disk3 manually. I moved a few files, stopped the array and started it. I then went to the user share and noticed that the files on Disk3 are not present in the share. At this point I'm lost because every part of the 2 previous transfers went thru with no problem.
  21. turns out the Flash drive just needed another wipe. All is well now. Thank you, sir