Jump to content

mikefallen

Members
 View Profile  See their activity

  • Posts

    155

  • Joined

  • Last visited

 Content Type 

Posts posted by mikefallen

    [HDD] Seagate Backup Plus 10TB Desktop External Hard Drive (can be shucked, should contain a IronWolf Pro NAS 10TB ) (279.99 - 50 = 229.99) [Bestbuy]

    in Good Deals!

    Posted · Edited by mikefallen

    Just bought one of these to shuck and was pleasantly surprised to get a Seagate IronWolf Pro NAS 10TB disk with the model # ST10000NE0008

     

     

    https://www.bestbuy.ca/en-ca/product/seagate-backup-plus-10tb-desktop-external-hard-drive-stel10000400-black/12315363?irclickid=wan3apysDxyOWFH0MdV3iVCmUkiyObSZW06ow00&ref=affiliate&utm_content=341376&utm_source=IR&acmp=RedFlagDeals&utm_term=644465&irgwc=1

    Preclear plugin

    in Plugin Support

    Posted · Edited by mikefallen

    Just finished pre-clearing 2 disks and go this error on the final output

     

    cat: /tmp/.preclear/sdq/smart_error: No such file or directory found

     

    It shows me the first graphic of the successful run with the steps 1-5 but then the area it supposed to show the change in smart data shows that

     

    Edit:

    Just realized these were SAS disks not SATA not sure if that would affect the outcome, i noticed SAS disks seem to have different smart data than SATA disks

     

     

    Issues with refurb SAS 4TB Hardrive

    in General Support

    Posted · Edited by mikefallen

    Hardware:

    Supermicro H8DM8-2  (link)

    3 x AoC-SAT2-MV8 (link)

    New HGST 4TB sas HDD (link)

    4u 24 bay supermicro case w/  SAS846TQ Backplane (link)

     

     

    From what i understand this backplane just does pass-through and has no issues with drives over 2.2TB in size as is has no expander onbaord. 

     

    Issue:

    This week I had a 2tb SATA HDD fail on me, quick search on ebay lead me to some refurb 4tb sas drives for 80$ shipped so i bought 1 to replace the failing drive. When i replaced the 2tb sata hgst drive with a 4tb hgst sas drive unraid will boot up to the point of "starting Rsyslogd daemon" and will hang there, if i pull the new drive while the system is hung there the boot process will continue and boot into unraid as expected. I can also boot straight into unraid just fine with the disk completely removed.

     

    I am assuming there is some kind of hardware incompatibility somewhere that i am not aware off and help troubleshooting this issue would be greatly appreciated ! 

    [Support] spikhalskiy - ZeroTier

    in Docker Containers

    Posted

    7 minutes ago, Dmitry Spikhalskiy said:

    @mikefallen Yeah, if it's really what you want to do - it should work.

    1. "Pretty sure Ford is right i just need to add a static route on my lan router pointing back to the zerotier network." Adding a static route on your router will make Zerotier hosts available for your local hosts.

    2. "setup ZeroTier on my openwrt router at home." This will bring your router to the ZT network and you will be able to add a static rule to your ZT network setup where to route your requests from ZT network for local network IP addresses, so it will expose your local network IPs to the ZT hosts.

     

    For what you describe "But i cannot ping anything else from awayPC to anything else on 192.168.2.0/24 only unRAID address (192.168.2.100)" you need to go by the second scenario, not the first one. But be mindful that if you do that, your Wi-Fi smart home lock for example will be exposed to any device added to your Zerotier network.

    Yeah thats what i'm trying to do basically right now i use openVPN, i like this solution better because it does not use a central server and peers can connect directly to each other.

    [Support] spikhalskiy - ZeroTier

    in Docker Containers

    Posted

    10 minutes ago, Dmitry Spikhalskiy said:

    @mikefallen I'm not sure if you got how ZT works. It creates own "virtual" network. Devices that are part of this network are accessible to each other using ZT IP addresses. So, your awayPCzt is able to access unRAIDzt using ZT IP address (172.22.0.100) and opposite - that's what ZT gives you and looks like it's working.

    ZT installed on one machine doesn't bring your whole home network to Zerotier virtual network, it brings only this one device into it. ZT installed on one network host thankfully can't expose all devices in this network outside and can't reroute traffic from other local hosts outside. Imagine buying a smart bulb that after turning on just automatically tunnel all your traffic from all your devices in the network to some third party server?

    What you want could be achievable by changing settings of your router, but I definitely wouldn't recommend to do it. If you want to access some other devices in your network - use a browser (which will see your home network) installed on your ZT server that you access using ZT IP address or ssh / make an ssh port forwarding to you ZT server and from that server you can ssh / access other devices in your home network.  

    Pretty sure Ford is right i just need to add a static route on my lan router pointing back to the zerotier network.

     

    This github issue might give you a better idea https://github.com/zerotier/ZeroTierOne/issues/805

    [Support] spikhalskiy - ZeroTier

    in Docker Containers

    Posted · Edited by mikefallen

    Quick question regarding an issue i have run into and wondering if anyone has a similar setup that is working. I'm trying to access my Home network LAN from other computers in the ZT network. From what i have read online i just create a managed route  in zero tier for 192.168.2.0/24 via 172.22.0.100 which i have done and make sure sysctl ip_forwarding is enabled on unRaid which it is.

     

    Home Network    = 192.168.2.0/24

    Away Network    = 192.168.0.0/24

    awayPC              = 192.168.0.150

    awayPCzt           = 172.22.0.150

    unRAID               = 192.168.2.100

    unRAIDzt            = 172.22.0.100

     

     

     on my awayPC i can see this route in "Route Print" for 192.168.2.0/24 via 172.22.0.100

     

    i can ping from awayPC ----> to both unRAID (192.168.2.100) and unRAIDZT  (172.22.0.100)

     

    But i cannot ping anything else from awayPC to anything else on 192.168.2.0/24 only unRAID address (192.168.2.100)

     

     

     

    Any ideas?

    [Support] Linuxserver.io - Qbittorrent

    in Docker Containers

    Posted

    On 2/4/2019 at 11:22 AM, trurl said:

    His sig has not been updated, probably since we moved to the new forum software. He probably isn't even aware we have sigs here since you have to enable them in order to see them.

     

     

    Yeah I'm on latest ...not much to go on nothing in the docker logs indicate any issues.....installed the BitTorrent docker with vpn and just disabled the vpn and it works fine.... weird  

    [Solved] HGST 3TB Disks Cause Kernel Panic and Crash

    in General Support

    Posted

    3 hours ago, johnnie.black said:

    It's not all devices, it's some recent devices.

    Do you know if there's any other pci-x cards that have better support for newer hard drives?

     

    I guess i could update to a newer motherboard cpu combo to get PCIe .....but i'm not sure what the compatibility with the backplane would be like... this backplane has 1 sata connector for every disk not a SFF-8087 connector.

     

    Just don't wanna spend a bunch of money for it to be incompatible....

    [Solved] HGST 3TB Disks Cause Kernel Panic and Crash

    in General Support

    Posted · Edited by mikefallen

    Hey guys i'm having the weirdest issue and i'm hoping someone can help.

     

    First off im using an older 24 - bay supermicro server with 3 x AOC-SAT2-MV8 cards in it and i already have 2 other 3TB hard disks running just fine in this setup.

    I bought some refurb hard disks off of ebay (newegg 55$ 3TB HGST) and as normal i put them into their caddies and pushed them into the hot swap bays and bam unraid locks up with a kernel panic.

     

    Upon restart i get a kernel panic on boot...i tried with all 3 new drives inserted....tried putting in one at a time. All has the same issues.. as soon as i remove them all boots up no problem and chugs along as usual.

     

    At first i was thinking maybe a compatibility issue with the AOC-SAT2-MV8 cards as they are older but i have a WD and SG 3tb disk already in the array with no issues...... any help would be greatly appreciated 

     

    kernel Panic screenshot

     

    tower-diagnostics-20181111-2123.zip

    Kernel Panic unraid 6.5.0

    in General Support

    Posted · Edited by mikefallen

    On latest unraid version i have been having some seemingly random kernel panics .... weirdly this causes my plex docker to stop working but the server is still up and running fine

     

    See a lot of errors related to IPMI so i uninstalled the IPMI plugin... see if that helps

      

    Apr 17 01:29:31 Tower /usr/sbin/ipmiseld[5507]: 192.168.2.254: Error connecting: connection timeout
Apr 17 01:57:56 Tower /usr/sbin/ipmiseld[5507]: 192.168.2.254: Error connecting: connection timeout
Apr 17 02:13:30 Tower root: /mnt/cache: 95.5 GiB (102534463488 bytes) trimmed
Apr 17 02:26:20 Tower /usr/sbin/ipmiseld[5507]: 192.168.2.254: Error connecting: connection timeout
Apr 17 02:54:44 Tower /usr/sbin/ipmiseld[5507]: 192.168.2.254: Error connecting: connection timeout
Apr 17 03:04:32 Tower kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000038
Apr 17 03:04:32 Tower kernel: IP: tcp_push+0x4e/0xee
Apr 17 03:04:32 Tower kernel: PGD 15f68a067 P4D 15f68a067 PUD 3dbefc067 PMD 0 
Apr 17 03:04:32 Tower kernel: Oops: 0002 [#1] PREEMPT SMP NOPTI
Apr 17 03:04:32 Tower kernel: Modules linked in: tun xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat xfs md_mod ipmi_devintf forcedeth amd64_edac_mod edac_mce_amd kvm_amd kvm k10temp sata_nv sata_mv button ipmi_si acpi_cpufreq [last unloaded: forcedeth]
Apr 17 03:04:32 Tower kernel: CPU: 4 PID: 12621 Comm: Plex Media Serv Not tainted 4.14.26-unRAID #1
Apr 17 03:04:32 Tower kernel: Hardware name: Supermicro H8DM8-2/H8DM8-2, BIOS 080014  10/22/2009
Apr 17 03:04:32 Tower kernel: task: ffff8803bd71cc80 task.stack: ffffc900052a8000
Apr 17 03:04:32 Tower kernel: RIP: 0010:tcp_push+0x4e/0xee
Apr 17 03:04:32 Tower kernel: RSP: 0018:ffffc900052abc70 EFLAGS: 00010246
Apr 17 03:04:32 Tower kernel: RAX: 0000000000000000 RBX: 00000000000005a0 RCX: 0000000000000000
Apr 17 03:04:32 Tower kernel: RDX: 0000000000000000 RSI: 0000000000004040 RDI: ffff88000fbae000
Apr 17 03:04:32 Tower kernel: RBP: ffff8803bd71d5a0 R08: 0000000000004920 R09: ffffffff8151be00
Apr 17 03:04:32 Tower kernel: R10: ffff88000fbae158 R11: 0000000000000000 R12: ffff88000fbae000
Apr 17 03:04:32 Tower kernel: R13: 0000000000000000 R14: ffff8802f8c42000 R15: 00000000ffffffe0
Apr 17 03:04:32 Tower kernel: FS:  0000151d235fe700(0000) GS:ffff88040fd00000(0000) knlGS:0000000000000000
Apr 17 03:04:32 Tower kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Apr 17 03:04:32 Tower kernel: CR2: 0000000000000038 CR3: 00000002b096c000 CR4: 00000000000006e0
Apr 17 03:04:32 Tower kernel: Call Trace:
Apr 17 03:04:32 Tower kernel: tcp_sendmsg_locked+0xa53/0xbac
Apr 17 03:04:32 Tower kernel: tcp_sendmsg+0x23/0x35
Apr 17 03:04:32 Tower kernel: sock_sendmsg+0x14/0x1e
Apr 17 03:04:32 Tower kernel: ___sys_sendmsg+0x1ab/0x229
Apr 17 03:04:32 Tower kernel: ? enqueue_task_fair+0x94/0x42c
Apr 17 03:04:32 Tower kernel: ? ttwu_do_wakeup.isra.4+0xd/0x87
Apr 17 03:04:32 Tower kernel: ? seccomp_run_filters+0xdc/0x106
Apr 17 03:04:32 Tower kernel: ? wake_up_q+0x2d/0x48
Apr 17 03:04:32 Tower kernel: ? __seccomp_filter+0x26/0x1c5
Apr 17 03:04:32 Tower kernel: ? ep_poll+0x2a9/0x2cb
Apr 17 03:04:32 Tower kernel: ? __sys_sendmsg+0x3c/0x5d
Apr 17 03:04:32 Tower kernel: __sys_sendmsg+0x3c/0x5d
Apr 17 03:04:32 Tower kernel: do_syscall_64+0xfe/0x107
Apr 17 03:04:32 Tower kernel: entry_SYSCALL_64_after_hwframe+0x3d/0xa2
Apr 17 03:04:32 Tower kernel: RIP: 0033:0x151d30332a6d
Apr 17 03:04:32 Tower kernel: RSP: 002b:0000151d235fdb00 EFLAGS: 00000293 ORIG_RAX: 000000000000002e
Apr 17 03:04:32 Tower kernel: RAX: ffffffffffffffda RBX: 0000151d235fdb30 RCX: 0000151d30332a6d
Apr 17 03:04:32 Tower kernel: RDX: 0000000000004000 RSI: 0000151d235fdb30 RDI: 000000000000006b
Apr 17 03:04:32 Tower kernel: RBP: 0000151d235fdb30 R08: 0000151d0fd25d58 R09: 0000151d0fd25d68
Apr 17 03:04:32 Tower kernel: R10: 0000000000000001 R11: 0000000000000293 R12: 0000151d235fe5b8
Apr 17 03:04:32 Tower kernel: R13: 0000000000000004 R14: 0000000000000001 R15: 0000151d0fd25d58
Apr 17 03:04:32 Tower kernel: Code: d0 75 02 31 c0 41 89 f3 41 81 e3 00 80 00 00 74 1a 44 8b 8f 68 05 00 00 41 d1 e9 44 2b 8f 6c 06 00 00 44 03 8f 74 06 00 00 79 10 <80> 48 38 08 8b 8f 6c 06 00 00 89 8f 74 06 00 00 40 80 e6 01 74 
Apr 17 03:04:32 Tower kernel: RIP: tcp_push+0x4e/0xee RSP: ffffc900052abc70
Apr 17 03:04:32 Tower kernel: CR2: 0000000000000038
Apr 17 03:04:32 Tower kernel: ---[ end trace 91a87adbe15f760f ]---
Apr 17 03:13:11 Tower root: /mnt/cache: 95.5 GiB (102571241472 bytes) trimmed
Apr 17 03:23:10 Tower /usr/sbin/ipmiseld[5507]: 192.168.2.254: Error connecting: connection timeout
Apr 17 03:40:02 Tower crond[1655]: exit status 1 from user root /usr/local/sbin/mover &> /dev/null
Apr 17 03:51:35 Tower /usr/sbin/ipmiseld[5507]: 192.168.2.254: Error connecting: connection timeout

    tower-diagnostics-20180417-1212.zip

    [Support] Linuxserver.io - Plex Media Server

    in Docker Containers

    Posted · Edited by mikefallen

    On 9/20/2017 at 7:54 PM, Addy said:

     

    I would, but the docker section on the forum boards are greyed out for me... not sure why I havnt logged into the forums before today. 

     

     

    EDIT: Found a random forum post saying to rename the codec directory and restart the docker. This seems to have fixed the issue for me.

     

     

     

    Having same issue can't find forum post your talking about do you mind detailing how you fixed it would be greatly appreciated!

     

     

    Found a fix

    Delete codecs folder in appdata:

    \appdata\plex\Library\Application Support\Plex Media Server\Codecs

    Restart the docker image and it fixes the issue

    OpenVPN Server & Client for unRAID 6.2+ (6.1 are still supported)

    in Plugin Support

    Posted

     

    4 hours ago, dscdsc said:

    I figured it out. Looks like the URL for the openvpn package was timing out. 

    the plg was pulling from:

    http://mirrors.slackware.com/slackware/slackware64-current/slackware64/n/openvpn-2.4.3-x86_64-1.txz

     

    I replaced it with this source and it was able to pull the package correctly.

    http://slackware.cs.utah.edu/pub/slackware/slackware64-current/slackware64/n/openvpn-2.4.3-x86_64-1.txz

     

    The install log didn't have any mention of the file not downloading correctly and the plug in reports back as install complete. maybe something you can look into for the next update?

     

    Had this exact some issue

×
×
  • Create New...