poopsie
Members
-
Joined
-
Last visited
-
What is even more odd is I have created new USB's for 6.8.2, 6.8.3 and 6.9.0, and it does it on all of them. My old USB that had 6.8.3 did not do it. But when it died, I moved to this one and it does this now.
-
I wanted to see if this was an expected behavior or a bug before I submit a report. When I go to the VM Settings, even if I do not make any changes at all, I get the banner from that point forward as seen in the picture. It happens the second I click the VM Settings icon, like I said, without changing any of the settings at all. It is really annoying to look at a setting for something, and have to reboot the server to clear the banner. Thoughts?
-
Under 6.7.2, I installed Server 2016 and Server 2019 VM's with no issues. I then upgraded to 6.8 RC3. Immediately noticed that my VM's no longer boot, giving me an error seen in the screen shot included with this. I then upgraded to RC4, with the same results. After doing some research it looked like maybe I had bad RAM. I ordered brand new RAM, different brand, same amount, and installed that. Same error booting the VM. I down graded back to 6.7.2 and the VM's boot up fine. I did try reinstalling both VM's while using 6.8 RC3 and RC4, same result-No boot. The screen shot included was pulled from the web, I did not snap one before I downgraded.
-
That is why you are the best Squid-Thanks!!
-
Gotcha, so the next question then is how are those backed up? Is it on the flash drive? What I am wondering is if I delete a Docker, how will I know it will have all the information when I reinstall it 3 years from now?
-
I have searched, and must be missing something. When I install a docker item, it used to ask me what template I wanted to use in the edit screen. That is no longer there. Did it get removed or moved to some other place? Yes I do have Community Apps installed- Thanks!!
-
I am not sure what I am doing wrong. When I have an SMB setup in UD, it works great. No issues. But, if the NAS I have it connected to is shut down, and UD can't find it, it freezes up unraid and will not clean shut down meaning a hard shut down. Is there a time out or does it just keep trying to connect indefinitely? Thanks!
-
Awesome!
-
I made this quick video, see if your stuff looks like mine CP.mov
-
As weird and easy as this sounds, and I say this from experience as I had the same issue when first installed. Have you clicked on the word "ROOT" to see if it expands? It doesn't look like it should, but it will.
-
Good, then you will have no problems. I set my /mnt/user to the storage, then in CP I choose what I want to backup. The only other thing I found earlier in this thread is to recover the files back to original location, you need to go to advanced view in the docker settings. Then click edit next to storage, and change it to RW, instead of read only.
-
Have you setup Dockers before? If not, I would go to Youtube and search for Space Invader 1 videos about Unraid. He does a few Docker ones in there, and once you have a the hang of doing them, they are easy. You will need to map your users/drives (Whatever you are backing up) to the Storage location when you edit the docker. Then, once you open Crashplan and tell it what you are backing up, you select "Storage" and you will see your drives/shares under that. Like I said, if you have not done this before, what I just wrote won't make a lot of sense.
-
You have nothing to worry about, it will resync everything when you readopt. You may need to log out, and log in again so it can readopt everything. I have done that a few times, and have never had to reupload my stuff. It will start out slow and look like it is reuploading, but after indexing is done, it will cruise pretty quick after that.
-
Ahh, there it is. Is there a reason that it is Read Only? Or is it safe to turn it to RW?
-
How do you all handle file restores? I tried one and it will not restore to orig file location, so it has to dump the restores to a folder I chose. Is this how everyone does it? The only issue is is if I do full restore, I have to dump it to the restore folder, then copy it back to orig location. With 3TB of data, that would double my restore time.
