Skip to main content
Solved

LLVM Profile Error: Failed to write file "default.profraw": Read-only file system - Deploy Command

P
Forum|alt.badge.img+3

After the upgrade to MacOS 12.3, the Jamf login screen went away, i found that running this command would fix the issue : 

/usr/local/bin/authchanger -reset -jamfconnect

Although after creating a policy and trying this through execute command i get the following error:

LLVM Profile Error: Failed to write file "default.profraw": Read-only file system

 

I tried the command in terminal manually with sudo permissions and it did work. 
How can i fix it ? 

Best answer by Wiebmer

I also see the same error "LLVM Profile Error: Failed to write file "default.profraw": Read-only file system on macOS Sonoma when running Jamf Connect Version: 2.29.0 Build 5339.

View original

    J
    Forum|alt.badge.img+7

    Executing the command via Jamf policy, I also got this as a script result.

     

    P
    Forum|alt.badge.img+3
    joshuaaclark wrote:

    Executing the command via Jamf policy, I also got this as a script result.

     


    Hi Joshuaaclark, thanks for helping me out. I have created a new policy and added the above command under Execute Command in Files and Processes. Is that what you meant ? because i still get the error.
    What am i doing wrong here ?


    J
    Forum|alt.badge.img+7

    No solution. I was posting here to say I am having the same issue. I am also looking for help.

     

    P
    1 person likes this
    • P
      Punjabiwifi
    K
    Forum|alt.badge.img+1
    • Kreegs
    • New Contributor
    • March 31, 2022

    Same here.  Applied the policy but getting the "LLVM Profile Error: Failed to write file "default.profraw": Read-only file system" error

    M
    Forum|alt.badge.img+1
    • MaryDuffy
    • New Contributor
    • April 6, 2022

    Also receiving this on a few macbooks after upgrading to Monterey.

    Steven_Xu
    Forum|alt.badge.img+7
    • Steven_Xu
    • Contributor
    • May 26, 2022

    same here.

    K
    Forum|alt.badge.img+1

    Any one find a fix? 

     

    Im getting this as well 

    S
    Forum|alt.badge.img
    • skedaddle
    • New Contributor
    • August 1, 2022

    Unfortunately, we ran into this issue with a Macbook from 2017 updating to Monterey. We ended up having to try the following in Recovery Mode to disable JAMF connect. 

    JAMF Docs 

    dvasquez
    Forum|alt.badge.img+16
    • dvasquez
    • Valued Contributor
    • October 11, 2022
    skedaddle wrote:

    Unfortunately, we ran into this issue with a Macbook from 2017 updating to Monterey. We ended up having to try the following in Recovery Mode to disable JAMF connect. 

    JAMF Docs 


    the link you posted does not work...

    Thank you.

    N
    Forum|alt.badge.img+3
    • n123
    • New Contributor
    • November 3, 2022

    Faced the same with Jamf Connect v 2.5.0, so I'd suggest you to check yours and update if possible.

    It was fixed in a Jamf Connect v 2.8.0:
    https://docs.jamf.com/jamf-connect/2.8.0/documentation/Release_History.html

    markopolo
    Forum|alt.badge.img+8
    • markopolo
    • Contributor
    • November 4, 2022

    I'm getting this too, with Jamf Connect 2.16 installed on 12.6.1. Anyone have a solution? I'm just trying to reset authchanger to default (no Jamf Connect) for some testing.

    S
    Forum|alt.badge.img+2
    • stu_ross
    • New Contributor
    • November 7, 2022

    I am also getting this with Jamf Connect 2.16 installed on 12.5.1

    C
    Forum|alt.badge.img+4
    • cmoran
    • New Contributor
    • November 7, 2022

    We saw this error but upgrading to 2.17 resolved it. 

    markopolo
    1 person likes this
    • markopolo
      markopolo
    markopolo
    Forum|alt.badge.img+8
    • markopolo
    • Contributor
    • November 28, 2022
    cmoran wrote:

    We saw this error but upgrading to 2.17 resolved it. 


    I just got this on 2.17.0 trying to reset authchanger to Jamf Connect.

    M
    Forum|alt.badge.img+2
    • memile
    • New Contributor
    • December 7, 2022

    Same.. Just pushed v2.17 and have seen this in the deployment logs. Does it affect any functionality?

    chafe
    Forum|alt.badge.img+4
    • chafe
    • Contributor
    • February 2, 2023
    memile wrote:

    Same.. Just pushed v2.17 and have seen this in the deployment logs. Does it affect any functionality?


    Im asking one of my users now about this. It says his failed and im not sure if its a problem or not

    eatkins
    Forum|alt.badge.img+1
    • eatkins
    • New Contributor
    • March 22, 2023

    I've been trying to run a script stored in the private/tmp folder keep getting this Read-Only file system error. I'm having trouble finding a way around it. Running the script as user.

    Wiebmer
    Forum|alt.badge.img+2
    • Wiebmer
    • Jamf Heroes
    • December 11, 2023

    I also see the same error "LLVM Profile Error: Failed to write file "default.profraw": Read-only file system on macOS Sonoma when running Jamf Connect Version: 2.29.0 Build 5339.

    S
    B
    M
    4 people like this
    • S
      stu_ross
    • B
      bsullivancadent
    • M
      memile
    • P
      Punjabiwifi
    chris_kemp
    Forum|alt.badge.img+20
    • chris_kemp
    • Jamf Heroes
    • February 20, 2025

    Resurrecting from the dead... Seeing this error returning from a script run from Self Service, v. 11.14. It worked functionally, but returned the LLVM Profile error as the result. Will let Jamf know what I'm seeing...

    Reply


    Terms & ConditionsCookie settingsAccessibility statement

    Cookie policy

    We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

     
    Cookie settings