saber1

@itimpi For shares we have the option to export especially for Time Machine: I prefer to use this option instead of an extra Docker if it isn't needed. So something is wrong in 6.10.X Reinstalling macOS is no option, as it works in 6.9.2 like a charm.

@kubed_zero All my hopes were going into the SMB-Extras-settings. But in my case it didn't work. ==== The Timemachine-Log after last (working) Backup under 6.9.2 (No special SMB-Extras set) ==== 2022-06-25 20:44:13rogress] .•••• . 2022-06-25 20:45:05redSizing] Skipping further sizing for finished volume xxxxxxxx 2022-06-25 20:45:05rogress] Finished copying from volume "xxxxxxxx - Daten" 2022-06-25 20:45:05Collection] Found 0 perfect clone families, 1 partial clone families. Shared space 9,1 MB (9080412 bytes). 2022-06-25 20:45:05al] Saved clone family cache for 'xxxxxxxx - Daten' at /Volumes/Time Machine-Backups/Backups.backupdb/xxxxxxxx/2022-06-25-203850.inProgress/xxxxxxxx/.xxxxxxxx.clonedb 2022-06-25 20:45:08ntDoneAnalysis] .•++**__-•••. 2022-06-25 20:45:08rogress] Time Estimates Evaluation 2022-06-25 20:45:08mages] Found disk2s2 xxxxxxxx 2022-06-25 20:45:09mages] Found disk2s2 xxxxxxxx 2022-06-25 20:45:09al] Unmounted '/Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/xxxxxxxx/2022-06-25-203848/xxxxxxxx - Daten' 2022-06-25 20:45:09al] Unmounted local snapshot: com.apple.TimeMachine.2022-06-25-203848.local at path: /Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/xxxxxxxx/2022-06-25-203848/xxxxxxxx - Daten source: xxxxxxxx - Daten 2022-06-25 20:45:09mages] Found disk2s2 xxxxxxxx 2022-06-25 20:45:09al] Unmounted '/Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/xxxxxxxx/2022-06-25-185038/xxxxxxxx - Daten' 2022-06-25 20:45:09mages] Found disk2s2 xxxxxxxx 2022-06-25 20:45:09al] Unmounted local snapshot: com.apple.TimeMachine.2022-06-25-185038.local at path: /Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/xxxxxxxx/2022-06-25-185038/xxxxxxxx - Daten source: xxxxxxxx - Daten 2022-06-25 20:45:13al] Marked as reference snapshot: com.apple.TimeMachine.2022-06-25-203848.local 2022-06-25 20:45:13al] Backup result: { 2022-06-25 20:45:13al] Completed backup: 2022-06-25-204509 2022-06-25 20:45:13al] Mountpoint '/Volumes/Time Machine-Backups' is still valid 2022-06-25 20:45:14al] Failed to mount 'disk1s3', dissenter { 2022-06-25 20:45:15al] Copying recovery system 2022-06-25 20:45:15al] Failed to copy recovery set, error: No such file or directory 2022-06-25 20:45:15pThinning] Thinning 1 backups using age-based thinning, expected free space: 1 TB actual free space: 1 TB trigger 50 GB thin 83,33 GB dates: ( 2022-06-25 20:47:10al] Mountpoint '/Volumes/Time Machine-Backups' is still valid 2022-06-25 20:47:10mages] Found disk2s2 xxxxxxxx 2022-06-25 20:47:10mages] Found disk2s2 xxxxxxxx 2022-06-25 20:47:40ight] Spotlight finished indexing for '/Volumes/Time Machine-Backups' ==== The Timemachine-Log after first (not working) Backup attempt under 6.10.3 (SMB-Extras set) ==== 2022-06-25 21:06:05pScheduling] Not prioritizing backups with priority errors. lockState=0 2022-06-25 21:06:05al] Starting manual backup 2022-06-25 21:06:05ing] Attempting to mount 'smb://yyyyyyyy@unBackup._smb._tcp.local/unMachine' 2022-06-25 21:06:06ing] Mounted 'smb://yyyyyyyy@unBackup._smb._tcp.local/unMachine' at '/Volumes/.timemachine/unBackup._smb._tcp.local/yyyyyyyy/unMachine' (1 TB of 4 TB available) 2022-06-25 21:06:06al] Initial network volume parameters for 'unMachine' {disablePrimaryReconnect: 0, disableSecondaryReconnect: 0, reconnectTimeOut: 60, QoS: 0x0, attributes: 0x1C} 2022-06-25 21:06:06al] Configured network volume parameters for 'unMachine' {disablePrimaryReconnect: 1, disableSecondaryReconnect: 0, reconnectTimeOut: 30, QoS: 0x20, attributes: 0x1C} 2022-06-25 21:06:07Management] TMPowerState: 2 2022-06-25 21:06:07al] Skipping periodic backup verification due to power conditions: (null) 2022-06-25 21:06:07al] 'yyyyyyyy.backupbundle' does not need resizing - current logical size is 11,4 TB (11.397.019.360.768 bytes), size limit is 3,8 TB (3.798.891.797.913 bytes) 2022-06-25 21:06:07al] Mountpoint '/Volumes/.timemachine/unBackup._smb._tcp.local/yyyyyyyy/unMachine' is still valid 2022-06-25 21:06:07al] Checking for runtime corruption on '/Volumes/.timemachine/unBackup._smb._tcp.local/yyyyyyyy/unMachine/yyyyyyyy.backupbundle' 2022-06-25 21:06:45mages] Failed to attach using DiskImages2 to url '/Volumes/.timemachine/unBackup._smb._tcp.local/yyyyyyyy/unMachine/yyyyyyyy.backupbundle', error: Error Domain=NSPOSIXErrorDomain Code=19 "Operation not supported by device" UserInfo={DIErrorVerboseInfo=Failed to initialize IO manager: Failed opening folder for entries reading} 2022-06-25 21:06:45al] Failed to unmount '/Volumes/.timemachine/unBackup._smb._tcp.local/yyyyyyyy/unMachine', Disk Management error: { 2022-06-25 21:06:45al] Failed to unmount '/Volumes/.timemachine/unBackup._smb._tcp.local/yyyyyyyy/unMachine', error: Error Domain=com.apple.diskmanagement Code=0 "No error" UserInfo={NSDebugDescription=No error, NSLocalizedDescription=Kein Fehler.} 2022-06-25 21:06:45al] Waiting 60 seconds and trying again. 2022-06-25 21:06:45llation] Cancelling backup because volume '/Volumes/.timemachine/unBackup._smb._tcp.local/yyyyyyyy/unMachine' was unmounted. 2022-06-25 21:06:45llation] Requested backup cancellation or termination 2022-06-25 21:06:46llation] Backup cancelled (22: BACKUP_CANCELED) 2022-06-25 21:06:46al] Failed to unmount '/Volumes/.timemachine/unBackup._smb._tcp.local/yyyyyyyy/unMachine', Disk Management error: { 2022-06-25 21:06:46al] Failed to unmount '/Volumes/.timemachine/unBackup._smb._tcp.local/yyyyyyyy/unMachine', error: Error Domain=com.apple.diskmanagement Code=0 "No error" UserInfo={NSDebugDescription=No error, NSLocalizedDescription=Kein Fehler.} 2022-06-25 21:06:46llation] Cleared pending cancellation request ==== The Timemachine-Log after first (working) Backup after downgrade again to 6.9.2 (SMB-Extras not set) ==== 2022-06-26 08:40:52rogress] .•••••• . 2022-06-26 08:41:01ight] Spotlight indexing queue is full (256 depth, 0 operations overflowed) 2022-06-26 08:41:27ight] Spotlight indexing queue is empty. 2022-06-26 08:41:56rogress] Finished copying from volume "zzzzzzzzz - Daten" 2022-06-26 08:41:56Collection] Found 6 perfect clone families, 1 partial clone families. Shared space 11,9 MB (11882900 bytes). 2022-06-26 08:41:59al] Saved clone family cache for 'zzzzzzzzz - Daten' at /Volumes/Time Machine-Backups/Backups.backupdb/zzzzzzzzz/2022-06-26-080502.inProgress/zzzzzzzzz/.zzzzzzzzz 2022-06-26 08:42:19ntDoneAnalysis] .•+______-••. 2022-06-26 08:42:19rogress] Time Estimates Evaluation 2022-06-26 08:42:19mages] Found disk2s2 zzzzzzzzz 2022-06-26 08:42:20al] Unmounted '/Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/SaberBookPro/2022-06-26-080500/zzzzzzzzz - Daten' 2022-06-26 08:42:20mages] Found disk2s2 zzzzzzzzz 2022-06-26 08:42:20al] Unmounted local snapshot: com.apple.TimeMachine.2022-06-26-080500.local at path: /Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/zzzzzzzzz/2022-06-26-080500/SaberBookPro - Daten source: zzzzzzzzz - Daten 2022-06-26 08:42:20mages] Found disk2s2 zzzzzzzzz 2022-06-26 08:42:20al] Unmounted '/Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/zzzzzzzzz/2022-06-25-203848/zzzzzzzzz - Daten' 2022-06-26 08:42:20mages] Found disk2s2 zzzzzzzzz 2022-06-26 08:42:20al] Unmounted local snapshot: com.apple.TimeMachine.2022-06-25-203848.local at path: /Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/zzzzzzzzz/2022-06-25-203848/zzzzzzzzz - Daten source: zzzzzzzzz - Daten 2022-06-26 08:42:31al] Marked as reference snapshot: com.apple.TimeMachine.2022-06-26-080500.local 2022-06-26 08:42:31al] Backup result: { 2022-06-26 08:42:31al] Completed backup: 2022-06-26-084227 2022-06-26 08:42:31al] Mountpoint '/Volumes/Time Machine-Backups' is still valid 2022-06-26 08:42:33al] Copying recovery system 2022-06-26 08:42:33al] Failed to copy recovery set, error: No such file or directory 2022-06-26 08:42:33pThinning] Thinning 2 backups using age-based thinning, expected free space: 993,42 GB actual free space: 994,17 GB trigger 50 GB thin 83,33 GB dates: ( 2022-06-26 08:53:01al] Mountpoint '/Volumes/Time Machine-Backups' is still valid 2022-06-26 08:53:02mages] Found disk2s2 zzzzzzzzz 2022-06-26 08:53:02mages] Found disk2s2 zzzzzzzzz 2022-06-26 08:53:32ight] Spotlight finished indexing for '/Volumes/Time Machine-Backups' 2022-06-26 08:53:42al] Unmounted '/Volumes/Time Machine-Backups' 2022-06-26 08:53:45al] Unmounted '/Volumes/.timemachine/unBackup._smb._tcp.local/zzzzzzzzz/unMachine' Under 6.9.2 all ist still fine. Right after upgrade to 6.10.X the Backup-Jobs not working anymore. Directly after downgrade to 6.9.2 the job starts without issues.

Mit unRaid auf Apple Hardware hatten sich schon vorher welche versucht. Hier: und hier: Sieht nicht gut aus...

Das setzt voraus, das wir alle TGF folgen und die Videos schauen. Was, no front, wohl eher nicht der Fall ist... Ich habe nur die für mich nötigen Nerdpack Tools installiert. NICHT alle.

Es geht bei einem MB ja nicht primär um CPU's, RAM und SSD's. Das sind ja Komponenten, die anschließend dazu kommen. Der Preis wird zustandekommen, weil die Preise für einzelne elektronische Bauteile (Kondensatoren usw.) enorm gestiegen sind. Ich bin beruflich in der Luftfahrt tätig. Die Preisaufschläge für elektronische Bauteile sind teils nicht nur um das doppelte sondern eher um das zehnfache gestiegen. Wenn man denn überhaupt dran kommt... Supermicro, oder jede andere Firma, hat eben auch nichts zu verschenken.

Okay. But what did change in 6.10 that Time Machine would not work anymore. There are still the Share/SMB Export Options > Yes/Time Machine There is some issue here in 6.10... Do Limetech know it?

Bei den Container-Settings die Pfade zu den jeweiligen Verzeichnissen angeben. So in etwa:

Ich habe meinem vorigen Server (damals noch mit OpenMediaVault) ebenfalls eine unRaid-Lizenz gegönnt. Dieser fungiert setdem als Backup-Server. Daten werden per rsync (Cronjobs) gesichert.

Hält sich tatsächlich sehr in Grenzen. Drei-Minuten-Sache.

I'm asking you about the procedure here. Okay, now i´m back on 6.9.2 i have no diagnostics. @pkoci1@mok Do you have the diagnostics from 6.10.X for "our" issue?

@JorgeB What to do here? Some people have issues with Time Machine and 6.10.X. For me the problems exists on 6.10.0 and .1. After downgrade to 6.9.2 the Backup working imediatly. And the disk i have declared for the Time Machine Share will not go to sleep under 6.10.X. No problem under 6.9.2.

Du kannst aber trotzdem, wenn Du bereits auf 6.10.1 bist, auf 6.9.2 zurück. Einfach die 6.9.2 laden (als ZIP) von hier (ganz nach unten scrollen). Auf dem Stick dann die vorhandenen bz-Dateien mit denen aus der ZIP ersetzen. Vor ein paar Stunden habe ich es genauso (6.10.1 > 6.9.2) gemacht.

Now i did a downgrade to 6.9.2 and the Backup starts and finishes without issues.

It stops working exactly at that point i did the upgrade from 6.9.2 to 6.10.0. It can't be a solution to reinstall macOS. The issue is not on Mac site. Look at @mok's comment.

I get something like this: error: Error Domain=NSPOSIXErrorDomain Code=19 "Operation not supported by device" UserInfo={DIErrorVerboseInfo=Failed to initialize IO manager: Failed opening folder for entries reading} error: Error Domain=NSPOSIXErrorDomain Code=19 "Operation not supported by device" UserInfo={DIErrorVerboseInfo=Failed to initialize IO manager: Failed opening folder for entries reading}

12.3.1

And whats also going on is that the disk for Time Machine did not go to sleep anymore.

The command gave me an usage on how to use grep

Really? For me since Update to 6.10 stable (Update from 6.9,2) the Time Machine Backups cannot be finished. macOS 12.3.1

Erstmal habe ich nur meinen Backup-Server auf 6.10 aktualisiert. Seit dem können keine TimeMachine Sicherungen mehr abgeschlossen werden. Dazu wurde auch schon ein Bug Report eröffnet: Leider noch keine Reaktion darauf...

Das kennst Du?: 😄

bald wird Dir geholfen. 😁 https://www.heise.de/news/Festplatten-Western-Digital-erhoeht-auf-22-und-26-TByte-7079355.html

Ein wirklich sehr interessantes Thema hier. Du sprichst immer im weitesten Sinne von Deinem "Anwendungszweck". Das macht irgendwie neugierig. Von was für eine Art von Daten sprechen wir hier, das man die Checksummen in gewissen, wiederkehrenden Zeiträumen prüfen muss? Was passiert da, das etwas an den Dateien, eventuell geändert wurde?

Das sollte aber auch nicht so sein. Bei welcher App kann man denn so ein Verhalten beobachten? Ich nutze u.a. Spark auf iOS (gibt es auch für Android). Musste nach einem Update noch nie die Mail-Konten erneut einrichten. Wenn ich so drüber nachdenke, musste ich noch nie bei einem Update irgendeiner App die Einstellungen wieder neu vornehmen...