GumGum

Members
  • Posts

    16
  • Joined

  • Last visited

Converted

  • Gender
    Male

Recent Profile Visitors

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

GumGum's Achievements

Noob

Noob (1/14)

1

Reputation

1

Community Answers

  1. The errors kept coming back and I was able to identify the root cause as a memory issue. Once I ran memtest on both modules, both showed multiple errors. Waiting for my replacements from GSkill. Hope that helps other folk who have faced something similar.
  2. I started it up in maintenance mode and ran a 'check' on the cache pool. This showed that there were errors, so I ran a `--repair` on it. That seems to have fixed the issue. I then ran a scrub and there were no errors. Will try to reboot back into normal mode and see if everything works. If everything gets back to normal, I will most likely move everything off the cache and reformat it to ZFS.
  3. I have attached the diagnostics file. I noticed that I could not start any docker container. Restarting docker failed. Docker won't start after reboot Logs indicate that cache has switch to read-only mode. Please help! apollo-diagnostics-20231221-2042.zip
  4. It looks like it auto updated last night and now I am getting this error. Unable to find image 'stashapp/stash:latest' locally docker: Error response from daemon: manifest for stashapp/stash:latest not found: manifest unknown: manifest unknown. See 'docker run --help'. Looks like someone forgot to tag `latest` to the new version.
  5. Love your videos SpaceInvaderOne. I want to pass the disks directly to the VM. But I am unable to get TrueNas to install. I followed your steps, but keep getting the below error. It keeps going to these retries and eventually fails saying there was a page fault.
  6. I had the same issue today and had to delete the nvidia-driver folder from the plugins folder on the flash drive. That fixed the issue. More details here
  7. I fixed it by deleting the nvidia-driver folder from the plugins directory in the Flash disk. After reboot, it downloaded and installed the latest version.
  8. Yup. Tried again and same result. See screenshot.
  9. Nope. Still gets stuck at the exact same place.
  10. Stopped the array and disabled/enabled SMB. apollo-diagnostics-20210811-1628.zip
  11. In safe mode I am able to access the webUI. And I have also able to start the Array up. But no plugins are running. I can see all my shares. When I boot in normal mode, I cannot get to the webUI and all I see on the console is the samba share starting part and it was like that all day today for about 4 hrs.
  12. I rebooted by NAS today morning and it is currently stuck at the starting samba level. I tried again in safe mode and downloaded the diagnostics. But its still stuck. The only thing I can think of that changed was I got a notification that the nvidia driver was updated and figured the reboot would switch the driver to the latest. Not sure if that is the issue though. apollo-diagnostics-20210811-1432.zip
  13. I copied all my data out of the shares and then re-created the shares and it worked.
  14. I can access the share just fine, but some folders and files with the share show that error message above. Other files within the same share can be accessed just fine. I will try to see if I can use krusader to copy the files out. Then I could just delete the share and start over.