rjorgenson

This is not feasible for me, and my HBA has previously supported TRIM prior to 6.4.0 with no issues. *edit* my HBA is a LSI 9207-8i

Since upgrading to 6.4.0 a couple days ago my trim job has failed every day with fstrim: /mnt/cache: FITRIM ioctl failed: Remote I/O error Did something change in the update? Plugin version is 2017.04.23a and has been since before the update. I received this error previously with the SSD's in my cache pool because my HBA didn't support some flag, I replaced the HBA with a newer version and TRIM worked just fine until I updated it. If it's relevant I haven't rebooted it since I installed the HBA until the update was installed.

For what it's worth, I just updated Fix Common Problems which caused it to re-run the scan and it did not find this issue again. Confirmed on the command line I was now able to ping github from this system. I'm not sure what changed.

At what point are you seeing this? Only at the initial array start or on all subsequent scans? I had some time and dug into this a little more. I saw in the code that it's running a ping check against github.com which is indeed failing from my unRAID machine. It does not fail from other systems on my network though and my unRAID box is still able to connect to github.com, just not over ICMP. root@mnemos:~/usr/local/emhttp/plugins/fix.common.problems# ping -c 2 github.com PING github.com (18.194.104.89) 56(84) bytes of data. --- github.com ping statistics --- 2 packets transmitted, 0 received, 100% packet loss, time 1005ms root@mnemos:~/usr/local/emhttp/plugins/fix.common.problems# telnet github.com 80 Trying 18.194.104.89... Connected to github.com. Escape character is '^]'. ^] telnet> quit Connection closed. root@mnemos:~/usr/local/emhttp/plugins/fix.common.problems# I don't see anything in iptables that would be blocking this(though I'm not the best with iptables so I could be missing something), and I am able to ping other public sites such as google and yahoo from the unraid host.

At what point are you seeing this? Only at the initial array start or on all subsequent scans? I continue to see the error if I rescan. I also haven't restarted my array since before this started. It showed up on my weekly scan on Sunday morning(~22 hours ago), and was not present the week before.

I'm seeing this same behavior. Fix Common Problems reports it's unable to communicate with github.com but all internet connectivity, including to github.com works from the host.

I already deleted the container from atribe, but it was all default settings with the exception of the password after switching over to your container. You're right though the only reference I could find to "node-jessie" was the documentation on this github page - https://github.com/hexparrot/mineos-docker - but I couldn't find anything indicating this repo was actually used for the builds. The dockerhub page indicates this repo - https://github.com/hexparrot/mineos-node - is the source repo. It does appear the docker file was migrated to there not too long ago though, and the build history of the docker hub page only shows builds going back that far. It seems atribe's config was for a previous build setup of mineos-node.

I'm currently using hexparrot's image from atribe's repository and the mineos-node build inside of it shows the latest commit version it is on as May 30th. It also has some weird update issues. Before today it said "not available" under updates. And today it says update ready but continues to say that even after updating the container in the UI. Same result of commit as well. I installed your version and did get the latest version of mineos-node, I originally went with hexparrots because I didn't need the dynmap stuff, but i'd much rather get software updates as well =] I have a thread open in atribe's thread regarding his container as well. Thanks.

Hi, I have a question about your mineos node container. I installed and noticed the version of mineos is quite old, form May 30th. Is there a way to update the version of mineos in the container? unRAID also seems to think there is an update for it, but it says "not available" on the docker page under version.

Is this still the case? I just installed the hexparrot container and the mineos node build was from May 30th. It also lists "not available" under updates for the container.

Thanks for the advice guys. If I did go with intel are there any chip sets I should avoid and/or look for when picking a motherboard? As far as drives I'll be getting two 3TB drives initially and once all the data is copied over from my Drobo i'll be throwing the 3 2TB drives that are in there into my unRAID system. For the power supply I used the calculator here - http://extreme.outervision.com/PSUEngine configued with a phenom processor, a 4x PCIe card, and 10 sata drives for future expansion, plus fans and it came out to 300 watts. The intel chip is even lower. Will a 430 watt power supply not be enough?

Hey everyone. So I'm working on replacing my Drobo FS with an unRAID server and have been working on a build. Here is what I have so far ... Motherboard - ASUS M5A88-M - $99.99 CPU - ?? - ?? Memory - Kingston ValueRam ECC 2x2GB 1333MHz - $19.74 x2 Power Supply - Corsair Builder Series CX V2 430 - $43.99 Chassis - Nexus Prominent 9 - $84.95 I'm not really tied to anything in particular but I like the 6 onboard sata 3 ports on the motherboard and the expand ability of the case with drive cages. I'd prefer a modular power supply but I'd like to keep the costs at a level I could recoup by selling the Drobo FS once all the data is copied over. As far as uses go the server will be used primarily as media storage and media server via plex(unlikely to have more than two clients streaming simultaneously) as well as time machine backups. Anyone have any sage advice to impart(specifically with CPU selection)? Most of the CPU's that I can find are either too low powered for transcoding or their power rating would require upgrading the power supply. Any and all help is appreciated! Thanks =D