betgear

Hi, Are there likely to be any issues running unraid on the new Z270 chipsets and Kobi lake processors? Cheers

Hi Jonathan, Thanks for the advice, I will give this a try and post back if I have any issues. Cheers Glen.

Hi, My Unraid 6 USB drive died, and I have no backup of the information on the drive (lesson learnt). I've downloaded a new version of unraid 6.2 onto a new USB stick and activated the trial key whilst I get my original key transferred over. I had 1 cache drive and 1 parity drive in the array prior to the usb stick dying. When starting the new array, if knows nothing of my previous setup and all drive are unassigned. How can I find my original cache and parity drives when setting up the new details? My parity and cache drives are both 4 TB, along with a number of other drives, so I can't simply look by drive size to allocate drives. I cannot see of way of browsing drives in the unraid setup to work out which drive is which. Any help most appreciated. Glen.

Hi, Thanks for the reply. Next noob question, how do I delete the orphaned container? Ideally I want to start afresh with docker, as there seems to be ALOT of subvolume information in the /mnt/btrfs/docker/btrfs directory. A clean start would be ideal, if possible. Cheers Glen.

Pulling image: linuxserver/deluge:latest IMAGE ID [latest]: Pulling from linuxserver/deluge. IMAGE ID [428b411c28f0]: Already exists. IMAGE ID [435050075b3f]: Already exists. IMAGE ID [9fd3c8c9af32]: Already exists. IMAGE ID [6d4946999d4f]: Already exists. IMAGE ID [f6e250afd5cc]: Already exists. IMAGE ID [80c1ef08f5e9]: Already exists. IMAGE ID [29ae179a0774]: Already exists. IMAGE ID [fdcdf46f55d4]: Already exists. IMAGE ID [9b883c576b37]: Already exists. IMAGE ID [e244385f01e3]: Already exists. IMAGE ID [024d35e3b959]: Already exists. IMAGE ID [414001b6cfcc]: Already exists. IMAGE ID [5b552f5cca8b]: Already exists. IMAGE ID [6b4caa3410d8]: Already exists. IMAGE ID [cf11287b3aae]: Already exists. IMAGE ID [a05773c3f782]: Already exists. IMAGE ID [a902b9f2a0ce]: Already exists. IMAGE ID [efcab156a748]: Already exists. IMAGE ID [4aa540e25d37]: Already exists. IMAGE ID [c851d1f7218b]: Already exists. IMAGE ID [5ac4b0f595fc]: Already exists. Pulling repository linuxserver/deluge. Pulling image (latest) from linuxserver/deluge. Pulling image (latest) from linuxserver/deluge, endpoint: https://registry-1.docker.io/v1/. Pulling dependent layers. IMAGE ID [428b411c28f0]: Download complete. IMAGE ID [435050075b3f]: Download complete. IMAGE ID [9fd3c8c9af32]: Download complete. IMAGE ID [6d4946999d4f]: Download complete. IMAGE ID [f6e250afd5cc]: Download complete. IMAGE ID [80c1ef08f5e9]: Download complete. IMAGE ID [29ae179a0774]: Download complete. IMAGE ID [fdcdf46f55d4]: Download complete. IMAGE ID [9b883c576b37]: Download complete. IMAGE ID [e244385f01e3]: Download complete. IMAGE ID [024d35e3b959]: Download complete. IMAGE ID [414001b6cfcc]: Download complete. IMAGE ID [5b552f5cca8b]: Download complete. IMAGE ID [6b4caa3410d8]: Download complete. IMAGE ID [cf11287b3aae]: Download complete. IMAGE ID [a05773c3f782]: Download complete. IMAGE ID [a902b9f2a0ce]: Download complete. IMAGE ID [efcab156a748]: Download complete. IMAGE ID [4aa540e25d37]: Download complete. IMAGE ID [c851d1f7218b]: Download complete. IMAGE ID [5ac4b0f595fc]: Download complete. TOTAL DATA PULLED: 0 B Command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="deluge" --net="host" -e PUID="99" -e PGID="100" -e TZ="Europe/London" -v "/mnt/user/appdata/deluge/":"/config":rw -v "/mnt/cache/Downloads":"/downloads":rw linuxserver/deluge Error response from daemon: EOF The command failed. Does anyone have any idea why I cannot reinstall deluge. I did have it set up and working, stopped the docker, and was unable to restart (shows as orphaned). When I try and reinstall, I get the above error. Any help most appreciated. Glen.

Hi, I've just installed Deluge and would like a way to stay anonymous on the net when it's connected. I have a VPN account, but Deluge doesn't deal with connecting direct to a VPN. A docker that has a proxy server to VPN connection would be ideal for this, as I don't want all my traffic going over VPN, I can then decide (via proxy settings) which traffic will travel through the vpn, and which wont. Something along these lines, but utilizing a docker instead of a VM. http://blog.sdbarker.com/installing-squid-sick-beard-deluge-and-an-always-on-vpn-ipvanish-on-archlinux-for-an-automated-seed-box/ Cheers Glen.

Thanks for that, hadn't spotted the 'only' option in use cache disk. Cheers Glen.

Hi, I'm a little confused with some of the setup procedure, I've searched through the forum and whilst I've gained quite a bit of knowledge, the answers to these simple questions seem to elude me (cant see the wood for the tree, so to speak). 1) I'm going to set up docker on my btrfs formatted cache drive, looking at midnight commander, I can see 2 separate drives one labelled cache, and another labelled btrfs, is this correct? 2) The default install for docker appears to be to mnt/cache/docker, will this not get moved by the mover script when it routinely runs? If so, how do I prevent it being moved? 3) I see mention of an appdata directory which is a cache only user share, how can I create this, and ensure it does not get moved by the mover script? Thanks for any help. Cheers Glen.

A system log is required in order to determine why the drive is not being recognised. http://lime-technology.com/forum/index.php?topic=9880.0 Glen.

Ok, installed 5 beta 14 and the disk is now in the array and parity is rebuilding. Cheers Glen.

After further research is would appear as though 4.7 does not support drives > 2.2TB I will bite the bullet and install the latest 5 beta 14 and see if this fixes the issue. Cheers Glen.

Hi I'm running unraid 4.7 and have attempted to replace my 2TB parity drive with a Seagate 3TB drive, but am having issues with unraid recognising the drive. I precleared the drive using the -A option, and my settings are set to 4k aligned (this will be the 1st > 2TB drive in the array). The drive appears in the list of unassigned drives, and I can use the drop down to assign it as parity. However on the main tab, parity drive is shown as missing. On checking the system log I see the following error Feb 6 09:33:21 Tower kernel: md: import disk0: BLKGETSIZE ioctl error: -27 (Errors) Feb 6 09:33:21 Tower kernel: md: disk0 removed (unRAID engine) Which I presume is why the drive is not showing as parity. I've checked the drive with preclear -t and get the following Pre-Clear unRAID Disk /dev/sdj ################################################################## 1.13 Device Model: ST33000651AS Serial Number: Z2911N9K Firmware Version: CC45 User Capacity: 3,000,592,982,016 bytes Disk /dev/sdj: 3000.5 GB, 3000592982016 bytes 255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdj1 1 4294967295 2147483647+ 0 Empty Partition 1 does not end on cylinder boundary. ######################################################################## ========================================================================1.13 == == DISK /dev/sdj IS PRECLEARED with a GPT Protective MBR == ============================================================================ Could anyone shed any light on why this is happening, and what I can do to get the drive working as parity. Appreciate the assistance. Glen.

I've sent it off to their bugs email address, so fingers crossed on a fast fix Glen.

Here is the zipped NZB, in case it's useful. The error was from giganews, if may be complete on other servers. I had a look through the log file, and it would appear as though par2 is being used for verifying, but I don't see the actual call to do the repair. Glen. #a.b.mm@efnet_-_req_59336_-_Cold.Case.S06E02.720p.HDTV.x264-CTU_-_ctu-x264-cold.case.zip

The files repaired correctly by opening a telnet session, and typing par2 r ctu-....vol00+1.par2 par2cmdline version 0.4, Copyright © 2003 Peter Brian Clements. Modifications for concurrent processing, Unicode support, and hierarchial directory support are Copyright © 2007-2008 Vincent Tan. Concurrent processing utilises Intel Thread Building Blocks 2.0, Copyright © 2007-2008 Intel Corp. Executing using the 32-bit x86 (IA32) instruction set. par2cmdline comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. See COPYING for details. Processing verifications and repairs concurrently. Loading "ctu-x264-cold.case.602.vol00+1.par2". Loaded 51 new packets including 1 recovery blocks Loading "ctu-x264-cold.case.602.vol01+2.par2". Loading "ctu-x264-cold.case.602.vol15+3.par2". Loaded 2 new packets including 2 recovery blocks Loaded 3 new packets including 3 recovery blocks There are 24 recoverable files and 0 other files. The block size used was 3456000 bytes. There are a total of 352 data blocks. The total size of the data files is 1173335766 bytes. Verifying source files: Target: "ctu-x264-cold.case.602.r00" - found. Target: "ctu-x264-cold.case.602.r03" - found. Target: "ctu-x264-cold.case.602.r01" - damaged. Found 14 of 15 data blocks. Target: "ctu-x264-cold.case.602.r02" - damaged. Found 14 of 15 data blocks. Target: "ctu-x264-cold.case.602.r04" - found. Target: "ctu-x264-cold.case.602.r05" - found. Target: "ctu-x264-cold.case.602.r06" - found. Target: "ctu-x264-cold.case.602.r07" - found. Target: "ctu-x264-cold.case.602.r08" - found. Target: "ctu-x264-cold.case.602.r09" - found. Target: "ctu-x264-cold.case.602.r10" - found. Target: "ctu-x264-cold.case.602.r11" - found. Target: "ctu-x264-cold.case.602.r12" - found. Target: "ctu-x264-cold.case.602.r13" - found. Target: "ctu-x264-cold.case.602.r14" - found. Target: "ctu-x264-cold.case.602.r15" - found. Target: "ctu-x264-cold.case.602.r16" - found. Target: "ctu-x264-cold.case.602.r17" - found. Target: "ctu-x264-cold.case.602.r19" - found. Target: "ctu-x264-cold.case.602.r18" - found. Target: "ctu-x264-cold.case.602.r20" - found. Target: "ctu-x264-cold.case.602.r21" - found. Target: "ctu-x264-cold.case.602.r22" - found. Target: "ctu-x264-cold.case.602.rar" - found. Scanning extra files: Repair is required. 2 file(s) exist but are damaged. 22 file(s) are ok. You have 350 out of 352 data blocks available. You have 6 recovery blocks available. Repair is possible. You have an excess of 4 recovery blocks. 2 recovery blocks will be used to repair. Computing Reed Solomon matrix. Constructing: done. Solving: done. Wrote 100000000 bytes to disk Verifying repaired files: Target: "ctu-x264-cold.case.602.r01" - found. Target: "ctu-x264-cold.case.602.r02" - found. Repair complete.