UUB86

Members
  • Posts

    7
  • Joined

  • Last visited

About UUB86

  • Birthday 01/18/1986

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

UUB86's Achievements

Noob

Noob (1/14)

0

Reputation

  1. I'm also running into the exact same problem with unraid 6.6.6. I'm passing through an ssd directly to the VM(I'm also passing through a GPU if that matters). For me I set up a brand new VM and am using OVMF as my bios for the VM. I can restart the VM however once I shut down the VM, I won't be able to start it again because of the above error. Before shutting down, the VM works fine and there is no indication that anything is wrong. With my previous VM I was doing roughly the same thing the only differences being seabios and a different gpu. Could the bios be causing this issue? I was using a radeon gpu but I upgraded to an nvidia gpu and I was hoping to not have to reboot unraid every time the VM needs a reboot. I've been struggling with this since last week and this seems to be the first related forum post that I could find. If anyone has any ideas I would appreciate it. If needed I can provide more logs/vm details once I get home from work.
  2. That script didn't help. Maybe it serves a different purpose, I didn't feel like re reading that forum. It only appeared to do a rm -Rf on the given directory and then unmounting the docker image. Here's what I did to get my docker working again. I unmounted the docker image and then I deleted the image. Then I uninstalled the docker plugin from the web ui. I then restarted the server. When the server restarted I was able to make new containers using some of the "my" templates in order to get the container configured exactly as it was before. After doing this with my plex I didn't need to rescan my libraries since all of that was saved in my appdata folder. All of my containers are back up and running now and I have plenty of space available on the image. This is probably more of a workaround rather than a solution.
  3. Hi, I got the same error you did. INFO[0000] [graphdriver] using prior storage driver "btrfs" INFO[0000] Listening for HTTP on unix (/var/run/docker.sock) FATA[0000] Error starting daemon: Insertion failed because database is full: database or disk is full If you run df -h you should se a list of directories and space available. For my case, the docker image was 100% full. /dev/loop0 15G 14G 0 100% /var/lib/docker I was pretty perplexed but after a little googleing there appears to be a bug with docker not properly destroying btrfs subvolumes after a container is destroyed https://github.com/docker/docker/issues/9939. I did a little poking around with this: ls -a /var/lib/docker/btrfs/subvolumes I saw that it was filled with a bunch of stuff so I did this to see exactly how much is in there: du -sbh /var/lib/docker/btrfs/subvolumes The command took too long to run, I wasn't sure what was going on with it. I took off the s option so I could see what the command was doing, there appears to be hundreds of files in there. Docker apparently hasn't fixed it yet but somebody wrote a script to safely clean out that directory https://github.com/docker/docker/blob/620339f166984540f15aadef2348646eee9a5b42/contrib/nuke-graph-directory.sh. I'm going to try running that script now, I'll let you know how it works out.
  4. If you access remotely through splashtop or teamviewer you can edit the resolution. I can access catalyst control center through splashtop.
  5. Looks like I'm returning my card. Luckily there are a few good deals on graphics cards today. I guess the solution is to not use an nvidia card if you don't have access to secondary graphics.
  6. Ugh, do you think there is any way I could get it to work? I guess I should have researched the card a bit before I bought it.
  7. Hello everyone. I've been using Unraid for a few years now. I just recently had a chance to test out pci passthrough with my radeon hd 6750. I went into my bios, I enabled iommu and as easy as that I was able to pass it through and start streaming games from a Windows 10 vm. I decided to upgrade my video card to a gtx 960(Specifically: http://www.newegg.com/Product/Product.aspx?Item=N82E16814500380). I have tried installing this thing onto a Windows 10 vm in multiple ways with no success. After a little searching through the forum I found this, http://lime-technology.com/forum/index.php?topic=42186.msg402181#msg402181. This persons solution was to switch to onboard graphics in the bios. Unlike this person my motherboard doesn't have onboard graphics and the alternative is to use a legacy pci graphics card...but the gtx 960 covers that port. However I'm holding out hope that this isn't my problem because as I mentioned before my radeon 6750 worked without issue. -I tried installing with vnc enabled(seabios and ovmf). After a driver is installed for the gtx 960 and I reboot the vm, it no longer boots up. -I used the vm with the radeon hd 6750 installed and upgraded the graphics card. I'm able to reboot the vm but the video card is never properly recognized by the os. -I'm unable to install without vnc because nothing appears on my monitor after starting the vm(seabios and ovmf). -I've tried using an image stored on my cache drive as well as an array drive. Please let me know if you need any additional information. Any help would be greatly appreciated. home-diagnostics-20150129-1443.zip