How can I delete a folder backed up via Time Machine to a .backupbundle disk image? When I try to delete the folder, I get the error message, "The operation can't be completed because backup items can't be modified." I found a similar question, "How can I delete a file marked as backup item?" The accepted answer says that this is a bug that will be fixed in a coming update. Unfortunately, this answer was written in 2011 –– 11 years ago. I tried to comment on the answer, but I did not have enough reputation. > A little more precision regarding what you tried would be helpful. > "when I Delete the folder". Which folder? Is that on the source disk, > or is it in the backup? And how did you try to delete? Also what > version of macOS and what format (HFS+ or APFS) is the backup disk > image? /Volumes/Time Machine Backups/Backups.backupdb/MacBook Pro (Retina)/2021-05-02-065359/Macintosh HD 1/Users/brianschack/Transmission Downloads On the backup. I tried dragging the folder to the Trash in the Dock. macOS Big Sur 11.2.3. Mac OS Extended (Case-sensitive, Journaled). > The accepted answer on your linked questin is basically wrong. The > highest voted answer is correct - you are trying to delete from a > protected area. You cannot just delete Time Machine files from Finder. @Ryccardo wrote the highest-voted answer to the question, "How can I delete a file marked as backup item?" He says, "[L]ocate the item in the 'in space' Time Machine view[.]" This is a backup of a computer that I traded in. When I go to the in-space Time Machine view on my current computer, it shows me the backup of my current computer –– not the computer that I traded in. He also writes, "There exists a helper program (command-line binary) [...] which allows you to supply a command and argument to completely bypass the access restrictions." When I navigate to /System/Library/Extensions, I do not see TMSafetyNet.kext. In a different answer, @Evan Kroske writes, "It seems like the bypass program doesn't exist on Big Sur." How can I delete a file marked as backup item?

Right now we have a single iMac in the house and I have two external hard drives. One is connected to the iMac and used for TimeMachine backups. The other is a few miles away (thanks Mom!) to act as off-site backup, and I swap them once every couple of weeks. Thinking of adding another computer to the mix and I don't necessarily want to purchase two more disks to keep it backed up, so I am considering upgrading to TimeCapsule. But it has an in-built disk. So how do people either do a) an offsite backup b) swap disks like I used to c) anything that will work similarly!

I have a Time Machine backup on an Airport Time Capsule (name: computername.sparsebundle). Now I want to access that backup on a USB disk formatted as exFAT. Several online resources describe the migration **to** a Time Capsule. My question relates to the opposite migration, away from the Time Capsule. Is this possible? If so, how can I migrate this backup from the Airport Time Capsule (sparsebundle) to a USB disk formatted as exFAT?

I have an external SSD that is attached to my MacBook Air whenever I'm at my desk (since the tiny 120GB internal drive cannot be upgraded). I recently discovered that the external drive had become corrupted, so I purchased a new one, and was able to to migrate most files successfully from the old drive to the new drive using rsync. In the process, I found that a number of files had "vanished", and I was able to rescue these from my backup. My concern now is that maybe other files have gone missing, and I would like to compare the contents of the drive with some previous Time Machine monthly snapshots, to get a list of files that are in the snapshot but not in the current drive. Then I can work out if they were files I had actually intended to delete, or if they just got lost and need to be restored. I could purchase another SSD, copy the whole Time Machine snapshot to that, and then use "rsync -ni --ignore-existing" to generate the file list comparing the two SSDs. But is there a better way, where I can just generate this information directly from interacting with the Time Machine snapshot? My first thought was to try rsync but I didn't expect it would work with a Time Machine backup, and after a long wait nothing was happening. I know tmutil can compare the most recent snapshot with the current state - but can it do that for a specified previous snapshot, and for a specific volume only? Or is there some other way? Thank you! (I am on a 2018 MacBook Air running Sonoma 14.6.1 - my Time Machine backup is on a 4th generation Time Capsule, usually connected wirelessly but currently connected wired)

I have old sparsebundle files on my Apple Time Capsule. I can't seem to mount them. Error I get is no volumes found. I can see package contents, and size on disk is 113.4 GB. I've tried: hdiutil attach -nomount -noverify -noautofsck /Volumes/Joy/.sparsebundle, however, that only loads as /dev/disk2, but against it it doesn't say GUID_Partition_scheme and there is no /dev/disk2s1 Apple_partition_map or /dev/disk2s2 Apple_HFSX. I've also tried to use Migration Assistant, it shows the Time Machine sparsebundle, but it says no volumes. Please advise. Can I create a new empty sparsebundle using hdiutil -create, and copy the package contents from the no volume sparsebundle to this new one? Any other ideas how to fix it? Thanks in advance.

Can I upgrade my Time Capsule to a larger internal drive and keep my original backup(s)? I'm aware you can drop in the new disk, the restore it as a new TC using AirPort Utility, and I'm also aware you can migrate backup(s) from an existing TimeMachine drive to a new one - but I want to do both: I want to replace the 500gb drive in my Time Capsule (2nd gen, 2009) to a 1tb drive, and I want to keep the existing backup(s) from the 500gb to the new drive, so everything is as it was, just with a larger internal drive. I understand it's not as simple as swapping the drive, restoring it as a new TC and then using CCC to copy the data from the original drive, so is there a solution to what I want to achieve? Basically I want to upgrade the original TC drive to a larger one and not lose my previous backup(s).

Due to [APFS having a mind of its own](https://www.reddit.com/r/mac/comments/75shcg/how_to_disable_time_machine_localmobile_backup/) and filling the hard disk with unwanted snapshots, I made a cron to run tmutil deletelocalsnapshots xxx. Later I found out that running this command while a backup is in progress will stop the backup. How can I know if a time machine backup is in progress to avoid running the command? The man page for tmutil doesn't list any status command. Right now I'm doing the following in the script, since now backups mount at /Volumes/Time Machine Backups/: ls -d /Volumes/Time* 2>/dev/null|grep Machin >/dev/null if [[ $? != 0 ]]; then # run here tmutil snapshot deletion commands fi However, this doesn't seem to be very precise. The volume may be mounted some minutes later after a backup has started, and also stopping a backup leaves that mounted volume for a while. Finally, the name of the mounted volume might change in the future, making the check useless.

I picked up an Airport Express before they disappeared from the market, with the objective of using its audio-out to connect remotely to a HiFi. My set-up is as follows: - Time Capsule connected to cable modem. Internet + Wifi + time machine working properly. - New, not yet hooked, Airport Express. I gave up after many failed attempts using AirPort Utility (under High Sierra 10.13.6 on a MacBook Pro) to extend the network: "An unexpected error occurred. Try again." Connecting the Airport Express using Ethernet to its LAN line, I created an independent WiFi network. Now I can AirPlay form iOS just fine. I can also AirPlay from the MacBook **but** only after I switch from the Time Capsule's Wifi to the Airport Express's Wifi. How can I extend the network? I've tried resetting the unit by disconnecting power, holding the reset button for 10 seconds, and then reconnecting power while the reset button is still pressed; as well as switching Wi-Fi TCP/IP to "Link-Local Only" under "Configure IPv6". I vaguely have the sense that it all worked nicely until I hit the "update firmware" red button for the Airport Express. Is there a way to regress the firmware?

First, I have none of this equipment, so I can't just test it and see ..Yet. I Know I could hack a Time Capsule into a RaidBox via SATA/eSATA connector, But that's not the route I'd like to go. If you plug in a NAS to a A1470 TC does acknowledge it's existence ? And Can you store to it? I want to get a TC A1470. replace the small drive with a larger TB unit. Use that for my Time Machine Backups. Then add a 16TB NAS (wired) to the ethernet on the TC. Like a Drobo 5-Bay DAS Storage. Mac, Mojave, External NAS, Time Capsule,

I have a MacBook Pro with Snow Leopard and a Time Capsule. In the last few days every backup took over 100GB of data. I don't know if there is some issue with permissions or something similar, but to be sure I removed all the old backups and reformatted the Time Capsule disk. I've also run filesystem checks and permission checks on my MBP disk using the installation disk. Then I've restarted backup from scratch, the first backup took 160GB and for a few days following backups has worked fine (with a decent quantity of data for each run). Now after some days I started my MBP and the backup is still in progress, when it was started it says that it needs to backup about 40GB of data (which obviously is not true) and while running the limit is increasing constantly, currently is at 95GB and it continue to grow. I suspect that there could be some hardware issue with Time Capsule, but not sure. Any hint to solve this issue?

I am using macOS Server's Time Machine service to centralize backups for my mac workstations/laptops. One of the laptops hasn't been backed-up since upgrading to a new MacBook Pro (using Migration Assistant) 6 months ago. I'm now connecting the laptop Time Machine to the server, but instead of using the old backups with the same name, it's creating new ones with a "1" at the end of the name (e.g. MacBook Pro 1 when the name of the existing backup and mac is MacBook Pro). How do I force Time Machine to use the existing backups so that we may keep all the backup history? For what it's worth, I believe the macOS Server Time Machine service is no more than a SMB share from the laptop's perspective. I have seen posts on how to do inherit a Time Machine backup on a locally attached drive, but I'm not sure how to do this on a remote sparsebundle.

Periodically Time Machine verifies sparsebundle backups with fsck_hfs. When the sparsebundle is on a Time Capsule (TC) it does this by creating a partial and much smaller representation of the sparsebundle on the TC, transferring the result to the Mac into

/private/var/db/com.apple.backupd.backupVerification

and then running fsck_hfs on it locally (it mounts the local sparsebundle as can be seen with diskutil list). The problem is that it takes a very long time for fsck_hfs to verify this representation of very large TC sparsebundles (e.g. >24hrs). [This leaves the timemachine process showing in the menu as if it was stuck 'verifying' with the real Time Capsule disk apparently no longer mounted under /Volumes - which confuses many into thinking the process has died] fsck_hfs is launched by its parent process backupd with the parameters -f -n -x -E. There are various posts about fsck_hfs working much more efficiently if allowed to use more memory (-c option). By default (at least on my system) it seems to be limited to 3Gb. My question is, is there any way to pass a config that might cause backupd to launch fsck_hfs with the additional (-c) parameter and so run faster?

I am trying to make a internet configuration to improve my wifi in the whole house, but I don't want to switch between different wifi names, I have a Airport Time Capsule Third Generation, Google wifi Router and a modem, my house is two stories and my basement, where I need internet signal too. My Problem; I have my modem and router in the same room, and I was able to connect an ethernet cable to my Time Capsule, so far so good, but I can make the Time Capsule extend my wifi connection. I read that doing a roaming configuration would be perfect in this case. However, I don't have the whole explanation to do that. When I connect the Google router and the Time Capsule, my understanding is I have to put in a bridge mode, but if I only do that and switch the wireless setting in the Time Capsule off, then the Network option goes off (bridge mode); too, but at that point the Time Capsule is not doing any internet wifi capabilities, to turn that option I have to go back to the wireless setting and chose the network Mode to Extend a wireless network and leave the name and password as they are, unfortunately if I do that my Time Capsule goes flashing amber, the google wifi goes amber too and the internet goes amber too. Could you help me to solve this?

With nothing else to do today, I decided to solve the lingering connectivity problems in the back yard. I have an old AirPort Extreme that I replaced with a Time Capsule many years ago, so I thought I would put that in the garage and pull some outdoor Ethernet. The system came up immediately when I plugged it in, and as expected I got a blinking amber light. I opened AirPort Utility on my Mac and plugged the Extreme into the TC using an Ether. It asked for a password, but I had no idea what it might be, so I did a factory reset. After the reboot, the system appears as a new WiFi device in Other Wi-Fi Devices in AirPort Utility under the "New AirPort Base Stations" group, which is what I would expect. However, when I select it in the menu, after briefly saying "Joining AirPort Extreme", a large dialog box appears: "An unexpected error occured. Try again" Off to a great start! I tried another reset, as well as a power cycle, same outcome. Where to go from here?

My Time Capsule is old and gives lots of errors in backups, so I bought a (LaCie) external HDD to connect it to and do my Time Machine backups from that instead; Apple tells me I can do this . As per Apple's instructions I reformatted the external HD as APFS with the new name and plugged it into the Time Capsule. I immediately got a notification on my computer asking me if I wanted to do a Time Machine backup on the newly named HD. I thought "great" and said yes... and then it refused to recognize it after that. In Time Machine preferences the new HD didn't appear, only the old Time Capsule. I go to AirPort Utility to the Time Capsule and go to Edit/Disks; "Enable file sharing" is turned on but only the Time Capsule appears there, not the new HD. Disk Utility doesn't recognize the new HD, nor does it appear on Locations in the finder sidebar or on Volumes in the terminal. The new HD is plugged in and its power light on the back is on, and the computer recognized it when it was plugged in before, but nothing. How can I get my Mac to recognize the HD and back up to it?

My 2 terabyte Time Capsule used to allow a guest wifi network but since I had to switch to bridge mode to accommodate my cable internet provider (while installing an Exchange server w/o a static ip address) I no longer have the guest option. Why? Is there a workaround?

For my backup I use an encrypted virtual disk on a sparsebundle file that is stored in an external hard drive attached on a router via USB. This file is accessed via samba but for one reason I decided to use the HD directly attached to my mac. So I changed permission to access the file, because previously they were assigned to the user created on the router to access via smb, but I haven't only chmod the directory. I chown it for my mac user. Now when I try to mount the .sparsebundle it mount but Time Machine says it's in a readonly state and I'm not even able to actually read it. I tried to search the web for some days but I wasn't able to find the solution. I tried to force fsck_hfs but below is the result. Anyone can help me? I specify that the physical volume on the external drive is an EXT4 filesystem because the router runs on Linux. Maybe it add information to find the solution. sudo hdiutil attach -nomount -noverify -noautofsck /Volumes/Data/Dati/Time\ Machine.sparsebundle/ /dev/disk3 Apple_partition_scheme /dev/disk3s1 Apple_partition_map /dev/disk3s3 Apple_HFS sudo fsck_hfs -rc -fd /dev/disk3s3 ** /dev/rdisk3s3 Executing fsck_hfs (version hfs-407.50.6). Invalid content in journal ** Checking Journaled HFS Plus volume. The volume name is Time Machine ** Checking extents overflow file. Unused node is not erased (node = 2784) ** Checking catalog file. ** Rebuilding catalog B-tree. Disk full error ** The volume Time Machine could not be repaired. Invalid content in journal (4, 0) **EDIT:** Actually it could be also a filesystem problem, not (only) a permission one hdiutil attach /Volumes/Data/Dati/Time\ Machine.sparsebundle/ hdiutil: attach failed - no mountable file systems For testing purpose I attached again the HDD to the router and reenabled the smb share. Here is some screenshot of my setup. The smb share mounted on macos, with the sparsebundle that always mount in readonly The HDD mounted on the homemade NAS (/dev/sda3) The configuration of the Samba share (access -> read and write, even if we cannot read it from the screenshot) The permission settings on the directory mounted on the router **EDIT 2:** Executed fsck directly from the smb share. I cannot understand the difference but the output is much more verbose: mbp:~ asdasd$ sudo hdiutil attach -nomount -noverify -noautofsck /Volumes/HDD-3TB/Time\ Machine.sparsebundle/ /dev/disk2 Apple_partition_scheme /dev/disk2s1 Apple_partition_map /dev/disk2s3 Apple_HFS mbp:~ asdasd$ sudo fsck_hfs -dyf /dev/disk2s3 journal_replay(/dev/disk2s3) returned 0 ** /dev/rdisk2s3 Using cacheBlockSize=32K cacheTotalBlock=32768 cacheSize=1048576K. Executing fsck_hfs (version hfs-407.50.6). Invalid content in journal ** Checking Journaled HFS Plus volume. The volume name is Time Machine ** Checking extents overflow file. Unused node is not erased (node = 2784) Unused node is not erased (node = 2785) Unused node is not erased (node = 2786) Unused node is not erased (node = 2787) Unused node is not erased (node = 2788) Unused node is not erased (node = 2789) Unused node is not erased (node = 2790) Unused node is not erased (node = 2791) Unused node is not erased (node = 2792) Unused node is not erased (node = 2793) Unused node is not erased (node = 2794) Unused node is not erased (node = 2795) Unused node is not erased (node = 2796) Unused node is not erased (node = 2797) Unused node is not erased (node = 2798) Unused node is not erased (node = 2799) Unused node is not erased (node = 2800) Unused node is not erased (node = 2801) Unused node is not erased (node = 2802) Unused node is not erased (node = 2803) Unused node is not erased (node = 2804) Unused node is not erased (node = 2805) Unused node is not erased (node = 2806) Unused node is not erased (node = 2807) Unused node is not erased (node = 2808) Unused node is not erased (node = 2809) Unused node is not erased (node = 2810) Unused node is not erased (node = 2811) Unused node is not erased (node = 2812) Unused node is not erased (node = 2813) Unused node is not erased (node = 2814) Unused node is not erased (node = 2815) ** Checking catalog file. hfs_swap_BTNode: invalid forward link (0xC4663BAF) hfs_swap_BTNode: invalid backward link (0x5C275BF7) hfs_swap_BTNode: invalid node kind (-86) hfs_swap_BTNode: invalid node height (125) hfs_swap_BTNode: invalid record count (0x7A07) Invalid record count (4, 138355) hfs_swap_BTNode: invalid forward link (0x4503418D) hfs_swap_BTNode: invalid backward link (0x2A4FB6A0) hfs_swap_BTNode: invalid node kind (13) hfs_swap_BTNode: invalid node height (204) hfs_swap_BTNode: invalid record count (0xA115) Invalid record count (4, 138349) hfs_swap_BTNode: invalid forward link (0xA89C3ED0) hfs_swap_BTNode: invalid backward link (0x01F29D8B) hfs_swap_BTNode: invalid node kind (58) hfs_swap_BTNode: invalid node height (244) hfs_swap_BTNode: invalid record count (0x4C27) Invalid record count (4, 117907) hfs_swap_BTNode: invalid forward link (0xBD984CDE) hfs_swap_BTNode: invalid backward link (0x605E0605) hfs_swap_BTNode: invalid node kind (82) hfs_swap_BTNode: invalid node height (255) hfs_swap_BTNode: invalid record count (0x545E) Invalid record count (4, 15346) hfs_swap_BTNode: invalid forward link (0x10253D99) hfs_swap_BTNode: invalid backward link (0xE20E4C52) hfs_swap_BTNode: invalid node kind (5) hfs_swap_BTNode: invalid node height (62) hfs_swap_BTNode: invalid record count (0x46A0) Invalid record count (4, 15350) hfs_swap_BTNode: invalid forward link (0x89065B23) hfs_swap_BTNode: invalid backward link (0xEC5EA33C) hfs_swap_BTNode: invalid node kind (109) hfs_swap_BTNode: invalid node height (138) hfs_swap_BTNode: invalid record count (0x22B2) Invalid record count (4, 15351) hfs_swap_BTNode: invalid forward link (0xCB62D10A) hfs_swap_BTNode: invalid backward link (0xE4D99839) hfs_swap_BTNode: invalid node kind (38) hfs_swap_BTNode: invalid node height (178) hfs_swap_BTNode: invalid record count (0xA660) Invalid record count (4, 15354) hfs_swap_BTNode: invalid forward link (0x96DA8F15) hfs_swap_BTNode: invalid backward link (0x0425140D) hfs_swap_BTNode: invalid node kind (55) hfs_swap_BTNode: invalid node height (193) hfs_swap_BTNode: invalid record count (0xB64A) Invalid record count (4, 15356) hfs_swap_BTNode: invalid forward link (0x1BFF8923) hfs_swap_BTNode: invalid backward link (0x322A6002) hfs_swap_BTNode: invalid node kind (-86) hfs_swap_BTNode: invalid node height (50) hfs_swap_BTNode: invalid record count (0x2556) Invalid record count (4, 15361) hfs_swap_BTNode: invalid forward link (0x55587FAC) hfs_swap_BTNode: invalid backward link (0xBFFCD97E) hfs_swap_BTNode: invalid node kind (53) hfs_swap_BTNode: invalid node height (31) hfs_swap_BTNode: invalid record count (0x3D2E) Invalid record count (4, 15363) hfs_swap_BTNode: invalid forward link (0xF0AB994A) hfs_swap_BTNode: invalid backward link (0xD761E74A) hfs_swap_BTNode: invalid node kind (52) hfs_swap_BTNode: invalid node height (241) hfs_swap_BTNode: invalid record count (0x83C7) Invalid record count (4, 15359) hfs_swap_BTNode: invalid forward link (0x8265BB41) hfs_swap_BTNode: invalid backward link (0xDBAB6D74) hfs_swap_BTNode: invalid node kind (-117) hfs_swap_BTNode: invalid node height (89) hfs_swap_BTNode: invalid record count (0xB62B) Invalid record count (4, 15366) hfs_swap_BTNode: invalid forward link (0xA075EE7A) hfs_swap_BTNode: invalid backward link (0xA396FB09) hfs_swap_BTNode: invalid node kind (4) hfs_swap_BTNode: invalid node height (249) hfs_swap_BTNode: invalid record count (0xE600) Invalid record count (4, 15367) hfs_swap_BTNode: invalid forward link (0x60AE6546) hfs_swap_BTNode: invalid backward link (0x2DC43D0E) hfs_swap_BTNode: invalid node kind (25) hfs_swap_BTNode: invalid node height (163) hfs_swap_BTNode: invalid record count (0x1620) Invalid record count (4, 15372) hfs_swap_BTNode: invalid forward link (0x14D20EF4) hfs_swap_BTNode: invalid backward link (0x6DA1EB27) hfs_swap_BTNode: invalid node kind (-43) hfs_swap_BTNode: invalid node height (13) hfs_swap_BTNode: invalid record count (0x3B82) Invalid record count (4, 15376) hfs_swap_BTNode: invalid forward link (0x4502411B) hfs_swap_BTNode: invalid backward link (0x27F70985) hfs_swap_BTNode: invalid node kind (-71) hfs_swap_BTNode: invalid node height (133) hfs_swap_BTNode: invalid record count (0x391E) Invalid record count (4, 15380) hfs_swap_BTNode: invalid forward link (0xD5E9CF80) hfs_swap_BTNode: invalid backward link (0x8D0C5384) hfs_swap_BTNode: invalid node kind (95) hfs_swap_BTNode: invalid node height (81) hfs_swap_BTNode: invalid record count (0x68C2) Invalid record count (4, 15384) hfs_swap_BTNode: invalid forward link (0xCD183754) hfs_swap_BTNode: invalid backward link (0x4162C8FC) hfs_swap_BTNode: invalid node kind (24) hfs_swap_BTNode: invalid node height (46) hfs_swap_BTNode: invalid record count (0x6AAA) Invalid record count (4, 15388) hfs_swap_BTNode: invalid forward link (0x30398884) hfs_swap_BTNode: invalid backward link (0x5D6E1DEF) hfs_swap_BTNode: invalid node kind (94) hfs_swap_BTNode: invalid node height (35) hfs_swap_BTNode: invalid record count (0xB4BA) Invalid record count (4, 15390) hfs_swap_BTNode: invalid forward link (0x9ED1D2C2) hfs_swap_BTNode: invalid backward link (0x927DFDD5) hfs_swap_BTNode: invalid node kind (-17) hfs_swap_BTNode: invalid node height (229) hfs_swap_BTNode: offset #0 invalid (0x9FF7) (blockSize 0x2000 numRecords 1843) Invalid node structure (4, 15392) hfs_swap_BTNode: invalid forward link (0x7293EA34) hfs_swap_BTNode: invalid backward link (0x1079EF12) hfs_swap_BTNode: invalid node kind (35) hfs_swap_BTNode: invalid node height (7) hfs_swap_BTNode: invalid record count (0x6341) Invalid record count (4, 15399) hfs_swap_BTNode: invalid forward link (0xC34E551E) hfs_swap_BTNode: invalid backward link (0xB58FFB11) hfs_swap_BTNode: invalid node kind (52) hfs_swap_BTNode: invalid node height (154) hfs_swap_BTNode: invalid record count (0x7A42) Invalid record count (4, 15406) hfs_swap_BTNode: invalid forward link (0x62012680) hfs_swap_BTNode: invalid backward link (0x25D211FD) hfs_swap_BTNode: invalid node kind (89) hfs_swap_BTNode: invalid node height (87) hfs_swap_BTNode: invalid record count (0x6038) Invalid record count (4, 15414) hfs_swap_BTNode: invalid forward link (0xE8995EC5) hfs_swap_BTNode: invalid backward link (0xACFEC80F) hfs_swap_BTNode: invalid node kind (115) hfs_swap_BTNode: invalid node height (240) hfs_swap_BTNode: invalid record count (0x6CED) Invalid record count (4, 15430) hfs_swap_BTNode: invalid forward link (0x4E0F412C) hfs_swap_BTNode: invalid backward link (0xEB45452D) hfs_swap_BTNode: invalid node kind (21) hfs_swap_BTNode: invalid node height (253) hfs_swap_BTNode: invalid record count (0x8B26) Invalid record count (4, 15439) hfs_swap_BTNode: invalid forward link (0x16E2F4F5) hfs_swap_BTNode: invalid backward link (0xB2D9EC11) hfs_swap_BTNode: invalid node kind (4) hfs_swap_BTNode: invalid node height (90) hfs_swap_BTNode: invalid record count (0x59F3) Invalid record count (4, 15443) hfs_swap_BTNode: invalid forward link (0xFE2CA3C7) hfs_swap_BTNode: invalid backward link (0x8E2D4CAA) hfs_swap_BTNode: invalid node kind (-11) hfs_swap_BTNode: invalid node height (238) hfs_swap_BTNode: invalid record count (0x8B13) Invalid record count (4, 15453) hfs_swap_BTNode: invalid forward link (0xB1B3FE24) hfs_swap_BTNode: invalid backward link (0x06F47091) hfs_swap_BTNode: invalid node kind (126) hfs_swap_BTNode: invalid node height (171) hfs_swap_BTNode: invalid record count (0x54F7) Invalid record count (4, 15457) hfs_swap_BTNode: invalid forward link (0x7B8EDD20) hfs_swap_BTNode: invalid backward link (0x86BB009C) hfs_swap_BTNode: invalid node kind (-30) hfs_swap_BTNode: invalid node height (82) hfs_swap_BTNode: invalid record count (0x9C0B) Invalid record count (4, 15459) hfs_swap_BTNode: invalid forward link (0x3385DB18) hfs_swap_BTNode: invalid backward link (0xD6BA8FAD) hfs_swap_BTNode: invalid node kind (-119) hfs_swap_BTNode: invalid node height (192) hfs_swap_BTNode: invalid record count (0x5DE7) Invalid record count (4, 15451) hfs_swap_BTNode: invalid forward link (0xF61BE3A7) hfs_swap_BTNode: invalid backward link (0xB9C758D4) hfs_swap_BTNode: invalid node kind (-8) hfs_swap_BTNode: invalid node height (132) hfs_swap_BTNode: invalid record count (0x9329) Invalid record count (4, 15466) hfs_swap_BTNode: invalid forward link (0xCE4305BC) hfs_swap_BTNode: invalid backward link (0xE513F9D8) hfs_swap_BTNode: invalid node kind (-103) hfs_swap_BTNode: invalid node height (227) hfs_swap_BTNode: invalid record count (0x5868) Invalid record count (4, 15470) hfs_swap_BTNode: invalid forward link (0xB6E6C582) hfs_swap_BTNode: invalid backward link (0xBF967F87) hfs_swap_BTNode: invalid node kind (16) hfs_swap_BTNode: invalid node height (95) hfs_swap_BTNode: invalid record count (0xD4BD) Invalid record count (4, 15474) hfs_swap_BTNode: invalid forward link (0x43C7A9AD) hfs_swap_BTNode: invalid backward link (0x55670FA5) hfs_swap_BTNode: invalid node kind (-61) hfs_swap_BTNode: invalid node height (43) hfs_swap_BTNode: invalid record count (0x6EFA) Invalid record count (4, 15476) hfs_swap_BTNode: invalid forward link (0xF930D5AA) hfs_swap_BTNode: invalid backward link (0x92E89158) hfs_swap_BTNode: invalid node kind (-66) hfs_swap_BTNode: invalid node height (97) hfs_swap_BTNode: invalid record count (0x3969) Invalid record count (4, 15478) hfs_swap_BTNode: invalid forward link (0x0356D5D6) hfs_swap_BTNode: invalid backward link (0x8C032195) hfs_swap_BTNode: invalid node kind (41) hfs_swap_BTNode: invalid node height (110) hfs_swap_BTNode: invalid record count (0x8BC2) Invalid record count (4, 15504) hfs_swap_BTNode: invalid forward link (0x719EAB8D) hfs_swap_BTNode: invalid backward link (0x866A3F4B) hfs_swap_BTNode: invalid node kind (60) hfs_swap_BTNode: invalid node height (52) hfs_swap_BTNode: invalid record count (0x4268) Invalid record count (4, 15510) hfs_swap_BTNode: invalid forward link (0xE9849E68) hfs_swap_BTNode: invalid backward link (0x4444F22C) hfs_swap_BTNode: invalid node kind (120) hfs_swap_BTNode: invalid node height (202) hfs_swap_BTNode: invalid record count (0xCA19) Invalid record count (4, 118664) Invalid node structure (4, 45169) Invalid sibling link (4, 45169) Node 45169's back link is 0x0; expected 0x7758 disk offset = 0xcd8fd000, size = 0x2000 Invalid sibling link (4, 45169) Node 45169's forward link is 0x0; expected 0xb074 disk offset = 0xcd8fd000, size = 0x2000 Invalid node height (4, 45169) Index key doesn't match first node key Invalid index key (4, 45169) Invalid node structure (4, 45189) Invalid sibling link (4, 45189) Node 45189's back link is 0x0; expected 0xb082 disk offset = 0xcd925000, size = 0x2000 Invalid sibling link (4, 45189) Node 45189's forward link is 0x0; expected 0xb081 disk offset = 0xcd925000, size = 0x2000 Invalid node height (4, 45189) Index key doesn't match first node key Invalid index key (4, 45189) Invalid node structure (4, 45185) Invalid sibling link (4, 45185) Node 45185's back link is 0x0; expected 0xb085 disk offset = 0xcd91d000, size = 0x2000 Invalid sibling link (4, 45185) Node 45185's forward link is 0x0; expected 0xb089 disk offset = 0xcd91d000, size = 0x2000 Invalid node height (4, 45185) Index key doesn't match first node key Invalid index key (4, 45185) Invalid node structure (4, 45200) Invalid sibling link (4, 45200) Node 45200's back link is 0x0; expected 0xb08e disk offset = 0xcd93b000, size = 0x2000 Invalid sibling link (4, 45200) Node 45200's forward link is 0x0; expected 0xb092 disk offset = 0xcd93b000, size = 0x2000 Invalid node height (4, 45200) Index key doesn't match first node key Invalid index key (4, 45200) Invalid node structure (4, 45206) Invalid sibling link (4, 45206) Node 45206's back link is 0x0; expected 0xb09a disk offset = 0xcd947000, size = 0x2000 Invalid sibling link (4, 45206) Node 45206's forward link is 0x0; expected 0xb09c disk offset = 0xcd947000, size = 0x2000 Invalid node height (4, 45206) Index key doesn't match first node key Invalid index key (4, 45206) Invalid node structure (4, 45212) Invalid sibling link (4, 45212) Node 45212's back link is 0x0; expected 0xb096 disk offset = 0xcd953000, size = 0x2000 Invalid sibling link (4, 45212) Node 45212's forward link is 0x0; expected 0x18d4b disk offset = 0xcd953000, size = 0x2000 Invalid node height (4, 45212) Index key doesn't match first node key Invalid index key (4, 45212) Invalid node structure (4, 45217) Invalid sibling link (4, 45217) Node 45217's back link is 0x0; expected 0xb09f disk offset = 0xcd95d000, size = 0x2000 Invalid sibling link (4, 45217) Node 45217's forward link is 0x0; expected 0xb0a5 disk offset = 0xcd95d000, size = 0x2000 Invalid node height (4, 45217) Index key doesn't match first node key Invalid index key (4, 45217) Invalid node structure (4, 45232) Invalid sibling link (4, 45232) Node 45232's back link is 0x0; expected 0xb0b5 disk offset = 0xcd97b000, size = 0x2000 Invalid sibling link (4, 45232) Node 45232's forward link is 0x0; expected 0xb0b7 disk offset = 0xcd97b000, size = 0x2000 Invalid node height (4, 45232) Index key doesn't match first node key Invalid index key (4, 45232) Invalid node structure (4, 101709) Invalid sibling link (4, 101709) Node 101709's back link is 0x0; expected 0xb0bc disk offset = 0xe92b5000, size = 0x2000 Invalid sibling link (4, 101709) Node 101709's forward link is 0x0; expected 0xb0bd disk offset = 0xe92b5000, size = 0x2000 Invalid node height (4, 101709) Index key doesn't match first node key Invalid index key (4, 101709) Invalid node structure (4, 45245) Invalid sibling link (4, 45245) Node 45245's back link is 0x0; expected 0x18d4d disk offset = 0xcd995000, size = 0x2000 Invalid sibling link (4, 45245) Node 45245's forward link is 0x0; expected 0xb0c1 disk offset = 0xcd995000, size = 0x2000 Invalid node height (4, 45245) Index key doesn't match first node key Invalid index key (4, 45245) Invalid node structure (4, 132677) Invalid sibling link (4, 132677) Node 132677's back link is 0x0; expected 0x20646 disk offset = 0xf84a5000, size = 0x2000 Invalid sibling link (4, 132677) Node 132677's forward link is 0x0; expected 0x7760 disk offset = 0xf84a5000, size = 0x2000 Invalid node height (4, 132677) Index key doesn't match first node key Invalid index key (4, 132677) Invalid node structure (4, 30560) Invalid sibling link (4, 30560) Node 30560's back link is 0x0; expected 0x20645 disk offset = 0xc66db000, size = 0x2000 Invalid sibling link (4, 30560) Node 30560's forward link is 0x0; expected 0x20655 disk offset = 0xc66db000, size = 0x2000 Invalid node height (4, 30560) Index key doesn't match first node key Invalid index key (4, 30560) Invalid node structure (4, 45251) Invalid sibling link (4, 45251) Node 45251's back link is 0x0; expected 0x18d50 disk offset = 0xcd9a1000, size = 0x2000 Invalid sibling link (4, 45251) Node 45251's forward link is 0x0; expected 0xb0d0 disk offset = 0xcd9a1000, size = 0x2000 Invalid node height (4, 45251) Index key doesn't match first node key Invalid index key (4, 45251) Invalid node structure (4, 45265) Invalid sibling link (4, 45265) Node 45265's back link is 0x0; expected 0x20683 disk offset = 0xcd9bd000, size = 0x2000 Invalid sibling link (4, 45265) Node 45265's forward link is 0x0; expected 0xb0d5 disk offset = 0xcd9bd000, size = 0x2000 Invalid node height (4, 45265) Index key doesn't match first node key Invalid index key (4, 45265) ** The volume Time Machine could not be verified completely. volume check failed with error 7 volume type is pure HFS+ primary MDB is at block 0 0x00 alternate MDB is at block 0 0x00 primary VHB is at block 2 0x02 alternate VHB is at block 1952453214 0x7460125e sector size = 512 0x200 VolumeObject flags = 0x07 total sectors for volume = 1952453216 0x74601260 total sectors for embedded volume = 0 0x00 CheckForClean - could not get VHB/MDB at block 1952453214 CheckHFS returned -1317, fsmodified = 0

My setup here is several MBPs backing up to an Apple Time Capsule. Backups are encrypted. 1. I boot to recovery mode on the MBP I want to restore to (Cmd+R). 2. Choose to restore from a Time Machine backup. 3. Choose the Time Capsule in the list, and enter its network password. Works fine. I can now see the backups. 4. Choose the particular MBP backup image I want to restore, and am prompted for its encryption password. 5. Enter this, but it doesn't work. Wrong password, apparently. Tried repeatedly. If I boot the MBP normally I can see in Keychain Access that the password I'm typing is 100% correct. No doubt about it. I made sure to set the keyboard language correctly in recovery mode (it defaults to US English but I'm British). Still locked out. I can browse the backup just fine when macOS is booted. I doubt the backup is corrupted but, like I say, in recovery mode I'm not even getting far enough to find out. The password for the encrypted backup image just isn't being accepted. I've had this happen too in the past when I was utterly sure I had the right password, and I ended-up just abandoning the backup and starting with a fresh install. I can't do that here. Anybody got a clue as to how I can access this backup? Why do I have a feeling I'm encountering one of those serious bugs that Apple knows about but brushes under the carpet?

My home network is served by a Time Capsule 802.11ac, connected to an Airport Extreme 802.11ac via wired Ethernet to extend the range of the Time Capsule. The Airport Extreme just died. I opened it up, checked that the power supply is OK (it's outputting 12 V just fine, and not just on its own, but with all connectors plugged in), cleaned everything with compressed air, but it's still dead. I'm looking for a replacement WiFi repeater/router, and obviously with the discontinuation of the AirPort line, it's not an option. Looks like mesh WiFi is all the rage these days. My question is, are they going to be compatible with the existing Time Capsule in the network? Can anyone recommend a specific model which they've had success with? And while beggars can't be choosers, I'd really like to keep using the Ethernet connection to avoid wasting wireless bandwidth if possible.

I want to make any possibility of losing files on my Mac completely obsolete. Time Machine is awesome, but saving files to single physical hard drive is, well, not safe at all. So, I guess, what I need is to back up Time Machine's backup to a cloud and make sure that my files are being stored in more than one copy in different locations. Then possibility of losing files is too insignificant to bother ever. And the second thing is encryption. Time Machine backups are not encrypted! Why, Apple? So, I need to encrypt it before saving to the cloud. This, probably, makes it even more complicated, as now i have one huge file instead of bunch of smaller independently synched files. Are there ready-to-use solutions? This problem seems quite important, so probably it's solved already, right? Though, I haven't found anything. Among possible solutions, i see this one: Backup data to a Time Capsule and backup Time Capsule to Google Cloud Storage using Syncovery, as suggested [here](https://apple.stackexchange.com/questions/195714/backup-time-capsule-to-cloud-online-backup-provider) . Though, I'm not sure how easy it will be to setup backing up from Capsule to the cloud.