The problem is the drive's firmware, not your iMac.
[doublepost=1512641650][/doublepost]
What contacts sync issue are you referring to? I use iCloud for contats syncing and I don't have any problems.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Releases macOS High Sierra 10.13.2 With Compatibility Improvements for Third-Party USB Audio Devices
- Thread starter MacRumors
- Start date
- Sort by reaction score
The problem is the drive's firmware, not your iMac.
[doublepost=1512641650][/doublepost]
What contacts sync issue are you referring to? I use iCloud for contats syncing and I don't have any problems.
Interestingly for me, the console still gets flooded with these error messages but the UserEventAgent process does not go haywire anymore. Before, as soon as I used an automatic date, it quickly consumed 70+ GB of memory and had a high CPU load.
For now, this seems to be gone.*Fingers crossed*
Some annoying banks ask you to install software called trusteer but it installs as rapportd.
Tried the el capitan one from the dmg and ended up in a boot loop.
Had to downgrade to build 15G31 via a bootable usb and update it again via mac app store instead.
So something is wrong with the dmg from the apple support website. Much better to go with the mac app store instead this time for el capitan.
Please see earlier post where I cite my problem as well as posts from other forums
Update: still experiencing this bug, with "you shut down your computer because of a problem" upon startup. The only difference is that this morning, the keyboard was lit up when I first opened the lid.
I hear that this fix (https://discussions.apple.com/message/32467950#32467950) works for some people; I just hope it doesn't mess up Examplify, which my university uses for exams.
OOps, (a bit of) macOS seems to be borked on my 10.13.2 (17C88) - having just upgraded
the demo class of System Preferences/Users & Groups/"Click the lock to make changes"
"System Preferences is trying to unlock Users & Groups preferences" which *was* compromisable with "U: root" "P:<anything> x 2"
now I try the trick, and thankfully "root" doesn't work, but NEITHER does my actual username & valid password, neither does using my Admin account and it's associated password. I cannot unlock U&G Prefs, I get a greyed out username after half-a-sec, then the shake.
Both my usernames & pw's work elsewhere in System Preferences, but looks like (at least in my case) that Apple might possibly have *over-repaired* their 10.13.1 bug?
Who needs to unlock Users & Groups preferences anyway!?
Thank you, John. Wonder how it ended up on my client since I never installed any bank-sw. I have pretty good control of processes and connections on my client and I'm pretty sure rapportd is part of 10.13.2.
UPDATE
So this is a stateful bug, as I had just tried the Root, and it then denied any attempt to get in, even with legit creds - having later retried without the root attempt first, I was correctly able to get past the strong security!
Security is now so strong in this part of the Preferences that it keeps giving me multiple Authentication pop-overs, for the same 'unlock' authentication challenge. If at first you dont succeed. . .
I can see someone getting a free MacBook one day, as there obviously arent any remaining 'features' in macOS10.13.2
apart from this, the combo update seems to work great on my MacPro hexacore.
It is part of the OS and has nothing to do with Trusteer. It looks like has something to do with cache management.
My iMac is stuck on a white screen with "Installation in progress. Calculating time remaining..." after clicking to install 10.13.2. Anyone else experiencing this? Any suggestions?
EDIT: never mind, I see someone else posted about it. Evidently its doing to hang there for a long time before moving on. Been 30 minutes now for me, hopefully this thing isn't hosed, I don't have time to rebuild today.
EDIT: never mind, I see someone else posted about it. Evidently its doing to hang there for a long time before moving on. Been 30 minutes now for me, hopefully this thing isn't hosed, I don't have time to rebuild today.
Last edited:
After installing the update, after rebooting, the Finder gave a message, "Time Machine could not be repaired" (or something like that). Previously, I hadn't received any such message, though I regularly received, "Time Machine Failed to Back Up". (Sometimes it did, sometimes it didn't.) The Finder message said I needed to reboot from Recovery to fix. So I ran Disk Utility, and it found something, couldn't fix it, and bailed. So I unmounted it manually, ran Disk Utility, and it found (and supposedly fixed) a million things...Disk Utility doesn't really indicate if it fixes anything - it just lists issues. Anyway, it seemed to get further, and then said it couldn't be fixed. I'm now running it again. I seem to have had a lot of issues with Time Machine since upgrading to High Sierra.
My Time Machine is a RAID created from three JBODs in Disk Utility. The disks, themselves, appear to be fine, and are brand-new enterprise drives.
Interested if anyone else has experienced the same issues?
My Time Machine is a RAID created from three JBODs in Disk Utility. The disks, themselves, appear to be fine, and are brand-new enterprise drives.
Interested if anyone else has experienced the same issues?
MAIL notifications still come many minutes after I've already read and deleted the email. This is ridiculous. What is the point of Notifications if you realize you have the email and have long since read it before NOTIFICATIONS tells you?
Epic fail again Timmy.
Epic fail again Timmy.
.2 version and still no APFS support on Fusion Drives?
What are these guys thinking of? Are they planning to support two file systems for the foreseeable future?
I am usually quite accommodating with issues and delays when a new OS version is released, but this is called taking the p**s.
What are these guys thinking of? Are they planning to support two file systems for the foreseeable future?
I am usually quite accommodating with issues and delays when a new OS version is released, but this is called taking the p**s.
I think you misunderstood, I said "Firmware does not fail" not "Firmware does not fail to install"
But I still disagree here, firmware almost always install, otherwise you would hear much more about it, and Firmware itself will never fail, by never I mean 1 in a million, they test that over and over, otherwise people end up with bricked Macs.