Jump to content

luisv

Members
  • Content Count

    177
  • Joined

  • Last visited

Everything posted by luisv

  1. Upgraded this morning; for now, I left C-State disabled... waiting for the next BIOS update.
  2. Interesting... at least that was a rather quick response. Maybe a tweet about expanding the team of one to at least two is in order?!?
  3. No, not a crash / hung state with C-State disabled... only seen a memory error when the system was on rc7a: https://forums.lime-technology.com/topic/59024-unraid-os-version-640-rc7a-available/?page=6&tab=comments#comment-600394 The 20 day remark was the longest uptime I have experienced thus far, but it was because I restarted the system to upgrade the BIOS.
  4. The system froze a few hours ago and I couldn't SSH nor log in via the console, so I had to perform a hard reboot. Upon reboot I disabled C-State. With C-State enabled, the longest uptime was around 2 days, with it disabled, it was 20 days and 11 hours... I restarted the system due to a BIOS upgrade. If anyone wants to see a diagnostic file or if they feel I should upgrade to RC13 please let me know.
  5. Just noticed this error today... any ideas? It happens over and over and over...
  6. Thanks for the explanation! Any thoughts on why the system keeps freezing with C-State enabled as the fixes are supposed to be incorporated into the current RCs? Current uptime is 1 day, 18 hours, 50 minutes.
  7. Not sure, but it's been frustrating for sure... especially when I forget to disable C-State after a BIOS upgrade and find the system hung two or so days later. When I checked console access, it was also hung, so I needed to perform another hard reboot. I left C-State enabled. Once at the log-on prompt, I noticed the following line: 192.168.1.0/24, dev br0 proto kernel scope link src 192.168.1.10, linkdown However, after the reboot the web console, all dockers, VMs and shares have been accessible. Uptime is 21hrs and 23mins. With C-State enabled, prior lockups occur around the 2 day mark. So needless to say, I'm very confused as the console shows linkdown, but it's obviously up.
  8. Sure @Tuftuf, I'm all for trying to figure out what the issue is as I feel disabling C-State is just masking the true underlying issue and as always, thanks for your help! The system hangs started around August 14th, a few days after the system was originally built; however, here's a run down of system changes after the initial build. System details are in my signature: Added Intel PRO/1000 Dual Port Server Adapter on August 23rd Added the final WD Red 4TB HD on October 22nd I migrated from a 4 year old Synology NAS and during my initial testing found read / write speeds were horrifically slow. Since my Synology had dual NICs and was bonded (I have managed switches), I purchased the above adapter to try and compare apples to apples. I was initially trading PMs with @Tuftuf as he had a Ryzen system and ran 2 dockers I was interested in running... Plex and the Unifi controller, so he received the brunt of my frustrations. After numerous tests, playing with network settings, enabling turbo write, disabling spin down, etc. I was able to achieve similar speeds between unRAID and the Synology NAS. November 3rd I had a memory error. After posting in the forums, it seemed to be related to Plex so I upgraded to rc10b. Memory error hasn't happened since. https://forums.lime-technology.com/topic/59024-unraid-os-version-640-rc7a-available/?page=6&tab=comments#comment-600394 While writing this, I was notified that my Unifi Video docker is not reachable. The unRAID console is not resolving via the browser; yet, I'm able to play a movie via Plex; both remotely and locally. I can resolve to the Plex console and other dockers via IP:Port, but the unRAID console is not reachable via IP nor DNS name. I can't SSH via IP, but I'm able to log into the console locally. Before the logon prompt, it shows the following: default via (IP of DHCP server) dev br0 metric 209 linkdown (Subnet range) dev br0 proto kernal scope link src (IP address of Server) linkdown I kicked off TimeMachine backups on 3 Macs and all are working fine. From Windows and Mac systems I'm able to browse shares on the unRAID server via DNS name and IP. So I'm confused to say the least... any help is appreciated. *** Edit - Forgot to mention, the system is on the lates BIOS 1201.
  9. Unfortunately the system hung this morning, console was not responding nor could I SSH to the system, so I needed to perform a hard reboot. Besides a reported memory error message, seemed like a Plex issue and that was only experienced once since August, if I leave C-State disabled, the system is rock solid. I see that c11i was released... thoughts anyone?
  10. I was originally looking at the Arc 2 Midi, but then decided on the R5 as I felt that over time, dust would make it's way into the case due to the design of the mesh top. mATX vs ATX decision... I felt the extra slots, ports, etc usually included with ATX boards was worth the slight cost difference for future growth and or repurposing reasons, but neither decision is wrong. I have a mITX in my Win10 workstation and love the small form factor. If you're in the US, holiday sales are around the corner and or local stores might provide combo discounts.
  11. Asus posted an updated BIOS, so I just updated it and left C-State enabled. I'll report back if my system locks up again.
  12. Since you're looking at mATX, are you trying to stay within a specific footprint or case?
  13. That has always been my issue... unless C-State is set to disable, my system freezes. I've always updated the BIOS when new updates were available, but now that this setting has been uncovered, I'll give enabling C-State a try again.
  14. Do you have C-State enabled? Only way I've been able to keep the system stable is to keep C-State disabled; however, I recently added the appropriate lines of code to the Syslinux configuration , so please let me know regarding C-State.
  15. The system has 32GB of ram. Mine was originally set to 10 and 20, so I changed it to 5 and 10... should I go lower? Although I read the thread, I'm not sure what to initially set it to.
  16. Thanks for looking at the diagnostic file. I'll comb through the Plex logs, but as per PlexPy, there wasn't any content activity during 11/1 at all. Interesting...
  17. Understood... hopefully the diagnostic file I posted will be helpful.
  18. Diagnostics attached. Just upgraded and error is gone. davault-diagnostics-20171103-2053.zip
  19. Not sure where to post this, but I just updated a couple of plugins as well as some dockers. I ran the Fix Common Programs plugin and it displayed the following error: Your server has run out of memory, and processes (potentially required) are being killed off. You should post your diagnostics and ask for assistance on the unRaid forums However, I'm seeing that the server shows plenty of free memory... any ideas?
  20. That's what I thought I needed to do and yes, that is the new drive I added. It's formatted and showing properly as part of the array now; however, it's showing under the Unassigned Devices section, Historical Devices as missing... should I remove the config or is there something else I need to do?
  21. My unRAID server has been operational since August and I just purchase another drive to add to array. After I ran the PreClear utility on the new drive and it passed all tests successfully, I tried adding it to the array, but it's showing as Unmountable. See screenshots below. I assume, I simply click on "Yes I want to do this" and then Format the drive, but I want to make sure I'm doing the right thing as this is the first time I added a new drive to an existing array.
  22. After updating the Unifi-Video docker this morning, my cameras were stuck in a managing state. I did a little research and based on the released notes for 3.8.0, it looks like folks will need to add another port or update the port list to the docker properties. https://community.ubnt.com/t5/UniFi-Video/NVR-3-0-8-Cameras-stuck-in-quot-managing-quot-State/m-p/2068710#M86596 https://community.ubnt.com/t5/UniFi-Video-Blog/UniFi-Video-3-8-0-Release/ba-p/2067768