Mindzman wrote:
sudo /Applications/Install\ macOS\ Sequoia.app/Contents/Resources/createinstallmedia --volume /Volumes/MyVolume
Password:
/Applications/Install macOS Sequoia.app does not appear to be a valid OS installer application.
Sounds like the installer is either incomplete or damaged. I would delete it and empty the Trash, then download it again.
Another possibility is some third party software is installed which is causing a problem. Typical culprits are anti-virus apps, cleaning/optimizer apps, and third party security software. Have you tried the Terminal command while booted into Safe Mode?
Are you imagining I do not know the size of a USB stick? I tested this and it took data, and transferred it back out. I did a brand new APFS then tried MacOS journaled
I never mentioned the size of the SSD. I mentioned the size of the macOS installer app within the Applications folder.....perhaps I did not make that clear enough. Sometimes when downloading the macOS installers from Apple, people may not always get the full installer. The error you mentioned made me think only part of the installer app has been downloaded to the Applications folder.
My reference to the USB stick was only about the extremely poor quality of many USB sticks. Even USB sticks from respected name brands tend to have a lot of issues. It is always best to try another USB stick, especially a different brand.
The USB stick needs to be erased as GUI Partition and MacOS Extended (Journaled). The GUID Partition is critical.
But that error message has ZERO to do with the USB stick.
Yes, I agree. However, I have seen so many macOS error messages which end up having nothing to do with the actual failure mentioned in the error message. That is why I mentioned trying another USB stick. Apple is terrible at producing good & accurate error messages.
The script is copied from an Apple.com site and was written by Apple. It was copied on an M2 mini running Sequoia 15.4 and the latest version of Terminal.
I gathered this from your other posts.
Asking to see the actual commands & errors is because so many people posting on this forum tend to misrepresent the commands & errors so it is best to see them to know for sure. With the command line, every character including spaces can be critical to the success of the command.
FYI, when posting Terminal commands & output, it is best to paste them here using the "Code Insertion" icon with an icon on the forum editing toolbar that looks like "</>" since it uses a monospaced font which more easily shows spaces and is better at distinguishing similar looking characters which is critical in analyzing Terminal commands.
I have been trying to avoid the DFU mode. We have done that before and it works but Never the first time.
Unfortunately that is very true & very common. I've done this many times and I still have issues getting a Mac into DFU Mode. The Apple instructions must be followed exactly down to the second when it mentions a time count. The USB-C cable and port used on the "broken" Mac are also critical.
Before you ask any more questions that could easily been taken as being insulting. I have own a little over 100 Macs in my 38 years of using Macs.
I think you misread my questions and their intent. I have seen a lot of odd things with Apple hardware and macOS. Sometimes my questions & comments may not appear pertinent, but there is a method to my madness.
When I think I may be posting something that could be interpreted by some as insulting, I try to mention that I'm not trying to insult the user. I didn't think I posted anything that would be considered insulting...I'm very sorry if I did.
Keep in mind I have no idea of your technical expertise & experience, so I tend to assume the user has little experience especially when it comes to using the command line. Many times in the past where I have assumed a user had more knowledge than they actually had even though their forum post made it seem like they had a great deal of technical knowledge....that caused even more problems since they could not understand the information posted or inferred.
This error code is bizarre at the very least.
Yes, it doesn't provide much information. My first instinct is the macOS installer is incomplete or corrupted/damaged. Next logical possibility is some third party software is interfering with the normal operation of macOS.
Actually just had another thought, have you installed Homebrew or MacPorts, or perhaps some other software that may have installed them? If so, perhaps they installed some duplicate command line utility which is taking priority over a built-in macOS version which could perhaps cause a problem.
