forg

Members
  • Posts

    2
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

forg's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Thanks for the input all! I found some time this weekend to play with my networking setup – turns out you were right about the connectivity issues. What's odd to me is that I could access the server itself and all of my dockers that were running, but couldn't manage the dockers or Unraid updates. After I removed the new Mikrotik switch, I updated my dockers, and then Unraid to 6.8.2. Completed another parity check without issue after the update. My next step is to open everything up, and spread out my SATA cables. I'm also going to try to check the power connections – I think there's at least 2 that are stretched pretty tight, maybe that's causing issues as well. If things persist after that, I'll spend some money on a new set of SATA cables from a brand name, instead of using the ones that came with the motherboard. Thanks again!
  2. Hey all, first off just want to say that I love Unraid, and have been a long-time user & supporter. Just recently, I've started to experience a number of issues that I didn't believe were related, but as I've attempted to diagnose them, I'm coming to the conclusion that they are in fact all being caused by the same root issue. I've listed individual steps / symptoms in chronological sequence below: 1. My original server motherboard (an AsRock C2550D4I motherboard with integrated Avoton C2550) dies. 2. I order a Rosewill RSV-L4412 server chassis, and transplant my Unraid drives into the new case with some old gaming PC hardware to get my server online again (this hardware is what you see in the diagnostic report). 3. Everything runs fine for a while, parity checks show no issues with array. 4. Drives begin to show 'CRC error count' issues. I google, and see that as long as these values don't continue to tick up, I shouldn't be too concerned. I assume it's due to the SATA cables being in close proximity at the hot-sway bays in the chassis. 5. I return from a trip to see that a single older 4TB drive has failed (I unfortunately don't have specifics on what when wrong with the drive atm, although I could plug it back in and check it's SMART status if helpful), and is being emulated. I keep an eye out for deals, and order a replacement 10tb drive. 6. I plug in the new drive and do a pre-clear successfully without issue. I go to turn off the array so I can swap drives, but the webUI becomes unresponsive. It appears it's waiting for the disks to finish spinning down. I attempt to navigate to another page in the webUI, and get 'webpage unavailable' errors in my browser. The physical server is on still, and I haven't sent a shutdown command, but I can't access the webUI. 7. After waiting a good while, I do a hard shutdown of the server out of frustration. I swap the drives out while it's off, and boot it back up. 8. The server comes back up, I put the new drive in it's place in the array via the webUI, and let it rebuilt the array. It completes without issue. 9. I later go to my docker tab, and see that every single docker is saying it has an update available. That's odd... let's try updating one. I get this onscreen: Pulling image: binhex/arch-krusader:latest TOTAL DATA PULLED: 0 B Removing container: binhex-krusader Successfully removed container 'binhex-krusader' Command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='binhex-krusader' --net='bridge' --privileged=true -e TZ="America/New_York" -e HOST_OS="Unraid" -e 'TEMP_FOLDER'='/config/krusader/tmp' -e 'WEBPAGE_TITLE'='Tower' -e 'VNC_PASSWORD'='' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -p '6080:6080/tcp' -v '/mnt/user':'/media':'rw' -v '/mnt/user/appdata/binhex-krusader':'/config':'rw' 'binhex/arch-krusader' e3fbc4748d02fcc092b2ba33a4f37093e73bd0c5a42cf4cb5dab3e78c74ea528 The command finished successfully! 10. Hmm, I'm also noticing that dockers like Plex are having issues accessing the array: "Conversion failed. A required codec could not be found or failed to install." 11. I randomly attempt to load the Community Apps page. Hmm: Download of appfeed failed. Community Applications requires your server to have internet access. The most common cause of this failure is a failure to resolve DNS addresses. You can try and reset your modem and router to fix this issue, or set static DNS addresses (Settings - Network Settings) of 208.67.222.222 and 208.67.220.220 and try again. Alternatively, there is also a chance that the server handling the application feed is temporarily down. You can check the server status by clicking HERE Last JSON error Recorded: Syntax error 12. At this point, I'm wondering if my appdata has been corrupted. I run some SMART tests, but they're all coming back clean. The only issue across my drives are those CRC error counts. 13. One last attempt – why don't I update Unraid itself just to see if that fixes something. Go to the Update OS page. Click "Check for Updates", hmm, tells me no updates are available. I'm on 6.7.2, so I know that's wrong. 14. Restart the server again and try starting up Docker / loading Community Apps / Check for Updates again. Same behavior. Now there's not even a "Check for Updates" button, and the status of 6.7.2 is listed as "Unknown". That brings us up to now. I'm currently running another parity check, and am 21.6% complete with 0 corrected sync errors, for what that's worth. I've attached my diagnostics file. I'm at a loss as to how to proceed / diagnose the issue. Is this one issue with my storage? Is it a storage issue combined with some misconfigured network setting? Should I be concerned with the CRC error counts? Can I prevent them with better SATA cables? Are shielded SATA cables a thing? TL;DR: 1. I occasionally get a CRC Error Count message. 2. Single drive in array died. 3. Server didn't shut down cleanly while turning off system to swap drive. 4. Server reboots, new drive is added to array, all is good. 5. Docker containers start insisting they all have updates, but updates fail. 6. Docker containers stop functioning. 7. Community Apps page stops loading. 8. Unraid fails to check for updates. I appreciate any help. Happy to answer any questions - hoping this is something stupid I'm just missing. Unraid 6.7.2 2019-06-25 Plugins: CA Auto Update Applications - Version 2020.02.13 CA Backup / Restore Appdata - Version 2017.10.28 CA Cleanup Appdata - Version 2019.09.15 Community Applications - Version 2020.02.13 Preclear Disks - Version 2020.02.13a Statistics - Version 2017.09.22 octo-diagnostics-20200221-1431.zip