Helmonder
Members
-
Joined
-
Last visited
Everything posted by Helmonder
-
Just had to reboot unraid…. After the reboot farming is unavailable and an error in connection… Been like that for an hour, can that still be a startup thing that will solve itself or is something else wrong ? Verzonden vanaf mijn iPhone met Tapatalk
-
Hi ! Sofar I have created 7 plots and that is continuing nicely. I am wondering however: how can I actually determine that the -farming- is working ? I am aware that it can take months and months before there could be any payout, but I do not see any indication that there is something going that is “farming” (besides the “farming active” on the main page). How can I see that I am at least -trying- to create a profit ? Verzonden vanaf mijn iPhone met Tapatalk
-
Soon (tm) is the answer you will get out of the forum ;-)
-
Its still just sitting there…. Cache drive has more then enough free… 100g+ .. I removed the plots and restarted the process with 1 plot at a time.. I had been fiddling with the type of cache drive (Only, Prefered). I can imagine that had created some conflicting data.. Since this morning it is tugging along at its first plot and now sitting at 3:4 but still running.. So I am guessing all is fine now !
-
Thanks ! Can I just change that while the docker is running ? It kind of looks like the process has halted ?
-
Nice docker to try.. I read the profitability of Chia is not to great at the moment but you never know :-) Fun to try ! I have installed the docker and it is plotting along. I created an extra cache pool of 350G with two old SSD's and set a share in "prefer" on there. Then the main folder for the finished plots on the array. Is that about what everyone is doing ? Its creating two plots at the moment, will plotman start making new ones when these are moved to the main folder ?
-
“The story of the lime” !
-
It appears therr already is a plugin that does just what I need, enabled it this weekend :-) So happy camper here ! Still looking for a completely out of the box way to make sure my secondary unraid server is up to date as a backup though, is that something ? Verzonden vanaf mijn iPhone met Tapatalk
-
Know what you mean… I was saying that if you purchase your own domain you can forward to that hash… that would solve the “remembering issue” (bookmark works also, and ofcourse internally in your network you do not need it).. Just giving options.. your own domain solves a lof of other issues also; your own email address and such.. Verzonden vanaf mijn iPhone met Tapatalk
-
You could get your own domain name and redirect from there... even cooler..
-
Ahead of you :-) I also noticed that and changed my post... And at the moment I am actually checking out SSD's :-) ROFL !
-
Cancel that request :-) It already exists: Amazing...
-
The following would be a great addition: I have an Unraid server running with 74 Terabyte total space. The extreme most of that is for movies/series from long ago.. I might not ever be looking at them. And with netflix, amazon prime and other services I honoustly make less use of it then I used to. In an effort to try and bring down electricity usage from an environmental perspective I am pondering the following: What if the cache drive would not be emptied by the mover totally at a certain point in time but it would move everything -older- then a certain point in time. That would keep all my new content for a specific timeslot available on the cache drive, I could watch all my series and stuff from the cache drive, stuff older then something like a month would be offloaded to the array and disks would remain spun down for a long time there.. Seems like a relatively easy thing to do.. ?
-
I used to respond to messages like this with the "Unraid is meant to be used within your network and should not be exposed to the internet" paradigm..
-
Absolutelly, to each his or her own ! personally I am using my mikrotik router as an openvpn endpoint and I keep it up to date, before that I used a raspberry pi with openvpn on it, very happy with it.
-
Exactly… but to each his or her own !
-
Its not that difficult.. I was just wondering why people prefer this to the von solution…. Also wondering my idea that a vpn is preferable is actually -true- or just me beiing an old guy.. Verzonden vanaf mijn iPhone met Tapatalk
-
I do wonder if its just not a lot easier to have a VPN system running on your router or another device (openvpn, wireguard).. Sure you need to set up the access before you can lopg on to the webpage but that does not seem like a big step to take ? Its the way I have been doing this for years... Is exposing your server to the internet (even with SSL) actually a good idea ?
-
The rsyslogd entries are "normal" after a reboot.. The syslogdeamon is trying to send data before the network is up..
-
Mellanox issue still present.
-
After a couple of days of mucking about I was able to update 6.8.3 to 6.9. Pretty proud of myself :-) I am now running 6.9 although without my 10GB card functioning. I am running on a bond with my 10GB in it together with two 1GB connections. My network speeds are at 1GB level so I safely assume that my 10GB is not active, this is also logical because with -only- that 10GB in use as connection there was no connection at all. For details on this issue see: At the moment, as stated, that upgrade has worked and I am now stuck withouy my 10GB as a seperate issue. It concerns a Mellanox SFP+ card with two uplinks: IOMMU group 12:[15b3:6750] 03:00.0 Ethernet controller: Mellanox Technologies MT26448 [ConnectX EN 10GigE, PCIe 2.0 5GT/s] (rev b0) Attached is also my current diagnostics. tower-diagnostics-20210308-2114.zip Contents of IP L SHOW : 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 3: gre0@NONE: <NOARP> mtu 1476 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/gre 0.0.0.0 brd 0.0.0.0 4: gretap0@NONE: <BROADCAST,MULTICAST> mtu 1476 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 5: erspan0@NONE: <BROADCAST,MULTICAST> mtu 1464 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff 6: ip_vti0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 7: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/sit 0.0.0.0 brd 0.0.0.0 12: eth3: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 00:02:c9:52:e9:61 brd ff:ff:ff:ff:ff:ff permaddr ac:1f:6b:94:71:62 13: eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 00:02:c9:52:e9:61 brd ff:ff:ff:ff:ff:ff permaddr ac:1f:6b:94:71:63 14: eth2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000 link/ether 00:02:c9:52:e9:60 brd ff:ff:ff:ff:ff:ff 15: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 00:02:c9:52:e9:61 brd ff:ff:ff:ff:ff:ff 16: bond0: <BROADCAST,MULTICAST,PROMISC,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UP mode DEFAULT group default qlen 1000 link/ether 00:02:c9:52:e9:61 brd ff:ff:ff:ff:ff:ff 17: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 00:02:c9:52:e9:61 brd ff:ff:ff:ff:ff:ff 18: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000 link/ether 52:54:00:64:42:af brd ff:ff:ff:ff:ff:ff 19: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq master virbr0 state DOWN mode DEFAULT group default qlen 1000 link/ether 52:54:00:64:42:af brd ff:ff:ff:ff:ff:ff 20: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq master br0 state UNKNOWN mode DEFAULT group default qlen 1000 link/ether fe:54:00:aa:46:a4 brd ff:ff:ff:ff:ff:ff 21: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default link/ether 02:42:06:45:db:64 brd ff:ff:ff:ff:ff:ff 23: veth3911429@if22: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP mode DEFAULT group default link/ether ce:61:ee:ba:fa:5d brd ff:ff:ff:ff:ff:ff link-netnsid 0 25: veth8a6fc6e@if24: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP mode DEFAULT group default link/ether 96:2b:5c:d4:58:04 brd ff:ff:ff:ff:ff:ff link-netnsid 1 The 10GB interface is the eth0, so: 15: eth0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 00:02:c9:52:e9:61 brd ff:ff:ff:ff:ff:ff For the life of me I do not see anything wrong with it ? Note: same behaviour on 6.9.1 Any help is appreciated.
-
The upgrade from 6.8.3 60 6.9 failed in my case. The update itself succeeded, reboot worked but the system did not become active on the network. No GUI, no share, no telnet. - I was able to IPMI into the system and get on console; - The system could ping its own IP address from console but not the default gateway. GUI mode also did not work from console; "page not found"; - Network setup appeared good, correct default gateway and such (ROUTE -N) - The port was shown as "linkdown" (IP ROUTE SHOW); - I have attached a diagnostics file (note: this is for the current situation, so with 6.8.3). - I also attach a syslog that I was able to capture on the flashdrive for the 6.9 config. Hopefully that will give someone some insight. - I reverted to 6.8.3 by restoring the flashdrive from the backup, that seems to have worked 100%. I am suspecting the issue lies with my ethernet controller: IOMMU group 12:[15b3:6750] 03:00.0 Ethernet controller: Mellanox Technologies MT26448 [ConnectX EN 10GigE, PCIe 2.0 5GT/s] (rev b0) Also: Tower kernel: emhttpd[17268]: segfault at 0 ip 00001489487cff36 sp 0000148943dfde80 error 4 in libc-2.30.so[1489487ab000+16b000] A segfault in emhttpd would also cause the GUI to be not reachable but I figure that would make the GUI unreachable but not telnet/shares.. So probably emhttpd crashed because of the closed eth0 ? tower-diagnostics-20210304-1414.zip syslog.bad
-
Hi.. I have some issues getting Syncthing to work with my secundary network... I would appreciate if if someone could look if I am doing something wrong: EDIT: Guess I was just TO anxious... It took a while for the system to complete scanning... Its running 300 Mb/s between the boxes now :-)
-
Thanks. I found one for a reasonable price and bought it... Have to find a way to double-connect my monitor now though.. Forgot abaout that :-) I gave the VM 4 of my 8 cores, cannot say its "quick' though.. but still fine fo find out how macos works..
-
Any advice on what GPU to add to unraid to make it work a bit more smooth ? Not to expensive.. Will not use it for anything but this... I am running on a Supermicro X11SSM-F Version 1.01 with an Intel® Xeon® CPU E3-1230 v6 @ 3.50GHz
