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.
Do not update crucial m4's firmware to 000F
- Thread starter Samimac
- Start date
- Sort by reaction score
The same thing happened to me with my caddy Hard Drive, I have my Home folder there, and it was having a lot of beach balls, I format my HD and everything worked fine later, I thought it was the ssd, but in the end it wasn't.
Is there anyway to install the new firmware without using the optical drive? I have a HDD in there and I don't want to go through the hassle of swapping it. I tried creating a USB using some sort of terminal command I found online but it didn't seem to work. However, my Lion USB is able to boot. So, I'm confused about USB booting.
I tried everything I could find (SYSLINUX, ISOLINUX, rollling my own linux, hacking other updaters, rEFIt, etc.) and could not get my MBP to boot all the way through to the Crucial updater via USB.
No luck here either.
I never found a way, which is why I have taken the datadoubler out of my MBP and put the Superdrive back in. I figured SSD technology is so immature that firmware updates are a way of life, so at least for now the internal superdrive is essential.
Options: Be prepared to put the superdrive back in just to do updates....doesn't take too long. Or find a friend who is willing to let you put your SSD in his machine for the purpose of updating firmware. Swopping out HDs is generally much easier than the optical bay. You don't need to keep a bootable HD in the machine for the exercise, just make the bootable firmware CD beforehand and boot from that.
EDIT....meant to say I updated my Crucial M4 512 to 000F without any problems.
EDIT 2.....Windows based bootable CDs and DVDs will not boot from external optical drives (USB or FW), but OSX based ones will. Not sure about Linux ones.
Last edited:
Thanks for the reassurance. I thought I was just doing something wrong with creating the USB boot drives. I really don't like opening my MBP since the wires around the SD bay is a bit tricky for me. Also, I've lost a couple screws and being held by tape (just to secure, but it's removable). Also, my SD is in a enclosure and that's another task.
In any case, looking at the changes in 000F, it seems as if there aren't really any major changes. I definitely would go through trouble if there was, but I dont think there are? I currently have the 0309 FW since it addressed the R/W failure, so it was essential. The only thing that I have issues with is that it often reports incorrect freespace and I have to boot into recovery mode to repair the disk to correct it. Not sure if this is hardware or software, or even if the firmware will address this.
Sounds more like a Finder problem....does it come back correct if you relaunch Finder?......right click the Finder icon in the Dock while holding down the alt key, select "relaunch".
Hmm.. I've never tried that method, however, I have done something similar, I think. I would reboot or login/out sometimes to sort of "refresh" but that never really "fixed" the problem. The problem only occurs only if I put several huge (multi GB) files that take up huge space on my drive and then delete them then. Emptying the trash doesn't free up the space per se, according the freespace indicator, only a percentage were deleted. But, the trash is empty and the files are gone, but they seem to be elsewhere. I just figured out recently that I have to boot into recovery and "fix" the drive to correct it.
Strange. Since it sounds like the files are still on your drive somehow they must be invisible, I would recommend a wonderful little app called Whatsize which will show you where they are and how all the HD space is being used, including invisible files.
Or any of the common utilities (Onyx, MacPilot, Tinkertool etc) have ability to make invisible files visible.
When you know if or where the files exist, it will be easier to know what to do.
Repair with Disk Utility, booted from the Recovery Partition, may indeed fix it. A more powerful Directory repair tool like Diskwarrior is more likely to.
I used OmniDiskSweeper and it pretty much does the same thing. There were no files that were hidden or anything. I also went into terminal and entered a command code to show all files.
No idea what Diskwarrior is, but I'll take a look at it. I didn't copy the details of the disk fix, but it said something about incorrect file structure. Also, something about incorrect blocks. Seems like a repair like this required the disk utility to unmount the disk/partition which is why I had to do boot from recovery.
So did the Disk Utility repair fix the problem?
As with CHKDSK in Windows, no computer can repair the directory it is running from. Has to be done while booted from another volume or the Recovery partition, or on boot up.
Diskwarrior actually rebuilds the directory, while Disk Utility repairs it. Sometimes Disk Utility says it can't repair and recommends trying a (more powerful) third party utility (like Diskwarrior). DU used to actually say this but not sure if it still does.
Yeah, Disk Utility fixed it. It took about 2-3 minutes. It went from about 40GB freespace to about 120GB freespace. Which is the correct number since according to Omnidisk I only had used about 125GB of data (but 40GB free prior to repair). I actually wasn't even sure what I was doing when I booted into the recovery partition to repair the disk instead of the permissions, since the disk repair is grayed out when booted into OSX. I have a HDD in the optibay and repair disk is available so I figured it had something to do with the current usage of the disk/partition. So, I lucked out and glad it worked. I've gone in a couple times just for sheer curiosity and the wording at the end of the repair left me a bit puzzled since it wasn't a confirmed answer that I'm used to seeing. It said something along the lines of "SSD Drive appears to be OK." Appears? Hmm..
Anyway, from here on out, I'm just going to stop saving my downloads onto my SSD and have go directly to my HDD that's in the optibay. Also, I'll do the same with videos I encode with HandBrake, especially since when it's finished and I add it to iTunes, it gets automatically copied over to the HDD anyway. I'm starting to get a bit more conscientious about the R/W limit of an SSD. I'm not sure if what I've experienced is "normal" or a sign that maybe something is wrong with my drive. It was purchased and installed in Feb 2012 and has FW 0309, so I can still have a warranty claim if there is a hardware issue. But, I have no idea if there is.
Glad it all fixed. Yes that message is all you get if there is no problem, in green I think.
What happened to you is not normal.
I only have one SSD Crucial M4 512Gb in my MBP, and so I do everything on it. I have TRIM enabled and the small write speeds are not dropping. They were before I enabled TRIM. After six weeks of normal use they were down to nearly half the new value.
Same problem here as the OP... Crucial m4 512GB SSD was beachball city after "upgrading" to 000F. It rendered my Mac almost useless.
Downgrading the Crucial firmware back to 0309 fixed the issue.
Downgrading the Crucial firmware back to 0309 fixed the issue.
I got my 128gb M4 about 2 weeks ago for my Hackintosh and a few days ago I suddenly went from 90gb free to 3gb free...I downloaded several programs to check what was taking up all the space and they reported I had 90gb free...Finder and Disk Utility however both said 3gb free no matter what I did...I actually had to format it and clone the boot drive back over...
Basically I had the same experience you did...so either we both have bad drives or it is a rare "bug"...
My M4 256gb just arrived. No idea what version it's on.
It's going in a 6,1 MBP (2010 i7). Now this will be the longest 8hrs of work ever lol
It's going in a 6,1 MBP (2010 i7). Now this will be the longest 8hrs of work ever lol
The M4's shipping from Amazon seem to be 000F, however I just installed one in my late 2011 15" MBP with absolutely no problems.
I realized after posting it says on the case. 0309 on it right now. I got mine from ebuyer
Before you did the format, did you try booting from your recovery drive? I did that and used Disk Utility to repair the drive. It had some file structure issues per the repair issues. After that, it showed the appropriate free space. It hasn't happened again after that.
000F MBP2010crash on wake up
+1 for having problem with firmware 000F.
Got the drive yesterday with latest firmware. Start having crashes after putting it to sleep. Roll back to 0309 and test the sleep/wake problem a few times. It is not beach balling any more. Too soon to tell if there might be other problems yet to show up. Will post back then.
+1 for having problem with firmware 000F.
Got the drive yesterday with latest firmware. Start having crashes after putting it to sleep. Roll back to 0309 and test the sleep/wake problem a few times. It is not beach balling any more. Too soon to tell if there might be other problems yet to show up. Will post back then.
Mine came with 000F installed on it. 256GB M4. No problems so far. Very pleased with it. Might be something with the 512GB Model maybe.
