wdelarme

Members
  • Posts

    106
  • Joined

  • Last visited

Posts posted by wdelarme

  1. I currently run an older 8 core AMD and I'm upgrading to (New to me) 1950X ryzen threadripper. Do I need to make any changes to my unraid configurations at this point? I have seen in the past there are changes that were needed for Ryzen cpu's and I'm wondering if the latest stable unraid fixes the need for these so the Ryzens are compatible without playing with it.

  2. My array is encrypted and at boot up  I'm required to enter the path to the keyfile. (right now stored on my flash drive) I'm limited because my router/pfsense is a docker so I can't copy the keyfile across from my network etc using wget. So if I store the keyfile on the flash can I do a command like cp /boot/config/ssh/sshkeyimusing to my go file as a temp measure? Where would I copy that file too at boot time? Yes I know this bypasses the whole idea of the encrypted disks. I really just wanted to try it out

  3. So I have all my old appdata on the cache drive and my array is still intact and started fine after I installed the fresh install of unraid on the flash drive. I can see all my dockers and my one pfsense vm and they look like they are grayed out in the dashboard and inaccessible. Is there anything I can do to reinstall those etc without losing all the information (Plex, deluge) Also one VM that was my pfsense box .

  4. On 9/28/2018 at 11:10 AM, limetech said:

    If there's an issue with some basic functionality which worked in previous release but does not work in current release, please post a Bug Report.

    I had this issue but just changed to intel nic from realtek and everything works fine now

  5. On 9/25/2018 at 8:23 PM, David524 said:

    Mine has been doing the same thing but mine seems to start when I start to move files around from one folder to another. I'm going to roll back to a older version for a while.

    I have the exact issue. I have a 4 port intel nic that only pfsense uses and it stays up and operational. The Realtek Nic onboard dies and cause me to reboot to get to unraid. I was able to find one last pcie slot on my board and have another intel nic on order. I will write an update after I install the intel nic and upgrade to 6.6.0

  6. I installed with no problem everything ran great for a few hours then unraid wouldn't allow any connections from any machine on my network also couldnt get to GUI. Couldn't access shares or dockers but my pfsense vm was accessible because pfsense only uses the intel quad port nic that I have installed and the rest of unraid uses the onboard realtek nic...I had to init 6 the unraid box and upon reboot everything worked fine for a few hours and again same issue. I reverted back to previous version of unraid and all is fine. I tried updating again and a few hours later same issue so I had to init 6 the box again and everything worked fine again for a few hours. I'm now reverted back for the second time with previous unraid version and all is stable. After some troubleshooting with help from unraid forum I have traced it down to the following, It seems to only happen during large file transfers.

     

    Ive added two diags from two separate times that this issue has occurred.

    tower-diagnostics-20180925-2154.zip

    tower-diagnostics-20180925-2138.zip

  7. 21 minutes ago, Frank1940 said:

    I can only tell you that I had an issue with the RealTek drivers a few years back.  LimeTech and I were involved with a behind-the-scene  investigation.  At that time, those drivers were a real mess.  (...and I suspect that is still the case!!!)  There were the drivers that were provided by the Linux team and a set of drivers for Linux from RealTek.  With some releases, one set would work and not the other. On the next release, the reverse was true.  Sometime, both sets would work...  At that time, I was told that LimeTech was throwing in the towel on trying to figure out which way to hop and would release ALL future upgrades using only the drivers for the RealTek chip set that was provided by the Linux team.  

    I sent a message to UNRAID admins to see if this is something they want to mess with or if I should just wait until a new kernel comes out and try to go to 6.6.0 then

  8. 3 hours ago, bnevets27 said:

    I can say that way back I was one of those with issues with a realtek NIC. It was a pain to figure out that it was the cause as it would do things like you're experiencing. Finally came to figuring it out that multiple concurrent transfers would cause a lock up/loss of network. A single transfer would be fine. Added an intel NIC and never had a problem after.

     

     

    This is exactly it! I have a quad port intel nic running all my pfsense stuff and an onboard realtek running the main unraid stuff. This explains why pfsense still works perfect when everything else dies. Is this something the unraid team can look into? I'm sure I'm not the only one using a realtek unboard nic

  9. 26 minutes ago, bnevets27 said:

    I can say that way back I was one of those with issues with a realtek NIC. It was a pain to figure out that it was the cause as it would do things like you're experiencing. Finally came to figuring it out that multiple concurrent transfers would cause a lock up/loss of network. A single transfer would be fine. Added an intel NIC and never had a problem after.

     

     

    I use the intel nic for my pfsense vm. I will prob just not upgrade to the new version of unraid until this gets sorted out. 6.5.3 works flawlessly.

  10. 11 hours ago, wdelarme said:

    Will try this later..I need to update to 6.6 again

     

    11 hours ago, wdelarme said:

    I installed with no problem everything ran great for a few hours then unraid wouldn't allow any connections from any machine on my network also couldnt get to GUI, Couldnt access shares or dockers but my pfsense vm was accessible....I had to init 6 the unraid box and upon reboot everything worked fine for a few hours and again same issue. I reverted back to previous version of unraid and all is fine. I tried updating again and a few hours later same issue so I had to init 6 the box again and everything worked fine again for a few hours. I'm now reverted back for the second time with previous unraid version and all is stable. Is there a specific log file I can get to when I update again for the third time that might help when I lose all connectivity besides my vm pfsense that I could post here to help? I did the update assistant and it said everything was ok to update just to verify it wasn't a known docker issue

    Ok added Diagnostics files tower-diagnostics-20180925-2138.zip .  tower-diagnostics-20180925-2154.zip these are right after it died

  11. 5 hours ago, Shyrka973 said:

    Hi, here is the diagnostic file.

    
    [75712.030094] ------------[ cut here ]------------
    [75712.030097] nfsd: non-standard errno: -103
    [75712.030128] WARNING: CPU: 0 PID: 12163 at fs/nfsd/nfsproc.c:817 nfserrno+0x44/0x4a [nfsd]
    [75712.030129] Modules linked in: macvlan xt_CHECKSUM iptable_mangle ipt_REJECT xt_nat ebtable_filter ebtables veth ip6table_filter ip6_tables vhost_net tun vhost tap ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat xfs nfsd lockd grace sunrpc md_mod it87 hwmon_vid bonding r8169 mii intel_powerclamp coretemp kvm_intel kvm crc32c_intel intel_cstate intel_uncore i2c_i801 i2c_core ahci mxm_wmi i7core_edac libahci pata_jmicron wmi button pcc_cpufreq acpi_cpufreq [last unloaded: mii]
    [75712.030165] CPU: 0 PID: 12163 Comm: nfsd Tainted: G          I       4.18.8-unRAID #1
    [75712.030166] Hardware name: Gigabyte Technology Co., Ltd. X58A-UD7/X58A-UD7, BIOS F2 11/10/2009
    [75712.030171] RIP: 0010:nfserrno+0x44/0x4a [nfsd]
    [75712.030172] Code: c0 48 83 f8 22 75 e2 80 3d b3 06 01 00 00 bb 00 00 00 05 75 17 89 fe 48 c7 c7 3b ba 1a a0 c6 05 9c 06 01 00 01 e8 8a cc ea e0 <0f> 0b 89 d8 5b c3 48 83 ec 18 31 c9 ba ff 07 00 00 65 48 8b 04 25
    [75712.030203] RSP: 0000:ffffc90001267df0 EFLAGS: 00010286
    [75712.030205] RAX: 0000000000000000 RBX: 0000000005000000 RCX: 0000000000000007
    [75712.030206] RDX: 0000000000000000 RSI: ffff880199216470 RDI: ffff880199216470
    [75712.030207] RBP: ffffc90001267e40 R08: 0000000000000003 R09: ffffffff82213400
    [75712.030209] R10: 0000000000000567 R11: 000000000001ba1c R12: ffff88019312d008
    [75712.030210] R13: ffffffffa01ab6d0 R14: 000000000000001c R15: ffffffffa01ab2a0
    [75712.030212] FS:  0000000000000000(0000) GS:ffff880199200000(0000) knlGS:0000000000000000
    [75712.030213] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    [75712.030215] CR2: 0000154eab4fa690 CR3: 000000014a0d8000 CR4: 00000000000006f0
    [75712.030216] Call Trace:
    [75712.030223]  nfsd_open+0x15e/0x17c [nfsd]
    [75712.030228]  nfsd_commit+0x5a/0xbf [nfsd]
    [75712.030233]  nfsd3_proc_commit+0x65/0x69 [nfsd]
    [75712.030238]  nfsd_dispatch+0xb4/0x169 [nfsd]
    [75712.030249]  svc_process+0x4b5/0x666 [sunrpc]
    [75712.030255]  ? nfsd_destroy+0x48/0x48 [nfsd]
    [75712.030258]  nfsd+0xeb/0x142 [nfsd]
    [75712.030263]  kthread+0x10b/0x113
    [75712.030265]  ? kthread_flush_work_fn+0x9/0x9
    [75712.030268]  ret_from_fork+0x35/0x40
    [75712.030271] ---[ end trace 1687ae2bf8531519 ]---

     

    tower-diagnostics-20180925-0719.zip

    Sep 25 05:15:25 Tower nginx: 2018/09/25 05:15:25 [error] 12237#12237: *212936 readv() failed (104: Connection reset by peer) while reading upstream, client: 192.168.0.203, server: , request: "POST /plugins/preclear.disk/Preclear.php HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "tower-int", referrer: "http://tower-int/Dashboard"

     

    Is this a preclear plugin incompatibility?

     

  12. 1 minute ago, Cessquill said:

    Unless I've misunderstood, you can get to the command line.  If you can, type diagnostics

     

    A diagnostics zip file will be put into your /boot/logs folder on the USB.  Reboot and get the file, or shutdown and put the USB drive into another machine to read it.

    Will try this later..I need to update to 6.6 again

  13. 20 hours ago, darkside40 said:

    Okay upgraded to 6.6.0 few days ago and have now downgraded to 6.5.3 again.

    Problem was that the server seemed to drop Network connection at a point. I simply was not able to access it anymore.

    Also had no Display here to check whats going on.

     

    I simply could not access it anymore, but it seemed that it did not completely stopped working. I had a parity check running one it happened and i saw all the light from the HDD drives flashing, but the Server was not accessable and i couldnt ping it.

    Sounds exactly like my issue. After I init 6 unraid it works fine again for a few hours then same issue...I have a pfsense vm that still works and routes traffic fine but no shares or dockers (example Plex) are accessible until I init 6 again

    • Upvote 1