pyrater

Members
  • Posts

    604
  • Joined

  • Last visited

Everything posted by pyrater

  1. Can anyone help me figure out why HW transcoding is no longer working??? I just reinstalled the latest docker and i can no longer get it to work. M/B: ASRock - Z370M Pro4 CPU: Intel® Core™ i5-8400 CPU Transcoding to /ramdisk (8GB) "Use hardware acceleration when available" settings enabled Unraid 6.5.0 root@HAL9000:/ramdisk# chown -R nobody:users /dev/dri chown: cannot access '/dev/dri': No such file or directory root@HAL9000:/ramdisk# ls -alh /dev/dri /bin/ls: cannot access '/dev/dri': No such file or directory root@HAL9000:/ramdisk# lsmod | grep i915 i915 1138688 0 iosf_mbi 16384 1 i915 drm_kms_helper 122880 1 i915 drm 294912 2 i915,drm_kms_helper intel_gtt 20480 1 i915 i2c_algo_bit 16384 2 igb,i915 i2c_core 36864 6 i2c_algo_bit,igb,i2c_i801,i915,drm_kms_helper,drm video 36864 1 i915 backlight 16384 2 video,i915 button 16384 1 i915 root@HAL9000:/ramdisk# Syscfg label unRAID OS GUI Mode menu default kernel /bzimage append pcie_acs_override=downstream initrd=/bzroot,/bzroot-gui i915.alpha_support=1 NVM got it working, needed to adjust my go file to include modprobe i915 chown -R nobody:users /dev/dri chmod -R 777 /dev/dri #copy docker-shell script cp /boot/custom/docker-shell /usr/local/bin #make 8gb ramdisk mkdir /ramdisk mount -t tmpfs -o size=8192m tmpfs /ramdisk # Start the Management Utility /usr/local/sbin/emhttp &
  2. dang this sucks @limetech ?
  3. thanx pwm ill do that. The original email link is no longer valid sooo i guess ill have to wait for the email.
  4. Mistakenly formatted my usb drive, whats the best way to go about getting a new / the same key i had sent to me again? https://lime-technology.com/replace-key/ This doesnt work in 6.5.0
  5. I am using two new seagate 8tb (ST8000DM004) drives both less than 30 days old ( horrible drives btw ). I woke up this morning with errors on the parity disks (around 5k of them). And smart errors on both drives. Do you guys think this is a drive issue or some other type of issue. I think its werid BOTH drive would start failing at the SAME time so early. From syslog ST8000DM004-2CX188_WCT09B3G-20180321-0856.txt ST8000DM004-2CX188_WCT09B3G-20180321-0859.txt syslog.1.txt
  6. I was able to get it to work using this method.
  7. Since doing this i keep getting: errors about low disk space unable to convert. I have 32 gb of ram and htop reports 22 gb in use. However when i look at my logs i see: Mar 17, 2018 16:50:33.422 [0x14c7793fd700] WARN - Low disk space: 176.4MB source file, 15.64GB capacity, 252.42MB available on "/transcode/Transcode/Sessions" Which makes ZERO sense. anyone have any tips or ideas? EDIT: I guess this no longer works without doing manual changes to the docker which will be wiped with each update.
  8. u-nas 810A is the upgraded version, i highly recommend getting it over the 800
  9. not sure i haven't tried sorry. I know it works well for plex using intel quicksync
  10. aforementioned script cd /mnt/user/dockers/plex/ nano epgscript.sh wget http://vaders.tv/p2.xml.gz gzip -d p2.xml.gz mv p2.xml /mnt/user/dockers/plex/ CTL + x chmod a+x epgscript.sh chmod 777 epgscript.sh crontab -e 00 00 * * * /mnt/user/dockers/plex/epgscript.sh
  11. can we get a simple script to feed the EPG? IE in the telly docker add 2 more paths, One for the IPTV EPG download and the other for the .xml location. So telly would pull the EPG.gz and extract the xml on the server to a mapped path that plex can see? This would save me from having to do cron jobs.....
  12. thanx frank!! Piece of mind is a beautiful thing =)
  13. thanx @johnnie.black your so helpful to the community, do you have a donate button / coffee fund? I seem to always get good replies / advise from you.
  14. Smart reports ST8000DM004-2CX188_WCT09B3G-20180228-1207.txt ST8000DM004-2CX188_ZCT032BP-20180228-1206.txt
  15. https://superuser.com/questions/393257/brand-new-seagate-hdd-has-high-raw-read-error-rate Would lead me to belive this is normal / fine....
  16. Both of these drives are brand new yet have huge numbers for raw read error rate???? Is this normal / a by product of adding a new drive? I find it unlikely that both drives are bad (2 days old)
  17. There are errors on Disk 6 so ill do the parity swap procedure. Thanx for the suggestions guys. Can i do both Parity disks at the same time? Or do i need to do ONE, then swap the other? IE: Stop the array (if it's started) Unassign the old drive (if it's still assigned) If the drive was a good drive and notifications are enabled, you will get error notifications for a missing drive! This is normal. Start the array (put a check in the Yes I want to do this checkbox if it appears (older versions: Yes, I'm sure)) Yes, you need to do this. Your data drive should be showing as Not installed. Stop the array again Power down [ Optional ] Pull the old drive You may want to leave it installed, for Preclearing or testing or reassignment. Install the new drive Power on Unassign the parity drive (BOTH!??) Assign the new drive in the parity slot (BOTH!??) You may see more error notifications! This is normal. Assign the old parity drive in the slot of the old data drive being replaced You should now have blue drive status indicators for both the parity drive and the drive being replaced. ASSIGN THE OTHER (OLD) PARITY DRIVE AS ADDITIONAL STORAGE?? Go to the Main -> Array Operation section You should now have a Copy button, with a statement indicating "Copy will copy the parity information to the new parity disk". Put a check in the Yes I want to do this checkbox (older versions: Yes, I'm sure), and click the Copy button Now patiently watch the copy progress, takes a long time. All of the contents of the old parity drive are being copied onto the new drive, then the remainder of the new parity drive will be zeroed. The array will NOT be available during this operation! When the copy completes, the array will still be stopped ("Stopped. Upgrading disk/swapping parity."). The Start button will now be present, and the description will now indicate that it is ready to start a Data-Rebuild. Put a check in the Yes I want to do this checkbox (older versions: Yes, I'm sure), and click the Start button The data drive rebuild begins. Parity is now valid, and the array is started. Because the array is started, you can use the array as normal, but for best performance, we recommend you limit your usage. Once again, you can patiently watch the progress, takes a long time too! All of the contents of the old data drive are now being reconstructed on what used to be your parity drive, but is now assigned as the replacement data drive. https://lime-technology.com/wiki/The_parity_swap_procedure
  18. So i have a 3 TB drive dying: 187 Reported uncorrect 0x0032 098 098 000 Old age Always Never 2 197 Current pending sector 0x0012 100 099 000 Old age Always Never 136 198 Offline uncorrectable 0x0010 100 099 000 Old age Offline Never 136 My current server has two 3 TB Parity drives, however due to price point and the ability to upgrade later i bought two 8 TB drives to fix the problem. My logic is to take one of the 8 TB drives and replace one of the good 3 TB parity drives. RESYNC. Then take the pulled 3TB old parity drive and replace the failing 3 TB drive and RESYNC. Finally take the last 3 TB pairty drive and replace it with the other 8 TB Drive. and RESYNC. Is this the best method / way to do this??? This is going to take 3-5 days due to the multiple re-builds. OR Would it be better to just go down to 1 pairty drive and use the other to replace the failing drive, once rebuilt, replace the remaining parity disk with both 8 TB drives?
  19. 90% 95? 98? 10 GB = 20GB 300 GB??
  20. I counted it (25 posts per page) and quoted above. its the post about disabling Privoxy. Which in my case didnt help.
  21. CP RunCMD root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='couchpotato' --net='bridge' --privileged=true -e TZ="America/Chicago" -e HOST_OS="unRAID" -e 'PUID'='99' -e 'PGID'='100' -p '5050:5050/tcp' -v '/mnt/user/Downloading/':'/downloads':'rw' -v '/mnt/user/Data/Movies/':'/movies':'rw' -v '/mnt/user':'/unraid':'rw' -v '/mnt/user/Downloading/':'/data':'rw' -v '/mnt/user/dockers/couchpotato':'/config':'rw' 'linuxserver/couchpotato' 05b44fde914c33cebbe1eff70677b2c58386c7f32aa8ab364756001901f676f3 The command finished successfully! root@05b44fde914c:/app/couchpotato$ ifconfig eth0 Link encap:Ethernet HWaddr 02:42:AC:11:00:07 inet addr:172.17.0.7 Bcast:0.0.0.0 Mask:255.255.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:434 errors:0 dropped:0 overruns:0 frame:0 TX packets:270 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:215147 (210.1 KiB) TX bytes:279251 (272.7 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
  22. Deluge runcmd root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-delugevpn' --net='bridge' --privileged=true -e TZ="America/Chicago" -e HOST_OS="unRAID" -e 'VPN_ENABLED'='yes' -e 'VPN_USER'='xxxxxxx' -e 'VPN_PASS'='xxxxxxx' -e 'VPN_PROV'='pia' -e 'VPN_OPTIONS'='' -e 'STRICT_PORT_FORWARD'='yes' -e 'ENABLE_PRIVOXY'='no' -e 'LAN_NETWORK'='192.168.2.0/24' -e 'NAME_SERVERS'='209.222.18.222,37.235.1.174,8.8.8.8,209.222.18.218,37.235.1.177,8.8.4.4' -e 'DEBUG'='false' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -p '8112:8112/tcp' -p '58846:58846/tcp' -p '58946:58946/tcp' -p '58946:58946/udp' -p '8118:8118/tcp' -v '/mnt/user/Downloading/':'/data':'rw' -v '/mnt/user':'/unraid':'rw' -v '/mnt/user/dockers/binhex-delugevpn':'/config':'rw' 'binhex/arch-delugevpn' 010f00bbe6c6457c923364c484eec4415354336df6a4ff92e7915728c11de25b AND IFCONFIG [root@010f00bbe6c6 /]# ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 172.17.0.8 netmask 255.255.0.0 broadcast 0.0.0.0 ether 02:42:ac:11:00:08 txqueuelen 0 (Ethernet) RX packets 1487 bytes 1099117 (1.0 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1019 bytes 541224 (528.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 loop txqueuelen 1000 (Local Loopback) RX packets 639 bytes 167655 (163.7 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 639 bytes 167655 (163.7 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 tun0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet xx.x.xx.xx netmask 255.255.255.255 destination xx.x.xx.x unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 100 (UNSPEC) RX packets 32 bytes 3050 (2.9 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 237 bytes 34661 (33.8 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0