Jump to content

laterdaze

Members
  • Content Count

    20
  • Joined

  • Last visited

Community Reputation

0 Neutral

About laterdaze

  • Rank
    Member

Converted

  • Gender
    Male
  • Personal Text
    Only the compiler guy needs to write clever code...

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. laterdaze

    WireGuard VPN support

    I have only tried what I described so far. Since it seems WireGuard will be in the Linux kernel soon I just thought it would be a natural fit for unRAID. I just see remotely separated unRAID systems bi-directionaly syncing data via WireGuard vpn with no need for a particularly powerful router as just port forwarding would be required. I do something similar with pfSense/OpenVPN and rclone. A private personal cloud by invitation only.
  2. laterdaze

    WireGuard VPN support

    I think supporting wireguard would be very useful for a lot of users. It could make unRAID a preferred home based cloud storage device. At least for me, anyway ;>) I built wireguard using the latest Slackware live iso and the info at https://slackbuilds.org/repository/14.2/network/WireGuard/ but couldn't figure how to insert it into the unRAID kernel. Probably would be trivial for you guys but not clear to me.
  3. laterdaze

    Preclear plugin

    FYI, This only happens in Dark(Black) Mode. The other modes, Azure, Grey, and White work as expeted.
  4. laterdaze

    Preclear plugin

    The problem is not Firefox dependant, does the same with Chrome or Edge. Still want the web console output?
  5. laterdaze

    6.6.0-rc4 Share Settings not discernable

    Changed Status to Closed
  6. laterdaze

    Preclear plugin

    When I have Preclear plugin 2018.09.17 installed on 6.6.0-rc4 the User Shares - Add Share - Share Settings Included disks and Excluded disks values are obscured. See https://screenshots.firefox.com/MYrjvbEQdcjM5RFf/192.168.10.50 There is a short thread in bug reports with diagnostics. Bug Reports Prereleases 6.6.0-rc4 Share Settings not discernable
  7. laterdaze

    6.6.0-rc4 Share Settings not discernable

    I remove preclear disks plugin 2018.09.17 and reboot, Share Settings works as expected. install preclear 2018.09.17 Share Setting fails as before. I'll move to the Preclear support thread. Thanks.
  8. laterdaze

    6.6.0-rc4 Share Settings not discernable

    Indeed, they appear as expected when in safe-mode. So, when you said "probably" you were already like 99.9 percent sure that was it... lol... How should I proceed, uninstall plugins one at a time or do you have a usual suspect?
  9. https://screenshots.firefox.com/MYrjvbEQdcjM5RFf/192.168.10.50 In Share Settings In Dark mode the included and excluded disks cant be seen. Highlighting with a mouse reveals the text. I think this is new in the latest rc series. tower-diagnostics-20180919-1225.zip
  10. laterdaze

    Dynamix File Integrity plugin

    Minor nit, inconsistent build status indicated.
  11. laterdaze

    ZFS plugin for unRAID

    Thanks for that, I'll give it a try.
  12. laterdaze

    ZFS plugin for unRAID

    I decided to use your instructions to build ZFS for unraid 6.3.2 and all went well until: Hunk #4 succeeded at 2515 (offset 2 lines). Hunk #5 succeeded at 2610 (offset 2 lines). patching file drivers/pci/quirks.c HOSTCC scripts/basic/fixdep scripts/basic/fixdep.c:105:23: fatal error: sys/types.h: No such file or directory #include <sys/types.h> ^ compilation terminated. make[1]: *** [scripts/basic/fixdep] Error 1 make: *** [scripts_basic] Error 2 3.1) Do you want to run Menu Config ? [y/N] y Are there other dependencies I should have installed first? Thanks for your work. I'm a long time ZFS user and would really like Lime-Tech to integrate ZFS support. The snapshot/rollback capabilities are unparalleled.
  13. I had a similar problem and as I remember I switched to an old MB that didn't know about EFI. Over the years this subject has been beaten into submission by FreeNAS and NAS4Free users. Google search of "failed to initialize PAL" will lead to their forums. Persistence is the key...
  14. laterdaze

    6.3.1 stack dump during interrupt handling.

    Thanks for that. Meanwhile I perused the kernel sources and it seems that while trying to coalesce some socket buffers some math didn't add up so it pulled the chain. Better safe than sorry. That stack of kernel code seems like a well worn path so it will take some one with "enlightened foreprudence" to figure that out...
  15. This has not happened before 6.3.1 upgrade, not that it means anything though. I've been running the Mellanox driver with a ConnectX-2 for quite a while. The BIOS has an update, will do that when I get a chance. Feb 14 11:35:21 unRAID kernel: ------------[ cut here ]------------ Feb 14 11:35:21 unRAID kernel: WARNING: CPU: 2 PID: 14091 at net/core/skbuff.c:4313 skb_try_coalesce+0x22f/0x31d Feb 14 11:35:21 unRAID kernel: Modules linked in: xt_nat veth vhost_net tun vhost macvtap macvlan kvm_intel kvm md_mod xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat mlx4_en mlx4_core ptp pps_core r8169 mii x86_pkg_temp_thermal coretemp ahci i2c_i801 i2c_smbus i2c_core libahci wmi video backlight [last unloaded: md_mod] Feb 14 11:35:21 unRAID kernel: CPU: 2 PID: 14091 Comm: Threadpool work Not tainted 4.9.8-unRAID #1 Feb 14 11:35:21 unRAID kernel: Hardware name: System manufacturer System Product Name/P8H77-I, BIOS 0904 10/15/2012 Feb 14 11:35:21 unRAID kernel: ffff88021fb03af8 ffffffff813a34fa 0000000000000000 ffffffff819a7fee Feb 14 11:35:21 unRAID kernel: ffff88021fb03b38 ffffffff8104d04c 000010d9132d9000 ffff8801e5d34d00 Feb 14 11:35:21 unRAID kernel: ffff8801e5d34f00 00000000000004c0 ffff88021fb03b94 0000000000000575 Feb 14 11:35:21 unRAID kernel: Call Trace: Feb 14 11:35:21 unRAID kernel: <IRQ> Feb 14 11:35:21 unRAID kernel: [<ffffffff813a34fa>] dump_stack+0x61/0x7e Feb 14 11:35:21 unRAID kernel: [<ffffffff8104d04c>] __warn+0xb8/0xd3 Feb 14 11:35:21 unRAID kernel: [<ffffffff8104d114>] warn_slowpath_null+0x18/0x1a Feb 14 11:35:21 unRAID kernel: [<ffffffff8157a3be>] skb_try_coalesce+0x22f/0x31d Feb 14 11:35:21 unRAID kernel: [<ffffffff815e58b8>] tcp_try_coalesce+0x38/0x97 Feb 14 11:35:21 unRAID kernel: [<ffffffff815e5db4>] tcp_queue_rcv+0x5c/0x101 Feb 14 11:35:21 unRAID kernel: [<ffffffff815ea7bb>] tcp_rcv_established+0x2b2/0x5ac Feb 14 11:35:21 unRAID kernel: [<ffffffff815f20ae>] tcp_v4_do_rcv+0x98/0x1c8 Feb 14 11:35:21 unRAID kernel: [<ffffffff815f47e7>] tcp_v4_rcv+0x8aa/0xaec Feb 14 11:35:21 unRAID kernel: [<ffffffffa0025215>] ? ipv4_confirm+0x7a/0xd0 [nf_conntrack_ipv4] Feb 14 11:35:21 unRAID kernel: [<ffffffff815d4faa>] ip_local_deliver_finish+0xf4/0x1c3 Feb 14 11:35:21 unRAID kernel: [<ffffffff815d5540>] ip_local_deliver+0xcc/0xe1 Feb 14 11:35:21 unRAID kernel: [<ffffffff815d4eb6>] ? inet_del_offload+0x40/0x40 Feb 14 11:35:21 unRAID kernel: [<ffffffff815d536d>] ip_rcv_finish+0x2f4/0x2ff Feb 14 11:35:21 unRAID kernel: [<ffffffff815d5896>] ip_rcv+0x341/0x358 Feb 14 11:35:21 unRAID kernel: [<ffffffff815d5079>] ? ip_local_deliver_finish+0x1c3/0x1c3 Feb 14 11:35:21 unRAID kernel: [<ffffffff81586b4c>] __netif_receive_skb_core+0x5e9/0x69f Feb 14 11:35:21 unRAID kernel: [<ffffffffa0377cd5>] ? mlx4_en_process_rx_cq+0x83e/0xa43 [mlx4_en] Feb 14 11:35:21 unRAID kernel: [<ffffffff815871c6>] __netif_receive_skb+0x13/0x55 Feb 14 11:35:21 unRAID kernel: [<ffffffff81588124>] process_backlog+0xa1/0x13f Feb 14 11:35:21 unRAID kernel: [<ffffffff81587f1f>] net_rx_action+0xe2/0x246 Feb 14 11:35:21 unRAID kernel: [<ffffffff81050eca>] __do_softirq+0xbb/0x1af Feb 14 11:35:21 unRAID kernel: [<ffffffff8105116e>] irq_exit+0x53/0x94 Feb 14 11:35:21 unRAID kernel: [<ffffffff8102009e>] do_IRQ+0xaa/0xc2 Feb 14 11:35:21 unRAID kernel: [<ffffffff8167db42>] common_interrupt+0x82/0x82 Feb 14 11:35:21 unRAID kernel: <EOI> Feb 14 11:35:21 unRAID kernel: ---[ end trace 790ce744c3e754ca ]--- unraid-diagnostics-20170215-0833.zip