Zer0Nin3r

Members
  • Posts

    160
  • Joined

  • Last visited

Everything posted by Zer0Nin3r

  1. Thank you for the reply and for the insight Squid! I appreciate it. Q: If I specify a specific drive for a particular share to use, then later change my mind and specify a different drive, will Unraid move the files to the new location I specified? Or do the files live in the old location and generate "Share is outside the list of designated disks"? Just trying to better understand how Unraid and shares work.
  2. Been experiencing the same thing here. I lose the ability to click whenever I switch from the VNC viewer to say Firefox (so I can watch some SpaceInvader One ) and back to the VNC viewer. Keyboard input is still functioning. This is happening with: VNC Viewer 6.18.907 Tiger VNC 1.9.0 Unraid's browser based VNC viewer VM logs from Unraid show a long string of: qxl_cursor: not implemented: type 1 qxl_cursor: not implemented: type 1 qxl_cursor: not implemented: type 1 **Update** I am losing the mouse after applying some changes inside the Windows VM. This last time, I lost the mouse after enabling networking in Windows 10 so that I can access the user shares on the array. 2018-10-25 07:40:33.079+0000: Domain id=9 is tainted: high-privileges 2018-10-25 07:40:33.079+0000: Domain id=9 is tainted: host-cpu 2018-10-25T07:40:33.123658Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0) Web search turns up: Bug 1611984 qemu prompt "qxl_cursor: not implemented: type 1" when boot Win2008R2 guest reported: 2018-08-03 https://bugzilla.redhat.com/show_bug.cgi?id=1611984 And: https://patchwork.ozlabs.org/patch/965487/ Monochrome cursors are still used by Windows guests with the QXL-WDDM-DOD driver. Such cursor types have one odd feature, inversion of colors. GDK does not seem to support it, so implement an alternative solution: fill the inverted pixels and add an outline to make the cursor more visible. Tested with the text cursor in Notepad and Windows 10. cursor_set_mono is also used by the vmware GPU, so add a special check to avoid breaking its 32bpp format (tested with Kubuntu 14.04.4). I was unable to find a guest which supports the 1bpp format with a vmware GPU. The old implementation was buggy and removed in v2.10.0-108-g79c5a10cdd ("qxl: drop mono cursor support"), this version improves upon that by adding bounds validation, clarifying the semantics of the two masks and adds a workaround for inverted colors support. Looks like the bug was patched and the commit pushed through September 3–5, 2018. I guess now we wait for Lime Tech to push through the update? Not sure how it works on their end. Either way we the end users will have to wait. Fingers crossed. **Update** Using a RDP like Splashtop, the mouse works fine from the client and also from any USB mice that are pushed through to the VM.
  3. I did something similar. I had setup Time Machine user share to disk4 which was a 250GB drive. Now, that I am grasping how Unraid works, I removed the 250GB drive, replaced it with a larger drive, added a few more drives and changed the Time Machine share to disk5. After doing a Compute on the user share, I see the message: Share is outside the list of designated disks What are the implications of this?
  4. I tried for the life of me on four USB sticks. The Lime Tech USB Creator v 1.5 wouldn't pick up the USB drive in step two. I tried attaching the sticks directly to the MacBook Air (2014 w/ High Sierra 10.13.6). Nothing. Even tried Etcher since it works with zip files, but Etcher wouldn't work with the zip image file from LT. Would it free up resources from LimeTech to just have an ISO that can be flashed with Etcher instead of custom writing a USB creator software in house? Sticks were formatted to FAT32 labeled UNRAID. Even the manual creation using the script in terminal would recognize the drive but throw up some sort of error about the partition. What worked: Using Disk Utility in Mac OS >> View >> Show All Devices >> Select the USB device >> Partition >> FAT32 >> Label it as UNRAID >> Ensure that Partition Map is set to Bootable Once the disk drive is formatted, then the script for the Manual Method worked as intended. I would like to update the Wiki to reflect this; I would be happy to update the wiki with this little tidbit. Also, can we get the Wiki updated in an official capacity? I'm finding it hard to navigate the manual/wiki in finding information that I need i.e., there is a lot of outdated information. Additionally, the backend for the unRAID forum isn't the greatest as the search isn't the best. I'm finding that appending the search operator: site:forums.unraid.net in DuckDuckGo/Startpage/Google to your search works better at finding what you are looking for than using the forum's search.) P.S. - After all that's been said and done, I was able to get unRAID going on a low profile SanDisk USB stick. Super cheap I might add.