Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About phenomeus

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

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

  1. #unassigned_devices_start #Unassigned devices share includes include = /tmp/unassigned.devices/smb-settings.conf #unassigned_devices_end
  2. Yes but it will not stay this way. The next backup will fail again until I stop and restart the array
  3. hey guys, I'm on 6.7.2 + macOS 10.14.6 and still have problems with an already presented TM backup/share over smb. the thing is still that it cant be reached from my MacBook(s). ONLY when I stop the array and restart the array immediately it finds the share and is working flawlessly and as expected. how can I extract my log for this bug to track down? it has to unraids side doesn't it?
  4. like me with pre final, I'm shutting down the array and restarting it, after that the TM share is visible or can be found by an already set up TM
  5. i reinserted it and commented everything out besides the low include command for unassigned shares. so its still working. something in the global part f'ckd something up
  6. finally did it. sreknobs tips couldn't help… so I took all the crap out of my smb extra configurations: [global] security = USER guest account = nobody public = yes guest ok = yes map to guest = bad user kernel oplocks = no oplocks = no level2 oplocks = no #unassigned_devices_start #Unassigned devices share includes include = /tmp/unassigned.devices/smb-settings.conf #unassigned_devices_end and emptied it. voila! it's working. can anyone tell me what was important in that config?
  7. I tried that already. still no luck… - afp is disabled - Enhanced macOS interoperability is on - public, secure or private doesnt matter - new share names - Different sizes - with or without cache drive - 2 MacBooks, brand new reinstalled or one that worked with afp - up2date macOS installations - …
  8. tried everything by now… not working. same odd error "The network backup disk does not support the required capabilities" even a freshly installed Mojave macOS on another macbook gets the same error. so I assume I have to search here at unraid for the solution. did exactly what everyone else did. hidden time machine, normal, secured, public, empty directory, deleted share, created a new one every time the same error. its mounting the drive but error 45 in console. I can upload files to it, its not about write permissions
  9. i have to connect to mine first and its not working. was working good with afp, so I will wait till 6.7 final and hope for the best… I tried everything already. all manual smb configs, reseting time machine on my Mac, etc. new shares, blank shares, everything
  10. i also have the feeling that its a macOS behaviour. adding the drive with cli I get the following error: sudo tmutil setdestination -a smb://name:password@server/Backups Disk does not support Time Machine backups. (error 45) The backup destination could not be added.
  11. hey, thanks but I did that and still, not working. its exported and visible but not connecting at the end its just creating this file in the share: .com.apple.timemachine.supported
  12. hi all, im on 6.7rc5 and can't get TM to work over SMB. its showing up and I can login but while adding, its saying something like: "The network backup disk does not support the required capabilities" what steps do I have to configure manually before its working with the 6.7. final release? thnx in advance
  13. Like you said. No trust. I tried add it back as parity and instantly there were read errors. So the drive goes back. And yeah i need to do something. The Seagate ran cooler and now it’s summer it died. My mistake
  14. is it safe to use it after this? I mean this drive was running 13 hours. right now the array Is unprotected so I tend to use it if its safe enough.