-
All replies
-
Helpful answers
-
Sep 2, 2016 7:08 PM in response to michael gardnerby michael gardner,I found a clone disk I made a few weeks ago, booted it. Used Terminal to go check /private/var/folders - and three of the folders were still there (with modify times of last boot attempt). I removed them. Rebooted and after a way too long wait, my system came up. So far, it all seems ok - but that is one scary episode I didn't need. Lost 4 hours of work tonight - now I'll lose four hours of sleep making up for it.
-
Sep 2, 2016 7:58 PM in response to michael gardnerby michael gardner,Well, the problem of booting a clone is you sometimes forget to unplug the clone and it boots and you think you are running a good system...... Unplugged, my system would not complete boot. 15 minutes at black screen. I'm now reinstalling with recover disk.
sigh
-
Sep 2, 2016 10:05 PM in response to michael gardnerby michael gardner,Re-install appears to have worked. App store says I have a Security update to install - no thanks!
-
Sep 3, 2016 7:29 AM in response to lvlikeby Bob Sabiston,How are you seeing this folder, using the Terminal? Then how are you getting the files to the trash? Do you use 'mv' to the Trash folder (where is that) or do you just Unix 'rm' the files? Then how do you empty the trash on the target disk? Will emptying the trash on the computer hosting the target disk also empty the trash on the target disk? Just want to be sure I try this right.
-
Sep 3, 2016 7:41 AM in response to lvlikeby Bob Sabiston,Wow, this worked for me! Spent two hours on the phone last night with a CLUELESS Applecare person. They were about to have me restore from an old Time Machine backup and lose a bunch of work. I balked at that since there was clearly not anything wrong with the hard drive. Had a store appointment today.
Thanks! Did you discover this fix? How in the world did you or whoever did figure it out?
Man Apple seriously screwed this up.
-
Sep 3, 2016 8:26 AM in response to Bob Sabistonby havemusicwilltravel,I also spent time on the phone with Apple yesterday morning who also was of no help. The end result of the conversation was that my Fusion drive was the problem and someone would have to look at my computer (like a computer repair service). I had honestly tried everything in the book for almost a 24 hour period including 3 full system installs and got nowhere until I read through these threads. I had always wondered about hidden files on the Mac. On PC's it's a snap to show hidden files. Why does Apple make it so hard?? But once I launched Terminal and did a copy and paste on the two command lines, to reveal, and then to hide again when done, it was a snap. I backed up the folders just to be ultra safe before trashing them, and my gut instincts were telling me not to trash the Folders folder even though I had no clue whatsoever on my own where or what to look for on this issue but for the thanks of a couple of individuals posting here. And like you, don't know who they are, but I am extremely thankful they came up with this. I have dealt with computers a long time but this fix was nothing I could have come up with on my own. Whenever I get totally stumped, and it has happened before, I usually can find help here, or online doing a Google search, to give me enough of a hint to get on the trail of the right fix. And I share your "Thank You All" out in cyberspace! Good job!! Once again you have excelled in support!!
-
Sep 3, 2016 8:32 AM in response to lvlikeby havemusicwilltravel,You are 100% spot on here. Kudos for a job well done!! Saved me on this one.
-
by havemusicwilltravel,Sep 3, 2016 12:53 PM in response to havemusicwilltravel
havemusicwilltravel
Sep 3, 2016 12:53 PM
in response to havemusicwilltravel
Level 1 (109 points)
Mac OS XOne last note here. After multiple backups of my working Mac Mini, I disconnected any external drives and took the downloaded dmg file and got brave and installed it. I think Apple should have thrown in a preface to the update stating something like "Please be patient and do not turn off your computer until the update is complete". I know that sounds a little bit like that should be a given, but I think that probably during the first attempt at the update I saw a black screen with nothing going on and thought "hmm, black screen, it's locked up. Maybe I should turn off and back on to see if the update is done or not!" I do remember a black screen and I was not really paying attention to the update status at that point and got impatient. The update did have to go through several stages as I paid close attention to it today, including the black screen and an OS X screen and a little screen image of my Mac Mini and the process did take maybe 7 or 8 minutes. This is not an update to get impatient with. Paying close attention and letting it "do it's thing" resulted in a flawless update on the second attempt after the first disastrous failed attempt. So I am not really wanting to diss Apple on this one. I think I probably am mostly the blame for the initial failed attempt to apply the update.
My Mac Mini is 3 & 1/2 years old with the fastest i7 CPU that was available at the time, 16 GB memory, and a Fusion drive. So it is a relatively fast little computer. And even then the update took a lot more time than I ever initially expected it to take. So for those afraid of the update to begin with, my point is, expect the update to take maybe a little more time and for goodness sake, do not get impatient and interrupt it under any circumstances. It took almost a full 24 hrs to get my computer running, and another 24 hours to do sufficient multiple backups to get the courage to actually go back and try the Security Update a second time. If this helps anyone avoid a crashed computer I am glad. The good news is, I have taken both my macs and updated all of the Time Machine backups and Carbon Copy Cloner backups and am preparing for the next major system upgrade, Sierra. Have I tried the beta version? No way in h*ll. I get enough grief just backing up and updating all of my computers and tablets and phones without ASKING for trouble!! Maybe in my younger days. After 30 years of technology advances I think I have mellowed out a tad. (or maybe worn out is more accurate) And thanks for the "hidden file" tips. I had always wondered and never really explored that little aspect of Macdom. I have to say that PC's and Windows have Apple beat on that little aspect. Granted, most people don't need to be messing with hidden system files on their computers, but sheesh Apple, must you make it so difficult?? I would hope that after all these years I could be trusted with something a little easier than what it took this time around to find the blasted Folders folder and the files therein!!
-
Sep 3, 2016 4:55 PM in response to havemusicwilltravelby michael gardner,When I first updated - the machine downloaded - rebooted - did "its thing" for some number of minutes, then came up - login window - just like normal. No messages. No, "please wait", nothing. finder windows would open, but never show files. All the application icons were generic and basically nothing would run. IF the operating system was doing some sort of security/validation/key-change - that could explain all this. Its an old macbookpro and I do have A LOT of applications. I waited 20 minutes before I rebooted. I've never seen anything like this in all my years with Apple. I will be updating my clone drive before I try the next time just to be sure.
-
by havemusicwilltravel,Sep 3, 2016 5:15 PM in response to michael gardner
havemusicwilltravel
Sep 3, 2016 5:15 PM
in response to michael gardner
Level 1 (109 points)
Mac OS XI saved the update on my older MacBook Pro (2007) model for last and it did fine. Took a while but completed and seems to be okay. You can't hurry the update. It takes it's time and even though it seems to hang a little it should complete if left alone. It is a fairly complicated update apparently. But I am done with my three Macs. Till the next time.
-
Sep 3, 2016 6:39 PM in response to David Biddixby Paul Cohen1,David,
That did it!!
Restarted from another drive at the Apple Store, removed the folders, and all is well.
Apple Genius wasn't aware of this. He recommended wiping the entire drive and re-installing.
Thanks for the help!
Paul
-
Sep 3, 2016 9:10 PM in response to Paul Cohen1by Matthew Caswell,Tried deleting the folders on my 27" iMac then rebooting to that drive and no joy (yes, I deleted the folders on the right drive, not the yosemite boot drive). it starts booting, my second monitor lights up then the monitors go black and the screen on the iMac will flash and it shows the little gear looking clock face for a second, then it goes black again.
What is this ******** apple? Yea, I have a backup, but this makes me think Microsoft bought apple and put out this security update!
I have no clue what to do now other than restore from my time machine backup. Both of my SSD's won't boot and they are el Capitan, but an external USB with Yosemite will. ***?
Really ****** off!
matt
-
by havemusicwilltravel,Sep 4, 2016 8:53 AM in response to Matthew Caswell
havemusicwilltravel
Sep 4, 2016 8:53 AM
in response to Matthew Caswell
Level 1 (109 points)
Mac OS XI would read this and try the Cmd-R boot and restore to see if that helps. Non-destructive and you can retain your data.
-
Sep 4, 2016 9:52 AM in response to havemusicwilltravelby Matthew Caswell,I have been unable to see my email until just now. Here's what worked. I formatted the drive, then installed a new El Capitan. Then I use the wizard to import all my data from my Time machine backup and it seems that I'm back up and running.
I WILL NOT BE INSTALLING THE SECURITY UPDATE!
Thanks to everyone that posted in this thread on what they tried and what worked for them, even if it didn't work for me.
If you're not using TimeMachine, you need to be since it seems Apple hired the same quality control people that Microsoft uses.
matt
-
Sep 4, 2016 3:52 PM in response to fredfxby Paul Cohen1,Solved the problem.
Rebooted from an external drive(in the Apple Store), removed the contents of private/vars/folder, and rebooted.
Everything worked.
Checking Console showed that Norton Antivirus was to blame. I had neglected to inactivate it before accepting the automatic security download.
Paul