How to change the boot order of APFS volumes? [duplicate]

This question already has an answer here:

  • How do I set OS X to boot by default? 2 answers

I recently set up a new APFS volume to support dual boot for the macOS Catalina beta alongside my Mojave install. Unfortunately, this new “beta OS” volume seems to have set itself up as the default boot volume.

How can I change the order of volumes so that the more stable OS takes priority?

Should i upgrade old volumes to new cryptsetup encyption mode?

old cryptsetup default is es-cbc-essiv:sha256. the new one is aes-xts-plain64:sha256. i don’t know that much about cryptography but i assume the standard was changed for a reason. also there can be found information like:

[…] if your device is still encrypted with the previous (cryptsetup <1.6.0) default cipher –cipher aes-cbc-essiv, more information leakage may occur from trimmed sector observation than with the current default.

so should i upgrade my old encrypted volumes?

How to prevent auto mounting of encrypted APFS volumes by diskarbitrationd

running 10.14.5 on a 2019 iMac.

diskarbitrationd is responsible for noticing the appearance of new block devices and mounting them. this kind of auto mounting can be prevented by configuring /etc/fstab with lines such as the following:

LABEL=VolumeName none apfs rw,noauto

This works for all types of filesystems (including unencrypted APFS) except encrypted APFS. On restart, diskarbitrationd attempts to mount the volume and a popup appears with an authentication dialog (one for each encrypted volume) requesting the encryption passphrase. Does anyone know how to stop diskarbitrationd from automatically mounting encrypted APFS volumes?

Thanks in advance.

ZFS volumes appearing in file manager

I am running Ubuntu 19-04

I have created a mirrored ZFS pool with drives /dev/sde and /dev/sdf

sudo zpool create -m /media/storage storage mirror /dev/sde /dev/sdf 

I created the pool mounted in the /media directory so it would show up in my file manager.

The output of “zpool status” is:

pool: storage state: ONLINE scan: none requested config:  NAME        STATE     READ WRITE CKSUM storage     ONLINE       0     0     0   mirror-0  ONLINE       0     0     0     sde     ONLINE       0     0     0     sdf     ONLINE       0     0     0  errors: No known data errors 

However there are two additional 8.4 MB volumes also now appearing in my file manager labelled /dev/sde9 and /dev/sdf9.

enter image description here

I am guessing these volumes are meta data associated with the pool?

Usually when I get unwanted volumes showing up in my file manager I fire up the Disks utility and edit the mount options, however in this case these volumes do not show up in Disks. I am assuming Disks does not recognize the ZFS file system.

Is there any way to stop these volumes appearing in my file manager GUI? They serve no purpose and just clutter up the GUI.

Win 10 +Ubuntu dual Boot – Live USB cannot see my SSD volumes but Win10 works fine

I am look for some advice/ help on this perplexing issue that has been hounding me for days now.

I am not sure if this is Ubuntu Issue or Lenovo issue.

I have X1 Carbon 6th Gen. It came with 512 SSD with windows 10. I split SSD into 2 parts, and installed ubuntu 18.04 into the second one. Grub is my boot manager

Everything was working fine. One day, Ubuntu crashes. On subsequent boot, it takes me to initramfs prompt, saying that I need to run fsck manually on /dev/nvme0n5. Once I run that, it says that it cannot re-mount nvme0n5 – no such file or directory exists. It happens every single time.

I googled a bit. I was told I need to run fsck on nvme0n5 outside of system using Live USB. I created Ubuntu Live USB using Rufus with Gpt and UEFI. When I boot in, I was not able to see nvme0n5 using $ fdisk -l. Moreover, I can’t see any partition except USB on Gparted

Since then I have tried:

Live USB with/ without Secure Boot option

  • Disabling Bitlocker Some people suggested changing SSD config to AHCI
  • from Raid. I cannot see any such option in my BIOS utility. In fact,
  • I hardly see any information on SSD in boot Disable UEFI only boot to
  • Legacy, Both options in BIOS
  • Run ubuntu in recovery option – it always gets stuck on purple screen with inital ramdisk … even with nomodeset options.

In all of this, Win 10 works perfectly fine. I thought about re-installing Ubuntu. However, all online guides suggest I do it via Live USB, and I can’t find my SSD volume when I try to install via Live USB option.

Any advice/ help would be a lifesaver!

Can I use variables when referring to volume groups and logical volumes in a kickstart file?

I have variables set up in the %pre section that look like this:

%pre VOLGROUP=$  (lvdisplay |grep VG | awk '{print $  3}' |head -1) vgchange -a y $  VOLGROUP ROOTVOL=$  (lvdisplay |grep root | grep Path | awk '{print $  3}') HOMEVOL=$  (lvdisplay |grep home | grep Path | awk '{print $  3}') SWAPVOL=$  (lvdisplay |grep swap | grep Path | awk '{print $  3}') %end 

Are those variables accessible to Anaconda? So far they seem to be ignored.

Access Apple’s APFS volumes from Windows

I have a SSD drive which is removed from my Macbook. I need to recover my files from this drive. Because of not having enough space on another Macbook drive, I must to use Windows computer but the computer doesn’t recognise the drive which has apfs volumes.

How can I represent apfs drive on windows? I’m using PhotoRec recovery application. I should show up my drive like others to use recovery application.

Deleted an APFS Volume, but it still shows as “Other Volumes” claimed space within the container

I have an older MacBook Pro running OS X 10.13.6, the last version supported on the hardware. It has an SSD which was upgraded to APFS a while ago. A few months back, unfixable filesystem corruption developed (APFS – sigh). The total amount of used space on the filesystem was less than half the size of the drive capacity, so I decided to “fix” the corruption by using Disk Utility to create a new Volume within the SSD Container and copied the boot volume to this with Carbon Copy Cloner.

The new Volume approach worked. After a few months I decided I was satisfied that it was all working as expected and I didn’t need the old Volume, so went to Disk Utility, selected the old Volume (at that point named “Old Mac HD”) and used the “remove” button in the toolbar. This did get rid of the named Volume, but not the space it consumed. It still gets listed as “Other Volumes” in all GUIs (e.g. About This Mac and Disk Utility), but is NOT showing up in a list obtained from diskutil.

What gives? How can this exist as far as the GUI is concerned (and all free space reporting tools) yet not exist as far as the usually more accurate, lower level command line tool is concerned? More to the point, how do I actually delete this now-invisible, unmountable, unwanted Volume?

  • This is not the same question as those related to the VM volume, preboot (as far as I know) or how to resize containers (and attempting to resize the disk1 container to maximum with diskutil just, unsurprisingly, complains that there’s no change in size being requested; the container is already at full size; it’s a problem with the APFS volumes within it).


$   diskutil apfs list APFS Container (1 found) | +-- Container disk1 1AD6D668-918D-49EF-BCFB-D47BA2B128A5     ====================================================     APFS Container Reference:     disk1     Size (Capacity Ceiling):      959987367936 B (960.0 GB)     Minimum Size:                 777500598272 B (777.5 GB)     Capacity In Use By Volumes:   692608249856 B (692.6 GB) (72.1% used)     Capacity Not Allocated:       267379118080 B (267.4 GB) (27.9% free)     |     +-< Physical Store disk0s2 3443C641-413D-4232-8BB7-BBAAA805899D     |   -----------------------------------------------------------     |   APFS Physical Store Disk:   disk0s2     |   Size:                       959987367936 B (960.0 GB)     |     +-> Volume disk1s2 311035E5-562D-4703-A61D-B95DA47C6D14     |   ---------------------------------------------------     |   APFS Volume Disk (Role):   disk1s2 (Preboot)     |   Name:                      Preboot (Case-insensitive)     |   Mount Point:               Not Mounted     |   Capacity Consumed:         135266304 B (135.3 MB)     |   FileVault:                 No     |     +-> Volume disk1s3 51EC93A4-2585-4729-A550-14AEA58D3F79     |   ---------------------------------------------------     |   APFS Volume Disk (Role):   disk1s3 (Recovery)     |   Name:                      Recovery (Case-insensitive)     |   Mount Point:               Not Mounted     |   Capacity Consumed:         2555449344 B (2.6 GB)     |   FileVault:                 No     |     +-> Volume disk1s4 90162998-42CB-42A7-B0AC-3DEF8231D23C     |   ---------------------------------------------------     |   APFS Volume Disk (Role):   disk1s4 (VM)     |   Name:                      VM (Case-insensitive)     |   Mount Point:               /private/var/vm     |   Capacity Consumed:         8589959168 B (8.6 GB)     |   FileVault:                 No     |     +-> Volume disk1s5 7ECF8825-686F-4D4B-A94A-10D7911C927E         ---------------------------------------------------         APFS Volume Disk (Role):   disk1s5 (No specific role)         Name:                      Macintosh HD (Case-insensitive)         Mount Point:               /         Capacity Consumed:         343116922880 B (343.1 GB)         FileVault:                 No 

Disk Utility screenshot

About This Mac screenshot

Volume info screenshot