Welcome to the MacNN Forums.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

You are here: MacNN Forums > Software - Troubleshooting and Discussion > macOS > MacOS Mojave.

MacOS Mojave. (Page 3)
Thread Tools
And.reg
The Mighty
Join Date: Feb 2004
Location: Well the sports issue was within arm's reach but they closed up shop and kicked me out. And I'm out of toilet paper.
Status: Offline
Reply With Quote
Aug 15, 2018, 06:20 PM
 
Also, in Safari, when on YouTube, "Never auto play" doesn't work and videos still auto play, after all these betas.

Edit: Wait, maybe it is working after trying a few other channels.
( Last edited by And.reg; Aug 15, 2018 at 06:38 PM. )
Yours truly, And.reg, "The Mighty" Pain in the Ass
     
And.reg
The Mighty
Join Date: Feb 2004
Location: Well the sports issue was within arm's reach but they closed up shop and kicked me out. And I'm out of toilet paper.
Status: Offline
Reply With Quote
Aug 18, 2018, 01:44 PM
 
^ It's still intermittent, sometimes it works, sometimes it doesn't, can't really tell.

Also, another watch out to beta testers that my Time Machine backup (of data on APFS Pro MacBook) keeps failing after about 8 GB with another 30 GB to go. No reason is given for the failure. The hard drive stayed connected.
Yours truly, And.reg, "The Mighty" Pain in the Ass
     
reader50
Administrator
Join Date: Jun 2000
Location: California
Status: Offline
Reply With Quote
Aug 18, 2018, 02:02 PM
 
Apple made it more difficult to follow TM log activity, since about Yosemite. The data is still present, but you have to hunt around.

I use a Terminal script (built by someone else) to follow TM when I'm troubleshooting.
Code:
#! /bin/sh filter='processImagePath contains "backupd" and subsystem beginswith "com.apple.TimeMachine"' # show the last 12 hours start="$(date -j -v-12H +'%Y-%m-%d %H:%M:%S')" echo "" echo "[History (from $start)]" echo "" log show --style syslog --info --start "$start" --predicate "$filter" echo "" echo "[Following]" echo "" log stream --style syslog --info --predicate "$filter"
Save this script as a file called "tmlog" in your home folder, without an extension. When you need to troubleshoot, open Terminal and type:

./tmlog

You might have to make it executable the first time. If so,

chmod +x tmlog

Since it fetches the last 12 hours of TM log entries, you can launch the script even after TM has started. Or after it's aborted. And still catch the error messages.
     
And.reg
The Mighty
Join Date: Feb 2004
Location: Well the sports issue was within arm's reach but they closed up shop and kicked me out. And I'm out of toilet paper.
Status: Offline
Reply With Quote
Aug 18, 2018, 03:33 PM
 
The output of the script is after this paragraph. Oh, and I should mention that I am attempting to back up my data to a Seagate 4 TB formatted MacOS Extended (Journaled) via USB 3.0, with 3 TB of free space still available on that drive.

While waiting for your reply, I also tried moving the .inprogress file to the Trash, though I could not delete it, because when I tried to empty the Trash, Finder just kept showing a progressing bar with "Deleting..." below it, and it didn't go away. So, I gave up, restarted the computer, turned off automatic backups, went into Disk Utility, and run the First Aid utility on the partition for Time Machine. The utility, however, got hung up/stuck/no further progress on "Checking catalog file," I waited like 10 minutes. So, I gave up on that as well, restarted my computer again, and turned on automatic backups. At this point, the (un-delete-able) .inprogress file from earlier today was still in the Trash.

So, I let the Time Machine backup carry on at 2:39pm, and here is the output of the script.


Code:
2018-08-18 14:39:52.154698-0400 localhost backupd[247]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Starting manual backup 2018-08-18 14:40:00.055020-0400 localhost backupd[247]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Failed to find matching sparsebundle in directory '/Volumes/Seagate Time Machine Backup', directory contents: ( ".com.apple.timemachine.donotpresent", ".disk_label", ".disk_label_2x", ".DocumentRevisions-V100", ".DS_Store", ".fseventsd", ".Spotlight-V100", ".TemporaryItems", ".Trashes", ".VolumeIcon.icns", "Backups.backupdb", "tmbootpicker.efi" ) 2018-08-18 14:40:15.368707-0400 localhost backupd[247]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Backing up to /dev/disk3: /Volumes/Seagate Time Machine Backup/Backups.backupdb 2018-08-18 14:40:20.658605-0400 localhost backupd[247]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Failed to remove attribute 'com.apple.backupd.SnapshotVolumeFSEventStoreUUID' from 'file:///', error: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted" 2018-08-18 14:40:20.658749-0400 localhost backupd[247]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Failed to remove attribute 'com.apple.backupd.SnapshotVolumeLastFSEventID' from 'file:///', error: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted" 2018-08-18 14:40:20.658837-0400 localhost backupd[247]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Failed to remove attribute 'com.apple.backupd.SnapshotVolumeUUID' from 'file:///', error: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted" 2018-08-18 14:40:20.658905-0400 localhost backupd[247]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Failed to remove attribute 'com.apple.backupd.PreviousSnapshotVolumeUUID' from 'file:///', error: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted" 2018-08-18 14:40:20.659039-0400 localhost backupd[247]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Failed to remove attribute 'com.apple.backupd.PreviousSnapshotVolumeName' from 'file:///', error: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted" 2018-08-18 14:40:20.659186-0400 localhost backupd[247]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Failed to remove attribute 'com.apple.backupd.VolumeBytesUsed' from 'file:///', error: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted" 2018-08-18 14:40:20.659426-0400 localhost backupd[247]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Failed to remove attribute 'com.apple.backupd.VolumeIsCaseSensitive' from 'file:///', error: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted" 2018-08-18 14:40:20.659513-0400 localhost backupd[247]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Failed to remove attribute 'com.apple.backupd.fstypename' from 'file:///', error: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted" 2018-08-18 14:40:20.659579-0400 localhost backupd[247]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Failed to remove attribute 'com.apple.backupd.VolumeIsEncrypted' from 'file:///', error: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted" 2018-08-18 14:40:20.664472-0400 localhost backupd[247]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Starting age based thinning of Time Machine local snapshots on disk '/' 2018-08-18 14:40:22.102912-0400 localhost backupd[247]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Failed to write unlock record UUIDs as extended attribute for disk '/', error: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted" 2018-08-18 14:40:22.192067-0400 localhost backupd[247]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Created Time Machine local snapshot with name 'com.apple.TimeMachine.2018-08-18-144021' on disk '/' 2018-08-18 14:40:22.194681-0400 localhost backupd[247]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Declared stable snapshot: com.apple.TimeMachine.2018-08-18-144021 2018-08-18 14:40:22.205230-0400 localhost backupd[247]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Mounted stable snapshot: com.apple.TimeMachine.2018-08-18-144021 at path: /Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/MacBook Pro (2)/2018-08-18-144021/KL17 source: KL17 2018-08-18 14:40:22.243730-0400 localhost backupd[247]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Event store UUIDs don't match for volume: KL17 2018-08-18 14:40:22.297857-0400 localhost backupd[247]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Deep event scan at path:/Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/MacBook Pro (2)/2018-08-18-144021/KL17 reason:must scan subdirs|new event db| 2018-08-18 14:40:22.298380-0400 localhost backupd[247]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Running deep scan - looking for changes after 2018-08-13 23:41:04 +0000 [Following] Filtering the log data using "processImagePath CONTAINS "backupd" AND subsystem BEGINSWITH "com.apple.TimeMachine"" Timestamp (process)[PID] 2018-08-18 14:45:51.514351-0400 localhost backupd[247]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Finished scan 2018-08-18 14:45:51.803674-0400 localhost backupd[247]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Saved event cache at /Volumes/Seagate Time Machine Backup/Backups.backupdb/MacBook Pro (2)/2018-08-18-144022.inProgress/616B0CA7-1472-4672-8E18-6FEE94A9DF0A/.BCE56C28-09D5-3C4A-B4BF-6EDA18EA6DE4.eventdb 2018-08-18 14:45:51.897229-0400 localhost backupd[247]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Not using file event preflight for / 2018-08-18 14:58:40.901507-0400 localhost backupd[247]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Will copy (35.39 GB) from KL17 2018-08-18 14:58:41.939676-0400 localhost backupd[247]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Found 463615 files (35.39 GB) needing backup 2018-08-18 14:58:42.454308-0400 localhost backupd[247]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] 45.77 GB required (including padding), 3.17 TB available 2018-08-18 15:30:51.854566-0400 localhost backupd[247]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Stopping backup. 2018-08-18 15:30:51.891068-0400 localhost backupd[247]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Error: (-8062) SrcErr:NO Copying /Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/MacBook Pro (2)/2018-08-18-144021/KL17/Users/[...my name...and then part of a long path to a folder with my academic data...]/2018/Spring/Lesson grading/Lesson 6 Part 2/Grading notes/.DS_Store to /Volumes/Seagate Time Machine Backup/Backups.backupdb/MacBook Pro (2)/2018-08-18-144022.inProgress/616B0CA7-1472-4672-8E18-6FEE94A9DF0A/KL17/Users/[...my name...same path snipped out...]/2018/Spring/Lesson grading/Lesson 3 Part 2/Lesson 6 Part 2 2018-08-18 15:30:51.905169-0400 localhost backupd[247]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Copied 118437 items (10.53 GB) from volume KL17. Linked 158589. 2018-08-18 15:30:52.564163-0400 localhost backupd[247]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Copy stage failed with error:11 2018-08-18 15:30:54.342522-0400 localhost backupd[247]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Unmounted local snapshot: com.apple.TimeMachine.2018-08-18-144021 at path: /Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/MacBook Pro (2)/2018-08-18-144021/KL17 source: KL17 2018-08-18 15:30:54.349703-0400 localhost backupd[247]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Backup failed with error 11: 11
Backup Failed

Time Machine couldn't back up to "Seagate Time Machine Backup".

An error occurred while copying files. The problem may be temporary. If the problem persists, use Disk Utility to repair your backup disk.


Eight minutes later, and Time Machine is trying to back up again, automatically.


Code:
2018-08-18 15:38:09.994088-0400 localhost backupd[1165]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Starting automatic backup 2018-08-18 15:38:09.996520-0400 localhost backupd[1165]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Failed to find matching sparsebundle in directory '/Volumes/Seagate Time Machine Backup', directory contents: ( ".com.apple.timemachine.donotpresent", ".disk_label", ".disk_label_2x", ".DocumentRevisions-V100", ".DS_Store", ".fseventsd", ".Spotlight-V100", ".TemporaryItems", ".Trashes", ".VolumeIcon.icns", "Backups.backupdb", "tmbootpicker.efi" ) 2018-08-18 15:38:10.633747-0400 localhost backupd[1165]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Backing up to /dev/disk3: /Volumes/Seagate Time Machine Backup/Backups.backupdb 2018-08-18 15:38:15.006217-0400 localhost backupd[1165]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Failed to remove attribute 'com.apple.backupd.SnapshotVolumeFSEventStoreUUID' from 'file:///', error: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted" 2018-08-18 15:38:15.010713-0400 localhost backupd[1165]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Failed to remove attribute 'com.apple.backupd.SnapshotVolumeLastFSEventID' from 'file:///', error: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted" 2018-08-18 15:38:15.010924-0400 localhost backupd[1165]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Failed to remove attribute 'com.apple.backupd.SnapshotVolumeUUID' from 'file:///', error: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted" 2018-08-18 15:38:15.011042-0400 localhost backupd[1165]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Failed to remove attribute 'com.apple.backupd.PreviousSnapshotVolumeUUID' from 'file:///', error: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted" 2018-08-18 15:38:15.011349-0400 localhost backupd[1165]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Failed to remove attribute 'com.apple.backupd.PreviousSnapshotVolumeName' from 'file:///', error: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted" 2018-08-18 15:38:15.011534-0400 localhost backupd[1165]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Failed to remove attribute 'com.apple.backupd.VolumeBytesUsed' from 'file:///', error: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted" 2018-08-18 15:38:15.011665-0400 localhost backupd[1165]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Failed to remove attribute 'com.apple.backupd.VolumeIsCaseSensitive' from 'file:///', error: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted" 2018-08-18 15:38:15.011756-0400 localhost backupd[1165]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Failed to remove attribute 'com.apple.backupd.fstypename' from 'file:///', error: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted" 2018-08-18 15:38:15.011861-0400 localhost backupd[1165]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Failed to remove attribute 'com.apple.backupd.VolumeIsEncrypted' from 'file:///', error: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted" 2018-08-18 15:38:15.217842-0400 localhost backupd[1165]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Starting age based thinning of Time Machine local snapshots on disk '/' 2018-08-18 15:38:15.222720-0400 localhost backupd[1165]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Age based thinning deleted Time Machine snapshot 'com.apple.TimeMachine.2018-08-17-145640' on disk '/ 2018-08-18 15:38:15.236763-0400 localhost backupd[1165]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Age based thinning deleted Time Machine snapshot 'com.apple.TimeMachine.2018-08-18-142608' on disk '/ 2018-08-18 15:38:27.141381-0400 localhost backupd[1165]: (TimeMachine) [com.apple.TimeMachine:TMLogError] Failed to write unlock record UUIDs as extended attribute for disk '/', error: Error Domain=NSPOSIXErrorDomain Code=1 "Operation not permitted" 2018-08-18 15:38:27.790134-0400 localhost backupd[1165]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Created Time Machine local snapshot with name 'com.apple.TimeMachine.2018-08-18-153826' on disk '/' 2018-08-18 15:38:27.793870-0400 localhost backupd[1165]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Declared stable snapshot: com.apple.TimeMachine.2018-08-18-153826 2018-08-18 15:38:28.202990-0400 localhost backupd[1165]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Mounted stable snapshot: com.apple.TimeMachine.2018-08-18-153826 at path: /Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/MacBook Pro (2)/2018-08-18-153826/KL17 source: KL17 2018-08-18 15:38:28.205418-0400 localhost backupd[1165]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Event store UUIDs don't match for volume: KL17 2018-08-18 15:38:29.456911-0400 localhost backupd[1165]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Deep event scan at path:/Volumes/com.apple.TimeMachine.localsnapshots/Backups.backupdb/MacBook Pro (2)/2018-08-18-153826/KL17 reason:must scan subdirs|new event db| 2018-08-18 15:38:29.457029-0400 localhost backupd[1165]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Reading cached event database from: /Volumes/Seagate Time Machine Backup/Backups.backupdb/MacBook Pro (2)/2018-08-18-153828.inProgress/616B0CA7-1472-4672-8E18-6FEE94A9DF0A/.BCE56C28-09D5-3C4A-B4BF-6EDA18EA6DE4.eventdb 2018-08-18 15:38:29.738059-0400 localhost backupd[1165]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Using cached disk scan 2018-08-18 15:38:29.946773-0400 localhost backupd[1165]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Saved event cache at /Volumes/Seagate Time Machine Backup/Backups.backupdb/MacBook Pro (2)/2018-08-18-153828.inProgress/DE3BEE98-494A-4FDE-B05E-C272C83F50E6/.BCE56C28-09D5-3C4A-B4BF-6EDA18EA6DE4.eventdb 2018-08-18 15:38:29.997578-0400 localhost backupd[1165]: (TimeMachine) [com.apple.TimeMachine:TMLogInfo] Not using file event preflight for /
Yours truly, And.reg, "The Mighty" Pain in the Ass
     
reader50
Administrator
Join Date: Jun 2000
Location: California
Status: Offline
Reply With Quote
Aug 18, 2018, 03:59 PM
 
Errors on a random file are non-fatal. TM goes on. The key part is "Backup failed with error 11".

The problem appears to be old inProgress folders. So TM thinks another instance of TM is already running. Deleting the inProgress folders can take a really long time via the Finder because of all the hardlinks.

Someone else suggested renaming the inProgress items in place, by adding "x-" at the beginning of each file. (they're actually folders, with permissions set to not allow opening). If need be, set the external drive to Ignore Permissions to make the name change. Then turn permissions back on after. The tip author suggested a more complicated ACL terminal command.

TM will ignore the mis-named items during the run, then delete them after a run completes. TM can delete them *much* faster than Finder can.

Source reference - but directed at network backups. Most of the steps don't apply to a local drive.
     
ghporter
Administrator
Join Date: Apr 2001
Location: San Antonio TX USA
Status: Offline
Reply With Quote
Aug 18, 2018, 04:31 PM
 
I'm concerned about the security and legal implications of having the phone automatically open when it sees your face. Someone could hold your phone up in front of you, wait for you to open your eyes, and then have full access to what's on your phone.

While the lower false positive rate sounds great, the false positive rate for TouchID is (according to Apple) 1 in 50,000. That's a theoretical rate, obviously. It means that TouchID's rejection rate is pretty high.

Apple says that FaceID has a 1 in 1,000,000 false positive rate, which sounds like "twenty times more secure!!!!!" It's not. FaceID builds a recognition matrix based on a much more complex. much larger structure than simple fingerprints, but it's not likely to be based on 20 times more data. And as I recall, TouchID had some rocky going when first introduced. I'm sure that more time out "in the wild" will both identify normal use issues and reveal exploits (child bypasses mom's FaceID?).

FaceID wins on gee whiz points, but I still feel that I'd be more comfortable with TouchID for the foreseeable future.

By the way, my MBP opens when it detects my Apple Watch. Why could Apple not add something like "if the face is recognized AND the correct Apple Watch is unlocked AND within the correct range of this phone, unlock the phone - else lock the phone and require a complex passcode to open." I would also feel a lot more comfortable about the security of a phone that offered to hard lock if that sort of attempt to open failed.

Glenn -----OTR/L, MOT, Tx
     
And.reg
The Mighty
Join Date: Feb 2004
Location: Well the sports issue was within arm's reach but they closed up shop and kicked me out. And I'm out of toilet paper.
Status: Offline
Reply With Quote
Aug 18, 2018, 06:35 PM
 
Originally Posted by And.reg View Post
another watch out to beta testers that my Time Machine backup (of data on APFS Pro MacBook) keeps failing
This may have been a false alarm, as I think that I figured out what's going on.

So, this morning, I connected my Time Machine backup drive to retrieve a file that I had discarded months ago, but because I was quick about getting the file and then ejecting the hard drive, I did not give the Time Machine backup any opportunity to go beyond some initial preparation, and no copying. But for whatever reason, that process corrupted either the .DS_Store file (see the "code" in my post above) or the snapshot reference to it. Why that file, and why that folder (which I haven't accessed in three months) I will never understand. But, deleting the original .DS_Store file from my Mac and then restarting Time Machine got it to work again. Backup successful.
Yours truly, And.reg, "The Mighty" Pain in the Ass
     
CharlesS
Posting Junkie
Join Date: Dec 2000
Status: Offline
Reply With Quote
Aug 19, 2018, 12:00 AM
 
I'd expect Time Machine to get a clean rewrite at some point to take advantage of APFS's features, many of which seem almost tailor-made for TM. It seems this isn't happening in Mojave, but I wouldn't be surprised at all to see it in the next release after it.

Ticking sound coming from a .pkg package? Don't let the .bom go off! Inspect it first with Pacifist. Macworld - five mice!
     
And.reg
The Mighty
Join Date: Feb 2004
Location: Well the sports issue was within arm's reach but they closed up shop and kicked me out. And I'm out of toilet paper.
Status: Offline
Reply With Quote
Aug 19, 2018, 07:42 PM
 
Wow.

In Finder, Command-L no longer creates an alias. You have to use Control-Command-A to create an alias of a folder/file/whatever in Finder. That's awkward.

In which beta did they change this?
Yours truly, And.reg, "The Mighty" Pain in the Ass
     
OreoCookie
Moderator
Join Date: May 2001
Location: Hilbert space
Status: Online
Reply With Quote
Aug 20, 2018, 12:41 AM
 
Originally Posted by CharlesS View Post
I'd expect Time Machine to get a clean rewrite at some point to take advantage of APFS's features, many of which seem almost tailor-made for TM. It seems this isn't happening in Mojave, but I wouldn't be surprised at all to see it in the next release after it.
Agreed. I wonder whether they will take a half-step measure by just modifying the client side or whether they will go for a full hog re-implementation. I can picture them initially using snapshots on the client side and transmit that to an HFS+-based client drive. A re-implementation may require something along the lines of ZFS send.

One of the big questions here is migration of backup drives: will they offer a HFS+-to-APFS conversion? Although Apple could just punt here and require you to start afresh.
I don't suffer from insanity, I enjoy every minute of it.
     
Chongo  (op)
Addicted to MacNN
Join Date: Aug 2007
Location: Phoenix, Arizona
Status: Offline
Reply With Quote
Aug 21, 2018, 12:11 PM
 
Questions from someone that does not currently have a TM backup drive. Since the multi TB external dives I have seen are HDDs, does Mohave still format them as HFS+ or APFS? I see there are issues backing up APFS drives to existing HFS+ TM drives. I need to get an external backup for my 3TB Fusion drive iMac. It’s that or sign up for Carbonite. Anyone using a cloud service with an APFS drive?
     
subego
Clinically Insane
Join Date: Jun 2001
Location: Chicago, Bang! Bang!
Status: Offline
Reply With Quote
Aug 21, 2018, 06:25 PM
 
You should do cloud anyway. Without it, everything is still vulnerable to fire, burglary, etc.

I prefer Crashplan to Carbonite, but it’s more expensive ($120/year).
     
OreoCookie
Moderator
Join Date: May 2001
Location: Hilbert space
Status: Online
Reply With Quote
Aug 21, 2018, 10:27 PM
 
Backblaze >> Crashplan (unless you want to backup a NAS)

But in my book this is all in addition to my Time Machine backup.
I don't suffer from insanity, I enjoy every minute of it.
     
subego
Clinically Insane
Join Date: Jun 2001
Location: Chicago, Bang! Bang!
Status: Offline
Reply With Quote
Aug 22, 2018, 01:51 AM
 
Originally Posted by OreoCookie View Post
(unless you want to backup a NAS)
[Raises hand]
     
reader50
Administrator
Join Date: Jun 2000
Location: California
Status: Offline
Reply With Quote
Aug 22, 2018, 02:38 AM
 
BackBlaze does back up NAS on their business plan. $50 per year, per computer. I suspect the NAS counts as one computer. If so, you could TM backup all your computers to the NAS. Then back it up to BackBlaze for $50 per year.
     
And.reg
The Mighty
Join Date: Feb 2004
Location: Well the sports issue was within arm's reach but they closed up shop and kicked me out. And I'm out of toilet paper.
Status: Offline
Reply With Quote
Aug 22, 2018, 11:10 AM
 
Breaking News:

"Never Auto-Play" still doesn't work on 18A371a.

And waking Pro MacBook back up from sleep will still sometimes prompt a typed password up front, rather than allow TouchID.
( Last edited by And.reg; Aug 22, 2018 at 11:30 AM. )
Yours truly, And.reg, "The Mighty" Pain in the Ass
     
andi*pandi
Moderator
Join Date: Jun 2000
Location: inside 128, north of 90
Status: Offline
Reply With Quote
Aug 22, 2018, 02:56 PM
 
we need a separate backup thread.
     
turtle777
Clinically Insane
Join Date: Jun 2001
Location: planning a comeback !
Status: Offline
Reply With Quote
Aug 22, 2018, 08:41 PM
 
Just learned something awesome.

Use https://automounter.app/ to mount your NAS somewhere other than /Volume/, and Backblaze will back it up.

H/t to Accidental Tech Podcast.

-t
     
And.reg
The Mighty
Join Date: Feb 2004
Location: Well the sports issue was within arm's reach but they closed up shop and kicked me out. And I'm out of toilet paper.
Status: Offline
Reply With Quote
Aug 28, 2018, 07:15 PM
 
Wow.

Security on macOS Mojave Time Machine backups are so tight, they're sealed tighter than Fort Knox.

I wanted to run sqlite3 on a Safari db file from a few months ago, but Mojave has all of my past home user backups in lock down that, even with sudo, I can't even make a copy of the file. Even though I can access the (visible) folders using Finder, I can't even do an ls or cd into the invisible archived ~/Library/ folder.

This will require some tinkering...
Yours truly, And.reg, "The Mighty" Pain in the Ass
     
And.reg
The Mighty
Join Date: Feb 2004
Location: Well the sports issue was within arm's reach but they closed up shop and kicked me out. And I'm out of toilet paper.
Status: Offline
Reply With Quote
Aug 29, 2018, 06:50 PM
 
Other question:

How do I delete the user "System Administrator" from the login screen?
Yours truly, And.reg, "The Mighty" Pain in the Ass
     
And.reg
The Mighty
Join Date: Feb 2004
Location: Well the sports issue was within arm's reach but they closed up shop and kicked me out. And I'm out of toilet paper.
Status: Offline
Reply With Quote
Sep 16, 2018, 07:07 PM
 
Just updated to the 10th beta. Not looking so great for the around-the-corner GM as some of the bugs that I reported like five betas ago have yet to be fixed.

Just to give you an idea:

http://www.intellicast.com/Local/Wea...ation=USCA0273

In the Mojave betas, it's a lot of blank space, where there should be graphs and charts.

Disable AutoPlay when browsing YouTube still isn't fixed.
Yours truly, And.reg, "The Mighty" Pain in the Ass
     
turtle777
Clinically Insane
Join Date: Jun 2001
Location: planning a comeback !
Status: Offline
Reply With Quote
Sep 16, 2018, 07:32 PM
 
As with the past couple of major MacOS updates, it's probably best to ignore x.0 and x.1, and wait for x.2 or x.3 with your upgrade.

I just upgraded to High Sierra 3 weeks ago

-t
     
reader50
Administrator
Join Date: Jun 2000
Location: California
Status: Offline
Reply With Quote
Sep 16, 2018, 07:36 PM
 
Originally Posted by And.reg View Post
How do I delete the user "System Administrator" from the login screen?
I'm not using Mojave yet, so these instructions are from High Sierra. Disable the root user using Directory Utility.

/System/Library/CoreServices/Applications/Directory Utility

Click the padlock to authenticate. Then go to Edit -> Disable Root User

Sounds like a bug. When the root account is enabled (or other accounts outside the Users folder) the login icon for "Other..." will appear. Which gives user / pass fields to fill in. Up through High Sierra, I've never seen login offer the root account by name.
     
And.reg
The Mighty
Join Date: Feb 2004
Location: Well the sports issue was within arm's reach but they closed up shop and kicked me out. And I'm out of toilet paper.
Status: Offline
Reply With Quote
Sep 17, 2018, 12:57 PM
 
I already disabled it a while back via Terminal. if I try to use Directory Utility then it just asks me to enable it again, then disable it. Same thing happens on login screen.
Yours truly, And.reg, "The Mighty" Pain in the Ass
     
Chongo  (op)
Addicted to MacNN
Join Date: Aug 2007
Location: Phoenix, Arizona
Status: Offline
Reply With Quote
Sep 24, 2018, 03:08 PM
 
I installed Mohave this morning. So far so good. It took about four minutes to download and about 40 minutes to install.
     
reader50
Administrator
Join Date: Jun 2000
Location: California
Status: Offline
Reply With Quote
Sep 24, 2018, 03:34 PM
 
I'm going to wait a little bit. I want to hear more reports on how APFS does on hard drives. Performance and/or bug reports.

Reports say you can still run Mojave from HFS+, but you have to install to a disposable volume using APFS. Then clone to an HFS+ volume. Followed by any user migrations. The report also claimed that Apple is not allowing OS updates if you manually run under HFS+. If true, you could still download and run the updates manually.

Now if Mojave APFS finally implements file checksums, that could get me to upgrade immediately. But I haven't heard any update on that. Without the checksums, I get the HDD performance hit (whatever it is now), with no desired feature additions.
     
And.reg
The Mighty
Join Date: Feb 2004
Location: Well the sports issue was within arm's reach but they closed up shop and kicked me out. And I'm out of toilet paper.
Status: Offline
Reply With Quote
Sep 24, 2018, 08:10 PM
 
Will update with my feedback on Mojave GM after the AdBlock extension is done being a pain in the ass to Safari...
Yours truly, And.reg, "The Mighty" Pain in the Ass
     
And.reg
The Mighty
Join Date: Feb 2004
Location: Well the sports issue was within arm's reach but they closed up shop and kicked me out. And I'm out of toilet paper.
Status: Offline
Reply With Quote
Sep 24, 2018, 08:23 PM
 
Alright, got a dilemma.

YouTube videos still sometimes autoplay upon loading the page, yet I have EVERY possible "Never Autoplay" setting enabled for YouTube.





And yes I am logged into my Google account and make sure that I have the Autoplay slider for each video set OFF.


What gives?

Meanwhile, can someone recommend an adblock extension that DOESN'T mess with Intellicast?

http://www.intellicast.com/Local/Wea...ation=USME0300
Yours truly, And.reg, "The Mighty" Pain in the Ass
     
reader50
Administrator
Join Date: Jun 2000
Location: California
Status: Offline
Reply With Quote
Sep 24, 2018, 09:10 PM
 
Apple has posted the low-level APFS documentation!

Go to their APFS dev page here. The actual specs are in a linked PDF, currently located here. Creation date for the PDF is just 10 days ago.

Could it be that no one has posted this news until now? I've already emailed Coriolis Systems pointing it out (iPartition, iDefrag). Also CharlesS (CharlesSoft). Probably should contact Alsoft too (DiskWarrior). Edit: done.
( Last edited by reader50; Sep 24, 2018 at 09:31 PM. )
     
CharlesS
Posting Junkie
Join Date: Dec 2000
Status: Offline
Reply With Quote
Sep 24, 2018, 10:44 PM
 
Ooooooh.... shiny.

Thanks for posting this, reader50!

Ticking sound coming from a .pkg package? Don't let the .bom go off! Inspect it first with Pacifist. Macworld - five mice!
     
reader50
Administrator
Join Date: Jun 2000
Location: California
Status: Offline
Reply With Quote
Sep 24, 2018, 11:38 PM
 
Skimming the PDF for possible future file checksums: checksums are mentioned when mounting volumes. That would be the metadata integrity checks we already know about. And hashes are mentioned for filename fields, which is kinda odd. I don't think filename corruption is all that common.

Object entries (files, folders) have no fields set aside for checksums/hashes, but there are multiple reserved Extended Fields. You're supposed to preserve their values if you encounter one. However, they don't mention wiping any of the reserved fields if an object is modified, which would be the proper way to handle a not-yet-implemented hash field.

note: APFS favors saving a modified version of a file, before wiping the old one. In that case, the advice on creating reserved fields (populate them with "0") is compatible with a future checksum field. Same result as wiping the hash if a file is overwritten in place.

The reserved field "INO_EXT_TYPE_RESERVED_12" has a unique note:
Donʼt create extended fields of this type. If you find an object of this type in production, file a bug against the Apple File System implementation.
Interesting, an illegal field. I wonder if there's a reward.
     
OreoCookie
Moderator
Join Date: May 2001
Location: Hilbert space
Status: Online
Reply With Quote
Sep 25, 2018, 03:12 AM
 
AFAIK APFS uses checksums to ensure the integrity of file metadata, and due to its flexible design, file data checksums could technically be implemented.
I don't suffer from insanity, I enjoy every minute of it.
     
reader50
Administrator
Join Date: Jun 2000
Location: California
Status: Offline
Reply With Quote
Sep 26, 2018, 12:23 AM
 
Correct. I was looking at definitions for reserved fields, to see how practical that would be. Or for hints that Apple is thinking about it. File checksums could always be added in extended attributes, but the directory entry is the more logical location.

Adding anything to the extended attributes counts as a file modification. Certainly Time Machine thinks so - I had to work around this very issue. But a field in the directory entry can be modified without that concern. And you'd get the checksum for "free" when reading in the directory tree. No need to load another file, or worse, check a resource on each and every file.
     
OreoCookie
Moderator
Join Date: May 2001
Location: Hilbert space
Status: Online
Reply With Quote
Sep 27, 2018, 12:21 AM
 
I am sure you've been following the discussion on file systems and my strong opinion on it: I would have preferred if data checksumming were a first class citizen in APFS that was baked more into the design. Right now, I am happy that it is at least possible to add it later, because apparently, Apple still isn't convinced that data checksumming is actually necessary.

Do you know how ZFS and btrfs implement data block checksumming?
I don't suffer from insanity, I enjoy every minute of it.
     
reader50
Administrator
Join Date: Jun 2000
Location: California
Status: Offline
Reply With Quote
Sep 27, 2018, 12:39 AM
 
Sadly, I do not. The last time I dug deep into low-level filesystems (and started coding a defragger) was with ProDOS on my Apple //GS. Also, my APFS reference skimming was directed at file checksums. I didn't look for evidence of block checksumming.

We'll find out more about file checksums when Apple switches Time Machine stores to APFS. As TM already stores file checksums, we'll see what APFS field Apple uses for that purpose.
     
OreoCookie
Moderator
Join Date: May 2001
Location: Hilbert space
Status: Online
Reply With Quote
Sep 27, 2018, 01:22 AM
 
Time Machine already uses checksums? I thought Time Machine monitors file access in the background and copies files that have been touched since the last backup. Or am I wrong?

Honestly, I was expecting that Apple had finished a rewrite of Time Machine from the ground up in time for Mojave. But I guess we have to wait until next year.
I don't suffer from insanity, I enjoy every minute of it.
     
reader50
Administrator
Join Date: Jun 2000
Location: California
Status: Offline
Reply With Quote
Sep 27, 2018, 03:34 AM
 
According to the tmutil man page:
verifychecksums path ...
Compute a checksum of data contained within a backup and verify the result(s) against checksum information computed at the time of backup.

No output is generated for matching checksums. Issues are reported using the following legend:

! The file's current checksum does not match the expected recorded checksum.
? The file's recorded checksum is invalid.

Beginning in OS X 10.11, Time Machine records checksums of files copied into snapshots. Checksums are not retroactively computed for files that were copied by earlier releases of OS X.
As of High Sierra, the man page makes no other mention of checksums. No command to return the actual value, for example. Or manually compute & store for older files & folders. I do not have Mojave installed yet to check for updates.

The quote above suggests it's only used for integrity checks within TM, probably performed when restoring a file.
     
reader50
Administrator
Join Date: Jun 2000
Location: California
Status: Offline
Reply With Quote
Sep 27, 2018, 03:43 AM
 
Question to anyone who has installed Mojave on a multi-partition drive. When Mojave converts things to APFS on the target partition, does it leave other partitions alone? Or does it try to absorb all the partitions on the drive, into APFS stores?

My main drive is partitioned heavily, with every OS version my MacPro can boot from. 10.5 Leopard through 10.13 High Sierra, with a few spare partitions. If the installer or APFS converter tries to take over the drive, all the older OSes will become unbootable. Everything before High Sierra.
     
OreoCookie
Moderator
Join Date: May 2001
Location: Hilbert space
Status: Online
Reply With Quote
Sep 27, 2018, 07:49 PM
 
I don't know. But I did notice that APFS seems reluctant to convert spinning platter drives (e. g. external hard drives). I am not sure why.

Also, thanks for digging up the info on TimeMachine. Seems like I didn't really understand how it worked under the wraps.
I don't suffer from insanity, I enjoy every minute of it.
     
And.reg
The Mighty
Join Date: Feb 2004
Location: Well the sports issue was within arm's reach but they closed up shop and kicked me out. And I'm out of toilet paper.
Status: Offline
Reply With Quote
Sep 28, 2018, 08:18 AM
 
Sometimes, when returning to my Pro MacBook after I already set the Lock Screen, and then I press any key to wake it, I will be asked to type my password instead of TouchID. This is with no accessories attached, with me using only Apple's apps (Numbers, Safari), and with plenty of battery.

Other times, it will allow me to use TouchID upon wake right away.

It's not consistent. This has been a problem all the way through the betas and they did NOT fix it. (This was never a problem in High Sierra 10.13. Any idea why? Yup, because it just worked in 10.13.)
Yours truly, And.reg, "The Mighty" Pain in the Ass
     
P
Moderator
Join Date: Apr 2000
Location: Gothenburg, Sweden
Status: Offline
Reply With Quote
Oct 1, 2018, 07:23 AM
 
On 10.12, it will ask for the password once a week or if you have been away from the MBP too long. Never bothered with 10.13, don't know if it changed there.
The new Mac Pro has up to 30 MB of cache inside the processor itself. That's more than the HD in my first Mac. Somehow I'm still running out of space.
     
reader50
Administrator
Join Date: Jun 2000
Location: California
Status: Offline
Reply With Quote
Oct 1, 2018, 08:19 AM
 
Installed Mojave. MacPro 4,1 flashed to a 5,1. The App Store was happy to offer Mojave.

It needs some install kinks worked out. Install to a fresh alt partition hung with a "cannot install on this Mac" error, just before the actual install would have started. The logs suggest a missing script file. Creating and booting from an external install drive did the trick, installing to the very same spare partition. Suddenly there were no errors.

The installer played nice with other partitions, only installing to the target partition. I tried with both APFS and HFS+. The installer does not seem to require APFS on an HDD partition. Using the external flash drive version, I did an install to the partition while it was formatted HFS+, and it remained HFS+.

Software Update worked after the HFS+ install (offering an updated print driver), so the rumor that running under HFS+ would disable updates appears to be just a rumor.

However, while I can install and run Mojave (under APFS or HFS+), every time I rebooted, it would hang. Apple logo, but the progress bar does not appear. This usually indicates a bad kextcache, but the usual trick (touch an Extensions folder) did not work for Mojave. I can boot into it exactly once, at the end of an install. Then run as long as I like. But next boot - hang. Until a reinstall.

Later versions of High Sierra gave me this kind of boot hang on some reboots. But touching an Extensions folder works reliably on HS, allowing boot to proceed normally. I haven't narrowed down the Mojave problem yet. Will probably wait for 10.14.1 before trying again. For now I've gone back to my HS partition.
     
reader50
Administrator
Join Date: Jun 2000
Location: California
Status: Offline
Reply With Quote
Oct 2, 2018, 03:41 AM
 
Found a solution, was able to boot back into Mojave. Still needs durability testing though.

I replaced the kextcache (preclinked kernel) with the one installed by the installer. Then locked it so it would not get updated. As the Extensions folders will always be newer than the copy from the installer, macOS will hopefully always do a full boot. This needs further testing though, to make sure the file lock is honored. That I don't have to set the file immutable too.
     
ghporter
Administrator
Join Date: Apr 2001
Location: San Antonio TX USA
Status: Offline
Reply With Quote
Oct 6, 2018, 10:09 PM
 
I haven’t gotten around to moving my 2013 MBP up to Mojave. I’m not sure I’m in a hurry to do it. So far, I haven’t seen anything “new and compelling,” while I certainly don’t have any problems with the current OS.

Glenn -----OTR/L, MOT, Tx
     
And.reg
The Mighty
Join Date: Feb 2004
Location: Well the sports issue was within arm's reach but they closed up shop and kicked me out. And I'm out of toilet paper.
Status: Offline
Reply With Quote
Oct 7, 2018, 08:34 AM
 
Originally Posted by And.reg View Post
Alright, got a dilemma.

YouTube videos still sometimes autoplay upon loading the page, yet I have EVERY possible "Never Autoplay" setting enabled for YouTube.





And yes I am logged into my Google account and make sure that I have the Autoplay slider for each video set OFF.


What gives?
Oh... I think that I JUST figured it out.

So, if Safari detects that the active tab is loading a page on YouTube with an embedded video, Safari will ignore all of those settings and auto-play it anyway. But if you tell Safari, "Hey, launch this YouTube page (with its video) in a separate tab and I'll look at it later" so that this browser tab remains in the inactive state, it won't play.

That's STILL NOT the same as "Never auto-play," so, Apple should fix this.
Yours truly, And.reg, "The Mighty" Pain in the Ass
     
 
Thread Tools
 
Forum Links
Forum Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Top
Privacy Policy
All times are GMT -4. The time now is 05:34 AM.
All contents of these forums © 1995-2017 MacNN. All rights reserved.
Branding + Design: www.gesamtbild.com
vBulletin v.3.8.8 © 2000-2017, Jelsoft Enterprises Ltd.,