pyrater

correct

this is post 154

that gives an instant connection failed whereas the "good ip" takes forever to not work lol

your signature is Sent from my LG-H815 using Tapatalk

how can i view the docker run command? I normally just let the webgui do it.

sadly that didnt fix it.

that was oddly specific lol thanx

is there a trick to get CP to work with Binhex-deluge ? It will not connect! It will however use backhole but then i lose automation... It doesnt connect and says check logs, which are empty... I have tried: localhost:8112 127.0.0.1:8112 192.168.2.4:8112

looks like it should work just fine =) however i would get this one: https://www.amazon.co.uk/Syba-Marvell-HyperDuo-Support-Brackets/dp/B00AZ9T264/ref=sr_1_fkmr0_1?s=computers&ie=UTF8&qid=1518881947&sr=1-1-fkmr0&keywords=SYBA+SI-PEX40057+PCI-Express+2.0+x2+Low+Profile+SATA+III+(6.0+Gb%2Fs)+4-port+RAID+Card As i know it works and used it in a friends build.

If you have PCIe slots, i would just use a cheap sata card like this: https://www.amazon.com/gp/product/B00AZ9T3OU/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1 (i use this one in my small server) Might need a riser cable if your server isnt 4U like: https://www.amazon.com/gp/product/B06W9HG8DB/ref=oh_aui_detailpage_o01_s01?ie=UTF8&psc=1

yea it triped a notification in unraid as i have it set to raw but not a stat error on the dashboard. Im gonna swap it with my external drive (shucked) that way if anything does go bad its not in my array.

I got a smart 187 today (never seen this one before). Its an old drive and i am running dual parity....... but should i go ahead and replace the drive? According to what i have found on the net this is a good indicator of a drive that will fail within the next 6ms. (https://www.backblaze.com/blog/hard-drive-smart-stats/) # Attribute Name Flag Value Worst Threshold Type Updated Failed Raw Value 1 Raw read error rate 0x000f 110 099 006 Pre-fail Always Never 152291873 3 Spin up time 0x0003 094 094 000 Pre-fail Always Never 0 4 Start stop count 0x0032 095 095 020 Old age Always Never 5717 5 Reallocated sector count 0x0033 100 100 010 Pre-fail Always Never 0 7 Seek error rate 0x000f 078 060 030 Pre-fail Always Never 77382975 9 Power on hours 0x0032 063 063 000 Old age Always Never 33040 (3y, 9m, 4d, 16h) 10 Spin retry count 0x0013 100 100 097 Pre-fail Always Never 0 12 Power cycle count 0x0032 100 100 020 Old age Always Never 192 183 Runtime bad block 0x0032 100 100 000 Old age Always Never 0 184 End-to-end error 0x0032 100 100 099 Old age Always Never 0 187 Reported uncorrect 0x0032 099 099 000 Old age Always Never 1 188 Command timeout 0x0032 100 100 000 Old age Always Never 0 0 0 189 High fly writes 0x003a 099 099 000 Old age Always Never 1 190 Airflow temperature cel 0x0022 068 051 045 Old age Always Never 32 (min/max 27/33) 191 G-sense error rate 0x0032 100 100 000 Old age Always Never 0 192 Power-off retract count 0x0032 100 100 000 Old age Always Never 115 193 Load cycle count 0x0032 001 001 000 Old age Always Never 253410 194 Temperature celsius 0x0022 032 049 000 Old age Always Never 32 (0 12 0 0 0) 197 Current pending sector 0x0012 100 100 000 Old age Always Never 0 198 Offline uncorrectable 0x0010 100 100 000 Old age Offline Never 0 199 UDMA CRC error count 0x003e 200 200 000 Old age Always Never 0 240 Head flying hours 0x0000 100 253 000 Old age Offline Never 10762h+34m+18.312s 241 Total lbas written 0x0000 100 253 000 Old age Offline Never 68795191328 242 Total lbas read 0x0000 100 253 000 Old age Offline Never 418855824077 Just dunno what to do with the pulled drive, maybe an external usb drive from all that shucking?

Advantage of gathering = Only one disk needs to be spun up as "older" data is on other drives that is not used that often. IE Old tv shows are on disk 1 but new tc shows are on disk 5. Disk 5 will be spun up almost all the time while disk 1 is never really used. Advantage of scattering = Increased throughput, 2 streams from different drives vs 2 streams from the same drive. Also since your drives are more balanced (less full) you will not have the speed of the drive fall off at the edge of the platter as much. (Think 50% full vs 90%) In the words of linkin park. In the end it doesnt really matter.

almost positive its because i moved the ssd to the sata cards which do not support SSD (oversight on my part).. Will update once confirmed UPDATED: this was the problem.... im a idiot.

I have reformatted the USB stick, installed a fresh copy of unraid, copied over config folder, made bootable and still same thing. Pulled SSD cache drive and it booted....makes no sense to me....

After upgrading to 6.4.1 i found crc errors climbing on my ssd (1 after upgrade -> 2 overnight) so i decided to move the ssd to a new caddy (instead of playing with cables and cards and connectors). Upon reboot the server just gets stuck (see attached). I have left it there for 30 minutes and nothing changes the cursor just flashes. I assume this has to do with the journal and it will eventually boot if i wait long enough???

Thanx! With the new fan design and side fan on the 810A case vs the 800, alot better. My CPU is normally hovering around 33C but i have not put it under a huge stress test yet. The 810 also has room for the stock Intel cooler unlike the unas-800. If the temps give me trouble i will upgrade all 3 fans with noctuas.

Since the big server (Icarus formally C.O.R.P.S.) is not super portable (wife wouldn't let me take it anyway), I have decided to build a new mobile server for all my travels. Introducing HAL9000 (with Icarus making a cameo in the background) Case: U-NAS NSC-810A http://www.u-nas.com/xcart/product.php?productid=17640 MB: ASRock Z370M Pro4 LGA 1151 (300 Series) Intel Z370 HDMI SATA 6Gb/s USB 3.1 Micro ATX https://www.newegg.com/Product/Product.aspx?Item=N82E16813157793 CPU: Intel Core i5-8400 Coffee Lake 6-Core 2.8 GHz (4.0 GHz Turbo) LGA 1151 (300 Series) https://www.newegg.com/Product/Product.aspx?Item=N82E16819117824 Memory: G.SKILL Ripjaws 4 Series 16GB (4 x 4GB) 288-Pin DDR4 SDRAM DDR4 2666 (PC4 21300) https://www.newegg.com/Product/Product.aspx?Item=N82E16820231821 Exp Card: IO Crest 4-port SATA III PCIe 2.0 x2 Controller Card Green, SI-PEX40064 https://www.amazon.com/gp/product/B00AZ9T3OU/ref=oh_aui_detailpage_o08_s00?ie=UTF8&psc=1 Exp card for 802.3 RR: Intel PRO/1000 VT Quad Port Server Adapter LP PCI-E EXPI9404VT https://www.amazon.com/gp/product/B002JLKNIW/ref=oh_aui_detailpage_o01_s00?ie=UTF8&psc=1 PWR: SP Group Mini ITX Solution / Flex ATX 80 Plus Platinum 500W https://www.amazon.com/gp/product/B01N4IGM0O/ref=oh_aui_detailpage_o09_s00?ie=UTF8&psc=1 Harddrives: 8TB - Western Digital Easy store (shucked) 8TB - Western Digital Easy store (shucked) 8TB - Western Digital Easy store (shucked) 8TB - Western Digital Easy store (shucked) 8TB Pairty - Western Digital Easy store (shucked) 1TB Cache - Samsung 960 PRO Series - 1TB PCIe NVMe - M.2

ty

I just installed a new cache drive in my server. Is there anything other than a daily trim plugin that i need to do to keep my system running well? i am also now getting this in my logs. "Feb 9 09:27:26 HAL9000 root: HDIO_DRIVE_CMD(standby) failed: Inappropriate ioctl for device"

thanx @jonp =)

Intel PRO/1000 VT is the Intel 82575GB chipset under the hood. The Linux* e1000e driver supports PCI Express Gigabit Network Connections except the 82575, 82576, 82580, and I350. Therefore i assume this card will use the e1000 driver. The e1000.x.x.x.tar.gz supports all PCI and PCI-X Intel® Gigabit Network Adapters/Connections. Bottomline: I will know monday if the card works in unraid. https://downloadcenter.intel.com/download/13663/Intel-Network-Adapter-Driver-for-82575-6-82580-I350-and-I210-211-Based-Gigabit-Network-Connections-for-Linux-?product=2469

Yea i got burned once before with RTL and unraid I should have known better.

Thanx for the reply jonnie, its the wrong driver that is being loaded (r8169) and unraid doesnt have the correct driver (r8168) built in. I have worked on it for many days, i have finally given up and bough an intel NIC. https://www.amazon.com/gp/product/B002JLKNIW/ref=oh_aui_detailpage_o00_s00?ie=UTF8&psc=1 Heres to hoping it works lol.

Tried to compile the proper drivers.... sadly i am unable to do so. I guess its time to return the nic and do the ol' hope unraid supports my next device that is supported by linux without issue.