Toskache

Members
  • Posts

    44
  • Joined

  • Last visited

Converted

  • Gender
    Male
  • Location
    Deutschland

Recent Profile Visitors

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

Toskache's Achievements

Rookie

Rookie (2/14)

8

Reputation

  1. I am not able to get this thing running 😞 When I select the timemachine-volume "Urzeitkapsel" and enter the credentials (defaults) my Mac says : "Das ausgewählte Backup-Volume im Netzwerk unterstützt die notwendigen Funktionen nicht." (The selected backup volume on the network does not support the necessary functions.). In the docker-log is this output: chpasswd: password for 'timemachine' changed dbus-daemon[42]: [system] org.freedesktop.DBus.Error.AccessDenied: Failed to set fd limit to 65536: Operation not permitted Found user 'avahi' (UID 86) and group 'avahi' (GID 86). Successfully dropped root privileges. avahi-daemon 0.8 starting up. WARNING: No NSS support for mDNS detected, consider installing nss-mdns! Loading service file /etc/avahi/services/smbd.service. Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.2.250. New relevant interface eth0.IPv4 for mDNS. Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1. New relevant interface lo.IPv4 for mDNS. Network interface enumeration completed. Registering new address record for 192.168.2.250 on eth0.IPv4. Registering new address record for 127.0.0.1 on lo.IPv4. Server startup complete. Host name is timemachine.local. Local service cookie is 641408420. Service "urzeitkapsel" (/etc/avahi/services/smbd.service) successfully established. INFO: CUSTOM_SMB_CONF=false; generating [global] section of /etc/samba/smb.conf... INFO: Creating /var/log/samba/cores INFO: Avahi - generating base configuration in /etc/avahi/services/smbd.service... INFO: Avahi - using urzeitkapsel as hostname. INFO: Avahi - adding the 'dk0', 'Urzeitkapsel' share txt-record to /etc/avahi/services/smbd.service... INFO: Group timemachine doesn't exist; creating... INFO: User timemachine doesn't exist; creating... INFO: Setting password from environment variable INFO: INFO: CUSTOM_SMB_CONF=false; generating [Urzeitkapsel] section of /etc/samba/smb.conf... INFO: Samba - Created Added user timemachine. INFO: Samba - Enabled user timemachine. INFO: Samba - setting password INFO: changed ownership of '/opt/timemachine' to 1000:1000 INFO: mode of '/opt/timemachine' changed to 0770 (rwxrwx---) INFO: Avahi - completing the configuration in /etc/avahi/services/smbd.service... INFO: running test for xattr support on your time machine persistent storage location... INFO: xattr test successful - your persistent data store supports xattrs INFO: entrypoint complete; executing 's6-svscan /etc/s6' dbus socket not yet available; sleeping... nmbd version 4.15.7 started. Copyright Andrew Tridgell and the Samba Team 1992-2021 smbd version 4.15.7 started. Copyright Andrew Tridgell and the Samba Team 1992-2021 INFO: Profiling support unavailable in this build. Failed to fetch record! ***** Samba name server TIMEMACHINE is now a local master browser for workgroup VU on subnet 192.168.2.250 ***** error in mds_init_ctx for: /opt/timemachine _mdssvc_open: Couldn't create policy handle for Urzeitkapsel Any Ideas?
  2. There is a php-error-message in the "balance-section":
  3. I had the same problem in rc2: SMB shares not working with macOS Monterey But with rc3 and an c"lean" extra-conf the issue seems to be solved (not tested a lot so far).
  4. Changed Priority to Urgent Working with our macOS devices is not possible under 6.10.0-rc2.
  5. There seem to be samba-problems in combination of macOS Monterey and 6.10.0-rc2. Mounting the smaba shares on macOS Monterey works fine but subjectively slightly slower. But immediately after starting a filecopy to the unraid-system, strange things happen: the destination folder goes blank for a moment then suddenly many previously existing folders appear multiple times you can not cancel the copy process the smb share drops I also have the impression that the reactivity/perfomance of the samba shares are much slower than in 6.9.2. The whole thing is reproducible. Unfortunately, I could only test with macOS Monterey. I cannot say whether the problem also occurs with other macOS versions. @Maxrad also Reported: Reverting to 6.9.2 or to 6.10.0-rc1 (Maxrad) worked. Tested with this "Samba extra configuration": #unassigned_devices_start #Unassigned devices share includes include = /tmp/unassigned.devices/smb-settings.conf #unassigned_devices_end [global] spotlight backend = tracker [data] path = /mnt/user/data spotlight = yes #vfs_recycle_start #Recycle bin configuration [global] syslog only = No syslog = 0 logging = 0 log level = 0 vfs:0 #vfs_recycle_end nas.fritz.box-diagnostics-20211108-1021.zip
  6. I have tested the 6.10.0-RC2 again. But even with the minimal SMB extra configuration it does not work. Immediately after starting the first copy strange things happen: - the destination folder goes blank for a moment - then suddenly many previously existing folders appear multiple times - you can not cancel the copy process I also have the impression that the reactivity/perfomance of the shares are much slower than in 6.9.2. I again reverted to 6.9.2.
  7. Problem with macOS Monterey? I updated from 6.9.2 to 6.10.0-rc2. At first everything looked fine... But then when I tried to copy two larger files from a macOS (Monterey) to a samba share, the copy process did not start. The share was even ejected. The share was mounted via simple "network browsing" (smb://nas._smb._tcp.local/data). The whole thing is reproducible. It seems that copying smaller files works. I reverted back to 6.9.2. There is the following "Samba extra configuration": [global] #unassigned_devices_start #Unassigned devices share includes include = /tmp/unassigned.devices/smb-settings.conf #unassigned_devices_end #vfs_recycle_start #Recycle bin configuration syslog only = No syslog = 0 logging = 0 log level = 0 vfs:0 #vfs_recycle_end
  8. I did a file system check with no "actions". Nothing. Afterwords no rebuild-option.... The question is: Wy was the disk "unmountable" just after a restart?
  9. Unfortunately, the online help was no real help. I have added the disk relatively fresh to the array. Because the disk was still unused, I simply formatted the disk. But I still do not know what happened during the reboot.
  10. Hi! after a reboot I have one device marked with "Unmountable: Unsupported partition layout". Unfortunately I don't know how to progress now. I attached also the diagnostic-package. Any suggestions? THX George nas.fritz.box-diagnostics-20211017-1636.zip
  11. I switched to another case with a new backplane. Works now fine for a while. THX.
  12. Have you tried to set the option in the "ocr.config" (usually in appdata/ocrmypdf-auto)?