PrisonMike

Members
  • Posts

    21
  • Joined

  • Last visited

Recent Profile Visitors

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

PrisonMike's Achievements

Noob

Noob (1/14)

2

Reputation

  1. Worked for me! Thanks man!!! I had to replace a corrupted SSD and this worked flawlessly.
  2. Hello, thanks for the help! Since I have a pool of two cache drives, can I remove the bad one and run the server off of a single cache drive until I can get a new drive?
  3. Hello, after trying to run a SMART extended test on CACHE 2 I get the following error "Errors occurred - Check SMART report" please find the smart report attached. Thanks for your assistance. poseidon-smart-20230202-1944.zip
  4. Hello @trurl, thank you for your response. I do not see any errors in pool devices. It looks like my log file keeps filling up after a few days. Here is a diagnostic file, request about 8 hours after a reboot. poseidon-diagnostics-20230130-2030.zip
  5. Hello, here is a copy of my diagnostics attached to the post. poseidon-diagnostics-20230127-1130.zip
  6. Anyone have any suggestions? Did I post the wrong diagnostic? I'm really not sure what to do at this point is my server even salvageable?
  7. Hello, unfortunately I am writing because I am having several problems with my unraid server. About a week ago, I was checking the GUI and noted that the cpu was pinned at %100. I waited for a day and checked again. It was still at %100. I tried rebooting and noticed that the cpu wasnt pinned when the docker service wasnt running. So I concluded there was maybe a problem with a docker. I updated some dockers that needed updating but the problem still persisted. In addition I was now not able to access some of my dockers such as sonarr, radarr, prowlarr. But some of my other dockers like audiobookshelf and mealie worked fine. Continuing on, I decided to update unraid to 6.11.5 from 6.9.2. Once I updated the OS nothing different happened. I normally use unraid with a static IP but I noticed that somehow unraid was reporting a mac address to my router (unifi) that the mac address was different but it was still using the same IP (192.168.1.5). So it seemed that unraid was somehow using two different mac addresses and they were both trying to use 192.168.1.5. So I switched to automatic DHCP un unraid and assigned the origional first mac address that I know is the mac for the adapter as 192.168.1.5. That seemed to work and I'm not having the address problem. However, I still could not access the dockers that I needed. So I figured I would delete one and try to reinstall it with unraid backup/restore. That didn't work so i resorted to deleting the vdisk. After deleting the vdisk I restarted the server. After a restart i got an error that the docker service couldnt be started. I looked for other solutions and some said they get this error when the vdisk is too full, so increased the size to 100gb (was 50gb). That didnt work either. I deleted the vdisk (btrfs) several times and cycled the server to no avail. I also tried switching to xfs, which didnt work either. In a final hail mary I rolled the server back to 6.9.2 via the GUI and I am still stuck. I also tried deleting the vdisk and switching to xfs and that didnt work. So I guess the first issue is figuring out why the docker service wont start. Once I figure that out, I can see what was pinning my CPU if even it is docker. Here is a link to the diagnostics: https://www.mediafire.com/file/n2gh16l3fb53xbu/poseidon-diagnostics-20230121-1955.zip/file
  8. Hello all, I am now getting a new error in my logs when I try to start the container. Please see my pastebin link for the logs
  9. Hello, I am still experiencing the same problem unfortunately. For what its worth I cant reach my USG on the same network at 192.168.1.1 either.
  10. Thanks for the reply! I have restored several times and I am still getting the same error!
  11. Well yes, but actually no. My server is 192.168.1.5 and I have unifi docker running on 192.168.1.2 so that shouldn't matter right?
  12. Hello, I had the same problem about a month ago. I just shut the docker container off and forgot about it until recently. When I fired up the docker again, I couldn't reach the web GUI for some reason. I deleted my app data and downloaded the container again just to be safe (twice). And I still cant reach the web GUI no matter what I do. This is very frustrating as I have been wanting to upgrade my APs. If anyone has an idea, please let me know. Thanks! LOGS
  13. Hello, I am experiencing some issues with unraid lately. The primary problem is that my plex server (container) will show as unavailable on devices that I've shared the server with. Not sure what the issue is but I've tried to restart the container and then that hangs up in the gui and does nothing. So I try to restart the entire server via web gui and that also hangs. The only way to fix it is to go to the server and do a physical reset on the server. I'll post my info below. Unraid OS 6.9.2 Motherboard: Intel DQ87PG, Version AAG74154-401 Version PGQ8710H.86A.0030.2013.0403.1355 BIOS dated: Wed 03 Apr 2013 12:00:00 AM PDT Processor: Intel Core i5-4670K Please know that I am not very knowledgeable about linux/docker and I have not collected any logs yet.