I would definitely leave it disconnected for a bit to see if your machine returns to normal. I don't see any evidence that that assignment is variable. I understand the advice about disconnecting the drive, and I will try it. I can't say that the full statement of the advice makes complete sense: This would be a good time to run it without any backup. It can be such a tangled web honestly. Ive had sketchy peripherals cause all kinds of stuff, usually USB though. Firewire has usually been a flawless deal for me. SMART should catch your drive if it were failing. It is variable.
Disk device allocations in OS X are dynamic, so while troubleshooting this, you may find it useful to run "diskutil list" at the start of each day to confirm which disks are which. You can't troubleshoot effectively when you have too many variables and having the external drive attached is complicating the situation. Clone it or run Time Machine first thing in the morning and then work for the day without the backup drive attached.
Put mission critical things on a server or in Dropbox, or even copy them to a USB thumb drive periodically. SMART won't identify a bad cable or logic board problem so I wouldn't rule them out as being the root of the trouble.
My wonderful Mac Mini has crashed twice since my last post. The first time was with TM turned off and the external HD connected. The second time was with TM turned off and the HD disconnected. No external devices except the keyboard, the display, and speakers were plugged into the Mini.
I think that this rules out, or at least militates against, external devices as the cause. I spoke to someone at Apple last week. I sent him all the info, including the crash log pictures. I haven't heard anything back. I'll call tomorrow. I predict that i it will be very hard or impossible to reach the same person, and ii when if I do reach him, he will not have anything useful to say. So far, I have called Apple about a dozen times about this. I have spent at least 6 hours on the phone with Apple.
I have taken the computer to the Apple Store, where they failed to diagnose the problem correctly. I have carried out testing on the computer. It still doesn't work properly. No further comment. It definitely does. There's pretty much only 2 issues that can cause it: I'm not sure why Apple is failing to diagnose this. Hopefully you have some sort of case number; if not, be sure to get one next time you contact Apple. This may be a good time to try the approach of emailing Tim Cook's office.
I don't know what the address is but it can be found. Alternatively, take the computer to a 3rd party authorized Apple service provider, and you may have better luck. A different Apple Store if you have one nearby might be useful as well. It is ridiculous that an obvious issue hasn't been resolved now that you've eliminated the external drives as the root of the problem— you may need to be more insistent than you have been. Apple Store managers have essentially unlimited latitude in satisfying customers; use that fact to your advantage. The Apple representative e-mailed me to say that Apple engineers have decided that the HD is failing.
Of course, the machine has an SSD from which all the errors emanate and an HD that has no files on it. I'd be more confident that Apple was actually paying attention to this or doing anything other than waiting for me to complain more if the rep hadn't written "failing hard drive. So, don't be surprised about the SSD being on it's way out. Especially considering the IO errors you're getting. Funny you should say that. Some HDD's, when you get a good one, do seem to last forever. I've got a stack of IDE and SATA drives that are still functional behind my desk here in the office that are no telling how many years old; obviously outlived the machines they were used in.
I see grounds for compliance.
In the end it could be a cable or some other component but, unless there is a visible defect, it's one of those problems you won't solve unless you start replacing parts somewhere. I'd say the SSD is most likely the culprit and that's a good starting place and that's what I'd insist they replace when I went back. I will admit this is very interesting, I don't really see this kind of thing with my macs.
I would say its quite odd. I did talk to the Apple representative. He said that the Apple engineer says that disk0s2 is failing. So, if I take the computer to my local Apple store, they will replace disk0s2, which I think means that they will replace the SSD. According to the Apple rep, the Apple Store has to do what the engineer recommends. I just have to find a day or so when I won't need the computer. I think that Apple-on-the-phone could have been better about solving this problem assuming that this is the solution.
I don't see that it would have been solved at all except that I kept Console running at all times and then looked at it while the computer was crashing.
Apple never suggested that I do that. Apple-on-the-phone did say two months ago that the SSD was likely failing after I described the error messages. I remain pretty annoyed at the Apple Store, because in my two visits there one to leave my computer, and one to pick up my unrepaired computer I had the feeling that I was bothering them with something they didn't want to do or didn't believe. When I picked up the computer, the store people essentially told me that it was working properly and that they couldn't do anything unless they could reproduce the failure.
To be specific, disk0 is the SSD. This error can also occur if the partition table is damaged, which would explain why SMART isn't failing but you're getting the errors. This will overwrite all of the partition information instead of skipping any. If the issue happens after that, definitely need the SSD replaced.
Also you may want to run http: Apple's disk utility is useless for checking smart errors. Hopefully Apple's drive replacement will fix all your issues! Disk failure is extremely common and can present itself in very insidious ways that can be easy, or difficult, to figure out. While not directly relevant to this thread, it's worth noting that the output from "df" ignores Core Storage volumes, as with Fusion drives or when using Bootcamp on a 3TB or larger disk. Ars Praetorian et Subscriptor. Ray Sanders. Ray Sanders wrote:.
Ars Tribunus Militum et Subscriptor. Sata cable? Ars Legatus Legionis et Subscriptor. Jump to: May 19, Posts: Thu Jun 06, 1: A hollow voice says "plugh. Apr 19, Posts: Thu Jun 06, 3: Feb 12, Posts: Thu Jun 06, 4: Thu Jun 06, 5: Lucky citizen of two police states. Jan 23, Posts: Thu Jun 06, 6: Oct 1, Posts: Fri Jun 07, 2: Fri Jun 07, 6: Fri Jun 07, 5: Sat Jun 08, 5: Ray Sanders Ars Praefectus Tribus: Timucua forest Registered: Oct 11, Posts: Sat Jun 08, Sun Jun 09, 4: Sun Jun 09, 5: Sun Jun 09, 8: London, sort-of-Great-Britain Registered: Nov 5, Posts: Mon Jun 10, 3: Dec 2, Posts: Mon Jun 10, Wed Jun 12, 1: Feb 19, Posts: Wed Jun 12, 2: Wed Jun 12, 3: Wed Jun 12, Tue Jun 18, 6: Tue Jun 18, 1: Tue Jun 18, 5: Ireland, UK Registered: Tue Jun 18, 7: Tue Jun 18, 8: Tue Jun 18, Once you see a bad sector on a hard disk, just one, it's time to backup your data and throw the disk away.
If you don't want to junk the disk, at least use it only for data you don't care about losing. You see, the way modern hard disks work is that they all have bad sectors. In the good old days, hard drives used to come with a printed list of known bad sectors and when you did a low level format on them a real low-level format, not just zeroing out the data you would then manually enter the list of known bad sectors, and then update that list with any new ones - in other words, you were in complete control over mapping out bad sectors.
With today's hard disks, the hard drive controller maps out bad sectors itself, without even telling you. It has a factory list of bad sectors, that you can't see. As it encounters bad sectors in normal use, it silently attempts to recover the data and move it to a chunk of spare sectors that all drives have for this purpose.
You generally aren't aware that anything has happened. Once a hard drive has mapped out enough bad sectors that it's starting to report to you there are bad sectors, this is the beginning of the end. I have not once had a hard drive last for a long period of time after reporting a bad sector, it always gets worse and worse. The best thing you can do is to power down the drive immediately and let it cool down to room temperature.
Get something to back up your data to and begin the backup process straight away. Zeroing out the disk may let the drive remap a few more sectors and give you the illusion of having everything fixed, but it's a very different picture behind the scenes. I agree it very often can be the first indication of a larger problem and that warning is definitely something I tell my clients and should have included here.
But it is not worthy of your opening sentence implying I just recommended something horribly wrong. But very often you have scenarios when a system is not under warranty and the user or reader of this forum does not want to spend the money on a new drive and would like to try all options available. Zeroing out is a viable option that can have good results.
My 2nd tip is for PowerPC users. Boot into Open Firmware single-user and type in "dir hd: Hope this helps someone! Disk Warrior fails, with an out of memory error, to repair volumes with a lot of files, links etc read: Time Machine volumes. Anyone know how to fix this?
It seems to be UI, that is Carbon, that can't address the memory required. Maybe using the command line?
Lost your password? Powered by the Parse. More Mac Sites: Macworld MacUser iPhone Central. Miniguide to fixing Volume-Filesystem errors Apr 29, '11 Here are some common symptoms that are indicative of some of them: Not able to boot the system: You tried to boot. Apple logo appeared, and wheel spun for about seconds, then machine turned off. This repeated every time you tried to boot the system. The system does not find your HD and thus the OS to boot. Everything seems to work fine till your system hangs briefly and in an unpredictable way.
You wait for a while, and the system magically comes back to normal. But after another while, the same thing re-occurs! This cycle repeats in the current session. You can do these simple things to check for other possible causes: Check the system log using Console. I don't claim to be an expert on this subject matter, just an over enthusiast Mac user. This guide is purely based on my personal experience and is bound to contain errors. Consider this hint to also serve as a reminder to check your backups Use Disk Utility and run "verify" to check it.
Your HD is dying. Before making any repair of the disk, make sure that you have the latest backups.
Then try doing a manual backup using commandline tools like cp or ditto. The disk usually gets mounted in read-only. This could be good to get a manual backup by cp. There are other modes to try backups if single-user mode is not available. Probably will point you towards the error due to which you are not able to go into Single User mode. Shift-key Safe mode T Target Disk mode: This works with FireWire. And now Thunderbolt as well. Not being able to mount the drive, I could not copy my files before trying the fix by any traditional means. What I did do was load Data Rescue from CD and used the clone function to clone the broken HD to a FireWire external - for some reason it could see the drive and execute the clone.
I then tried the fix on the clone first. Disk Utility can verify your computer's startup disk volume without starting up from another volume. Here are Apple's instructions. This feature is called 'Live Verification. You can't repair your startup volume while your computer is started from it.
Very important: The thing which can tell if it works is if you are getting a different output of the Repair in successive runs. So log the successive runs and if the error reported is changing in successive runs, it is likely that REPAIR is fixing some problems in each run and it could be possible that using REPAIR repeatedly could solve your problem.