btrcp2000

Does anyone have any feedback at all on this? I have no idea where to begin, and it's just a matter of time before windows will update again. I now have a months old drive showing an offline uncorrectable error, running smart extended now. How could a VM updating/restarting be affecting the GUI?

Left it go all night but it never recovered, so I had to hard reset once again and it's now running a parity check. This time it came up with offline uncorrectable errors upon reboot. What should I be doing differently with these windows updates?

Happening again. Win10 wanted to update again, and I cannot reach the GUI or data on shares. Don't know about ssh because i can't remember the IP of the unraid server, and the router is a unifi running in the docker, which is of course also inaccessible. Does anyone have any insight?

Twice in the past several months my Win10 VM has wanted to update itself, last night was the big Fall Creators one. Both times the GUI became unresponsive, the shares disappear from the network, and I cannot get it to respond to Putty. Only thing I can do is a hard reset and parity check. Since I couldn''t get to the GUI or putty, the best I could think of is the attached "screenshot" (literally a photo of the monitor screen). Diags are from after the hard reset, not sure if that is helpful but I didn't know how else to get them before resetting. Up and running again with the VM successfully updated, so hopefully parity check goes well. Obviously I'm doing something wrong with these updates. How should I handle this in the future? tia unraid-diagnostics-20171208-0835.zip

Had to rebuild a Win10 VM and trying to figure out why my USB 3.0 controller card (click here for specs) is not working. Here is the USB Card that VM doesn't see, as well as the video card that it DOES see: Here is a Hauppauge Colossus that is working fine: Here is the XML where I have attempted to make the changes recommended in this thread: What am I not seeing? unraid-diagnostics-20171113-1125.zip

Disregard the part about recovering the one file, I was able to get into the .img file with 7zip. Would still like to know if there is anything to learn from the logs.

Win10 VM has been up and running for a while now without issue. Some things that rely on it were misbehaving so I rebooted it (VM not UNraid). I usually use Chrome Remote desktop to access it, but that wouldn't come up like it normally does, so I stopped it and rebooted again. It now doesn't come up at all and I cannot get into it with noVNC either as it will not accept the password. I am suspecting that it was in the middle of doing to the Creators Update (maybe even on the screen where it tells you not to shut off the PC) when I killed it, so I'm guessing the image is corrupted and I have to start over. Not the end of the world, but I thought I would throw it out here and see if anyone has any ideas. I thought that CA backup was covering the VMs too, but apparently not the case. There is only one file on the whole image that would be very nice to have back. Is there a way I can mount the disk image to try and get ahold of it? Here's the VM log, diag also attached: 2017-11-08 12:55:55.179+0000: starting up libvirt version: 2.4.0, qemu version: 2.7.1, hostname: UNRAID LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'guest=Windows 10-Sage Drivers,debug-threads=on' -S -object 'secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-1-Windows 10-Sage Driv/master-key.aes' -machine pc-i440fx-2.7,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/95548dcb-3a02-5498-1305-e592fc25308d_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 8192 -realtime mlock=off -smp 8,sockets=1,cores=4,threads=2 -uuid 95548dcb-3a02-5498-1305-e592fc25308d -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-1-Windows 10-Sage Driv/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -devchardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev 'socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-1-Windows 10-Sage Driv/org.qemu.guest_agent.0,server,nowait' -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device usb-tablet,id=input0,bus=usb.0,port=1 -vnc 0.0.0.0:0,websocket=5700,password -k en-us -device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pci.0,addr=0x2 -device vfio-pci,host=82:00.0,id=hostdev0,bus=pci.0,addr=0x6 -device vfio-pci,host=81:00.0,id=hostdev1,bus=pci.0,addr=0x8 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x9 -msg timestamp=on Domain id=1 is tainted: high-privileges Domain id=1 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0) unraid-diagnostics-20171108-0851.zip

IP address seems to have been the solution, which gives me an idea on some of my other issues too. Have a beer!

I am having issues with software on my Win10 VM seeming to lose sight of the UNRAID shares. Specifically a Playon recording directory and the SageTV Fanart directory, both of which seem to come and go. Sometimes win explorer finds and opens them, other times it complains of not enough resources. Server has 32GB and VM has 8gb. Can someone check these logs to see what my be happening? thanks! unraid-diagnostics-20171105-1355.zip

I recently moved my plex server from Win10 to the Docker. We didn't have a whole lot going on in terms of customized settings so I just setup from scratch, but I was informed that my daughter had created a bunch of playlists. I still have the older server intact, it just doesn't know where the media is anymore. Is there a way I can extract playlists to move to the Docker version?

I am attempting to use Hanewin to mount an NFS share that is hosted on a windows VM, that itself is hosted on Unraid. If I ssh into Unraid and use the showmount command, there share is visible, however I cannot get Unraid to mount it using Unassigned devices. The folks in that thread were very patient and responsive, but no luck figuring out why UD can't see it. Is there another way to mount a share using the CLI or something else? Reason I am doing this is because I have a tv tuner that will only run on windows, but it needs to accept instruction from Docker (sagetv). Docker wants to send the recording location in linux-speak, which the windows tuner cannot figure out. If I use an SMB path, docker prepends some linux path syntax before sending it to the tuner, making it unusable as well

Ok, thanks for the time you put in

Some of these were posted earlier, but here are all the settings of the Hanewin NFS Server that is installed on the VM. Also below is a screenshot of the firewall rule i setup to deal with the ports (although the firewall has been off completely while I'm working on this)

What is the difference then between UD being able to find the share on its own when I click Load Shares and not being able to mount it?

Still banging away on my NFS share issue. Per your suggestion above, I looked into the question of whether the Win10 VM (which is now static ip of 192.168.1.101) responds to a ping. The Error entries from the log below are when the WinVM's firewall is active. When it is shut down, that specific error goes away. Below that is an ssh session first with firewall on where showmount times out, and second with the firewall off, where it sees the share. Below that is the successful ping from UNRAID ssh. Since the ssh showmount command sees the share on the WinVM, it seems like there is an issue with the UD ping? This is with UD updated to 2017.10.30b

That was one of the first things I did: Back to having Unraid mount an outside NFS share, for whatever it's worth, here are the settings on the other end which again is a Win10 VM hosted on the Unraid server, using hanewin as the NFS server. Firewall is completely off for testing purposes, and I have tried checking/unchecking "Allow mount of remote devices":

If this is what you're saying, I think I've tried the "vice versa" approach before, having the Unraid share be the NFS server, and using windows as the NFS client, so I just tried again. This is what the windows VM (192.168.1.138) shows. Unraid is 192.168.1.100 If I edit the sagetv docker config file to show R:\r5000 as the recording drive, upon startup of the docker it gets changed to /opt/sagetv/server/R\:\r5000 which the windows software of course can't find Just throwing stuff at the wall to see what sticks: Recording drive as \\192.168.1.100\mnt\user\r5000 prevents the docker from even starting /mnt/user/r5000 lets the docker start but it complains that the drive is out of space upon recording (it's not) This link is where all this began almost three weeks ago, listing all the stuff i've tried.

Agreed, but in my mind that's what I'm trying to do. Sagetv docker passes through a Linux path to the Windows software when it tells it what and where to record. Windows complains it can't find the path. So I need Linux to tell windows to use a path both can see. If I understood the person on the link I sent correctly, they created an nfs share on Windows and mounted it to a Linux server (although not unraid), then adjusted the sagetv properties a certain way. I'm very comfortable with that last part but cannot figure out the shares. I am very open to any other ideas and would have given up by now if I hadn't discovered a possible solution in the link. Also at the point where I would be willing to pay someone to stand this up.

I have a TV tuner for sagetv that can only run on windows. The sagetv docker controls it but it instructs it to record programs to a Linux directory, which windows can't see. I have found one other person on the planet who has gotten this to work, but they haven't responded, so I'm trying to recreate(see here) Goal is to dump my standalone windows sagetv server and use unraid for everything, but I'm stuck with the r5000 tuner as I am under contract. If this can't be done I will have to abandon sagetv docker and leave it on the windows VM. Not the end of the world but now that I'm getting more comfortable with *nix I like windows less and less

I ssh'd into unraid as root and had it ping 138, it responded as expected. The only folder that exists now on the Nfs server is c:/r5000. The entry from 17:25 is from when I actually had a share called /mnt/user/r5000 on the win VM to test. I had removed it from the Nfs server but not yet from UD, so it was still looking for it when the log was taken. Appreciate the effort, and apologies if I'm a step or two behind. I am a *nix late bloomer

I removed the existing share to start over, entered the IP ending 138. "Load Shares" found the folder as shown: Clicking "Add" results in this without any edits to the mount point: Clicking Mount results in a "Mounting" but it never completes. Log (also attached) looks like this: unraid-unassigned.devices-20171027-2106.zip

The UD mount command is what UNRAID found when I clicked load shares, i didn't enter it like that. No matter what I put in the mount point it reverts to this: (this was because i wasn't hitting enter before clicking mount). now i see this in the log: but /mnt/disks/r5000 definitely exists: and UNRAID can see the win10 NFS share from its CLI what am I not seeing?

A little progress. I dumped FreeNFS and installed Hanewin as an NFS Server on my Win10 VM, although I'm not sure that matters now. I apparently had a firewall issue on the WinVM, now fixed, so within UD, typing in the VM's IP and clicking Load Shares now finds the folder. It is also visible to my UbuntuVM and a standalone Win10 PC with NFS Client running. Neither UD nor Ubuntu will mount it though, which I think has something to do with syntax because I have little idea what I'm actually doing. I have a share setup on Unraid called r5000 (export=yes, security=public for both NFS and SMB). Here's what UD log shows: Same error from Ubuntu VM (for testing only, I do not plan to

Same here, no impact from clearing cache

Plugin showed a date of 10/7, so I uninstalled/reinstalled and it is now 10/22, but still looks like the below. This is via chrome and edge on a standalone win10 computer (not the VM)