You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I have the cache directory on an external drive, it complains about the "cache directory settings incorrect". Doing a "repair" does not work. Using a volume on the internal drive works fine. I have also tried the following to manually set them:
DRIVE_NAME=$1
DRIVE_PATH="/Volumes/$DRIVE_NAME"
# Check if the drive exists
if [ ! -d "$DRIVE_PATH" ]; then
echo "Drive $DRIVE_NAME not found at $DRIVE_PATH. Make sure it's connected and the name is correct."
exit 1
fi
# Step 1: Attempt to ignore ownership on this drive
echo "Setting 'Ignore ownership on this volume' for $DRIVE_NAME..."
sudo diskutil enableOwnership "$DRIVE_PATH" # Enable to modify permissions
sudo diskutil disableOwnership "$DRIVE_PATH" # Disable ownership to ignore
# Step 2: Reset flags and permissions on the entire drive, including any cache directories
echo "Resetting flags and permissions for $DRIVE_NAME (including cache directories)..."
sudo chflags -R nouchg "$DRIVE_PATH"
sudo chown -R $(whoami) "$DRIVE_PATH"
sudo chmod -R 755 "$DRIVE_PATH"
sudo chmod -R -N "$DRIVE_PATH"
Even after the above, it still complains. I have tried this on multiple machines and with freshly formatted drives/volumes. This looks to be similar to issue #19.
📋 Steps to Reproduce
Open Mist
set the cache directory to a newly formatted external drive.
try to download / install a macOS installer
get the error
click on repair
try again - same result
✅ Expected Behaviour
be able to repair and download to external drive
💻 Environment
Mist version (App menu ⇨ About Mist): 0.20.0 (and earlier versions)
macOS Version (sw_vers): 12.7.6 (and other version of 12)
Hardware (system_profiler SPHardwareDataType):
multiple systems : MacBook air 2013/2015/2017, Macbook Pro 2015/2018
📷 Screenshots
ℹ️ Additional context
The text was updated successfully, but these errors were encountered:
I am having the same issue when configuring Mist to use, as the cache directory, a location on an external drive. Well, in this case, it is another internal drive but a drive that is NOT "Macintosh HD."
I have a 2015 iMac that shipped with the 2TB Fusion Drive. I've decoupled the drives and am using the 128GB SSD as my "Macintosh HD" boot drive formatted as APFS and running 15.2 Sequoia. According to System Profiler, the SSD interface is SATA on this machine. The 2TB mechanical hard drive is formatted as HFS+ (Mac OS Extended, Journaled) and identified as "Internal HD." This drive is connected via SATA.
The original post states "external drive" and I just assumed that meant a physically external drive connected via USB, FireWire, Thunderbolt, etc. I post my comment only to share that the issue also occurs with non-external drives that aren't the primary "Macintosh HD" system drive.
My gut tells me that the issue lies with the cache not being on the macOS system drive (or the permissions not being set correctly when the cache is set to a location not on the macOS system drive) and the problem exists whether the non-system drive is an internal or external drive.
🪲 Description
When I have the cache directory on an external drive, it complains about the "cache directory settings incorrect". Doing a "repair" does not work. Using a volume on the internal drive works fine. I have also tried the following to manually set them:
Even after the above, it still complains. I have tried this on multiple machines and with freshly formatted drives/volumes. This looks to be similar to issue #19.
📋 Steps to Reproduce
Open Mist
set the cache directory to a newly formatted external drive.
try to download / install a macOS installer
get the error
click on repair
try again - same result
✅ Expected Behaviour
be able to repair and download to external drive
💻 Environment
sw_vers
): 12.7.6 (and other version of 12)system_profiler SPHardwareDataType
):📷 Screenshots
ℹ️ Additional context
The text was updated successfully, but these errors were encountered: