01111000

Members
  • Posts

    199
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

01111000's Achievements

Explorer

Explorer (4/14)

1

Reputation

  1. Great, thanks again. The cables are very old at this point so hopefully it works either way.
  2. Gotcha. Time to buy new cables for that backplane.
  3. Parity, SDZ and SDY are the problem disks right now. There are no smart warnings that I can see, only indication of something being wrong is the parity disk being disabled. Scrutiny doesn’t indicate anything either but I don’t know how it polls its data. This is a server running at my parents house, I no longer live with them and am usually not around due to my job. That’s also why it hasn’t been updated, I haven’t been around and have not had time to really sit down and work through any potential issues after the upgrade. This build has been particularly bulletproof throughout the years. Here’s the weird part of this, maybe related? The server is physically located on top of a cabinet, 6 feet or so above the ground. On the same day of this issue, the basement bathroom flooded this area. I’m thinking it’s possible that they bumped that cabinet a few times while dealing with this aftermath. I can’t tell for sure though. That’s why I’m asking for help, I was thinking about trying to reseat the cables but what would be the best way to determine this potentially fixed an issue? Or am I crazy for thinking this could be a cause? Thanks again for your help
  4. Well, duh. Sorry about that server-diagnostics-20240127-1604.zip
  5. Hey, it's been some time. Recently, I have a 3 drives, including a parity drive, report errors. How should I proceed at this point?
  6. Well, that was an id10t error. Thank you
  7. ugh, should've realized that. Attached server-diagnostics-20191214-1319.zip
  8. Recently upgraded to 6.8. I disabled Docker but am unable to re-enable it. The directory shows red and cache is not available in the dropdown. My cache drive is still accessible. Any ideas?
  9. He can actually use a P2000 for what he needs to do.
  10. Before I do any OS upgrades or major changes, I make a backup of my Flash drive (I know I did for the 6.4 and 6.4.1 upgrades). If my backup does have these template files, can I simply drag it back over, restart docker and be good to go? I really appreciate the help guys.
  11. These Dockers were setup a while back (over a year), using Community Apps. When I went to 6.4, I did end up reinstalling some of my plugins, this is likely the cause. What would be the easiest way to fix the issue- recreating each docker container? Just threading as lightly as possible as I don't want to have to reconfigure everything from scratch. lol, I didn't know what to put as my username so I went with x since it's a variable and can be anything.
  12. I know this is probably a simple fix, but all of my Dockers that I've had installed on 6.3 give me this error when trying to upgrade it on 6.4. Fix Common Problems is unable to fix the issue (Template URLs are missing). What is the easiest way to fix this issue; I'm not sure where to add the missing information.
  13. AKR- with the new 6.4 release, Unraid’s GUI is utilizing 443. You will need to change that to 442 or something similar and forward the ports as needed.
  14. I had the same issue. I tried rebooting but it did not work, so I ended up rebooting via IPMI. The next restart it was stuck on Mounting Drives. Still stuck trying to shut down.
  15. Having a few issues, and my log file is from 6.3.5. First off, the after downloading the upgrade, I was unable to reboot or shutdown the server via the webgui. It went through the motions as if it was shutting down but it remained in the Array Offline state. I ended up restarting the server via IPMI which worked. After it came up as 6.4, it was stuck on Starting Services on the bottom left. I left it running for at least 30 minutes and the status never updated. My docker containers were running as if the array was fully functional. I ended up hitting Shutdown via the webgui and was stuck once again, so I rebooted via IPMI. On the next reboot, I was stuck on Mounting disks (for over 30 minutes) and I hit shutdown via the webgui. I am now stuck once again, here's what I see via IPMI. The most recent log on the Server was from 6.3.5 and it has not saved any new logs since the upgrade. How should I proceed? server-diagnostics-20180113-1956.zip