![]() ![]() System is a late 2015 iMac 27" Did Apple Change the OS install? I've never been asked about keyboard / mouse prior to the 10.14.1 installer, nor has the USB installer ever had issues with the magic mouse. I haven't tried making a disk from version 8.0.1. I used a clean 8GB SanDisk USB stick, and a fresh download of the Mojave install app. Also the restore partition seems to remember the setup, so I haven't been asked again if I have to use it again. Oddly enough the Restore partition on the hard drive brought up the same assistant, but was able to link with the mouse just fine. On the USB stick, the system was never able to link with the magic mouse, even though it was on, and pressing the button / holding the button didn't seem to work. I have the Magic Mouse 2, and Apple Aluminum USB keyboard with the hub. CD replication, or CD pressing, is the most common way to manufacture CDs. While the process completed correctly, the issues came up after booting from the USB drive.Īpparently as of 10.14.1, the wireless Mouse / Keyboard assistant pops up. James arthur won the uk x factor 2012, Que tengas buena tarde mi amor, Uri in pregnancy icd 9. However, because I am not experienced modifying the firmware on Macs, and the machine is booting and running just fine with the only issue being not being able to select the Macintosh HD from the Startup Pref pane - I would leave it alone and hand it back to the client if it will not allow you to install the current EFI firmware or find out what mods the client has made.I had an unusual issue when using DiskMakerX version 8 to create a Mojave install disk. The "-setBoot" command would be for a system with OS 9 and OS Xįor a volume with OS X only, you would use the "Folder Mode" command, not the "Mount Mode" command. Reading at the bottom of the page under "Examples", Am thinking instead of trying to use the bless command, I might try downloading/installing the most current EFI firmware for that machine. ![]() I would, however, try the PRAM reset if you have not done so. I have to believe your client has made some modification to the firmware on that machine that even a PRAM reset will not affect. So, when booted to the internal drive - it does not permit you to select the internal drive as the Startup Disk?īased on the developers OS X man page for Mavericks here: For each of the methods I tried, I get the same error message, as shown below : In the past, I have created USB installers of 10.7, 10.8 and 10.9 successfully and without incident. Once again, Im pretty sure it was successful, but the USB installer wont work. Personally, and because I do everything for free basically, I will no longer work on a machine with a drive that has begun failing until that drive has been replaced. I then tried to create the USB installer by using DiskMaker X 4b4. The headaches on the rest of them are just not worth it. Yes, sometimes they can be repaired and are fine for quite awhile. I've gone through all these headaches time and time again with drives that started having issues. If the above doesn't work, then I would try the same with my Yosemite USB installer instead of my Mavericks installer to see if it may be the problem. Run the Verify command again - if it finds something wrong, Stop, Do not pass Go and Do not collect $200 - go buy a new drive - if the report is ok. Open DU and run the Repair Disk command (or re-run it) - Run it repeatedly until it says it did not repair anything. ![]() The other half are talking about running "clusters" of Macs where they are installing the system folder as "hidden".Ĭonsidering the above and you're not going to replace this drive, I would try: Half of the above users admitted to having problems with the HD prior to the issue and were wondering if they needed to replace the driveĤ. Most of them are related to PPC Macs and most of them running OS 8 or 9ģ. Nothing related to individual Intel MacsĢ. Would think the issue is due to the system file it is looking for has likely been written to a bad block and is unreadable.Įspecially when you consider the search results for the bless command while disregarding all of them related to installing Linux, you have:ġ. Was the Repair Disk run on this drive prior to reinstalling the OS? This installation went onto the same drive that DU said is corrupt? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |