Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 896
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 896
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 843
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 896
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 843
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 896
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 843
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 896
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 843
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 896
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 843
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 896
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 843
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 896
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 843
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 896
Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EDT/-4.0/DST' instead in /homepages/15/d265490231/htdocs/macristocracy/vanilla/library/Framework/Framework.Functions.php on line 843
-
Okay, so, I went to software update, and told it to install three updates (Safari 5.0.2, Snow Leopard Graphics Update, and Security Update 2010-005).
It logged out and started to update. Immediately, it told me there was an error updating and that none of the updates were installed. Then it proceeded to restart: First it gave me this screen:
and then after a few minutes the progress bar went away. After a little while, the screen turned light blue, and then my screen turned into this:
Then after a few seconds, that went away and my computer booted up fine. Everything works except for Finder. Nothing shows up on my desktop, and I have a spinning beachball whenever I try to do anything with Finder. The same thing happens for this Simplenote-syncing notes app (I forgot what it was called, but here's a screenshot of it). I also get a spinning beachball anytime I open the save/load file dialogue.
SO. Any one have any ideas about what's going on?!?
-
Try opening up Console.app, copy anything from there that looks error-ish.
-
You HDD is near death… When this loading bar is showing, it means that your mac is trying to fix problems on the disk… And in most case, your drive is dead.
-
Posted By: Fantattitude
You HDD is near death… When this loading bar is showing, it means that your mac is trying to fix problems on the disk… And in most case, your drive is dead.
That's absolutely not the only explanation for that bar. From my experiences, that bar comes up whenever the computer has detected anything out of ordinary and then it runs a bunch of diagnostics/repairs. My computer's hard drive is still alive and kicking and that bar has shown its face several times.
-
I would assume there is a graphics driver error. I recognize that screen from when I tried to hackintosh a friends computer and I could not get compatible graphics kexts.
-
That bar appears when the OS is running fsck on the main partition. It can occurs for many reason : the os has detected an error linked to a physical failure (ie you hdd is dying), the os has detected a minor sector error, like those that can occur when you hard reboot a computer, and in some system (Linux) fsck is launched every other n reboot (n~50 for those I used)
-
I've been booting up from an external HD for the time being… Luckily I made a clone of my entire hard drive about two weeks ago, so I'm not losing any data.
I started up today from that clone and got a message saying that the internal HD "couldn't be repaired" and that I can still edit, copy, and move files, but I can't boot up from it.
-
If you open Disk Utility.app and tell it to repair the drive, it'll probably give you a little more information about what's wrong. Let me know what it says.
1 to 8 of 8