• Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by wreave

  1. This build has appeared to clear up my issues, thanks!
  2. Does this plugin's CLI commands still work? I'm on 6.8.3 and a parity.check pause does not seem to be working.
  3. Just updated and it's all up and running. Thanks so much!
  4. This appears to be the same issue that I mentioned here: Looks like the OOT driver for these NICs might not have made it into this build of Nvidia Unraid.
  5. Is it possible there was a regression for the RTL8125 driver in the Unraid Nvidia 6.8.1 build? I am running into the identical issue I had on the 8.8.0-rc5 build. Reverting to Unraid Nvidia 6.8.0 has my NIC working correctly again. Thanks again for all the work put into this project.
  6. I love how easy it has been to convert friends and co-workers to unraid. SSD array support would be nice.
  7. I can confirm the RTL8125 driver is working now. Thanks!
  8. Awesome to hear. Looking forward to the release.
  9. The Realtek RTL8125 (driver added in 6.8.0-rc2) does not work on Nvidia Unraid 6.8.0-rc5. I have a full break down of tests and diagnostics over on this thread. Any insight here would be appreciated as I really would like to be able to continue using the Nvidia builds. The summary is that the RTL8125 works on both stock Unraid 6.8.0-rc5 and rc7 but it fails to work on Nvidia Unraid 6.8.0-rc5.
  10. So after a bunch of tshooting this morning with Unraid versions here is what I've found. The onboard RTL8125 NIC works in both stock Unraid on rc5 and rc7. The USB NIC I was testing with (ASIX Electronics Corp. AX88772) does not work on rc5 or rc7. The exact opposite is true for the Nvidia Unraid build. When testing on rc5 the RTL8125 does not work while the AX88772 does. All of this was using the same cable on the same switch port. Looks like I'll need to reach out on the Nvidia Unraid plugin thread about this issue. Odd that the USB NIC wouldn't work with stock Unraid though.
  11. I know the RTL8125 driver was added in 6.8.0-rc2 but it appears to not be working correctly on rc5 (currently using Unraid Nvidia build). Problem: - Network connectivity fails to establish - Device connected to Unraid machine auto negotiates to 100 Mbps - Unraid auto negotiates to 10 Mbps - No network traffic appears to correctly pass. (For example DHCP process does not complete) Troubleshooting: - Connected Unraid machine to a router, a switch, and directly to my desktop PC NIC. All devices connected to the Unraid machine show a 100 Mbps connection while running 'ethtool eth0 | grep -i speed' directly from Unraid shows 10Mb/s. - Using a USB NIC I had lying around (100Mbps) everything works as expected at Diagnostics were retrieved by running 'diagnostics' directly on the machine and grabbing the resulting file. Please let me know if there is other information I can gather. Edit: Also note they before switching motherboards I was using a 1 gig NIC without issue. So it's shouldn't be a hardware side issue (that's part of the reason I also tested connecting directly to a PC). supremacy-diagnostics-20191125-2014.zip
  12. Fix Common Problems is recommending I post my diagnostics on this particular issue. For context the USB stick had died which was then replaced and a parity check was run. I woke up to the warning. Any insight is greatly appreciated. tower-diagnostics-20191120-1414.zip
  13. Unraid was the best thing to happen to my server! Looking forward to future features.
  14. That's too bad, I'll trial out the traditional troubleshooting as requested. Thanks!
  15. My parity drive has gone disabled and reported a read error, I am not able to see what might have caused this. I had a similar issue previously but wasn't able to get the logs at the time. This has only happened with my parity drives, both are on the same SATA connector as the first 2 data drives so it seems odd that only the parity drives have had issues. Diagnostics are attached. Drive is sdi. Let me know what else I can provide. supremacy-diagnostics-20181105-1557.zip
  16. I am on the 6.6.0-rc1 build and I cannot seem to acknowledge or ignore the unclean shutdown warning. It acts like it worked until I refresh the page and it is still there. Nothing in the Chrome console when I click the buttons. Edit: I've also tried clearing the cache and all that fun stuff.
  17. Struggling with an issue around htpasswd, no matter what I do the auth fails. Here is my latest test I tried - Create plaintext .htpasswd for testing root@1f99f655951c:/config/nginx$ htpasswd -cpb .htpasswd test test Warning: storing passwords as plain text might just not work on this platform. Adding password for user test - verify .htpassword root@1f99f655951c:/config/nginx$ cat .htpasswd test:test - test the user:pass (with inline password and without) root@1f99f655951c:/config/nginx$ htpasswd -vb .htpasswd test test password verification failed I've gone as far as running chmod 777 .htpasswd, nothing seems to fix this. Anyone have any ideas?
  18. What is your reasoning behind this? I haven't added a drive to unRAID that wasn't precleared in a long time. Ignoring the benefit of putting extra stress on the drive to detect early failures does unRAID handle non-precleared drives better with more recent versions? Before if I didn't preclear a drive my whole array would be offline until the new drive was processed, which could take a long time for larger drives.
  19. My understanding is that this is unlikely to happen since there is no indication that any one group/person will provide continued support for the plugin.
  20. Just as further confirmation that the patched plugin works I've successfully cleared 5 8TB hard drives with it.
  21. So I am trying to switch the validation from HTTP to TLS-SNI but I am getting an error Different validation parameters entered than what was used before. Revoking and deleting existing certificate, and an updated one will be created Generating new certificate Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator standalone, Installer None Obtaining a new certificate Obtaining a new certificate Performing the following challenges: Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA. Client with the currently selected authenticator does not support any combination of challenges that will satisfy the CA. IMPORTANT NOTES: - Your account credentials have been saved in your Certbot configuration directory at /etc/letsencrypt. You should make a secure backup of this folder now. This configuration directory will also contain certificates and private keys obtained by Certbot so making regular backups of this folder is ideal. ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the container I have made sure all my ports are lined up as well. Not sure what I am missing here. Any help is greatly appreciated.
  22. As I approach the end of my 2nd year using unRAID I've felt the need to express my mass appreciation to Lime Tech and the community as a whole. I started using unRAID in February of 2016. Issue after issue on my Windows Server build led to an eventual collapse of my 10 TB RAID array and the loss of all the data. At the time it felt pretty terrible as I stayed up late into that night trying to salvage what data I could only to finally accept there would be no salvage. Within the first 2 months of using unRAID I already felt like my server meltdown was the best thing that could have happened to me. Since then unRAID has provided tools to do powerful things easily and every issue I have ever had the community has resolved within days if not hours. I currently work at a computer network company and am happy to have evangelized the hell out of unRAID as I was the first person there to use it. We now have many who have done things from replacing their ESXi build, that was a more complex system than they needed, to running their server and desktop off the same machine to save on cost and space, keeping their spouse happy. So thank you Lime Tech for making a product that fuels my home server hobby and thank you to the community for making that hobby (mostly) stress-free.
  23. I am thinking this could have been related to when some disks had empty folder or folders containing a file that is exceptionally small. I'll try and do some more testing.