Helmonder

Members
  • Posts

    2815
  • Joined

  • Last visited

Everything posted by Helmonder

  1. 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
  2. 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
  3. You could get your own domain name and redirect from there... even cooler..
  4. Ahead of you :-) I also noticed that and changed my post... And at the moment I am actually checking out SSD's :-) ROFL !
  5. Cancel that request :-) It already exists: Amazing...
  6. 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.. ?
  7. 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..
  8. 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.
  9. 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
  10. 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 ?
  11. So far I a have been using allmost exclusively WD RED's in my system. I am due for a few replacements. Next step for me should be 10 TB or more. My regular go-to would be 10TB WD RED, which is EUR 274,- or 12 TB WD RED, which is EUR 333,- or 14 TB WD RED, which is EUR 403,- However: Seagate EXOS X16 10TB is EUR 230 Seagate EXOS X16 12TB is EUR 257 Seagate EXOS X16 14TB is EUR 290 The 12TB EXOS looks real interesting to me... Anyone any experience ?
  12. The rsyslogd entries are "normal" after a reboot.. The syslogdeamon is trying to send data before the network is up..
  13. Ok.... did somethin else now.. The not working 10GB was eth0, which was now in a bond with eth1 and 3. eth1 and eth3 are regular lan ports on my motherboard. - I now swapped eth0 and eth1 so the 10GB is now my 10GB. - Then I removed the 10Gb eth1 from the bond (connectivity still ok) - Then I tried to configure the 10GB interface.. AND THE THING GOT AN IP ADDRESS !! That means that the card itself -is- working on an OS level... This is getting more and more curious... - Now I moved the eth1 10GB card back into the bond - Tested connectivity: back on 10GB speeds ! - Did a reboot half expecting it to not work again but alas... it still works !
  14. That is what I had... just the 10GB... perfectly working in 6.8.3.. But when I then update to 6.9 there is no network, see I only made this bond to be able to get 6.9 running... The situation basically is the same only the other nic's in the group do work which is why my server is reachable.. If I now remove the bond that will only result in a server not beiing reachable anymore..
  15. What do you want me to do with it ? It is installed and shows info but nothing I think I can do something with ?
  16. 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.
  17. Changed Status to Solved I did a hail mary.. I added my onboard NICs to my mlx4... After that the update worked and I had networking.. Attached are diagnostics of prior and after this situation.. tower-diagnostics-20210308-1914 - bonded.ziptower-diagnostics-20210308-1932 bonded on 6.9.zip Now to see if I actually have 10GB , or if I am now running on backup..
  18. I do not have an issue getting the system to boot anymore... Switching to UEFI boot solved that.
  19. I solved this by using UEFI boot in stead of Legacy...
  20. I did some extra checks, the above might be a bit garbled with info: 1) I have a working, running 6.8.3, I have rebooted just to be sure the usb drive works: it does 2) I run an upgrade to 6.9, this results in a "BOOT ERROR" , before stuff gets loaded so it looks to me like the bootloader is not recognised or something 3) I copy back all of my 6.8.3 files over the 6.9 migrated usb stick, the stick continues to not work and give me a "BOOT ERROR" when booting, I think that shows its not the files., dockers, plugins (also: the issue also occurs with a safe boot) If I want to make it work again I have to recreate the thumbstick and copy back my 6.8.3 files, then I have a perfectly working system. This triggered me, if it is to due with the bootloader/bootpartition.. Maybe its linked to my way of booting ? I am using legacy boot.. I changed to UEFI and now I have been able to boot ! However... No network... No GUI, no shares. I was able to use console: Route-N and IP Route Show output attached. Both look fine to me... I grabbed the syslog and also attached that to the post: syslog.0803211812 I also started the system in safe mode. This does not make a difference, also no network. I also grabbed the syslog fro mthe safe mode: syslog-safe.08031211824 I am no expert here but I do notice that there -is- a message "eth4: link up", but there is no message for "eth0: link up". Should that not be there ?
  21. Well you are not alone... I have the same issue: The following worked for me (have done it several times trying to get 6.9 to work: 1) Create your USB new with the USB tool (that will clean it totally and make it fresh) 2) Copy the backup you made before upgrading to 6.9 back over it. 3) Reboot All should work.. Very curious on this boot error thing..