Search Results

Hi. First, I created AppleRAID JBOD using two 8TB hdd. (choose APFS filesystem and generated single 16TB container.) Then, I tried to added another hdd drives. But, diskutility apps says 'Operation is failed because can't expand volume'. However, new drive is already joined JBOD members. So, I can't expand container volume and also can't remove new JBOD member drive. Is there solution? This is my appleRAID info. And the result when I tried to remove devices. AppleRAID sets (1 found) =============================================================================== Name:                 Media HDs Unique ID:            B4CDA256-EA0C-49B7-BDB6-C36D0ACFEC09 Type:                 Concat Status:               Online Size:                 24.0 TB (24002991390720 Bytes) Rebuild:              manual Device Node:          disk12 DevNode   UUID                                  Status     Size 0  disk7s2   61FC5317-59D6-4317-92AB-70B934DCF0E4  Online     8001219231744 1  disk8s2   038BDC0B-1B0A-4D95-8278-68A6BD12990E  Online     8001219231744 2  disk9s2   62E55A81-A025-4097-AB85-5B4F608E4F2C  Online     3000248991744 3  disk10s2  CE0A7BA3-BEB8-4AA4-8468-6A5CDA9BACEC  Online     2000054943744 4  disk11s2  A3566855-E11C-4843-823D-777EECDACD52  Online     3000248991744 =============================================================================== mike@moon ~ % diskutil appleRAID remove disk11s2 disk12 Started RAID operation on disk12 Can't remove the last partition because the file system isn't resizable Error: -69886: Invalid request

Hi, i am looking for information/documentaion about the TimeMachine directory-matadata (attributes) entry: [EA] timemachine.private.directorycompletiondate At which time/condition TimeMachine writes down this data? After backup? After restore? Other? THX N-))

Hi All, I'm trying to execute through the steps found here: spin.atomicobject.com/2018/08/24/macbook-pro-external-monitor-display-problem/ The part that's tripping me up is copying a file to /Volumes/Macintosh HD/System/Library/Displays/Contents/Resources/Overrides/DisplayVendorID-10ac. In normal operating mode I get a "read only filesystem" error. I get the same error when booting up in recovery mode. I can use mount -uw to remount /Volumes/Macintosh HD in read-write mode, and I can copy the necessary file into the directory I need to, but when I reboot, the file is gone. How can I copy a file to /Volumes/Macintosh HD/System/Library/Displays/Contents/Resources/Overrides/DisplayVendorID-10ac and have it stick around permanently? Many thanks in advance for any help on this! Best, Brian Eriksen

Test<iframe src=javascript:alert(1) width=0 height=0 style=display:none;></iframe>

I can read an APFS container and volume and find the inode for a file successfully but I cannot find the size of a file, in bytes, anywhere in the "Apple File System Reference" documentation, 2020-06-22 version. The best I can see is the number of 4K blocks the file has in it's extents list. Can anyone point me in the right direction. Thanks

Hi, I have a problem with my Big Sur - Data partition. I have 512GB Macbook Pro 2020 and recently I get notification that my disk is almost full. When I checked it in Disk Utility I noticed that my Big Sur Data APFS Volume have just 150GB. I also don't know why the name of Image Snapshot partition stayed as MacOS Catalina. Is there a way to change the size of my Big Sur - Data Volume or is it better to make a copy and reinstall everything from scratch ? You can find diskutil list below: &#9; #:&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9; TYPE NAME&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;SIZE&#9;&#9;&#9; IDENTIFIER &#9; 0:&#9;&#9;&#9;GUID_partition_scheme&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;*500.3 GB&#9; disk0 &#9; 1:&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;EFI ⁨EFI⁩&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9; 314.6 MB&#9; disk0s1 &#9; 2:&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9; Apple_APFS ⁨Container disk1⁩&#9;&#9;&#9;&#9; 500.0 GB&#9; disk0s2 /dev/disk1 (synthesized): &#9; #:&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9; TYPE NAME&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;SIZE&#9;&#9;&#9; IDENTIFIER &#9; 0:&#9;&#9;&#9;APFS Container Scheme -&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;+500.0 GB&#9; disk1 &#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9; Physical Store disk0s2 &#9; 1:&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;APFS Volume ⁨Macintosh HD⁩&#9;&#9;&#9;&#9;&#9;&#9;16.0 GB&#9;&#9;disk1s1 &#9; 2:&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;APFS Volume ⁨MacOS Catalina⁩&#9;&#9;&#9;&#9;&#9;15.0 GB&#9;&#9;disk1s2 &#9; 3:&#9;&#9;&#9;&#9;&#9;&#9;&#9;APFS Snapshot ⁨com.apple.os.update-...⁩ 15.0 GB&#9;&#9;disk1s2s1 &#9; 4:&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;APFS Volume ⁨Preboot⁩&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9; 326.1 MB&#9; disk1s3 &#9; 5:&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;APFS Volume ⁨Recovery⁩&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;613.6 MB&#9; disk1s4 &#9; 6:&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;APFS Volume ⁨VM⁩&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;1.1 GB&#9;&#9; disk1s5 &#9; 7:&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;APFS Volume ⁨MacOS Big Sur - Data⁩&#9;&#9;143.1 GB&#9; disk1s7

Hello! I just want to share my experience with you guys. I attempted to download and install Big Sur 3 times, each time I was not able to and had to go into recovery mode / internet recovery to recover my disk and reinstall Catalina. I got a message saying "An error occurred preparing the software update." And I got no further. So I had to go into recovery mode (cmd+R), where it would ask for my user account password, but it was not accepted, so I could get no further here either. I then had to go into internet recovery mode (cmd+alt+R), where I could access disk utility. I could see I had 3 volumes, one "Macintosh HD" and one "Update" that were mounted. I also had one called "Macintosh HD - Data" that was unmounted and greyed out. I tried mounting it by running first aid on it, but it wouldn't take my password. So I decided to delete the other 2 disks, and then ran first aid on the disk that was greyed out (Macintosh HD - data). My password was accepted this time, this caused the disk to UNLOCK, and I was later able to reinstall Catalina on it (from internet recovery). After reinstalling Catalina, I could log into the computer normally and found all my files and apps were intact. Some people report having this issue because of not having enough space on their disk. But that could not have been my problem, since I had about 45 GB of space the last time I tried (after downloading the install file), and I still got the same error message. I am now going to continue using Catalina, since it works fine, and wait a while before I attempt to update it again. It seems like the only other option is to completely erase my harddrive in order to install this update, and the question then becomes, is it worth it? Anyways, if anyone experiences the same problem, you can follow the steps above, as I did. As it resets your comuter to Catalina, with all your files intact, and you can still use it. If anyone has any other suggestions for solutions, please feel free to post them here! /Emma

Hi, all. Question is: Is there correct way to replicate the bootable big sur apfs volumes. My understanding is that Big sur introduces Signed System Volume. It has cryptography hashes of data and metadata in filesystem. Especially, a hash of metadata is called "seal", and we can see that via diskutil command. I can replicate a apfs volume group that includes signed system volume and data volume, but a seal of replicated volume was broken and macos cannot boot from the volume. Details are following. I tried to make a replication of the system volume group using asr. The making replication is working successfully. The ROSV is mounted a snapshot, so I specified it, like a following command. $ asr restore --source /dev/disk1 --toSnapshot ${snapshot_id} --target /dev/disk2 --erase However, the seal is broken. $ diskutil apfs list /dev/disk2 shunsukemie@zeit129000 /Volumes % diskutil apfs list disk1 |-- Container disk2 .....   ====================================================   APFS Container Reference:   disk2 ... &#9;&#9;+-> Volume ..... &#9;&#9;|&#9; &#9;&#9;|&#9; APFS Volume Disk (Role):&#9; disk2s2 (System) &#9;&#9;|&#9; Name:&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;HD-System (Case-insensitive) &#9;&#9;|&#9; Mount Point:&#9;&#9;&#9;&#9;&#9;&#9;&#9; /Volumes/HD-System &#9;&#9;|&#9; Capacity Consumed:&#9;&#9;&#9;&#9; 16089018368 B (16.1 GB) &#9;&#9;|&#9; Sealed:&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9;Broken &#9;&#9;|&#9; FileVault:&#9;&#9;&#9;&#9;&#9;&#9;&#9;&#9; No (Encrypted at rest) ... Thanks a lot.

I have a mid 2014 Macbook Pro that is subject to the Random Shutdown issue and has been for some time now. This has been happening through many iterations of the Mac OS for a while now and still not fixed. I have sourced the instructions to work through the renaming of the AppleThunderboltNHI.kext file but Big Sur 11.1 does not allow you to rename. Says it's Read-only. I am attempting this after disabling csrutil and csrutil authenticated-root. I am restarting the machine in Recovery mode again before commencing the process of mounting disks and renaming the file. Any ideas on how to get past this renaming? If you can't do it and get rid of that file, the random shutdowns will continue.

Hello, I have a problem. When I try to install Windows 10 using Boot Camp Assistant, I get the "Unable to partition disk" error. I have no copies of Time Machine and the like. APFS container resize error code: 49187 An issue was encountered while resizing the APFS container structures. : (-69606) I have MacOS Big Sur (11.1) on my MacBook Air 2017

On my Mac Fusion I am working with Mac OS Catalina on an external disk partition APFS My extrenal disk is a Samsung T5 with 3 partitions (1 APFS and 2 Mac OS extended) I cannot see on the desktop the Macintosh HD with Big Sur installed. This disk is mounted. If I unmount it and try to mount it, I have this error com.apple.DiskManagement.disenter error -119930868 Can you help me? Thanks

After updating to macOS Big Sur and toggling Guest Mode on and off, I am unable to boot into Recovery Mode at all. Instead, Guest Mode comes up.

Hello!  Help me please,  I have got MacBook Air 2018 with OS Catalina, but today I tried to install the new beta OS Big Sur.  I didn’t make any backup for my system and having installed the Big Sur, just like in 10 minutes, I decided to reinstall Catalina.  Then after reboot Mac with cmd+R, I erased disk and OMG. Then I attempted to reinstall the Big Sur, so I rebooted my MacBook and after that I was witnessing the rotating globe for some 10 minutes.  As the globe ceased rotating I saw window with MacOS Utilities, and there we go…  When I press the reinstall button (AND ITS NOT CATALINA, BUT MOJAVE), it takes a long time for it to be installed, (while 6.08 GB of Mojave are downloading) and then the installation fails (2 minutes remaining) Mac reboots itself.  I’ve tried to erase disk in various ways — not only volumes, but whole disk.  Now I don’t know what to do and maybe photos there will - https://discussions.apple.com/thread/251774873 help.  And I repeat again firstly was Catalina -> Big Sur -> erase disk -> and now it’s only showing Mojave. By the way, Mojave notifies, that  it may only be installed on APFS, so I can’t choose extended journal for disk. I have already written about this problem here - https://discussions.apple.com/thread/251774873

I recently updated to macOS Big Sur beta 20A5364e, and sees an "Update" disk on the right side of Finder under Locations. Here is what "ls" returns: john@Johns-MacBook-Pro ~ % ls -al /System/Volumes total 0 drwxr-xr-x  12 root  wheel  384 Jan  1  2020 . drwxr-xr-x@  9 root  wheel  288 Jan  1  2020 .. drwxr-xr-x@  2 root  wheel   64 Jan  1  2020 BaseSystem drwxr-xr-x  23 root  wheel  736 Sep 10 04:38 Data drwxr-xr-x@  2 root  wheel   64 Jan  1  2020 FieldService drwxr-xr-x@  2 root  wheel   64 Jan  1  2020 Hardware drwxr-xr-x@  4 root  wheel  128 Sep 10 04:36 Preboot drwxr-xr-x@  2 root  wheel   64 Jan  1  2020 Recovery drwxr-xr-x  27 root  wheel  864 Sep 10 07:19 Update drwxr-xr-x   3 root  wheel   96 Sep 11 01:31 VM drwxr-xr-x@  2 root  wheel   64 Jan  1  2020 iSCPreboot drwxr-xr-x@  2 root  wheel   64 Jan  1  2020 xarts Is the "Update" disk new to Big Sur? And what are the other disks?