Acheron4171

Members
 View Profile  See their activity

  • Posts

    10

  • Joined

  • Last visited

 Content Type 

Everything posted by Acheron4171

  1. Acheron4171
    I wasn't able to save much of anything. Thanks for your help though. Reformat complete. Docker containers reinstalled using pre-existing templates. Reconfiguring containers and rebuilding VMs.
  2. Acheron4171
    Alright. I have disabled overclock. I have completely replaced the RAM. I try to scrub the cache pool but it immediately aborts. Fix Common Problems gives me the attached error. New diagnostics also attached. aperturescience-diagnostics-20230125-2018.zip
  3. Acheron4171
    Ah. I have since separated them, but my server used to host my gaming/work rig. Specs formerly dedicated to my gaming/work VM: 24 threads at 4Ghz (with the overclock) 64 GB of RAM 2TB SSD passed-through 3080 ti It ran my VR rig and everything.
  4. Acheron4171
    Will do. My new RAM arrives Wednesday. Out of curiosity, I had the CPU overclocked by 8%. I don't know if that overclocked the RAM as well. Could that have led to the RAM failure? I had pretty high-end RAM (G.Skill Ripjaws V Series) and it was only about a year old.
  5. Acheron4171
    Looks like I have a bad RAM stick. After I replace the stick, what then?
  6. Acheron4171
    I was running Unraid 6.11.1 and my Docker Service wouldn't start, with the quoted error. I upgraded to 6.11.5 and it started (some containers but not most). I disabled and re-enabled the Docker service and now the service refuses to start again (with the same quoted error). I have tried recreating the docker image file, to no effect. Please help. You'll find my diagnostics attached. aperturescience-diagnostics-20230120-0809.zip
  7. Acheron4171
    This was the issue. It is now resolved. Thank you for your help.
  8. Acheron4171
    Looks like I'm going to be waiting for awhile for the parity rebuild. I'll let you know the results, once that's done.
  9. Acheron4171
    Here is the requested diagnostics archive. aperturescience-diagnostics-20220623-2236.zip
  10. Acheron4171
    I have recently migrated all of my drives/dockers/VMs from Unraid 6.9.X (I don't remember what the last number was) to 6.10.3 Now, the array will not auto-start. I have enabled auto-start in the disk settings but it won't auto-start. Please help and please let me know if I can provide any info that can help. Regards, Ash