martinf

Only installation (running latest, 6.11.1 of unraid) my docker with iproute2 does not work with 22.8.16. On my installation, it eats up my ram quite quickly and does not start up in a usable way. Cheers Martin

Finally got it working. Going back to 22.3.16 To sum it up. Install the missing ip command we see in the log. start Xeoma and "quickly" click the icon and select $_ console run the commands apt update apt install iproute2 stop the Xeoma docker container Download Linux 64bit version from https://felenasoft.com/xeoma/en/changes/ (scroll down a bit) Put it in your config folder, for me it is /mnt/user/appdata/Xeoma Rename the file to xeoma_22.3.16.tgz Put it in /mnt/user/appdata/Xeoma/downloads/ I also unpacked it via a shell by going to the downloads folder and running the command tar zxvf xeoma_22.3.16.tgz then I went back to /mnt/user/appdata/Xeoma changed the config file as below # The password for clients to use to connect. Avoid backslashes and apostrophes. PASSWORD='xxxxxxxxx' # The version to use. Valid values are a string like '17.5.5', 'latest', 'latest_beta', or a URL. VERSION='22.3.16' Started Xeoma in the Unraid docker tab. I'm back up and running. With the missing ip command, it may work with the latest but right now, I just want to be up and running again.

I finally got it working on my setup. You have to upgrade with a Plex pass. Hardware decoding is now a "paid" feature. /Martin

I know this is an old thread. However, thought it would be usefull for for others coming across this. When you have working with multiple networks on a server (any computer), you have to think about routing. There is no guarantee that the return traffic is going back on the same interface as the request arrives on. Traffic may arrive on nic1 but return traffic may go back via nic2. On linux, you can control this in detail by createing unique routing tables per nic etc. You will however get a very complicated network setup.... if you have multiple networks, you can use specific routing where network a, b, and c are using nic1 (with routing entries in unraid) and network d, e, and f are using nic2 (with rouging for that in unraid). However, I would strongly suggest, using LACP and bond your network cards to that (must be same speed). (sure, you may have to buy a managed switch for a couple o hundred dollars, but worth every penny) If need to, configure QOS on your switch. Sending data to Unraid, while streaming, should not be a problem as you are looking at dataflows in two different directions. Make sure you have a cache drive that is minimum twise the speed of your network, and configure yours shares to use the cache drive to write new content. (I.e. you stream from your hdd, write new content to cache) Rule nr 1. Keep it simple! Rule nr 2. Simplify, i possible. Rule nr 3. Go to 1. /Martin

It fixed itself after my post. In my testings I also installed Firefox as a docker app. It had good speed, along with some other apps. One docker app have manage to get speeds over 800Mbit. Currently, my unraid "speedtest" never go above 650. Putting that down to the speedtest app and the remote end. I never got to the stage where I uninstalled and reinstalled the speedtest software. At the same time (as I found out after my initial post), I had the "same" problem with the speed test checking from my firewall. I _think_ the problem was on my ISP side... Possible filtering something to keep the bandwidth down. /M

If you need more SATA ports, I recommend you go for a SAS card and break out cables (sas -> 4 SATA connectors). Ideally two SAS ports giving you up to 8 SATA devices. However, this allows you in the future to use the card for SAS back planes. There are plenty of Dell (LSI) cards out there for not much money. I picked up mine on EBay for about $40 with 2 break out cables. I use to have PCIe SATA card (4 ports) but occationally, they generated CRC errors with fast disks (SSD). My $0.02... Martin

I'm using (recently built it) the X470D4U with a Ryzen 5 3600 (gen 3) and 16GB ECC Ram. You don't need a keyboard and mouse for the Mobo. You can use the IPMI to manage the server from another computer. I.e. IPMI allow you to manage the server such as power off/on, patch firmware, remote console etc. Apart from the two USB3 in the back, there is one socket for another two USB3 ports. I installed a two port USB3 adapter directly on the mobo so my USB Unraid device id "directly" on the mobo. Apart from the IPMI port, there are two more ethernet ports that I have in active/active mode to improve the network throughput. Yet to play with the different options for optimum performance. Connected to a Unifi switch so it can in theory do all the different modes. The M.2 seem a bit sad. Was looking at using them for NVMe cache. But I can not find any NVMe SSD to match the "specs". Have any of you found workable SSD for the M.2? If so, what are you using and what read/write speed to you get? Cheers Martin

Think I have a corrypt ram slott. Used 3 sticks. Removed one and are now waiting to see. Will get a new computer when shops are open again. Cheers

Thanks johnnie.black I start to pull out some of the ram then. And buy a new server when New Zealand are back in business... Cheers Martin

Why is this happening? 1 to 4 times per month, I have this problem. Getting sick of it. Any way to use xfs rather than btrfs? Have had the same problem with two different ssd, 3 different controllers.... /Martin

I'm on 6.8.3 and have the same problem with btrfs. Docker immage gets corrupted. BTRFS gets corrupted and I have to wipe and rebuild Docker. (Thankfully, I found the template function so reinstalling is quick.) I have tried 3 different controllers (Motherboard SATA, SATA controller and a Dell LSI SAS/SATA controller). I have tried 3 different SSD. In Mirror, Single, with and without Encryption. Does not matter. After a couple of weeks or so, it gets corrupted, SSD (BTRFS) read only. Last time, I tried mount in main mode. Was able to run fs-check on the disk with the recover/fix option. Then remount disks and scrub it. Now it is working again. Dont really care about the corruption part, I can always rebuild. However, why is it happening in the first hand? Ram, motherboard issue? Cheers Martin

Yay. something changed updated. Now I'm getting 2020-03-27 10:13 FriTrustpower Ltd (Tauranga)224.58 km17.171 ms Down 616.95 Mbit/s Upp 103.89 Mbit/s

I have an even more strange issue. My docker images have good internet speed. Sometimes, I've been testing 800mbit download and same up. I have a 1/1gig internet connection. Best ever speed has been 950mbit. However, unraid itself has some issues. I can pull down ubuntu iso files fine from Wellington, New Zealand in a few hundred mbit speed. I installed the speedtest app and it use to show mid 700 mbit speeds. However, a few days ago, I constantly getting # speedtest --server 4954 Retrieving speedtest.net configuration... Testing from Vodafone New Zealand (n.n.n.n)... Retrieving speedtest.net server list... Retrieving information for the selected server... Hosted by Vodafone New Zealand (Wellington) [254.27 km]: 3069.999 ms Testing download speed................................................................................ Download: 3.35 Mbit/s Testing upload speed................................................................................................ Upload: 3.34 Mbit/s I'm on the latest unraid immage. Strange. As all other computers, including docker images are testing with many hundreds of mbit download speeds, I suspect it may be something with unraid. Ps. I have installed the speedtest App for speed tests

I cant get past it. dont know what the password is for that checksum so I generated my own and still not able to get past.

I followed the guide. Installed Boinc, signed up at Rosetta, joined the unraid team. However, all I have is _Console... Any thoughts, suggestions? Cheers Martin

I'm currently trying to add it manually via cli. docker network create -d macvlan --subnet=192.168.15.0/24 --gateway=192.168.15.1 -o parent=br0.15 CCTV Any better ways? Cheers

Greetings I'm working on setting up some ip cameras and shinobi_pro after looing at the excellent videos from spaceinvader one. First, the vlans would not stick but after turning off vlans and then enable vlans and create the first vlan at the same time, I got the vlans to stick and work. I now have the vlans I need and I can also see them in cli "ip addr" show them as br0.[nr]. In docker, I have pulled down shinobi_pro and I can only choose between [bridge, host, none, custom:br0] None of the vlans is shown in the list. The same if I change to advanced mode. Any suggestions what I'm doing wrong? Thankfull for any hints. Cheers

By far the most simple NAS solutions to deploy, with the added bonus of mixing disk size and no requirement of ECC ram. Would love to see built in backup features (plug in external drive and copy shares a d or folders in shares to it). Can do via cli but woul be nice via Gui. Well done team!

Different port on expansion card. Will move to a motherboard port.

Over Xmas, I built a new server. Cache is based on two ssd. SSD have given me problems since start. Smart indicated cable and or controller problem so I replaced data cable and changed sata port. Since then, it has not fallen off / disappeared, require reboot. Yet, I see errors in the log. Some info from syslog below. Thoughts, comments? Cheers Martin Jan 2 06:28:25 Tower kernel: ata8.00: cmd e7/00:00:00:00:00/00:00:00:00:00/a0 tag 12 Jan 2 06:28:25 Tower kernel: res 51/04:00:00:00:00/00:00:00:00:00/00 Emask 0x1 (device error) Jan 2 06:28:25 Tower kernel: ata8.00: status: { DRDY ERR } Jan 2 06:28:25 Tower kernel: ata8.00: error: { ABRT } Jan 2 06:28:25 Tower kernel: ata8.00: configured for UDMA/133 Jan 2 06:28:25 Tower kernel: ata8.00: device reported invalid CHS sector 0 Jan 2 06:28:25 Tower kernel: sd 8:0:0:0: [sdf] tag#12 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Jan 2 06:28:25 Tower kernel: sd 8:0:0:0: [sdf] tag#12 Sense Key : 0x5 [current] Jan 2 06:28:25 Tower kernel: sd 8:0:0:0: [sdf] tag#12 ASC=0x21 ASCQ=0x4 Jan 2 06:28:25 Tower kernel: sd 8:0:0:0: [sdf] tag#12 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00 Jan 2 06:28:25 Tower kernel: print_req_error: I/O error, dev sdf, sector 0 Jan 2 06:28:25 Tower kernel: ata8: EH complete Jan 2 06:53:39 Tower root: Fix Common Problems Version 2019.12.29 Jan 2 06:53:44 Tower root: Fix Common Problems Version 2019.12.29 Jan 2 06:53:47 Tower root: Fix Common Problems: Other Warning: Unassigned Devices Plus installed ** Ignored Jan 2 06:53:52 Tower root: Fix Common Problems: Other Warning: Unassigned Devices Plus installed ** Ignored Jan 2 07:32:27 Tower kernel: md: sync done. time=27146sec Jan 2 07:32:27 Tower kernel: md: recovery thread: exit status: 0 Jan 2 07:47:28 Tower kernel: mdcmd (54): spindown 0 Jan 2 07:47:29 Tower kernel: mdcmd (55): spindown 1 Jan 2 08:29:47 Tower kernel: mdcmd (56): spindown 0 Jan 2 08:29:47 Tower kernel: mdcmd (57): spindown 1 Jan 2 09:50:16 Tower kernel: usb 4-1: USB disconnect, device number 3 Jan 2 10:02:04 Tower kernel: mdcmd (58): spindown 0 Jan 2 10:10:12 Tower kernel: mdcmd (59): spindown 1 Jan 2 10:23:26 Tower kernel: btrfs_print_data_csum_error: 1071 callbacks suppressed Jan 2 10:23:26 Tower kernel: BTRFS warning (device dm-1): csum failed root 5 ino 24691 off 7954432 csum 0xcfa10387 expected csum 0xe6b460b2 mirror 1 Jan 2 10:23:26 Tower kernel: BTRFS warning (device dm-1): csum failed root 5 ino 24691 off 7946240 csum 0x98cedc4c expected csum 0xcef63324 mirror 1 Jan 2 10:23:26 Tower kernel: BTRFS warning (device dm-1): csum failed root 5 ino 24691 off 7974912 csum 0x99ae0a4a expected csum 0xd39032bb mirror 1 Jan 2 10:23:26 Tower kernel: BTRFS warning (device dm-1): csum failed root 5 ino 24691 off 7999488 csum 0x2f10fcd8 expected csum 0x269a3145 mirror 1 Jan 2 10:23:26 Tower kernel: BTRFS warning (device dm-1): csum failed root 5 ino 24691 off 7987200 csum 0xae91e6ab expected csum 0xcb613bf9 mirror 1 Jan 2 10:23:26 Tower kernel: BTRFS warning (device dm-1): csum failed root 5 ino 24691 off 7983104 csum 0x68af43b8 expected csum 0xb07935f4 mirror 1 Jan 2 10:23:26 Tower kernel: BTRFS warning (device dm-1): csum failed root 5 ino 24691 off 7933952 csum 0x610e459b expected csum 0x26a6cb07 mirror 1 Jan 2 10:23:26 Tower kernel: BTRFS warning (device dm-1): csum failed root 5 ino 24691 off 7950336 csum 0x6b4f16fc expected csum 0x60526509 mirror 1 Jan 2 10:23:26 Tower kernel: BTRFS warning (device dm-1): csum failed root 5 ino 24691 off 7995392 csum 0xa9138887 expected csum 0xba2194d2 mirror 1 Jan 2 10:23:26 Tower kernel: BTRFS warning (device dm-1): csum failed root 5 ino 24691 off 7979008 csum 0x5edf42d6 expected csum 0xcdf3b158 mirror 1 Jan 2 10:23:26 Tower kernel: repair_io_failure: 524 callbacks suppressed Jan 2 10:23:26 Tower kernel: BTRFS info (device dm-1): read error corrected: ino 24691 off 7946240 (dev /dev/mapper/sde1 sector 87499880) Jan 2 10:23:26 Tower kernel: BTRFS info (device dm-1): read error corrected: ino 24691 off 7974912 (dev /dev/mapper/sde1 sector 87500040) Jan 2 10:23:26 Tower kernel: BTRFS info (device dm-1): read error corrected: ino 24691 off 7999488 (dev /dev/mapper/sde1 sector 87501016) Jan 2 10:23:26 Tower kernel: BTRFS info (device dm-1): read error corrected: ino 24691 off 7933952 (dev /dev/mapper/sde1 sector 87501608) Jan 2 10:23:26 Tower kernel: BTRFS info (device dm-1): read error corrected: ino 24691 off 7954432 (dev /dev/mapper/sde1 sector 87501648) Jan 2 10:23:26 Tower kernel: BTRFS info (device dm-1): read error corrected: ino 24691 off 7950336 (dev /dev/mapper/sde1 sector 87502064) Jan 2 10:23:26 Tower kernel: BTRFS info (device dm-1): read error corrected: ino 24691 off 7995392 (dev /dev/mapper/sde1 sector 87502280) Jan 2 10:23:26 Tower kernel: BTRFS info (device dm-1): read error corrected: ino 24691 off 7979008 (dev /dev/mapper/sde1 sector 87500968) Jan 2 10:23:26 Tower kernel: BTRFS info (device dm-1): read error corrected: ino 24691 off 7929856 (dev /dev/mapper/sde1 sector 87502128) Jan 2 10:23:26 Tower kernel: BTRFS info (device dm-1): read error corrected: ino 24691 off 7991296 (dev /dev/mapper/sde1 sector 87503968

Hi I'm new to unraid but have used linux for a long time. There is a tool called fdupes in linux. Not sure how hard it would be to add to unraid standard cmd commands. But for now, you could nfs mount a share to a unix/linux computer and run fdupes agains the nfs share. When / if fdupes can be included in unraid, you could run it agains /mnt/user/sharename and find duplicated per share or across all shares fdupes /mnt/user My $0.02 /Martin