Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Indmenity83

  • Rank

Recent Profile Visitors

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

  1. This makes managing the files on the system really complicated. Unraid really expects all the content to be 99:100. Read through coppit's message below; is this something that can be adapted into your container? I'm willing to make the PR if its something you would support.
  2. Closing this issue as backups appear to be working. I'll open a new thread for the include/exclude bug that was the root cause.
  3. Well here's an interesting observation; this may be a different but related issue. I'm not at home to fully test TimeMachine. I had set a single "include disk" on the share in order to target a disk with a good amount of free space. As part of the testing suggested above, I created a .sparsebundle locally and tried to move it to the share and found that I get an error about there not being enough free space. In fact, I can't even create a folder in the share. However, if I remove the single "include disk" then there are no issues adding content to the share. I've done some additional testing and anytime I set an "include disk" the share will not accept content UNLESS I select 'disk 1' as the included disk. Similarly, if I exclude disk 1 at all I cannot write to the share. When I get home tonight I'll see if this free space issue is what was causing TimeMachine to throw the "does not support the required capabilities" error (TimeMachine doesn't see the share over VPN).
  4. The operating system "OS X" officially changed its name to "macOS" in 2016, probably time to update the UI in Unraid to follow suit. Places where this shows up: SMB Settings: ENHANCED OS X INTEROPERABILITY There may be other locations where "OS X" or "OSX" might show up too, I'll try to list them here or can create new reports if that is easier.
  5. I tried public, private and secured ... all had the same error message; so while I'm not sure if its still required, it is at least a system check that I believe happens after whatever is causing my current failure.
  6. Thanks, I had TimeMachine backups on Unraid working prior to the AFP -> SMB changes (High Sierra I think that was?). I've never had it work since then. I've got a backup running now to a USB device, I'll try copying the file over to Unraid and then picking the drive to see if that make any difference This is interesting ... I did upgrade an existing Unraid box and had to go enable "Enhanced OS X interoperability" and I certainly had an existing connection to Unraid SMB shares prior to making that change. Would a restart of the MacOS machine reset the "first tcon" or is it more than that (if anybody knows). Either way, I'll make sure I restart my laptop when I get home and try again.
  7. I had added the 'time-machine' share after the initial post as a test to see if it was just some client-side caching tied to the network name of the share. Both shares result in the same error. [edit, output moved to attached file to save scrolling] output.txt
  8. Diagnostics attached calcifer-diagnostics-20190304-1758.zip
  9. Whoops; that was not what I meant to do. But after changing it (to 2000000 and removing it completely) I still get the same error.
  10. A picture is worth a thousand words; - Running Unraid 5.7.0-rc5 - Share named 'backup' exported as SMB time machine - After picking share in Time Machine and entering appropriate username and password for the share I'm told the disk does not support required capabilities. Not sure what I'm doing wrong here, or if something is actually broken?
  11. I was hoping to prove it out on the hardware before spending any money on a newer card; might just have to bite a bullet and roll some dice.
  12. Another note, because I realized I haven't mentioned it anywhere, is that if I set the GPU/Soundcard back to VNC/None that the machine boots just fine.
  13. The full XML for the VM too <domain type='kvm' id='5'> <name>Windows</name> <uuid>4c45436f-34d0-e0c7-349e-7b5720b3d0a9</uuid> <description>SeaBios Win 10 Box</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>6</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='5'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='6'/> <vcpupin vcpu='4' cpuset='3'/> <vcpupin vcpu='5' cpuset='7'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-q35-2.11'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='3' threads='2'/> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Window on the Sea/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Win10_1607_English_x64.iso'/> <backingStore/> <target dev='hda' bus='sata'/> <readonly/> <boot order='2'/> <alias name='sata0-0-0'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.141-1.iso'/> <backingStore/> <target dev='hdb' bus='sata'/> <readonly/> <alias name='sata0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='sata' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='pci' index='0' model='pcie-root'> <alias name='pcie.0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <alias name='pci.1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <alias name='pci.2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <alias name='pci.3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <alias name='pci.4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x14'/> <alias name='pci.5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <interface type='bridge'> <mac address='52:54:00:92:c4:83'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/1'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/1'> <source path='/dev/pts/1'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-5-Window on the Sea/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <graphics type='vnc' port='5900' autoport='yes' websocket='5700' listen='' keymap='en-us'> <listen type='address' address=''/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <alias name='video0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </memballoon> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>
  14. I've followed numerous guides, forums and google but I just can't seem to get GPU passthrough working. I had it working once, but after installing the nvidia drivers on the virtual windows box and restarting its never worked again. Setup: Host system is a Dell PowerEdge R510 server with Xeon L5630 Graphics card is an Alienware GTX 555 (made by EVGA I belive - https://www.techpowerup.com/vgabios/115134/alienware-gtx555-1024-111111) Attempt 1 - Pass GFX card without specifying rom No boot, no output on graphics card, and I get the following error in the log: 2018-08-22T15:02:29.730245Z qemu-system-x86_64: vfio-pci: Cannot read device rom at 0000:04:00.0 Device option ROM contents are probably invalid (check dmesg). Skip option ROM probe with rombar=0, or load from file with romfile= Attempt 2 - Pass GFX card specifying rom (downloaded from techpowerup.com) No boot, no output on graphics card and no apparent error in the log; it just seems to hang during boot, the last event in the log is: 2018-08-22T15:16:41.726069Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/1 (label charserial0) Other Info - Cannot extract rom from card I've tried to extract the rom from the card directly too following spaceinvader's video guide, but I always get a "cat: rom: Input/output error" when I try to dump it. Questions for the group: Is it possible that I've somehow messed up the rom on the card? (worked once, then driver update broke it?) Is this something to do with the Nvidia error 43 thing? Anybody have any further suggestions? Thanks all, really appreciate any support that can be provided.