GumGum
-
Posts
16 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by GumGum
-
-
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.
-
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!
-
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.
-
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.
-
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
-
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.
-
1
-
-
Yup. Tried again and same result. See screenshot.
-
Nope. Still gets stuck at the exact same place.
-
Stopped the array and disabled/enabled SMB.
-
2 minutes ago, trurl said:
You don't seem to have config/shares.cfg on flash. Can you access the webUI? You might try going into Settings - SMB and setting it up again.
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.
-
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.
-
I copied all my data out of the shares and then re-created the shares and it worked.
-
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.
-
1 hour ago, trurl said:
Post diagnostics
Attached.
-
Hi everyone, I am currently getting this error when I try to browse folders within a share. Anyone have any idea what is going on? I can see the files if I browse through the unraid UI or using krusader. But I cannot open the folders in windows (I can access some of the files in the share though)
This is happening to just a few folders and not all of them.
Some background
I have been testing unraid on a test computer and some hard drives using the trail license and was experimenting with all the features. For the last 2 months though the system was powered off and the trial license had expired. This week I ordered new parts for my new unraid server and wanted to try a few things on the test system again. Now since the trial had expired, I re-imaged the usb and started fresh (again using the trial license).
After booting, the hard drives were already in the previous configuration and ready to be started. So I did. It rebuilt the parity but all the files were still present. When I accessed the share, I can see the files, but can access only a few of them and keep getting the above error.
The data is not important, but was just curious on what is going on.
Cache mounting as read-only. Need help
in General Support
Posted
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.