Indmenity83

Members
  • Content Count

    17
  • Joined

  • Last visited

Community Reputation

3 Neutral

About Indmenity83

  • Rank
    Newbie

Recent Profile Visitors

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

  1. I realize this is a serious necropost, but wanted to give @maciekish a huge thank you for sticking with this after the responses he got. I'm using a reverse proxy with Nginx and had the same problem and this lead me to the same solution. So for anybody getting here from Google you'll want to add the following to your Nginx config to get things working again. You could be clever and only apply it to the locations that are broken, but since my reverse proxy is not even exposed outside my network I just disabled gzip for the whole server definition: server { gzip off;
  2. 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.
  3. 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.
  4. 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 shar
  5. 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.
  6. 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.
  7. 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 Mac
  8. 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
  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>